How To Install An Appsense Desktop Manager On A Windows 7.5 (Windows 7) With A Windows (Windows 8) (Windows) (Powerpoint) (Amd64) (Apple Windows 7) (Networking

(1)

Version 8 FR4 SP

2

Manager

Installation and

Upgrade Guide

(2)

All rights reserved. No part of this document may be produced in any form (including photocopying or storing it in any medium) for any purposes without the written permission of AppSense Limited, except in accordance with applicable law. Furthermore, no part of this document may be sold, licensed or distributed. The doing of an unauthorized act in relation to a copyright work may result in both a civil claim for damages and criminal prosecution. The information contained in this document is believed to be accurate at the time of printing and may be subject to change without notice. Any reference to a manufacturer or product does not constitute an endorsement of, or representation or warranty (whether express, implied or statutory) in respect of, the manufacturer or product or the use of the product with any AppSense software.

This document does not grant any right or license to you in respect of any patents, patent applications, trademarks, copyrights, or other intellectual property rights in or relating to the subject matter of this document. Where relevant, any AppSense software provided pursuant to or otherwise related to this document shall only be licensed to you on and subject to the end user license agreement which shall be displayed and which you shall be required to accept prior to accessing or using the software.

AppSense is a registered trademark of AppSense Holdings Limited or its affiliated companies in the United Kingdom, the United States and/or other countries, Microsoft, Windows and SQL Server are all registered trademarks or Microsoft Corporation in the United States and/or other countries. The names of actual products and companies mentioned in this document may be the trademarks of their respective owners.

24

Load Balancing Status Request

25

Licensing

25

(5)

Section 3 Upgrades

27

Upgrade Environment Manager

28

Preparing to Upgrade

28

Upgrading from pre-8.1 Versions of Environment Manager

28

Components to Upgrade

29

Server

29

Database

29

Agents

30

Configurations

31

Upgrade Order

32

Enterprise Mode Upgrade

33

Agents and Configurations Upgrade to 8 FR4 from a pre-8.1 Version

35

Standalone Mode Upgrade

36

Standalone Configuration Upgrade Process

37

Desktop Settings on Upgrade

37

Desktop Settings 8.4 Upgrade Behavior

38

Certificates on Upgrade

38

Section 4 Server Configuration

39

Server Configuration for Environment Manager

40

Personalization Server Configuration Utility Wizard

41

Configure a Server Using Low SQL Privileges

45

Configuring Secure Communications

46

Section 5 Configuration

47

Environment Manager Architecture

48

Console

48

Configurations

51

Agent

51

(6)

Section 6 Environment Manager Browser Interface

54

About the Browser Interface

55

Installation

55

Configuration

56

Section 7 Personalization Database Replication

59

Principles

60

Prerequisites

61

Initial Steps

61

Performing the Setup

62

Post Setup Steps

62

Replication and Personalization Server Upgrades

63

Upgrade Replication Servers

63

Manually Removing Replication from Personalization Servers

64

Replication and Personalization Server Upgrades from Pre-8.3 Versions

65 Appendixes

(7)

In this Section:

 About This Document on page viii  Terms and Conventions on page viii  Feedback on page viii

(8)

A

BOUT

T

HIS

D

OCUMENT

This Product Guide is for use by AppSense Environment Manager administrators. It provides information on how the Environment Manager works and describes its components and architecture.

The aim of the guide is to enable the administrator to optimize the effectiveness of Environment Manager and assist in troubleshooting any issues that may arise.

T

ERMS AND

C

ONVENTIONS

The following tables shows the textual and formatting conventions used in this document:

F

EEDBACK

The AppSense Documentation team aim to provide accurate and high quality documentation to assist you in the installation, configuration and ongoing operation of AppSense products. We are constantly striving to improve the documentation content and value any contribution you wish to make based on your experiences with AppSense products.

Please email any comments to: documentation.feedback@appsense.com

Convention Use

Bold Highlights items you can select in Windows and the product interface, including nodes, menus items, dialogs and features.

Code Used for scripting samples and code strings.

Italic Highlights values you can enter in console text boxes and titles for other guides and Helps in the documentation set.

Green + underlined Indicates a glossary link.

> Indicates the path of a menu option. For example,

(9)

Introduction

 Overview on page 2  Key Benefits on page 3  Feature Summary on page 4

(10)

O

VERVIEW

AppSense Environment Manager is a user virtualization solution which ensures users always receive a consistent, predictable and personalized working experience.

For virtualized desktop environments, user virtualization represents a fundamental change in the way the corporate desktop is constructed, delivered and managed.

Environment Manager enables standard desktop images to be used to deliver fully

configured and personalized desktops to all employees. The user component of a desktop (user personality) is decoupled from the operating system and applications, managed independently and applied into a desktop as required. This is achieved without scripting, group policies or use of roaming user profiles - regardless of how the desktop is delivered. Environment Manager provides a more efficient alternative to roaming profiles, reducing the potential for profile corruption and providing users with a consistent and seamless working experience.

By applying user data on-demand, delivery methods can be combined, user migration between platforms and operating systems can be performed and the corporate desktop can be updated with no impact on the user experience.

Environment Manager uses a combination of Policy Configuration and User Personalization to enable comprehensive user virtualization.

 Policy Configuration - Corporate policy is used to set up a corporate desktop

environment and specifies what users have access to, how they access it and what they can do with it.

 User Personalization - Constitutes anything a user is able to customize on their

endpoint. This includes the desktop look and feel, application menus and buttons, language settings and screen resolution.

The Environment Manager User Interface provides the ability to create and modify both Policy and Personalization configurations. Both of these are created and deployed to endpoints in different ways. Policy configuration settings are stored in the a configuration file (AEMP) which must be deployed to endpoints before it can take effect. For User

Personalization, the user interface maintains a live connection to the database. Changes are immediately saved to the database and take effect at each endpoint the next time it performs a configuration poll.

AppSense Environment Manager enables users to have a single personality which is accessible from any location and any device. The settings save on disconnection enabling the user to work offline. Any changes made to their personality whilst offline are

(11)

K

EY

B

ENEFITS

 Streaming user settings on-demand in response to user actions, reducing network traffic

and logon times.

 Simple migration of user profile data and settings between desktops, operating systems

and delivery systems.

 Personalization settings are managed and streamed at application level enabling

independent management of user profile data on a per application basis and allowing applications to be upgraded and swapped with no user impact.

 Assist migration of users to Microsoft Windows 7.

 Automatic management of user application personalization.  Remove the potential for profile corruption.

 Enable consistent quality of service to the user regardless of the environment delivery

mechanism.

 Manage personalization settings across distributed server silos.  Simple migration from existing profiles.

 Malicious or accidental user environment changes can be automatically self-healed.  Minimize support costs and maximize user productivity.

(12)

 Ensure users remain compliant with policy regardless of how they receive their working

environment.

 Quickly implement business policies which can be shared and utilized across operating

system boundaries and different application delivery mechanisms by use of triggers, actions and conditions.

 Introduce pre-built corporate policy best practice with AppSense Policy Templates.

F

EATURE

S

UMMARY

This section provides a summary of the main features of Environment Manager.

User Personalization

Automated Personalization Management

Automatically monitor and manage user personalization settings by saving and restoring only the application changes that have been made within a user’s session. This reduces administrative overhead and the complexity associated with identifying the personalization settings.

Streamed Application Profiles

Manage user personalization settings when applications are started and stopped, as opposed to only user log on or off, by streaming personalization settings as and when required. This improves user logon times and makes the latest application personalization settings available across concurrent open sessions.

Personalization Analysis

Generate tabular and graphical reports based on personalization settings across a group, an individual user or an application, identify resource bottlenecks and streamline

personalization settings to improve end user performance. Personalization Rollback

Create personalization restore points so that personalization settings can be restored, on a per user or application basis, in the event of data loss or to restore a desired state.

Offline Mode

Ensure mobile users have access to the latest version of their personalization settings whilst working offline and ensure their settings are synchronized across open concurrent sessions when back online.

Migration Mode

Seamlessly migrate existing local or roaming user profiles or upgrade older versions of Environment Manager to use the application personalization streaming solution.

(13)

Flexible Action Event Triggers

Configure personalization or policy settings to apply when certain triggers occur. This enables more flexible control of user environments under heterogeneous delivery mechanisms.

Computer Action Event Triggers

Computer Actions can be configured to apply when the computer starts up or shuts down, or when a process is started or stopped.

User Event Triggers

User Actions can be configured to apply when:

 A user logs on or off

 An application is started or stopped  A network is connected or disconnected  A session is disconnected or connected  A session is locked or unlocked.

Microsoft App-V Management

The ability to customize App-V sequenced application settings based on user, session and computer based rule conditions. Extend the delivery mechanism of App-V applications to the client or user by enabling both custom OSD and icon file delivery.

Folder Redirection

Folder redirection allows end user data, such as personal documents and corporate data to be stored outside of the profile. This has the added benefit of minimizing network bandwidth consumption, saving and loading only the relevant areas of a user’s profile, rather than transferring the whole profile across the network.

Lockdown

Lockdown removes unwanted functionality such as buttons, tree view options and menu items from Windows applications.

Environment Manager allows you to strip out unwanted functionality from third party software either for security reasons or to reduce the complexity of the end user experience.

Lockdown actions include the following:

 General Lockdown - Hide or disable user interface controls.

 Keyboard Lockdown - Block keyboard shortcuts for all or specific applications.  Office Lockdown - Disable any supported Microsoft Office application menu item,

(14)

Self Healing

Ensure critical files, registry settings, processes and services remain unaltered using the Self Healing mechanism.

Self Healing actions restore computer and user settings to their original state in the event of software failure or unauthorized changes.

Self Healing actions can be applied to processes, services, files and the registry. Self Healing can be used to ensure critical applications, such as security software, are restarted or repaired immediately following any failure resulting from malicious or accidental actions and provides security against the threat of malicious software attempting to infiltrate and alter registry settings or modify content.

The self healing mechanism restores settings in real-time. For example, if a Trojan virus is added to any of the Windows start up keys, Self Healing immediately removes the threat.

AppSense Policy Templates

Create a library of configuration snippets by exporting templates from a full configuration to a specified location, saving as XML files. These policy templates can then be imported in to another configuration at a later date.

Windows ADM/ADMX File Support

Uses Windows ADM/ADMX files (Administrative templates) to create and apply user and system policies.

Windows ADM/ADMX files can be referenced, bringing the management of existing policies into the Environment Manager console, complementing existing Active Directory

environments or extending settings to computers outside of Active Directory control.

Auditing

The auditing facility allows you to specify which events are included in the audit and the location of the related audit logs.

Configuration Profiler

Configuration Profiler allows you to generate summary reports of Environment Manager Configuration settings enabling analysis and troubleshooting of complex configurations. Reports can be set up to provide information about actions, conditions and triggers relating to specific users or groups, published applications and machines.

Currently only 32-bit and 64-bit applications are fully supported by the self healing process mechanism. It is not recommended to self heal DOS or 16-bit applications using this method. Attempting to self heal a DOS or 16-bit application process may present multiple instances of the same application in a short period of time.

(15)

Environment Manager Browser Interface

Environment Manager comes complete with a Browser Interface which provides

management of Personalization data, similar to the capabilities of Personalization Analysis, simply by navigating to a URL. This allows support teams to safely carry out routine maintenance for end users in a focused environment without using the main Environment Manager console. This removes the need to have full configuration access to the database to perform these tasks.

Environment Manager Administrative Tools

Environment Manager is packaged with the following standalone tools which assist

administrators when creating configurations and working with the Personalization Database.

 Configuration Assistant

 Environment Manager Personalization (EMP) File Utility  EMP Migrate Utility

 EMP Registry Utility  Log Viewer

 Extra Session Data

 File Based Registry (FBR) Explorer  Debug Setup Tool

(16)

Installation

 Prerequisites on page 9

 Installing AppSense Environment Manager on page 10  Service Pack Installation on page 22

 Status Request on page 24  Licensing on page 25  Uninstallation on page 26

(17)

P

REREQUISITES

This section gives details of the system requirements for AppSense Environment Manager.

Supported Languages

 English

 German

 French

Supported Operating Systems and Technologies

The Supported Operating Systems and Technologies are detailed in the compatibility matrix available on myAppSense. Select Software > DesktopNow > Environment Manager > EM Compatibility Matrix.

Required Utilities and Components

Client

 Microsoft Windows Installer 3.1 - minimum requirement (included in Microsoft Windows

Server 2003 Service Pack 1)

 Microsoft Core XML Services (MSXML) 6.0  XML Lite 1.0.1018.0

 Microsoft Visual C++ 2010 Redistributable Package Personalization Server

 Microsoft .NET Framework 3.5  Internet Information Services (IIS)

 Microsoft Visual C++ 2010 Redistributable Package  Microsoft ASP.NET 2.0

 Microsoft Core XML Services (MSXML) 6.0 Browser Interface

 Microsoft .NET Framework 4.0  Internet Information Services (IIS)  Microsoft ASP.NET 4.0

(18)

User Interface

 Microsoft .NET Framework 3.5

 Microsoft Visual C++ 2010 Redistributable Package

Installed Components

The following components are installed as part of the AppSense DesktopNow installer:

 Windows Installer 3.1 Redistributable (v2)  Microsoft Core XML Services (MSXML) 6.0

 Microsoft .NET Framework 3.5 SP1Redistributable Package

 Microsoft Visual C++ 2010 SP 1 Redistributable package (x86) and (x64)

I

NSTALLING

A

PP

S

ENSE

E

NVIRONMENT

M

ANAGER

Environment Manager can be installed with the Management Center to create integrated enterprise scale solutions or installed as a standalone product aimed at evaluations. The AppSense DesktopNow Installer provides a comprehensive process for installing any combination of AppSense products, including Environment Manager, in a single, fully integrated sequence. The installer performs a complete check for system prerequisites and provides the option of installing required technologies automatically.

Alternatively, product components can be installed manually, by running the product installer packages for each component.

 AppSense DesktopNow Installer  Manual Installation

Packages

Installer packages for each component in the AppSense Environment Manager product set include 32-bit and 64-bit versions as follows:

 EnvironmentManagerAgent.msi  EnvironmentManagerConsole.msi  PersonalizationServer.msi

 EMBrowserInterface.msi

 EnvironmentManagerDocumentation.msi

When installing AppSense products manually, you must ensure that all the required technologies and AppSense components, listed in the Prerequisites section are added.

(19)

Additional prerequisite third-party software components are provided with the installation media and can be installed automatically via the DesktopNow Installer or manually by running the relevant packages provided.

Client-server Authentication Mode

Prior to 8 FR4, Environment Manager used anonymous authentication as the default method of communication between clients and servers. From 8 FR4 the default method for new installations is Windows Authentication - communication between clients and servers is authenticated by users’ credentials supplied when logging on to a managed endpoint. Once installed, the authentication method can be changed to your required method using the Server Configuration Utility (SCU).

Upgrades

When upgrading to 8 FR4, Environment Manager maintains the current anonymous authentication method.

Phased Upgrades

During a phased upgrade, clients which have not been upgraded can still connect to an 8 FR4 server. However, each request to the server is challenged and requires the client to resubmit the request with the user’s credentials. This has a performance impact and it is therefore recommended that clients are upgraded before Windows authentication is enabled.

Upgrades from 8.0

If Windows authentication is enabled, personalization will fail between 8.0 clients and 8 FR4 servers. To ensure personalization continues to work, upgrade all 8.0 clients to 8 FR4 before enabling Windows authentication.

A quick test to ensure that AppSense Environment Manager has installed correctly is to start the Task Manager and check the running System Processes for EMCoreService.exe

(20)



S

ETTINGTHE

A

UTHENTICATION

M

ETHOD 1. Open the SCU:

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

2. Select PersonalizationServer. 3. Select the required authentication:

Required Install Order

For Environment Manager to install and function correctly, install the following components in this order:

1. Servers and Databases 2. Consoles

3. Agents and Configurations

AppSense DesktopNow Installer

This section provides an overview of the installation process using the DesktopNow installer as follows:

 Enterprise Installation Using the DesktopNow Installer  Standalone Installation

There are additional Environment Manager Tools available which are not part of the DesktopNow Installer. For further details refer to Manual Installation on page 18.

(21)

Enterprise Installation

Enterprise installation allows you to install the full suite of product consoles together with the AppSense server components. You are prompted to select which server products to install. The Enterprise Suite includes:

 AppSense Application Manager  AppSense Environment Manager  AppSense Performance Manager  AppSense Management Center

Enterprise installation is completed by running the Server Configuration Utility (SCU) for each installed server product. This does not apply to Application Manager as it does not have an SCU.

Enterprise Installation Using the DesktopNow Installer

1. Run the installer by executing setup.exe on the installation media. 2. In the Welcome screen, click Next.

3. In the User Information screen, enter user and company names and click Next. 4. Read the license agreement, if you accept the terms, select and click Next.

5. In the License Validation screen, enter a product license code and activation code for Environment Manager or select to use the evaluation license (valid for 21 days) and click Next.

6. In the Installation Type screen, select Enterprise and click Next.

 Enterprise Installation is only available when the AppSense DesktopNow Installer is launched on

a Server operating system.

 In a distributed environment where product consoles and server components are installed on

separate management computers, you need to run the installer again on each computer to install the relevant components.

For more information about product licenses see:

 Licensing on page 25

 The Licensing chapter in the AppSense Environment Manager Personalization Product

guide.

 The AppSense Management Center Product Guide.

The AppSense Environment Manager Agent is entered into the Management Center database when you run the Management Server Configuration utility after the installation has completed.

(22)

7. In the Product Selection screen, select Management Center and Personalization Server and click Next.

8. In the SQL Server Installation screen, if a local Microsoft SQL Server is not detected, you are prompted to install either a Microsoft SQL Server or browse to select an existing remote SQL Server and instance.

If an existing SQL server is not selected, the Microsoft SQL Server Express Edition is installed as part of your Enterprise installation. If you select this option, accept the license agreement and follow the prompts of the Microsoft SQL Server Setup to complete the installation.

9. The Prerequisite Management screen detects which of the installation prerequisites are Installed, Not Installed and those that Require Manual Installation.

 The prerequisites which require manual installation should be installed first, outside of the installer. For example, Internet Information Services (IIS) are part of the Operating System and must be installed using the relevant Server configuration options, available in the Operating System.

 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. When installing in Enterprise mode, the Environment Manager Console is installed with the Management Center and the AppSense Environment Manager Agent is added to the Management Center database ready to be deployed to endpoints.

For further information on deploying Agents from the AppSense Management Center refer to the AppSense Management Center Installation and Upgrade Guide.

You can skip this step and configure remote servers later using the Server Configuration Utility for each of the products.

(23)

10. Once all prerequisites are installed, click Next.

11. In the Installation Directory screen, select a location for installing the AppSense product files using the Browse button. The default location is C:\Program Files\AppSense. Once selected, click Next.

12. The Summary screen shows the items ready to be installed, the installation mode, install directory and whether a reboot is required. Click Install.

13. The Install Complete screen displays with the following components:

 If required for the installation, the Restart the computer now check box. Your computer automatically restarts upon install completion. Deselect to bypass this and manually restart later.

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

 Buttons to run the Management Server and Personalization Server Configuration Utilities. Both utilities can be run as required from the start menu:

Start > All Programs > AppSense and select the product for the utility. The Server Configuration Utility must be run to fully complete the installation.

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

documentation.

 For information on how to use the Personalization Server Configuration Utility, refer to Server Configuration on page 39.

(24)

Standalone Installation

Standalone installation installs the product consoles and agents together on the host system. Standalone products can be installed on server or desktop computers.

1. Run the installer by executing setup.exe on the installation media. 2. In the Welcome screen, click Next.

3. In the User Information screen, enter user and company names and click Next. 4. Read the license agreement, if you accept the terms, select and click Next.

5. In the License Validation screen, enter a product license code and activation code or select to use the evaluation license (valid for 21 days) and click Next.

6. In the Installation Type screen, select Standalone. For more information about product licenses see:

 Licensing on page 25

 The Licensing chapter in the AppSense Environment Manager Personalization Product

guide.

(25)

7. In the Product Selection screen, select Environment Manager and click Next.

8. The Prerequisite Management screen detects which of the prerequisites for installation are Installed and which are Not Installed.

Click Install All to install the required prerequisites. 9. Once all prerequisites are installed, click Next.

10. In the Installation Directory screen, select a location for installing the AppSense product files using the Browse button. The default location is C:\Program Files\AppSense. Once selected, click Next.

11. The Summary screen shows the items ready to be installed, the installation mode, install directory and whether a reboot is required. Click Install.

12. The Install Complete screen displays with the Restart the computer now check box selected. Deselect if you want to manually restart later. Once the computer has been restarted the install process is complete.

The Install Complete screen links you to the DesktopNow documentation and the myAppSense web portal (www.mysppsense.com). These areas can also be accessed independently from the installation location and via your internet browser respectively. 13. Click Finish to complete the install.

A message displays if any reboots are required. Click OK to continue or Cancel to change your selection.

(26)

Manual Installation

The table below shows the list of the Windows Installer Packages (MSI) for each of the components in the AppSense DesktopNow, which you can run manually on the host computers.

When installing AppSense products manually, you must ensure that all required

technologies and AppSense components are added. These are detailed in the Prerequisites section.

Installation File Description

Environment Manager

EnvironmentManagerConsole32.MSI EnvironmentManagerConsole64.MSI

Installs the Environment Manager Policy and Personalization individual or combined consoles for:

 Creating configurations to deploy to managed computers

hosting the agent

 Configuring the Personalization database.

EnvironmentManagerAgent32.MSI EnvironmentManagerAgent64.MSI

Installs the AppSense User Virtualization Service on managed computers. When a configuration is installed, the agent implements the configuration rules.

PersonalizationServer32.MSI PersonalizationServer64.MSI

Installs the Personalization Server which synchronizes user personalization settings between the SQL database and the managed computer.

Must be configured using the Personalization Server Configuration Utility.

EnvironmentManagerDocumentation32.MSI EnvironmentManagerDocumentation64.MSI

Installs:

 Environment Manager Actions and Conditions Scripting

Guide

 Environment Manager Administrative Tools Guide  Environment Manager Installation and Upgrade Guide  Environment Manager Personalization Product Guide  Environment Manager Policy Product Guide  Environment Manager Help.

EnvironmentManagerTools32.MSI EnvironmentManagerTools64.MSI

Installs the Environment Manager Administrative Tools which are a range of standalone tools to assist administrators when working with the Personalization Database and creating configurations. The tools run independently from Environment Manager and all other AppSense products.

EMBrowserInterface32.MSI EMBrowserInterface64.MSI

Installs the Environment Manager Browser Interface which provides a web based platform for support teams to safely carry out routine maintenance, similar to Personalization Analysis, for end users in a focused environment without using the main Environment Manager console.

ConfigurationAssistant32.MSI ConfigurationAssisant64.MSI

Installs the Configuration Assistant which is a standalone application that assists in the configuration of Environment Manager User Personalization. It does this by identifying applications that may be grouped together in order to share personalization data and identifying where certain data should be provided as Session Data.

(27)

Manually Installing the Environment Manager Console

There are three variants of the Environment Manager console:

 Personalization - Installs only the personalization element of Environment Manager  Policy - Installs only the policy element of Environment Manager

 Both consoles - Installs the combined console; both personalization and policy are

installed.

The traditional Environment Manager installation, using Setup.exe, automatically installs the combined console. Some administrators may not require access to both. For example, they may only be responsible for configuring personalization and have no need for the policy side of the console. Installing the Personalization or Policy consoles can only be done using the EnvironmentManagerConsole MSIs. This is explained in the procedure below.



M

ANUALLY

I

NSTALLAN

E

NVIRONMENT

M

ANAGER

C

ONSOLE 1. Double-click the installer appropriate to the operating system:

 EnvironmentManagerConsole32.MSI  EnvironmentManagerConsole64.MSI 2. Click Next.

3. Read the license agreement, if you accept the terms, select and click Next. 4. Click Next.

Installation File Description

Management Center

ManagementConsole32.MSI ManagementConsole64.MSI

Installs the Management Center Console which provides an interface to the Management Server and the other components of the Management Center.

ManagementServer32.MSI ManagementServer64.MSI

Installs the Management Server which manages data access and storage, security control, network discovery services and software deployment to managed computers, resource management and enterprise auditing.

Must be configured using the Management Center Server Configuration Utility

ClientCommunicationsAgent32.MSI ClientCommunicationsAgent64.MSI

Installs the Client Communications Agent (CCA) to manage communications between the product agents and the AppSense Management Center.

ManagementCenterDocumentation32.MSI ManagementCenterDocumentation64.MSI

Installs the Management Center Installation and Upgrade Guide, the Management Center Product Guide and the Management Center Help

Licensing

LicensingConsole32.MSI LicensingConsole64.MSI

Installs the Licensing Console for managing licenses for products installed in Standalone mode.

(28)

5. Select the console(s) you want to install:  Personalization

 Policy

 Select both options to install the combined console (this is the default setting)

6. Click Next. 7. Click Install.

(29)

Low Privilege Database Setup

Administrators can update the CreateDatabase.sql script in order to make creating the database easier. When the updated script is run, a database is created which allows a user with fewer privileges to run the SCU.

The process must be completed prior to running the SCU.

1. Install Environment Manager as detailed in Installing AppSense Environment Manager

on page 10.

Do not start the SCU and if it starts automatically, cancel and exit the application. 2. Open the CreateDatabase.sql script, which located in the Scripts directory:

C:\Program Files\AppSense\Environment Manager\Personalization Server\Scripts

3. Create two SQL Server logins, one for the configurer account and one for the service account.

4. Edit the CreateDatabase.sql script with the name of the database and the two logins, as shown in bold below:

declare @DatabaseName sysname

set @DatabaseName = 'Personalization' declare @EMConfigurationLogin sysname

set @EMConfigurationLogin = 'Domain\Configurer' declare @EMServiceLogin sysname

set @EMServiceLogin = 'Domain\Servicer'

5. Run the script to create the database and give both logins appropriate access to the new database.

The SCU can now be run to set up the database using the Configurer and Service accounts set up using the script.

Once all personalization servers have been set up by the SCU, the db_owner privilege may be revoked from the configurer account as it is not required for normal running.

If you installed to a location other than the default, amended the path accordingly.

Privileges for these accounts are set by the CreateDatabase.sql script. The configurer is made the owner of the personalization database and the service account is added to the

(30)

S

ERVICE

P

ACK

I

NSTALLATION

AppSense Service Packs are self contained packages or patches that are used to update specific files within a DesktopNow application without reinstalling the full application. Service packs can be applied more often and reduce the need for system restarts on your endpoints. Service packs are delivered as a Windows Installer patch (MSP) file and are often referred to as patch files.

To view previously installed patches, navigate to Control Panel > Programs > Programs and Features > Installed Updates.

Installing Service Packs

Service Packs can be installed or deployed using the same technology and techniques used when installing MSIs. Both Microsoft System Center and the AppSense Management Center 8 FR4 can deploy MSPs. If neither of these products are available, service packs can be installed using the command line interface.

For example, the command:

msiexec.exe /p EnvironmentManagerAgent64.msp

installs any files that have been amended as part of the patch for just Environment Manager 64 bit agent.

The following command installs the base version of the Environment Manager Agent (MSI) and the Environment Manager patch file (MSP) simultaneously:

msiexec.exe /i EnvironmentManagerAgent64.msi PATCH=c:\fullpath\EnvironmentManagerAgent64.msp

If the patch file contains driver or hook files that are currently in use on the machine the patch is being applied to, you are informed that a reboot is required. If you chose to continue, the system is restarted when the patch has been applied.

Installation Order and Dependencies

It is recommended that all components of a service pack are installed and that the

PersonalizationServerXX.MSP is installed first. All other components have no required install order.

A base version must be installed before the patch file can be applied.

For information on installing and upgrading service packs using Management Center 8 FR4, see the

(31)

Rolling Back Service Packs

There are two ways to roll back, or uninstall AppSense Service Packs:

 Using the Windows Control Panel  Using Management Center 8 FR4

Rolling Back Service Packs Using Windows Control Panel

The procedure used to roll back service packs varies depending on the Operating System: For Windows 7

1. Navigate to Control Panel > Programs > Programs and Features > Installed Updates.

2. Highlight the selected patch and click Uninstall. When using Windows XP

1. Navigate to Start > Control Panel > Add or Remove Programs > Change or Remove Programs.

2. Select Show updates.

3. Highlight the selected patch and click Remove.

Rolling Back Service Packs Using Management Center 8 FR4

1. In the Management Center console, select Overview > Deployment Groups tab > Deployment Groups.

2. Highlight the Deployment Group and select Settings > Assigned Packages.

The Assigned Packages work area displays a list of all the AppSense products and their associated packages.

3. Highlight the required Environment Manager service pack and click Unassign from the Actions menu.

4. Click Review and Submit.

The Submit Changes dialog displays.

5. Check the details are correct and click Submit.

The patch is unassigned based on the deployment group Installation Schedule.

If a service pack is uninstalled the installation reverts to the previous latest build, whether a service pack or base version.

All agent and console service pack components except the Personalization Server component patch file (PersonalizationServerXX.msp) can be uninstalled.

(32)

S

TATUS

R

EQUEST

To test whether a Personalization Server is installed, running and to test the database connection, enter the following URL in your internet browser, replacing <SERVER> with the name of the required server: http://<SERVER>/PersonalizationServer/status.aspx.

The status.aspx file for a server shows whether the server connection was successful and further details about the connection, database and server.

When status.aspx is run, not all client facing parts of server are initialized. Therefore, the first person to log on may experience a delay to personalization applying.

(33)

Load Balancing Status Request

If using a load balancer monitor to check the server status page (status.aspx) where the server is set to Windows Authentication, the monitor must provide Windows credentials in the HTTP headers or the server will respond with an "unauthorized" reply. As an alternative, use one of the following methods, appropriate to your setup should be used.

To check the health of load balanced servers use the following methods, appropriate to your setup.

IIS7 - Windows Server 2008 and R2

Use the following URLs in an internet browser, replacing <SERVER> with the name of the required server:

 http://<SERVER>/PersonalizationServer/dbmonitor.aspx - Checks the

connection with the database. Returns "OK" if the database can be contacted and "FAIL" if it cannot.

 http://<SERVER>/PersonalizationServer/pingmonitor.aspx - Checks whether the personalization server address is reachable returning "OK" if successful. No response indicates an error.

IIS6 - Windows Server 2003

For IIS6, the SetMonitorAnonymousIIS6.vbs script must be used to set up dbmonitor.aspx and pingmonitor.aspx for anonymous access. For further details, contact AppSense Support.

L

ICENSING

The three AppSense license types are listed in the table below

.

License Description

AppSense DesktopNow  Full Suite license.

 Requires activation using the activation code sent from AppSense with the

license code. AppSense Environment

Manager _ Single product license._{Requires activation using the activation code sent from AppSense with the} license code.

Evaluation  Full Suite or single product licenses.

 Evaluation licenses are available during the first installation of the product

and do not require activation. They are valid for 21 days.

If AppSense Environment Manager was installed in Standalone mode, a quick test to check the product is licensed correctly is to start the Task Manager and check the running processes for EMUser.exe

(34)

U

NINSTALLATION

AppSense Environment Manager is uninstalled using the AppSense DesktopNow Installer. 1. Run the AppSense DesktopNow Installer by executing setup.exe on the installation

media.

2. In the Welcome screen, select Uninstall and click Next.

3. The Summary screen shows the items ready to be uninstalled and further information about your installation. Click Install.

4. In the Uninstall Complete screen, click Finish.

 Any user created configurations will not be uninstalled with the product, the AEMP files must

be manually deleted from where they were saved (default location:

C:\ProgramData\AppSense\Environment Manager).

 Environment Manager can also be uninstalled from the Control Panel. If using this method

ensure you uninstall each component of Environment Manager and DesktopNow.

If AppSense Environment Manager has been installed in Standalone mode then you must use

(35)

Upgrades

 Upgrade Environment Manager on page 28  Components to Upgrade on page 29  Upgrade Order on page 32

 Enterprise Mode Upgrade on page 33

 Agents and Configurations Upgrade to 8 FR4 from a pre-8.1 Version on page 35  Standalone Mode Upgrade on page 36

 Desktop Settings on Upgrade on page 37  Certificates on Upgrade on page 38

(36)

U

PGRADE

E

NVIRONMENT

M

ANAGER

This chapter guides you through the process required to upgrade AppSense Environment Manager.

Preparing to Upgrade

It is recommended that the following actions are carried out prior to an upgrade:

 Back up all databases

 Save all product configuration packages from the console

 Disconnect all users from the Personalization Servers.

 Take all Personalization Servers offline until the upgrade is complete.  Run the whole suite installer to upgrade components.

Upgrading from pre-8.1 Versions of Environment Manager

If you are using AppSense Management Center you must upgrade the Management Center to the latest 8.2 version before upgrading Environment Manager to v8.2. This is because the upgrade process requires the Management Center Configuration Installation Schedule functionality.

Microsoft SQL Server 2000 Support

Microsoft SQL Server 2000 database support has been deprecated. Environment Manager does not allow upgrades or clean installations of a Personalization Database using SQL 2000.

If you are using Microsoft SQL Server 2000 and want to upgrade Environment Manager, you must upgrade your SQL Server instance before upgrading your Personalization Servers.

This applies to versions of Environment Manager later than 8.3.192.0, when support for Microsoft SQL Server 2000 ceased.

Before upgrading, backup all existing AppSense databases and save product

configuration packages from all the existing consoles, as MSI files. If necessary, save earlier versions of the product agent software which you would like to maintain. For more information about saving configurations files from product consoles, see the Environment Manager Help.

Environment Manager has changed significantly since version 8.0. When upgrading to version 8.2 from a pre-8.1 version of Environment Manager, it is essential that you follow all steps in this upgrade process. Failure to do so will result in loss of functionality and data.

The Environment Manager release notes details the changes and updates which were implemented for each release. The release notes are available from your myAppSense web portal

(37)

C

OMPONENTSTO

U

PGRADE

The following Environment Manager components must be upgraded:

 Server  Database  Agents  Configurations

Server

All servers connected to a single database must be upgraded at the same time. Upgrading to a newer release includes a database schema change. Therefore all personalization servers are locked out of the database until the upgrade process is complete.

Load Balanced Servers

When Personalization servers are load balanced and operate as individual entities using a common IP address, it is recommended that all Personalization servers are taken offline before upgrading. When the upgrade is complete, servers can be brought back online and added back to the network load balanced configuration.

When upgrading Personalization servers, the first Personalization Server to be upgraded also upgrades the database. This ensures that the server and database versions match after the schema change. During an update of a server and the database, all other

Personalization servers are locked out.

After the upgrade of each Personalization Server, repeat the steps in the AppSense Network Load Balancing Guide entitled Configure Application Pools to ensure that all App Pools are using the correct Windows identity.

Upgrading Replication Servers

Upgrades cannot be performed whilst replication is enabled. Replication must be disabled on the master and subscribers prior to upgrading all servers to the same version.

Database

Upgrading the database requires database administrator access rights.

If you do not upgrade the database through the Suite Installer, database scripts which install with the Personalization Server, can be used to configure the database.

Upgrading Environment Manager to a newer release includes a database schema change so all databases need upgrading. This is done as part of the Suite Installer upgrade through the SCU.

For details of how to set up and upgrade replication servers, see Personalization Database Replication on page 59.

(38)

Agents

Where possible, it is recommended that all agents are upgraded at the same time. However, this may not always be possible so Environment Manager can support a phased approach to upgrading agents. A combination of clients with upgraded agents and those clients yet to be upgraded can be connected to an upgraded server.

If upgrading from a pre 8.0.951.0 version of Environment Manager to a subsequent release, there may be reduced functionality in Desktop Settings, Session Data and Certificates. Session Data was introduced in version 8.0.951.0 of Environment Manager and some Desktop Settings were moved to Session Data. Therefore when upgrading from an earlier version to a subsequent release, there may be instances where data is not applied as expected.

Where a server has been upgraded from 8.0 to a subsequent release, any Certificates stored on the 8.0 server are migrated. However, if a phased upgrade of agents has been implemented meaning a mixture of 8.0 and clients from a later release are connected to the server, any changes made to Certificates on newer clients are not reproduced on the 8.0 clients.

Although older agents are compatible with upgraded servers, this is not true the other way round; upgraded agents will not function correctly with older server versions. It is important that the upgrade order is followed.

See Upgrade Order on page 32.

For further information, refer to Agents and Configurations Upgrade to 8 FR4 from a pre-8.1 Version on page 35.

(39)

Configurations

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.

(40)

U

PGRADE

O

RDER

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.

(41)

E

NTERPRISE

M

ODE

U

PGRADE

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.

(42)

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.

(43)

Testing Server Upgrades

On completion of the Personalization Server upgrade, test to ensure the server is functioning by visiting the PersonalizationServer website at:

http://localhost/PersonalizationServer/status.aspx or

https://localhost/PersonalizationServer/status.aspx

Replace localhost with the server name if you are running the test from a remote location to the Personalization Server. After approximately 30 seconds, a page displays to confirm successful connection. Check the details are correct and the tests are successful. When connection is complete the Personalization Server can accept requests from managed endpoint devices.

A

GENTS AND

C

ONFIGURATIONS

U

PGRADETO

8 FR4

FROMAPRE

-8.1 V

ERSION

The configuration structure has changed significantly since Environment Manager 8.0. This means that version 8.0 configurations are not compatible with 8.1, 8.2, 8.3 and 8 FR4 agents. Therefore, configurations must be upgraded at the same time as agents.

Follow this procedure to upgrade both agents and configurations:

1. Upgrade AppSense Management Center and the CCA on all endpoints.

2. Open the configuration in the Environment Manager console and Save to Management Center as an 8.2 configuration.

If you are using a load balancer monitor and the server is set to Windows Authentication. See Load Balancing Status Request on page 25.

It is important that this upgrade procedure is followed; the configurations and agents must be upgraded together for the upgrade process to be successful.

Environment Manager supports a phased approach to upgrading agents with an upgraded Personalization Server.

For further information see Agents on page 30.

Configuration Installation Schedule functionality was introduced in versions 8.1.407.0 of the Management Center and 8.1.408.0 of the Client Configuration Agent (CCA) to enable installations to be scheduled as required.

To use this feature, the Management Center and CCA must be upgraded to the above versions or later and then deployed. To ensure the feature works correctly the upgrade must be complete and the schedule configured, prior to upgrading the Environment Manager agent and configurations to 8.2.

The configuration schedule will remain as ’immediately’ on endpoints that are running older versions of the CCA than 8.1.408.0, regardless of how the server is configured.

For further information about Configuration Installation Schedule functionality, see the

(44)

3. Assign the upgraded configuration and 8.2 agent to Deployment Groups. The configurations and agents will be deployed according to the schedule.

S

TANDALONE

M

ODE

U

PGRADE

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, click Upgrade.

3. In the Prerequisite Management screen, a list of required components displays split into Installed and Not Installed components.

Select Install next to each Not Installed component or select Install All to install all missing prerequisites.

4. Once all components are installed click Next.

5. The Summary screen lists the products you selected to install, the installation mode, install directory and whether a reboot is required. Click Upgrade.

When the installation is complete, you are prompted to reboot the computer to complete the installation of the product agents.

The upgrade process is complete.

To ensure that the installation of configurations and agents is synchronized you must have the Installation Schedules set to one of the following:

Agent Schedule

 At Computer Startup  Schedule

Configuration Schedule

 At Computer Startup  Schedule from Agent

 Schedule - if selected, this must be exactly the same as the Agent Schedule.

The schedule must not be set to Immediately for either the Agent or Configuration. The Agent and Configuration schedules must match, i.e. if At Computer Startup is selected for the agent schedule the configuration schedule must also be set to At Computer Startup.

(45)

Standalone Configuration Upgrade Process

Environment Manager policy configuration files are upgraded automatically when opened in the combined or policy consoles. When you open a configuration created in an older version of the console, you are asked if you want to upgrade the configuration. Click Yes to upgrade. Save the configuration to complete the upgrade and ensure compatibility with the latest version of the console. Once the configuration has been saved it is ready to be deployed using a deployment mechanism.

D

ESKTOP

S

ETTINGS ON

U

PGRADE

When Environment Manager is upgraded from 8.0 to 8.1, all keys in the original desktop settings key list which are not managed by desktop settings are copied into the session data list and if not enabled already, session data is enabled for personalization groups.

The background service goes through each user and copies any registry data for session data keys in a user’s desktop settings profile to their session data, creating a new profile if necessary. If a user logs in before this happens the conversion is performed via the personalization server.

If a legacy client which supports session data (build 8.0.959.0 or later) logs in, it receives the desktop settings list without the replaced desktop settings and session data list. If the user logs in on both a legacy client which supports session data and a new client, both session data and desktop settings will roam between them. Any desktop settings keys saved by the new client which are not in the old desktop settings list will not roam back to the old client. If a legacy client which does not support session data (pre 8.0.959.0 build) logs in, it receives all the original settings keys (including the ones replaced by session data) and all the data. As with post 8.0.959.0 clients, the desktop settings roam to the new client but any changes to the keys which were replaced by session data will not roam.

Policy configurations cannot be upgraded in the Personalization only console. They can only be upgraded if opened in the policy or combined console.

When upgrading from Environment Manager 8.1 or 8.2, any registry key captured as session data is migrated into desktop settings and removed from session data.

In 8.3, desktop settings were expanded to manage additional registry keys. If these keys were already managed as session data in the previous version, they will be moved to desktop settings during the upgrade. Any new settings which were not previously in session data will be set to Off. Existing desktop setting which were previously enabled will continue to be enabled after the upgrade.

Extra Desktop Settings on Upgrade

Some desktop settings in 8.3 were updated to manage extra registry keys not included in the 8.2 release. When upgrading, if such a setting was enabled in 8.2, it will be enabled in 8.3 and 8 FR4 with the extra keys included.

For a full list of desktop settings and to see which are affected on upgrade, see the Desktop Settings Appendix in the AppSense Personalization Product Guide.

(46)

Desktop Settings 8.4 Upgrade Behavior

If you upgrade Environment Manager from 8.0 to 8.1, all desktop settings are enabled regardless of how they were set in 8.0.

If you upgrade from 8.1 to 8 FR4, your settings are persisted; the settings you applied in 8.1 will be matched in 8 FR4. New desktop settings in 8 FR4 will be set to Off.

An upgrade from 8.0 to 8 FR4 will not necessarily give you the same setting state as you would have upgrading from 8.1. This is because an initial upgrade from 8.0 to 8.1 is performed, enabling all desktop settings, before upgrading to 8 FR4 which persists these upgraded settings. New desktop settings in 8 FR4 will be set to Off.

C

ERTIFICATESON

U

PGRADE

The client maintains both the legacy format and the saved certificates and credentials in the same profile. When a new client logs on with an old profile, the client uses the old format to restore the certificates if there is no new-format data, and saves it in the new format. From then on there is no roaming between legacy and new clients.

Note on Session Data

If a registry key, personalized through desktop settings in 8.0, is converted to session data during an upgrade to 8.4, session data is automatically enabled for all personalization groups for which desktop settings are enabled in 8.0. Enabling session data for a personalization group personalizes all registry keys in the Global Session Data list. This could therefore lead to some registry keys being personalized when not required.

Therefore, following an upgrade, we recommend that session data is reviewed for each personalization group to ensure that only the required registry keys are personalized.

(47)

Server Configuration

 Server Configuration for Environment Manager on page 40  Personalization Server Configuration Utility Wizard on page 41  Configure a Server Using Low SQL Privileges on page 45  Configuring Secure Communications on page 46

Microsoft SQL Server 2000 Support

Microsoft SQL Server 2000 database support has been deprecated. Environment Manager does not allow upgrades or clean installations of a Personalization Database using SQL 2000.

If you are using Microsoft SQL Server 2000 and want to upgrade Environment Manager, you must upgrade your SQL Server instance before upgrading your Personalization Servers.

This applies to versions of Environment Manager later than 8.3.192.0, when support for Microsoft SQL Server 2000 ceased.