You are on page 1of 10

E N V I R O N M E N T M A N AG E R Release Notes (version 8.0.890.

0)
AppSense Environment Manager (version 8.0.890.0) release notes include:


New Features

New Features Components in this Release Supported Operating Systems and Technologies Required Utilities and Components Bugs Fixed Known Issues

Components in this Release


Component Console Agent Documentation

Support for Microsoft App-V 4.6

Version 8.0.890.0 8.0.890.0 8.0.890.0 8.0.719.0

Personalization Server

1999-2010 AppSense Ltd. All Rights Reserved.

1/ 10

ENVIRONMENT MANAGER

Supported Operating Systems and Technologies


Component Personalization Server

Supported Operating Systems and Technologies

RELEASE NOTES (VERSION 8.0.890.0)

Supported Operating Systems Microsoft Windows Server 2008 R2 (Standard and Enterprise) Microsoft Windows Server 2008 (Standard and Enterprise) Optional: Service Packs Microsoft Windows Server 2003 R2 (Standard and Enterprise) Optional: Service Packs Microsoft Windows Server 2003 (Standard and Enterprise) Optional: Service Packs

Environment Manager Console

Microsoft Windows Server 2008 R2 (Standard and Enterprise) Microsoft Windows Server 2008 (Standard and Enterprise) Optional: Service Packs Microsoft Windows Server 2003 R2 (Standard and Enterprise) Optional: Service Packs Microsoft Windows Server 2003 (Standard and Enterprise) Optional: Service Packs Microsoft Windows 7 (Professional, Ultimate and Enterprise) Microsoft Windows Vista (Business, Ultimate and Enterprise) Optional: Service Packs Microsoft Windows XP Professional Optional: Service Packs

Environment Manager Agent

Microsoft Windows Server 2008 R2 (Standard and Enterprise) Optional: Service Packs Microsoft Windows Server 2008 (Standard and Enterprise) Optional: Service Packs Microsoft Windows Server 2003 R2 (Standard and Enterprise) Optional: Service Packs Microsoft Windows Server 2003 (Standard and Enterprise) Optional: Service Packs Microsoft Windows 7 (Professional, Ultimate and Enterprise) Microsoft Windows Vista (Business, Ultimate and Enterprise) Optional: Service Packs Microsoft Windows XP Professional Optional: Service Packs

1999-2010 AppSense Ltd. All Rights Reserved.

2/ 10

ENVIRONMENT MANAGER

Required Utilities and Components

RELEASE NOTES (VERSION 8.0.890.0)

Technologies

Citrix XenApp (Presentation Server) 3.0 up to 5.0 Citrix XenApp Streaming Client 5.1 and 5.2 Citrix XenDesktop 2.0 and higher. Microsoft App-V 4.2 up to 4.6 Symantec Workspace Virtualization 6.1. Symantec Software Virtualization Solution 2.1. VMware View 3.0 and 4.0.

Required Utilities and Components


Component Database

Required Utilities and Components Microsoft SQL Server 2000 all editions Microsoft SQL Server 2005 all editions Microsoft SQL Server 2008 all editions

Personalization Server

Microsoft Windows Installer 31 minimum requirement (included in Microsoft Windows Server 2003 Service Pack 1) Microsoft NET Framework 30 Internet Information Services (IIS) installed and ready Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package Microsoft ASPNET 20 Microsoft Core XML Services (MSXML) 60

Environment Manager Console

Microsoft Windows Installer 31 minimum requirement (included in Microsoft Windows Server 2003 Service Pack 1) Microsoft NET Framework 30 Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package

Environment Manager Agent

Microsoft Windows Installer 31 minimum requirement (included in Microsoft Windows Server 2003 Service Pack 1) Microsoft Core XML Services (MSXML) 60 Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package

1999-2010 AppSense Ltd. All Rights Reserved.

3/ 10

ENVIRONMENT MANAGER

RELEASE NOTES (VERSION 8.0.890.0) Bugs Fixed

Bugs Fixed

AppSense Environment Manager Agent

Actions

Child Node Actions are executing before Parent Node Custom Actions complete.

Conditions

ICA Client connection protocol condition applying on console.

General

Settings not applying on Japanese MUI. EMAgentAssist.exe crash on logoff.

Personalization

When a global or application specific registry exclusion is defined in the Personalization Console, RIP keys are still captured under the excluded key. EMAgentAssist crashing when posting data to personalization Server. Incorrect calling convention in PVCLoader dll.

Refresh

When the window metrics size is set to 120 DPI a conversion error occurs, resulting in icons becoming shrunk. When connecting via RDP or ICA the default language is not being set to that of the connecting client.

AppSense Environment Manager Personalization Server

Known Issues

General

Personalization failing to save between 32-bit and 64-bit servers.

Child process checks in the Profile Management Module (PMM) do not take place when an unmanaged process is discovered via the 'Discover All Processes mechanism. This can result in unmanaged processes, spawned from a managed parent process, not taken into consideration for personalization. Attempting to convert a discovered application from the by application report can cause the Personalization Analysis dialog to crash. A workaround is to convert the discovered application from within the by user report. Windows Vista includes transacted registry access, similar to SQL transactions, with the ability to rollback changes. This method is not currently supported by Environment Manager User Personalization.

1999-2010 AppSense Ltd. All Rights Reserved.

4/ 10

ENVIRONMENT MANAGER

RELEASE NOTES (VERSION 8.0.890.0) Known Issues

When Environment Manager is used with VMware View 4.x, the environment variables that VMware provides to give client side details such as IP address and device name are not available during logon but appear at some arbitrary time later. This is observed with both PCoIP and RDP protocols. When a large number of reusable nodes and reusable condition nodes are created in an Environment Manager configuration, a thread is added to the thread pools for each referenced node to prevent deadlock. Currently each thread will reserve 1MB of virtual memory and commit 4kb of memory. This leads to situations where virtual memory may become exhausted, if for example there are 2000 reusable nodes in the configuration. A new algorithm has been created in the 8.0.884.0 build to calculate the thread usage required for the given configuration, and allow the maximum number of action and node threads created to be controlled.

It is enabled by adding the following registry value for the endpoint: Key : HKLM\Software\AppSense Technologies\Environment Manager Name: ThreadCountOverride Type: REG_DWORD Data: <Non-zero value to enable, zero to disable>

This can also be set per user, by using the following key: Key : HKCU\Software\AppSense Technologies\Environment Manager Action thread limits can be set with the following value: Key : HKLM\Software\AppSense Technologies\Environment Manager Name: ActionThreadLimit Type: REG_DWORD Data: <Thread size>

Node thread limits can be set with the following value: Key : HKLM\Software\AppSense Technologies\Environment Manager Name: NodeThreadLimit Type: REG_DWORD Data: <Thread size>

These keys also have HKCU equivalents.

By default, Windows 7 jump lists are not automatically controlled when using Environment Manager Personalization. However, Jump List personalization can be captured by adding the following entry to the Folder Include list for Personalization Applications in the Environment Manager Console: APPDATA%\Microsoft\Windows\Recent\AutomaticDestinations

In order to personalize Adobe Reader dictionary settings, the administrator must add a folder inclusion for '%UserProfile%\AppData\LocalLow' to the Adobe Reader application in the Environment Manager Console. Theme refresh fails on Windows 7 when UAC is enabled when switching between the Windows 7 Aero theme and High-Contrast. Any other theme as the start theme works without issue.

1999-2010 AppSense Ltd. All Rights Reserved.

5/ 10

ENVIRONMENT MANAGER

RELEASE NOTES (VERSION 8.0.890.0) Known Issues

Attempting to self heal the 64-bit version of the Internet Explorer 8 process when UAC is enabled results in multiple instances being spawned when the application is closed. Disabling the Environment Manager Agent is the only way of alleviating this. Self Healing of the PVCLoader entry in the App_Init key on a 64-bit operating system only checks the native path (32-bit or 64-bit). The WOW hive is never self healed. A workaround is to also self-heal the WOW hive independently. It has been observed that Citrix Desktop Toolbar can sometimes consume 100% CPU when User Personalization is enabled. In this particular case the issue was seen when resuming the computer from sleep. The problem occurs when the Citrix Desktop Toolbar enumerates registry keys. It deletes a registry value mid way through an enumeration, then queries the value expecting it to have gone. The process gets stuck in a loop deleting and querying hence the 100% CPU. If a user has a German character, for example, "" in their NETBIOS name or Computer name condition, the condition in question will fail. This is because there is no valid conversion of the lower-case character in German. In the extended ASCII table the translates to the number 162 but there is no upper-case equivalent (this is not like 'a' and 'A'). Any attempted conversions will therefore fail. Client OU Membership conditions can fail due to the include sub OUs flag not being correctly assigned on the managed device resulting in only a base level search rather than the sub tree. To work around this issue, change the Client OU Membership condition to include the exact sub OU argument. Specific conditions do not work dynamically in Active Directory when the Evaluate Once Per Session option is disabled. This applies to User OU Membership, Client Computer OU Membership, Computer OU Membership, Computer Group Membership and User Group (when not local group) conditions. Currently, some advanced Appearance settings held under the Control Panel\Desktop\WindowsMetrics key are not persisted / refreshed including Active title bar font size and Active title bar size. Internet Explorer can run very slowly when User Personalization is enabled and Spybot is installed. This issue can be resolved by excluding the following path from User Personalization: HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Zonemap and then deleting any existing IE virtual caches from the personalization database and managed end-point device.

1999-2010 AppSense Ltd. All Rights Reserved.

6/ 10

ENVIRONMENT MANAGER

RELEASE NOTES (VERSION 8.0.890.0) Known Issues

Mouse performance issues can be experienced when reconnecting to either Citrix MetaFrame, Citrix Presentation Server, Citrix XenApp or Citrix XenDesktop when connecting via RDP, ICA or other remote connection software that leverage the Terminal Services API. This is due to a session policy being set in the HKCU\Remote\x\ key where x is the relevant session number. When Environment Manager executes its refresh, it reads the real values of these from the profile itself not the overridden ones. The real values have never been set, so Mouse Shadowing is turned back on unexpectedly. A workaround is to set the mouse policies as part of the profile itself or use Environment Manager Registry actions to set them to the desired values. When upgrading a configuration where two nodes depend on a single node, it will fail to add the second dependent node correctly. This can result in unexpected behaviour. A workaround is to check the configuration manually, post upgrade, for dependencies that are not correct. Multiple dependencies can be implemented using reusable nodes. For example, make 'Node A' a reusable node and then make Depend1 and Depend2 sub nodes or actions of the reusable node 'Node A'. A console exception can be experienced when using an older version of the Environment Manager Console to view personalization settings edited in a newer version of the Personalization Analysis dialog. A workaround is to take the FS_Library_dll.dll file from the latest agent directory and copy it into the console directory for the earlier version of the console. Child processes associated with managed applications may fail to personalize when Discover All Processes is enabled. This is because the child process check does not take place when an unmanaged process is discovered, so the child processes are effectively ignored. A workaround is to add the child processes to the managed whitelist. Build 8.0.732.0 introduced functionality that attempts to ensure that all applications are closed down gracefully before Environment Manager EMAgentAssist.exe exits this has a default timeout of 5 seconds (as per Windows Vista). If any applications have not closed by this time, then their personalization settings will not be saved out. This works well for system tray applications, but is not 100% reliable for user applications, for example Microsoft Outlook.

It must be noted that this problem also exists for user applications, such as Microsoft Outlook, using native Windows without Environment Manager on the endpoint. We recommend all user applications are closed before logoff or shutdown. An engineering key in the registry is available to prolong this timeout period for applications that require a longer length of time to close. Please contact support@appsense.com for further information.

A disabled item in a reusable node causes a Stop If Fail action to be processed incorrectly. It is not possible to import an AppSense Policy Template exported from either the Computer or User node into a reusable node. User Personalization does not support folders that have been redirected to network locations.

1999-2010 AppSense Ltd. All Rights Reserved.

7/ 10

ENVIRONMENT MANAGER

RELEASE NOTES (VERSION 8.0.890.0) Known Issues

When personalizing Citrix XenApp Streaming Client applications, placing the Citrix XenApp RADECACHE on a secondary disk does not work. It must be on the system disk for streaming to work. A small performance hit is incurred on first launch after User Personalization data is upgraded in the database to the new Personalization protocol format, introduced in Environment Manager 8.0 Service Pack 2. The upgrade takes place on demand as applications are used. However, once the upgrade for all endpoints and data is complete, the performance of User Personalization is much higher than previous releases and scalability is dramatically improved. When upgrading the Environment Manager Console with an earlier version of the console still open on the same machine by another user, the installer displays a list of PIDs instead of application names in the Files in Use dialog. User Personalization will fail to retrieve a configuration file if the user does not have access to the system defined %TEMP% variable location, resulting in no User Personalization. If an action is configured to execute on the Computer Process Stopped trigger and the process starts before Environment Manager, the actions will not execute. This means that services set to start automatically will often not trigger events the first time the process stops. However, if the process is restarted once Environment Manager is running and then stops, the actions will trigger correctly. A process launched as another user by means of the Run As function is not terminated when logging off the original user. Please contact support@appsense.com for further information. On Windows XP and Server 2003 Operating Systems, the Environment Manager Console can, under certain circumstances, experience a system access violation crash due to an older version of the .Net Framework being utilized. Please contact support@appsense.com for further information. Environment Manager Agent can fail to load and process an associated configuration when the configuration contains an invalid character. Please contact support@appsense.com for further information. Self Healing a Citrix XenApp Streaming Client application causes multiple instances of the application to be launched. Please contact support@appsense.com for further information. When installing the Environment Manager agent on a German 64-bit Operating System the 32-bit agent installer incorrectly constructs the x86 path when setting the App_Init key in the Wow6432 registry. It currently has hard coded checks for 'program files' which it replaces with 'program files (x86)'. This does not work on German Operating systems as 'program files' is now 'programme' (and 'programme (x86)'). The workaround is to modify the AppInit_DLLs entry under the Wow6432Node,

From: C:\progra~1\appsense\enviro~1\agent\pvcloa~1.dll To: C:\progra~2\appsense\enviro~1\agent\pvcloa~1.dll

1999-2010 AppSense Ltd. All Rights Reserved.

8/ 10

ENVIRONMENT MANAGER

RELEASE NOTES (VERSION 8.0.890.0) Known Issues

When running AppSense Environment Manager on a German version of windows server 2003 64-bit there are two 64-bit agent assists rather than a 64-bit and a 32-bit. This occurs during installation:

Under the registry key HKLM\Software\Wow6432Node\AppSense Technologies\Environment Manager\ the AgentPath value is set to: C:\Programme\AppSense\Environment Manager\Agent The AgentPath value should be: C:\Programme (x86)\AppSense\Environment Manager\Agent\ Changing the value manually and restarting the service fixes the issue.

The Personalization Server Configuration utility intermittently detects Windows Communication Foundation (WCF) as a missing prerequisite. To resolve the issue, re-register ASP.NET on the Personalization Server by executing the following command:

On 32-bit platforms, execute:


%SystemRoot%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe i

On 64-bit platforms, execute:

Note The execution of this command causes all application pools on the local machine to be recycled, potentially affecting other web applications installed alongside the Personalization Server.

%SystemRoot%\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis.exe -i

Windows Vista and Server 2008 do not support the redirection of some special folders. For further details please see: http://technet.microsoft.com/enus/library/cc766489(WS.10).aspx) or contact support@appsense.com for further information. When managing Internet Explorer 7.0 or 8.0 on Windows Vista with UAC enabled, a personalization application group must be created that contains iexplore.exe, ieuser.exe and ielowutil.exe in order for synchronization to be successful at application start and stop. There is an issue with Citrix XenApp Streaming Client applications not being virtualized correctly when Citrix mfaphook.dll appears after AppSense pvcloader.dll in the AppInit_DLLs registry value. Ensure the pvcloader.dll entry appears after mfaphook.dll in this registry value. MSAA Lockdown in certain Office 2007 applications can be circumvented using keyboard shortcuts. Internet Explorer menu lockdown works intermittently for IE6. Lockdown of system tray icons fails. It is not currently possible to lockdown .Net applications, which use dynamic control IDs. Office Lockdown fails for MS Access 2003 on the toolbar window. Cannot lockdown Office 2007 menu items that expand in nature. The NETBIOS Name condition does not work on loopback session.

1999-2010 AppSense Ltd. All Rights Reserved.

9/ 10

ENVIRONMENT MANAGER

RELEASE NOTES (VERSION 8.0.890.0) Known Issues

Mozilla Firefox is supported by User Personalization but requires some initial configuration to operate. Please contact support@appsense.com for further information. Managed application executable names cannot have wildcards, but the console allows them to be set. If they are set, they do not match any executable names. For example, mspain*.exe fails and only mspaint.exe succeeds. User Personalization does not currently support VMware ThinApp. User Personalization does not currently support applications delivered by InstallFree. Managed applications can crash on application close if write access to the virtual cache root folder is prohibited (which is hidden by default). The Run node and condition list is slow to populate when large amounts of reusable nodes and conditions have been configured. Text shown in the Detected Clashes dialog can be truncated if resolution is set at specific level. The Personalization Server Configuration utility can fail if the user name which is entered is equal to user. If the Citrix XML Service is running on the Personalization Server, the Personalization Server website fails to run. Stop and disable the Citrix XML Service via services.msc to continue. If the database service account is the dbo, the user that created the database, it is not possible to add roles to that account, since roles cannot be added to the dbo, because dbo already includes all roles. Devices are still blocked from being accessed when using an upgraded configuration that contains removable storage control actions and the configuration is set to allow read-only or full access to all devices. Please contact support@appsense.com for further information.

1999-2010 AppSense Ltd. All Rights Reserved.

10/ 10