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

Transcription

1 Environment Manager Installation and Upgrade Guide Version 8 FR4 SP2

2 INSTALLATION AND UPGRADE GUIDE ii AppSense Limited, 2013 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.

3 C O N T E N T S Welcome vii About This Document viii Terms and Conventions viii Feedback viii Section 1 Introduction 1 Overview 2 Key Benefits 3 Feature Summary 4 User Personalization 4 Flexible Action Event Triggers 5 Microsoft App-V Management 5 Folder Redirection 5 Lockdown 5 Self Healing 6 AppSense Policy Templates 6 Windows ADM/ADMX File Support 6 Auditing 6 Configuration Profiler 6 Environment Manager Browser Interface 7 Environment Manager Administrative Tools 7 iii

4 INSTALLATION AND UPGRADE GUIDE iv Section 2 Installation 8 Prerequisites 9 Supported Languages 9 Supported Operating Systems and Technologies 9 Required Utilities and Components 9 Installed Components 10 Installing AppSense Environment Manager 10 Required Install Order 12 AppSense DesktopNow Installer 12 Manual Installation 18 Manually Installing the Environment Manager Console 19 Low Privilege Database Setup 21 Service Pack Installation 22 Installing Service Packs 22 Rolling Back Service Packs 23 Status Request 24 Load Balancing Status Request 25 Licensing 25 Uninstallation 26

5 INSTALLATION AND UPGRADE GUIDE v 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 Setup Tasks 52

6 INSTALLATION AND UPGRADE GUIDE vi 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 Appendix A Licenses 67

7 WELCOME In this Section: About This Document on page viii Terms and Conventions on page viii Feedback on page viii

8 INSTALLATION AND UPGRADE GUIDE WELCOME About This Document viii ABOUT THIS DOCUMENT 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. TERMS AND CONVENTIONS The following tables shows the textual and formatting conventions used in this document: Convention Bold Code Italic Green + underlined Use Highlights items you can select in Windows and the product interface, including nodes, menus items, dialogs and features. Used for scripting samples and code strings. Highlights values you can enter in console text boxes and titles for other guides and Helps in the documentation set. Indicates a glossary link. > Indicates the path of a menu option. For example, Select File > Open" means "click the File menu, and then click Open." FEEDBACK 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 any comments to: documentation.feedback@appsense.com

9 1 Introduction In this Section: Overview on page 2 Key Benefits on page 3 Feature Summary on page 4

10 INSTALLATION AND UPGRADE GUIDE 1 INTRODUCTION Overview 2 OVERVIEW 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 synchronized with the corporate network upon connection.

11 INSTALLATION AND UPGRADE GUIDE 1 INTRODUCTION Key Benefits 3 KEY BENEFITS 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. Apply user policy dynamically in any desktop delivery mechanism.

12 INSTALLATION AND UPGRADE GUIDE 1 INTRODUCTION Feature Summary 4 FEATURE SUMMARY User Personalization 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. This section provides a summary of the main features of Environment Manager. 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 INSTALLATION AND UPGRADE GUIDE 1 INTRODUCTION Feature Summary 5 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 Microsoft App-V Management Folder Redirection Lockdown An application is started or stopped A network is connected or disconnected A session is disconnected or connected A session is locked or unlocked. 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 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 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, toolbar or ribbon.

14 INSTALLATION AND UPGRADE GUIDE 1 INTRODUCTION Feature Summary 6 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. 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. AppSense Policy Templates Windows ADM/ADMX File Support 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. 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.

15 INSTALLATION AND UPGRADE GUIDE 1 INTRODUCTION Feature Summary 7 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 For further information, see the AppSense Environment Administrative Tools Guide.

16 2 Installation In this Section: 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 INSTALLATION AND UPGRADE GUIDE 2 INSTALLATION Prerequisites 9 PREREQUISITES This section gives details of the system requirements for AppSense Environment Manager. Supported Languages English German French Supported Operating Systems and Technologies Required Utilities and Components The Supported Operating Systems and Technologies are detailed in the compatibility matrix available on myappsense. Select Software > DesktopNow > Environment Manager > EM Compatibility Matrix. Client Microsoft Windows Installer minimum requirement (included in Microsoft Windows Server 2003 Service Pack 1) Microsoft Core XML Services (MSXML) 6.0 XML Lite Microsoft Visual C Redistributable Package Personalization Server Microsoft Windows Installer minimum requirement (included in Microsoft Windows Server 2003 Service Pack 1) Microsoft.NET Framework 3.5 Internet Information Services (IIS) Microsoft Visual C Redistributable Package Microsoft ASP.NET 2.0 Microsoft Core XML Services (MSXML) 6.0 Browser Interface Microsoft Windows Installer minimum requirement (included in Microsoft Windows Server 2003 Service Pack 1) Microsoft.NET Framework 4.0 Internet Information Services (IIS) Microsoft ASP.NET 4.0

18 INSTALLATION AND UPGRADE GUIDE 2 INSTALLATION Installing AppSense Environment Manager 10 Installed Components User Interface Microsoft Windows Installer minimum requirement (included in Microsoft Windows Server 2003 Service Pack 1) Microsoft.NET Framework 3.5 Microsoft Visual C Redistributable Package 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 SP 1 Redistributable package (x86) and (x64) INSTALLING APPSENSE ENVIRONMENT MANAGER 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 When installing AppSense products manually, you must ensure that all the required technologies and AppSense components, listed in the Prerequisites section are added. 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

19 INSTALLATION AND UPGRADE GUIDE 2 INSTALLATION Installing AppSense Environment Manager 11 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. 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 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.

20 INSTALLATION AND UPGRADE GUIDE 2 INSTALLATION Installing AppSense Environment Manager 12 SETTING THE AUTHENTICATION METHOD 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 AppSense DesktopNow Installer 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 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 INSTALLATION AND UPGRADE GUIDE 2 INSTALLATION Installing AppSense Environment Manager 13 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 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. 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. 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. 6. In the Installation Type screen, select Enterprise and click Next. 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 INSTALLATION AND UPGRADE GUIDE 2 INSTALLATION Installing AppSense Environment Manager In the Product Selection screen, select Management Center and Personalization Server and click Next. 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. 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. You can skip this step and configure remote servers later using the Server Configuration Utility for each of the products. 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.

23 INSTALLATION AND UPGRADE GUIDE 2 INSTALLATION Installing AppSense Environment Manager 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 ( 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 INSTALLATION AND UPGRADE GUIDE 2 INSTALLATION Installing AppSense Environment Manager 16 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. 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. 6. In the Installation Type screen, select Standalone.

25 INSTALLATION AND UPGRADE GUIDE 2 INSTALLATION Installing AppSense Environment Manager In the Product Selection screen, select Environment Manager and click Next. A message displays if any reboots are required. Click OK to continue or Cancel to change your selection. 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 ( These areas can also be accessed independently from the installation location and via your internet browser respectively. 13. Click Finish to complete the install.

26 INSTALLATION AND UPGRADE GUIDE 2 INSTALLATION Installing AppSense Environment Manager 18 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 EnvironmentManagerAgent32.MSI EnvironmentManagerAgent64.MSI PersonalizationServer32.MSI PersonalizationServer64.MSI EnvironmentManagerDocumentation32.MSI EnvironmentManagerDocumentation64.MSI EnvironmentManagerTools32.MSI EnvironmentManagerTools64.MSI EMBrowserInterface32.MSI EMBrowserInterface64.MSI ConfigurationAssistant32.MSI ConfigurationAssisant64.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. Installs the AppSense User Virtualization Service on managed computers. When a configuration is installed, the agent implements the configuration rules. 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. 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. 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. 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. 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 INSTALLATION AND UPGRADE GUIDE 2 INSTALLATION Installing AppSense Environment Manager 19 Installation File Description Management Center ManagementConsole32.MSI ManagementConsole64.MSI ManagementServer32.MSI ManagementServer64.MSI ClientCommunicationsAgent32.MSI ClientCommunicationsAgent64.MSI ManagementCenterDocumentation32.MSI ManagementCenterDocumentation64.MSI Installs the Management Center Console which provides an interface to the Management Server and the other components of the Management Center. 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 Installs the Client Communications Agent (CCA) to manage communications between the product agents and the AppSense Management Center. 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. 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. MANUALLY INSTALL AN ENVIRONMENT MANAGER CONSOLE 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.

28 INSTALLATION AND UPGRADE GUIDE 2 INSTALLATION Installing AppSense Environment Manager 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. 8. When the installation is complete, click Finish.

29 INSTALLATION AND UPGRADE GUIDE 2 INSTALLATION Installing AppSense Environment Manager 21 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 If you installed to a location other than the default, amended the path accordingly. 3. Create two SQL Server logins, one for the configurer account and one for the service account. 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 ProfileServerService role. 4. Edit the CreateDatabase.sql script with the name of the database and the two logins, as shown in bold below: sysname = 'Personalization' sysname = 'Domain\Configurer' sysname = '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.

30 INSTALLATION AND UPGRADE GUIDE 2 INSTALLATION Service Pack Installation 22 SERVICE PACK INSTALLATION 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 A base version must be installed before the patch file can be applied. 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. For information on installing and upgrading service packs using Management Center 8 FR4, see the AppSense Management Center Install and Upgrade Guide. 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.

31 INSTALLATION AND UPGRADE GUIDE 2 INSTALLATION Service Pack Installation 23 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 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. 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.

32 INSTALLATION AND UPGRADE GUIDE 2 INSTALLATION Status Request 24 STATUS REQUEST 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: 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. The status.aspx file for a server shows whether the server connection was successful and further details about the connection, database and server.

33 INSTALLATION AND UPGRADE GUIDE 2 INSTALLATION Licensing 25 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: - Checks the connection with the database. Returns "OK" if the database can be contacted and "FAIL" if it cannot. - 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. LICENSING 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 INSTALLATION AND UPGRADE GUIDE 2 INSTALLATION Uninstallation 26 UNINSTALLATION 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 Control Panel > Add\Remove Programs applet to uninstall.

35 3 Upgrades In this Section: 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 INSTALLATION AND UPGRADE GUIDE 3 UPGRADES Upgrade Environment Manager 28 UPGRADE ENVIRONMENT MANAGER This chapter guides you through the process required to upgrade AppSense Environment Manager. Preparing to Upgrade 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 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 , when support for Microsoft SQL Server 2000 ceased. 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 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. 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 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. 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. 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 INSTALLATION AND UPGRADE GUIDE 3 UPGRADES Components to Upgrade 29 COMPONENTS TO UPGRADE The following Environment Manager components must be upgraded: Server Server Database Agents Configurations 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. For details of how to set up and upgrade replication servers, see Personalization Database Replication on page 59. 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 further information refer to Enterprise Mode Upgrade on page 33.

38 INSTALLATION AND UPGRADE GUIDE 3 UPGRADES Components to Upgrade 30 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. 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. If upgrading from a pre 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 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. For further information, refer to Agents and Configurations Upgrade to 8 FR4 from a pre-8.1 Version on page 35. After an agent upgrade a reboot is required.

39 INSTALLATION AND UPGRADE GUIDE 3 UPGRADES Components to Upgrade 31 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. 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. 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.

40 INSTALLATION AND UPGRADE GUIDE 3 UPGRADES Upgrade Order 32 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 UPGRADE ORDER It is important that when upgrading to Environment Manager 8.2 from a pre-8.1 version you upgrade AppSense Management Center first. For further information on upgrading AppSense Management Center, refer to the AppSense Management Center Installation and Upgrade Guide. 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. 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 ( ) 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 ( ) 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 INSTALLATION AND UPGRADE GUIDE 3 UPGRADES Enterprise Mode Upgrade 33 ENTERPRISE MODE UPGRADE 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 INSTALLATION AND UPGRADE GUIDE 3 UPGRADES Enterprise Mode Upgrade 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 ( 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 INSTALLATION AND UPGRADE GUIDE 3 UPGRADES Agents and Configurations Upgrade to 8 FR4 from a pre-8.1 Version 35 Testing Server Upgrades On completion of the Personalization Server upgrade, test to ensure the server is functioning by visiting the PersonalizationServer website at: or 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. If you are using a load balancer monitor and the server is set to Windows Authentication. See Load Balancing Status Request on page 25. AGENTS AND CONFIGURATIONS UPGRADE TO 8 FR4 FROM A PRE-8.1 VERSION 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. 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. Follow this procedure to upgrade both agents and configurations: 1. Upgrade AppSense Management Center and the CCA on all endpoints. Configuration Installation Schedule functionality was introduced in versions of the Management Center and 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 , regardless of how the server is configured. For further information about Configuration Installation Schedule functionality, see the AppSense Management Center Product Guide. 2. Open the configuration in the Environment Manager console and Save to Management Center as an 8.2 configuration.

44 INSTALLATION AND UPGRADE GUIDE 3 UPGRADES Standalone Mode Upgrade Assign the upgraded configuration and 8.2 agent to Deployment Groups. The configurations and agents will be deployed according to the schedule. 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. STANDALONE MODE UPGRADE 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.

45 INSTALLATION AND UPGRADE GUIDE 3 UPGRADES Desktop Settings on Upgrade 37 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. Policy configurations cannot be upgraded in the Personalization only console. They can only be upgraded if opened in the policy or combined console. DESKTOP SETTINGS ON UPGRADE 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 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 build) logs in, it receives all the original settings keys (including the ones replaced by session data) and all the data. As with post clients, the desktop settings roam to the new client but any changes to the keys which were replaced by session data will not roam. 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 INSTALLATION AND UPGRADE GUIDE 3 UPGRADES Certificates on Upgrade 38 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. 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. CERTIFICATES ON UPGRADE 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.

47 4 Server Configuration In this Section: 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 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 , when support for Microsoft SQL Server 2000 ceased.

48 INSTALLATION AND UPGRADE GUIDE 4 SERVER CONFIGURATION Server Configuration for Environment Manager 40 SERVER CONFIGURATION FOR ENVIRONMENT MANAGER This section provides details of the server configuration process for AppSense Environment Manager. If Environment Manager has been installed in Enterprise mode there are two servers to configure using their respective Server Configuration Utilities (SCU): Management Server Personalization Server The Management and Personalization servers do not need to be installed on the same machine and do not need to use the same instance of SQL server. AppSense database products always require both a Configuration account and a Service account. The Configuration account and Service account must be two separate accounts. For details of how to configure the Management Server and use the Management Server Configuration Utility, see the Management Center Installation and Upgrade Guide.

49 INSTALLATION AND UPGRADE GUIDE 4 SERVER CONFIGURATION Personalization Server Configuration Utility Wizard 41 PERSONALIZATION SERVER CONFIGURATION UTILITY WIZARD The Personalization SCU is used to install and maintain the web site configuration for the Personalization Server. The SCU first runs as a wizard in which you specify the settings for the Personalization Server. After this, the SCU can be launched from the Start menu as required, allowing the existing settings to be modified and any problems or variances corrected. During the server configuration process, you are prompted for authentication including the following types: SQL authentication = SQL Authenticated Account Windows authentication = The current windows account Impersonated authentication = A custom windows account Server Configuration Wizard Steps The wizard guides you through the following steps: 1. Prerequisites The prerequisite check provides a list of the required components and indicates whether each component is installed. Any components which are not installed are indicated and the View button allows you to display and fix the list of variances by installing components which are not installed. Some missing components can be fixed by the installer but other components, such as IIS (Internet Information Services), must be installed manually. You can proceed or fix the relevant issues and return to the wizard later. If you proceed without resolving outstanding issues, a message notifies you that the product might not operate correctly.

50 INSTALLATION AND UPGRADE GUIDE 4 SERVER CONFIGURATION Personalization Server Configuration Utility Wizard Web site - Select a valid Personalization Server web site. The utility lists all existing websites. The selected website controls the port used to access the server. The default website is sufficient unless you have a specially designated website which already exists. If the Personalization Server is hosted on a site with a port other than 80, then initial registration of the server is incorrect and must be fixed manually in the console. The default website is usually sufficient unless you have a specially designated website which already exists.

51 INSTALLATION AND UPGRADE GUIDE 4 SERVER CONFIGURATION Personalization Server Configuration Utility Wizard Configuration Credentials and Database Selection Enter the credentials for the Configuration account. The Configuration account must be a separate account to the Service account. The privileges required for the Configuration account vary according to what you want the SCU to do. For further information on accounts and privileges, refer to the AppSense Environment Manager Personalization Product Guide > Personalization Server Configuration Utility Appendix. Select the Authentication Type: Windows Authentication Pass-through authentication where the currently logged on domain user credentials are automatically provided to access the database. Impersonated Windows Authentication A username and password must be supplied and then this account is impersonated to provide access to the database for the duration of the SCU session. SQL Authentication An SQL Authentication account can be specified to provide access to the database. Accounts, including both username and password are created within the SQL Server itself rather than making use of existing Windows domain accounts. Enter the Username and Password for the Configuration account.

52 INSTALLATION AND UPGRADE GUIDE 4 SERVER CONFIGURATION Personalization Server Configuration Utility Wizard 44 Specify the SQL Server and Instance to use, in the format <servername>\<instance>,<port> and enter or select an existing Database. Instance and Port are optional elements. 4. Database Service Credentials The Service account must be a member of the ProfileServerService role in the Personalization database. Enter the credentials for the Service account. The Web service uses these credentials for the database connection on an ongoing basis after the SCU has exited. Select the Authentication Type: Impersonated Windows Authentication A Windows username and password must be supplied and then this account is impersonated each time access to the database is required. SQL Authentication An SQL Authentication account can be specified to provide access to the database. Accounts, including both username and password are created within the SQL Server itself rather than making use of existing Windows domain accounts. If the Service account does not already exist in the SQL Server and the Configuration account has securityadmin server privileges, a new account is created.

53 INSTALLATION AND UPGRADE GUIDE 4 SERVER CONFIGURATION Configure a Server Using Low SQL Privileges Summary A summary of the settings displays with details of pending actions, such as create a database with a specific name or update an existing database. Click Accept to carry out the actions. The Personalization Server Configuration Utility can be run at any time, refer to the AppSense Environment Manager Personalization Product Guide for details. CONFIGURE A SERVER USING LOW SQL PRIVILEGES AppSense Personalization Server uses an SQL Server database to store personalization data. The installation procedure requires sysadmin access to the SQL Server instance in order to create and initialize the personalization database. The SCU requires the Configuration account to have sysadmin access otherwise an Insufficient Privileges warning is generated. If you upgrading an existing database db_owner rights are required. 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. SET UP THE DATABASE WITH LOW PRIVILEGES 1. Install Environment Manager as detailed in the AppSense Environment Manager Installation and Upgrade Guide. 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 If you installed to a location other than the default, amended the path accordingly. 3. Create two SQL Server logins, one for the configurer account and one for the service account. 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 ProfileServerService role. 4. Edit the CreateDatabase.sql script with the name of the database and the two logins, as shown in bold below: sysname = 'Personalization' sysname = 'Domain\Configurer' sysname

54 INSTALLATION AND UPGRADE GUIDE 4 SERVER CONFIGURATION Configuring Secure Communications 46 = '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. CONFIGURING SECURE COMMUNICATIONS You can optionally configure the Personalization Server web site to use Secure Socket Layers (SSL) to provide encrypted communications using Active Directory. For further information on configuring secure communications, refer to the AppSense Environment Manager Personalization Product Guide.

55 5 Configuration In this Section: Environment Manager Architecture on page 48 Setup Tasks on page 52

56 INSTALLATION AND UPGRADE GUIDE 5 CONFIGURATION Environment Manager Architecture 48 ENVIRONMENT MANAGER ARCHITECTURE AppSense Environment Manager consists of the following components: Console Configurations Agent Console The Environment Manager Console launches from the start menu: Start > Programs > AppSense > Environment Manager.

57 INSTALLATION AND UPGRADE GUIDE 5 CONFIGURATION Environment Manager Architecture 49 Application Menu The Application Menu provides options for managing configurations including create new, open existing, save, import and export configurations and print. The Preferences option allows you to modify the Console schemes and to set basic behavior settings such as, Show splash screen. Table 5.1 Option New Open Save Save As Description Creates a new default configuration which is locked for editing. Opens an existing configuration from one of the following locations: Live configuration on this computer Configuration from the Management Center Configuration file from disk: AppSense Environment Manager Package Files format (aemp). Note A live configuration is located on a computer which has Environment Manager Agent installed and running. Saves the configuration in one of the following states: Save and continue editing - Saves the configuration and keeps it locked and open for editing, you will not be able to deploy the configuration while it is locked. Save and unlock - Saves the configuration and unlocks it ready for deployment. The current configuration closes and a new default configuration opens. Unlock without saving - Unlocks the configuration without saving changes. The current configuration closes and a new default configuration opens. Note These save options are Management Center specific. Saves the configuration with a new name to one of the following locations: Live configuration on this computer - Saves the current configuration as the live configuration on this computer. Configuration in the Management Center - Creates this configuration in the package store on the selected Management Center. Configuration file on disk - Saves the current configuration as a file on a local or network drive. AppSense Environment Manager Package Files format (aemp). Note A live configuration is located on a computer which has Environment Manager Agent installed and running. Warning If using Microsoft Vista or Windows Server 2008 operating systems with UAC enabled, you must ensure that you open the Console with Administrator privileges. Import & Export Import configuration from MSI - Imports a configuration from an existing MSI package, for example, legacy configurations which have been exported and saved from legacy Consoles. Export Configuration as MSI - Exports the current configuration as a MSI package. Exit Closes the Console. You are prompted to save any changes you have made to the current configuration.

58 INSTALLATION AND UPGRADE GUIDE 5 CONFIGURATION Environment Manager Architecture 50 Quick Access Toolbar The Quick Access Toolbar provides easily accessible options for managing configurations and using the Environment Manager console. Option Description Save Saves changes to the configuration. The configuration will remain locked if opened from the AppSense Management Center. Save and unlock this configuration Saves the current configuration in the Management Center and unlocks to allow other users to edit the configuration. Undo Clears the action history. Up to 20 previous actions are listed. Select the point at which you want to clear the actions. The action selected and all preceding actions are undone. Redo Re-applies the cleared action history. Up to 20 cleared actions are listed. Select the point at which you want to redo the actions. The action selected and all preceding actions are redone. Back Navigates back through the views visited within the current session. Forward Navigate forward through the views visited within the current session. Ribbon Pages Ribbon Pages include buttons for performing common actions arranged in ribbon groups according to the area of the Console to which the actions relate. For example, the Home ribbon page includes all common tasks, such as Cut, Copy and Paste, and Help. Split ribbon buttons contain multiple options and are indicated by an arrow just below the button. Click the arrow to display and select the list of options, or simply click the button for the default action. Double-click a ribbon page tab to show and hide the ribbon pages. Help The Environment Manager help can be launched in three ways: Click the help button from the Home > Help & Support ribbon group. Click the help button in the top right-hand corner of the console. Press F1. The system displays help in context with the area of the console which you are using.

59 INSTALLATION AND UPGRADE GUIDE 5 CONFIGURATION Environment Manager Architecture 51 Navigation Pane Work Area The Navigation Pane consists of the navigation tree and navigation buttons. The navigation tree is the area for managing nodes of the configuration. The navigation buttons allow you to view the different areas of the Console, i.e. the Policy Configuration and User Personalization. The Work Area is the main area for managing the settings of the configuration and product. The contents of the work area are in context to the node selected in the navigation tree and the selected navigation buttons. Additional Console Features Shortcut Menu - Right-click shortcuts are available in the navigation tree and areas of the console. The recommended screen resolution for the console is 1024 x 768 pixels. Configurations A configuration is a collection of control settings which contain functionality and settings for management of your system. The configuration is made up of two main nodes, trigger nodes and sub nodes. Configuration files can be saved from the Console and exported/imported to other computers which have the AppSense User Virtualization Service running. You can use the Find and Replace facility to help manage your configurations, for example, if you need to change the name of a server located within your configuration or the IP address of a machine. Agent The Environment Manager agent is software that runs as a Windows service to carry out tasks on a computer, as specified by the configuration deployed to that computer.

60 INSTALLATION AND UPGRADE GUIDE 5 CONFIGURATION Setup Tasks 52 SETUP TASKS Once all Environment Manager components have been installed, configure and set up Environment Manager using the following steps. Step 1 Configure Computer Startup Nodes Step 2 Step 3 Step 4 Step 5 Step 6 Configure User Logon Nodes Enable User Personalization Connect the console to the Personalization Database Configure User Personalization Settings Apply the configuration to the Agent For further details on configuring Environment Manager, refer to the Environment Manager Personalization Product Guide and the Environment Manager Policy Product Guide. S TEP 1 C ONFIGURE COMPUTER STARTUP NODES Create relevant nodes under Computer > Startup to support actions and conditions for items that need to be applied when a computer starts up. This could include actions such as setting environment variables for the computer base don specific conditions such as operating system type or site membership. S TEP 2 C ONFIGURE USER LOGON NODES Create relevant nodes under User > Logon to support actions and conditions for items that need to be applied when a user logs on. This could include actions such as redirecting folders, configuring desktop settings via the registry or applying group policy settings via ADM & ADMX actions. S TEP 3 E NABLE USER PERSONALIZATION Enable User Personalization in the Policy, Personalization and Combined consoles console by listing Personalization Servers to communicate with. This ensures that when a user logs on to a managed endpoint, they receive the latest configuration from the Personalization database. For details of how to enable personalization and how to configure a list of Personalization servers, in each of the consoles, see the Configuring Personalization Servers chapter in the Environment Manager Personalization Product Guide. S TEP 4 C ONNECT THE CONSOLE TO THE PERSONALIZATION DATABASE Select the User Personalization navigation button and select Connect to make a connection to the Personalization database. This allows the administrator to configure User Personalization settings for the environment.

61 INSTALLATION AND UPGRADE GUIDE 5 CONFIGURATION Setup Tasks 53 S TEP 5 C ONFIGURE USER PERSONALIZATION SETTINGS Create Personalization Groups, assign membership rules and choose which application and operating system content will be managed by Environment Manager. Configure granular control of the environment including Desktop Settings, User Certificates, Session Data and Offline Mode. S TEP 6 A PPLY THE CONFIGURATION TO THE AGENT Once you have created the configuration apply it as the live configuration on your computer. Select Save As > Live Configuration from the application button. The configuration can also be saved in the Management Center or as an AEMP file on a local network drive.

62 6 Environment Manager Browser Interface In this Section: About the Browser Interface on page 55 Installation on page 55 Configuration on page 56

63 INSTALLATION AND UPGRADE GUIDE 6 ENVIRONMENT MANAGER BROWSER INTERFACE About the Browser Interface 55 ABOUT THE BROWSER INTERFACE The AppSense Environment Manager Browser Interface 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 Environment Manager console. This removes the need to have full configuration access to the database to perform these tasks. For more information and for full details on how to use this product, see the Environment Manager Browser Interface online help which is accessed using the Help link in the interface. The installation of the Environment Manager Browser Interface is a two step process: The installer creates any folders and copies the required files to the correct locations The EM Browser Interface Configuration Utility configures the interface INSTALLATION The Browser Interface has its own installer which installs the Browser Interface and Service. The installer configures IIS, copies the required files and provides a platform to be configured by the Browser Interface Configuration Utility. The Browser Interface installer is included with the Environment Manager installation media in 32 and 64-bit versions: EMBrowserInterface32.msi EMBrowserInterface64.msi The Browser Interface requires an existing SQL Server Personalization Database. It can be installed on any server which is the same specification as the Personalization Server but it does not necessary have to be installed on a Personalization Server. Earlier versions of the Personalization Server will not work with the Browser Interface as the background service has been updated for 8.2 to handle the Browser Interface. However, 8.1 clients can be used with the Browser Interface as they can communicate with the 8.2 database. The Browser Interface requires Microsoft.NET Framework 4.0 to be installed. As the Browser Interface utilizes the background service which is part of the Personalization Server installation, all other prerequisites are the same as those detailed in the AppSense Environment Manager Installation and Upgrade guide.

64 INSTALLATION AND UPGRADE GUIDE 6 ENVIRONMENT MANAGER BROWSER INTERFACE Configuration 56 INSTALLING THE ENVIRONMENT MANAGER BROWSER INTERFACE 1. Locate the EMBrowserInterface32.msi or EMBrowserInterface64.msi. 2. Double-click the MSI for your operating system. The Welcome dialog is displayed. 3. Click Next. 4. Enter the location for the install. The Browser Interface should be installed at the same location as the Personalization Server. The default location is C:\Program Files\AppSense\Environment Manager\Browser Interface. 5. Click Next. 6. Click Install. The Browser Interface is installed at the selected location. CONFIGURATION The Browser Interface has its own configuration utility which is installed from the MSI during the Installation process described above. If the default location is used, the utility is accessed from: Start > All Programs > AppSense > Environment Manager > AppSense EM Browser Interface Configuration. The EM Browser Interface Configuration Utility opens an initial screen which enables you to run a wizard to guide you through the configuration. For subsequent configuration and troubleshooting, each component can be accessed from the tree in the left-hand navigation pane.