Environment Manager

Home

This page refers to an older version of the product.
View the current version of the User Help.

Configure Personalization Servers

To configure a personalization server, you must first establish a connection. Once connected you can create a configuration to control personalization for you enterprise. A list of servers can then be created to manage which servers your managed users connect to.

For details about configuring Personalization Servers, see the User Workspace Manager help.

In this section:

Connection
Personalization Servers in the Combined Console
Personalization Servers in the Personalization Console
Personalization Server Selection Using Group Policy

Connection

In order to configure personalization for your users, you must first establish a connection to a Personalization Server. The Connect button allows you to list one or more Personalization Servers and connect to the required one.

To configure Personalization, localhost is automatically added to the Select Personalization Server dialog if the following conditions are true:

A Personalization Server is installed and configured on the same machine as the console.
A Personalization Server has not previously been configured in the Select Personalization Server dialog

Connect to a Personalization Server

Select the User Personalization navigation button.
From the Server ribbon, click Connect.

The Select Personalization Server dialog displays.
Click the new server button .

The Add Server dialog displays.
Enter a Friendly Name for the server. This can be any text but should be something which will enable you to identify the server. If no text is entered, the server name is used.
Select the required protocol - http or https.
Enter the server name or browse for the required server by specifying locations and searching for server names.
Enter the port number. The port range for Personalization servers is 7771 to 7790 and the default port is 7771.

Once the server details have been added, the URL for the server is displayed.
Click Add.

The server is listed in the Select Personalization Server dialog.
Repeat steps 2 to 6 to add more servers.

Servers in the list can have their details edited or be deleted from the list using the buttons at the top of the dialog.
Select the server you want to connect to and click Connect.

When you return to this dialog, any servers you have listed are available for selection.

The Environment Manager and Client Communication agents now perform extra checks during HTTPS communications and will now fail on any certificate errors, for example. self-signed certificates. This can be overridden by the using the IgnoreCertificateErrors registry setting:

Value Name: IgnoreCertificateErrors
Value Type: DWORD
Location: HKLM\Software\Appsense\Common
Possible values:
- 0 or not present - do not ignore certificate errors
- 1- Ignore all certificate errors

Personalization Servers in the Combined Console

This feature is only available in the combined console. In the Personalization console, the server list is configured using the Endpoint Server List.

When creating an AEMP configuration in the combined console, a list of personalization servers can be configured. When the configuration is pushed out to endpoints it determines whether endpoints are personalized and if they are, to which server they will connect. It is recommended that multiple personalization servers are listed so alternative servers can be automatically selected for failover purposes.

The first time a user logs on to a managed endpoint, the Environment Manager agent contacts the first Personalization Server to request the actual list of servers the endpoint should use (based on the sites configured in the database). The client then contacts the correct server to pull down the User Personalization configuration, containing the list of the applications which should be personalized for the user.

If all attempts to connect to a Personalization Server fail, then the configuration is not downloaded and Personalization does not take place.

If no servers are configured, endpoints managed by this configuration are not personalized.

To cater for such a scenario it is recommended that the 9661 - Timeout Communicating with Personalization Server auditing event is enabled.

Configure a Personalization Server List

Select the Policy Configuration navigation button.
From the Manage tab select Personalization Servers.

The Configure Personalization Servers dialog displays.
Click the add server button .

The Add Server dialog displays.
Enter the server name or click the ellipsis to search for the required server by specifying locations and searching for server names.

Do not select or enter Localhost as the server name. If Localhost is entered as the server name it is added to the configuration.aemp file as the location of the Personalization Server. The client tries connecting to http://localhost/Personalization which is incorrect and User Personalization is disabled.
Enter a Friendly Name for the server. This can be any text but should be something which will enable you to identify the server. If no text is entered, the server name is used.
Select the required protocol - http or https.
Enter the server name or browse for the required server by specifying locations and searching for server names.
Enter a port number. The port range for Personalization servers is 7771 to 7790 and the default port is 7771.

Once the server details have been added, the URL for the server is displayed.
Click OK.

The server is listed in the Select Personalization Server dialog.
Repeat steps 3 to 9 to add more servers.

Servers in the list can have their details edited or be deleted from the list using the buttons at the top of the dialog.
If you have added more than one server, use the arrow buttons to reorder the list. When the configuration is deployed, endpoints attempt to connect to each server in turn. If a connection cannot be made with any server in the list, Personalization does not occur.
Click OK to save the server list.

When the configuration is deployed to endpoints, this list is used to determine which servers managed users connect to.

Personalization Servers in the Personalization Console

This feature is only available in the Personalization console. In the combined console, the server list is configured in the Policy side of the console using the Personalization Servers option from the Manage ribbon.

The Endpoint Server List allows you to create an AEMP configuration file containing the Personalization Servers to which endpoints can connect.

It is recommended that, where possible, multiple servers are added to the Select Personalization Server dialog so alternative servers can be connected to for failover purposes.

Environment Manager supports SQL 2012 Always-On functionality.

When a user logs on to a managed endpoint, an attempt is made to connect to the first server on the list. If a connection cannot be made to that server, connection with the next server in the list is attempted and so on until a connection is established.

If all attempts to connect to a server fail, personalization does not take place.
An AEMP configuration created from the Endpoint Server List in the Personalization console can be opened and edited in the combined console.

Likewise, an AEMP configuration with configured servers, created in the combined console, can be opened and edited in the Endpoint Server List in the Personalization console.

You cannot upgrade policy configurations in the Personalization only console. policy configurations can only be upgraded in the combined Policy only consoles.

Configure and Save a Personalization Server List

Open the Environment Manager Personalization console.
From the Server ribbon, click Endpoint ServerList.

The Personalization configuration dialog displays.
Click the new server button . The Add Server dialog displays.
Enter the server name or click the ellipsis to search for the required server by specifying locations and searching for server names.

Do not select or enter Localhost as the server name. If Localhost is entered as the server name it is added to the configuration file as the location of the Personalization Server. The client tries connecting to http://localhost/Personalization which is incorrect and User Personalization is disabled.
Enter a Friendly Name for the server. This can be any text but should be something which will enable you to identify the server. If no text is entered, the server name is used.
Select the required protocol - http or https.
Enter the server name or browse for the required server by specifying locations and searching for server names.
Enter the port number. The port range for Personalization servers is 7771 to 7790 and the default port is 7771.

Once the server details have been added, the URL for the server is displayed.
Click OK.

The server is listed in the Select Personalization Server dialog.
Repeat steps 2 to 6 to add more servers.

Servers can have their details edited or can be deleted from the list using the buttons at the top of the dialog.
If you have added more than one server, use the arrow buttons to reorder the list. When the configuration is deployed, endpoints attempt to connect to each server in turn. If a connection cannot be made with any server in the list, Personalization does not occur.
Click OK to save the server list.

When the configuration is deployed to endpoints, this list is used to determine which servers managed users connect to.
Click File and select the required save option.

Personalization Server Selection Using Group Policy

Environment Manager 8.3 client software allows the personalization server to be selected using group policy. As detailed in the sections above, a list of personalization servers is normally specified in the configuration. However, this can be overridden by the group policy list.

Using group policy templates, a list of servers can be created that will be used by endpoints as a fail-over list. There is also an option to bypass the site processing on the server and use the specified server directly. This provides new configuration options and offers better performance for large numbers of users.

Group policy selection of personalization servers works even if no configuration file is deployed to the client.

The following group policy administrative template files are supplied with the Environment Manager Personalization and combined consoles:

AppSensePersonalizationServers.admx
AppSensePersonalizationServers.adml
AppSensePersonalizationServers.adm

Upgrades for Endpoints with Personalization Applied by Group Policy
If an endpoint with an 8.2 configuration file without personalization servers, is upgraded to software version 8.3 or later, the configuration file should be upgraded by loading it into the console and saving it out again. Errors are not generated if the configuration file is not updated but policy actions will not be applied to managed processes.

Configure a Personalization Server List with Group Policy

Navigate to the Group Policy folder:

C:\Program Files\AppSense\Environment Manager\Console\Templates\Group Policy

This is the default installation file path. If you have installed to an alternative location, find the Group Policy folder in you install location.
Complete the setup action for your operating system:
- Copy the AppSensePersonalizationServers.admx file to:
  C:\Windows\PolicyDefinitions (where C:\Windows is the system root).
- Copy the AppSensePersonalizationServers.adml file to:
  C:\Windows\PolicyDefinitions\en-US (where C:\Windows is the system root).
Open Group Policy Editor. Policy templates are available for user and computer policies. User policies can be tailored to individual users and computer policies apply to the endpoint.
Select Administrative Templates > AppSense > Environment Manager for either the user or computer policy.
Select the required option:
- Specify list of personalization servers - Specify a list of personalization servers for endpoints to connect to and use as a failover list. The AEMP configuration server list is overridden by the list created.
  Select Enabled and enter the required server name(s). Each server must be preceded by http:// and where more than one server is required, separated by a comma. For example, http://server1,https://server2,http://server3:3000.
- Bypass server site processing - Normally, initial contact is made with the server listed in the AEMP file. Once contact is made, the database rules are evaluated to determine which server the client should connect to. Enabling this option means clients ignore the database site rules and connect directly to the server determined by Group Policy.
  Select Enabled to bypass server site processing.
Click OK to save your settings and update personalization server selection to use group policy.

Evaluation Order

When deciding which server to connect to, the following evaluation order is used:

User Policy
Computer Policy
AEMP File

Each source is evaluated in order until a server list is found; if a server is not found, evaluation moves to the next source. If no servers are found, the user is not personalized.

If a server is listed in User Policy, for example, but is unavailable, processing ends and the user is not personalized.