Secure Mobile Access 12.4 Administration Guide

Download PDF
Technical Documentation > Secure Mobile Access 12.4 Administration Guide > Installation > Installation and Initial Setup > Installation and Deployment Process > Configuring the Appliance Using the Management Console

Configuring the Appliance Using the Management Console

The final installation and deployment settings are done in AMC.

To configure the appliance in the AMC

  1. Log in to AMC.

  2. Register the appliance on MySonicWall and retrieve your license file.

    When you register your appliance, you must enter both your serial number and your authentication code, which is the hardware identifier for the appliance you purchased:

    • The serial number is printed on a label on the outside of your appliance and also available in the Licensing page..
    • The authentication code is displayed in AMC: click General Settings from the main navigation menu, and then look in the Licensing area.

    When you receive your SMA appliance there is a single user license on it, valid for three days. To become familiar with the AMC and test it in your environment with additional users, request a lab license. After initial setup and testing, download your license file from MySonicWall and then import it to the appliance.

    See Managing Licenses.

  3. Define one or more authentication servers.

    Authentication is used to verify the identity of users. When configuring an authentication server, you are prompted to specify a directory type (LDAP, Microsoft Active Directory, RADIUS, or local users) and a credential type (username/password, token, or digital certificate).

    See Managing User Authentication.

  4. Configure a server certificate.

    The appliance encrypts information using the Secure Sockets Layer (SSL) protocol. You can use Let's Encrypt certificate authority that is public, free, API-driven, and trusted by browsers/clients. You can create a selfsigned certificate using AMC for evaluation or testing purpose.

    See Certificates.

  5. Define application resources and groups.

    Application resources include TCP/IP-based resources (such as client/server applications, file servers, or databases), Web-based resources (including Web applications or Web sites) that run over HTTP, and Windows network share resources (to be accessed in WorkPlace). Resource definitions can include variables, so that a single resource can, for example, derive its network name or address based on each user.

    See Creating and Managing Resources.

  6. Define users and groups.

    User and group definitions are used in access control rules to control access to application resources.

    See Managing Users and Groups.

  7. Define realms and communities.

    Realms enable the appliance to directly integrate with authentication servers, eliminating the need to create and manage accounts for each user who needs access to your network. Communities aggregate users with similar access needs and End Point Control requirements.

    See Managing User Authentication.

  8. Create access control rules.

    Access control rules determine what resources are available to users and groups.

    See Access Control Rules.

  9. Configure shortcuts for WorkPlace.

    To provide your users with easy access to a Web, file system, or graphical terminal resource from within WorkPlace, you may want to create shortcuts in WorkPlace.

    See Working with WorkPlace Shortcuts.

  10. (Optional) Configure the network tunnel service.

    If you plan to deploy the network tunnel clients, you must configure the network tunnel service and allocate IP address pools for the clients.

    See Configuring the Network Tunnel Service.

  11. (Optional) Enable and configure End Point Control.

    End Point Control optionally deploys data protection components designed to safeguard sensitive data and ensure that your network is not compromised when accessed from PCs in untrusted environments. End Point Control is deployed through communities.

    See End Point Control and Using End Point Control Restrictions in a Community.

  12. Apply your changes.

    To activate your configuration changes, you must apply them.

    See Applying Configuration Changes.

  13. Test system accessibility.

    Verify that the appliance can access your external user repositories, and ensure that the resources on your network are accessible.

    See Troubleshooting.

Was This Article Helpful?

Help us to improve our support portal

Yes! Not Really

Techdocs Article Helpful form

  • Hidden
  • Hidden

Techdocs Article NOT Helpful form

  • Still can't find what you're looking for? Try our knowledge base or ask our community for more help.
  • Hidden
  • Hidden