General properties (server-specific)

• The external DNS names of this server.
• This setting allows you to use different names depending on the IP address of the client.
• Only change this setting if this server is known by different names on the network, for example, inside and outside a firewall.
• Each name has the format client IP pattern:external DNS name, where client IP pattern is a regular expression matching an IP address, for example 192.168.10.*.
• If this server only has one name, use one line matching all clients, for example:
  
  *:www.indigo-insurance.com.
• The order of the names is important. The DNS name for the first matching IP pattern is used. For example if the following names are defined:
  
  192.168.10.*:boston.indigo-insurance.com

*:www.indigo-insurance.com
  
  clients with IP addresses beginning 192.168.10 connect to boston.indigo-insurance.com, and all other clients connect to www.indigo-insurance.com.
• In Array Manager, press the RETURN key after each name definition. On the command line, use a space to separate the names, for example:
  
  --server-dns-external "192.168.10.*:boston.indigo-insurance.com" "*:www.indigo-insurance.com"

Note You must restart this Secure Global Desktop server for a change to this setting to take effect.

• Where diagnostic logs are stored on this host.
• You can set the Log Filter on the Array properties panel.

Note This is a read-only attribute and can't be changed.

• A string identifying the location of the array member, used for intelligent array routing.
• Leave blank unless your array spans a WAN (or includes slow links) and you use the intelligent array routing load balancing feature.
• More than one string is allowed, but this slows application launch.
• This setting constrains emulator session and application server load balancing to ensure optimal bandwidth usage. Secure Global Desktop servers are chosen with the same location as application servers, where possible.
• If used, you should set this attribute on all array members, and for appropriate host objects in the organizational hierarchy.

• Whether to allow users to log in to this Secure Global Desktop server.
• Choose Not Allowed (disabled) to "decommission" a Secure Global Desktop server: no users may log in and no new emulator sessions can start. Users currently logged in to this server, or with emulator sessions hosted on this server, are not affected. Users may log in to another array member and resume emulator sessions hosted on this server.
• Users are redirected to the web page defined in the Redirection URL. Typically, you would set this to another Secure Global Desktop server in the array.

• The URL that client devices are redirected to if this Secure Global Desktop server is not allowing users to log in.
• If blank, redirects to a page telling users that they may not log in.