INFORME DEL CICLO DE EGRESOS DE EFECTIVO

The Environment Manager configuration format changed from version 8.1. The configuration AEMP file from version 8.1 and later is made up of the following parts:

 configuration.xml - similar to v8.0 configuration file for the console.

 emxconfiguration.xml - for the agent. This section of the configuration has been

restructured to fit the new client engine, it is faster to process than the Console.xml.

Configuration Compatibility

Agents and configurations must be of the same major and minor version number. For example, an 8 FR4 configuration is only compatible with an 8 FR4 console However, if you open an older configuration in a new console, you can, and will be prompted to upgrade. To ensure consistency the console automatically runs staged upgrades. For example, if you open an 8.0 configuration in an 8 FR4 console, the configuration is upgraded first to 8.1 and then to 8.2 and finally to 8 FR4. This action is performed automatically and is not visible to the user.

If a configuration is loaded in an older console, the console may attempt to convert it to the older version. This should be avoided as the results are not reliable. This behavior is described in the table below.

Any work in progress configurations are deleted during the upgrade process so they must be saved before upgrading.

The Environment Manager group policy editor in versions 8.1 and later allows policies for Windows XP and 2003 onward. Therefore the following policies are no longer supported:

 Remove Run command from Start menu  Remove folders from Settings on Start menu  Remove Taskbar from Settings on Start menu  Remove Find command from Start menu

 Hide Network Neighborhood

 Remove Shut Down command from Start menu  Remove Run command from Start menu

 Remove folders from Settings on Start menu  Remove Find command from Start menu  Hide Network Neighborhood

 Remove Shut Down command from Start menu

When upgrading configurations which include actions containing these policies, they should be replaced with equivalent policies.

For further information see Group Policy in the Action Management chapter of the Environment Manager Policy Product Guide.

U

O

It is important that when upgrading to Environment Manager 8.2 from a pre-8.1 version you upgrade AppSense Management Center first.

Once the Management Center has been upgraded the Environment Manager components

must be upgraded in the following order for the upgrade process to be successful. Configuration

Version

Console

Version Behavior

8.1, 8.2, 8.3 or 8

FR4 8.0 or older You are warned that the configuration is not compatible with the console and it will not open. 8.3 or 8 FR4 8.1 or 8.2 In most cases, the new configuration opens in the older console without prompt and can be subsequently saved as an 8.1 or 8.2 configuration. However, errors can occur preventing conversion.

For details of upgrading configurations to from pre-8.1 versions, see:

 Agents and Configurations Upgrade to 8 FR4 from a pre-8.1 Version on page 35  Standalone Configuration Upgrade Process on page 37

For further information on upgrading AppSense Management Center, refer to the AppSense Management Center Installation and Upgrade Guide.

When upgrading to 8.2 from a pre-8.1 version it is very important that you upgrade in the order specified in this chapter to ensure that all AppSense Management Center and Environment Manager components are compatible and all functionality is available.

Order Components Details

1 All Personalization

Servers and Databases _ Must match version with console - no backwards compatibility._{Compatible with earlier versions of the AppSense Environment} Manager Agent, with limitations on functionality support. 2 All Consoles Must Match version with servers - no backwards compatibility. 3 All Agents and

Configurations Compatible with all versions of the Personalization Server although there may be some limitations on functionality support between older agents and newer servers.

Using the Windows Authentication server mode when upgrading clients from 8 FR3 (8.3.157.0) or earlier will cause clients to fail when synchronizing their personalization settings. This setting is off by default on an upgrade and should not be enabled in the Server Configuration Utility until all clients are at 8 FR3 SR1 (8.3.192.0) or later.

For details of how to change the authentication mode, see Appendix F - Personalization Server Configuration Utility in the AppSense Environment Manager Personalization Product Guide.

E

M

U

Use the AppSense DesktopNow Installer to upgrade the Environment Manager components to the latest available version.

1. Run the Installer by executing setup.exe, on the installation media. 2. In the Welcome screen select Upgrade and click Next.

3. The Prerequisite Management screen detects which of the installation prerequisites are

Installed, Not Installed and those that Require Manual Installation.

 Any prerequisites which require manual installation should be installed first outside of the installer.

 The Not Installed prerequisites are automatically installed as part of the Enterprise Installation. Click Install to install individually or Install All to install them all with one click.

4. Once all prerequisites are installed, click Next.

5. The Summary screen shows the items ready to be upgraded or installed, the installation mode, install directory and whether a reboot is required. Click Upgrade.

6. The Upgrade Complete screen displays.

The following options are available:

 Links to the DesktopNow documentation, including the Environment Manager guides. These can be accessed at any time from your installation location.  A link to myAppSense web portal (www.myappsense.com).

 Option to launch the Personalization SCU.

7. Click Launch Personalization Server Configuration to open the SCU.

8. Click Finish to close the DesktopNow Installer, this part of the upgrade is now complete. The SCU must be run to fully complete the upgrade process. During the process you will be prompted to upgrade the database. Click Yes to proceed.

If you choose not to run the SCU from within the Suite Installer, you can select to run it anytime from the start menu:

Start > All Programs > AppSense > Environment Manager > Personalization Server Configuration

For further information on the SCU, refer to the Server Configuration chapter.

The Management Server Configuration Utility also needs to be run to upgrade the AppSense Management Center.

For further information on the AppSense Management Server Configuration Utility and deploying Agents and Configurations refer to the AppSense Management Center documentation.