Release Notes for Update Pack PowerFuse 2010 SR2 revision 5 (9.0.2.5). ====================================================================== This update pack can be installed on top of RES PowerFuse version 2010 SR2 revision 9.0.2.0. Replaced executables: pfwsmgr.exe pwrtech.exe pwrgrid.exe res.exe islogoff.exe pwrcache.exe ------------------------------------------------------------ Changes in revision 9.0.2.1: Enhancements: - The following 2 options have been added to the Lockdown and Behaviour of "Start Menu and taskbar": 1) Hide "Lock desktop" icon in system tray 2) Hide "Show tasklist" icon in system tray Fixes: - In some desktop environments (especially with virtual desktops) remote assistance did not always work properly. The connection was not established. - In a Xen Desktop environment, subscribed tasks were not always properly shown after a user had 'roamed' (disconect and reconnect) to another desktop. - Sometimes a published aplication uses a download manager (such as DFSVC.EXE) to download and start an application. Because the DFSVC.EXE process doesn't stop, the published powerfuse application will not stop even if the user ends the downloaded application. This has been fixed, but to work properly the following registry value must also be created: Key: HKEY_LOCAL_MACHINE\Software\RES\PowerFuse Value: (string) ExcludeProcesses Data: dfsvc.exe| e.g. if the downloaded application is process aaa.exe, the data of the registry key must be "dfsvc.exe|aaa.exe" - Starting a Thinapp application on a XenDesktop environment might result in a runtime error generated by picasvc.exe. This behaviour can be blocked by setting the following registry. Key: HKEY_LOCAL_MACHINE\Software\RES\PowerFuse Value (REG_SZ) : BlockPicaSvcFix Data: yes - Under some circumstances folder redirection was properly installed, but not recognized at the time PowerFuse is building up the desktop, start menu and so on. As a workaround, it is now possible to force PowerFuse to resolve the special folders from the registry by creating the following registry value: Key: HKEY_LOCAL_MACHINE (or HKEY_CURRENT_USER) \Software\RES\PowerFuse Value: (STRING value) SpecialFoldersFromRegistry Data: Yes - In an environment with several nested PowerZones (Locations and Devices), the resulting set of PowerZones in a session were sometimes not calculated correctly. As a result the session would have the wrong PowerZones assigned. - In an environment with many applications, the time needed to perform 'Composing File Type Associations' during startup of a RES PowerFuse session has been reduced. - In rare circumstances the following error can be seen in the PowerFuse errror log: Process: res.exe Procedure: frmMain.tmrStart_Timer Error: 20105 Discription: IPDeamon is already listening Process - Switching an application to OU Membership in the Management Console can cause the server/session to hang. This issue occurs only when using all of the following 1) A VMWare Infrastructure Client 2) A Windows 2008 R2 Server. 3) The SVGA driver delivered with VMWare Tools. There are many articles on the internet describing similar problems with this combination. (e.g. http://teamedl.com/165/windows-2008-r2-and-windows-7-freeze-on-vmware-vsphere-4/) In code we have provided a workaround to prevent this hang to happen. ------------------------------------------------------------ Changes in revision 9.0.2.2: Fixes: - Logging off from a RES PowerFuse session might result in Event ID 1517 "Windows saved user Domain\User registry while an application or service was still using the registry during log off". - From Workspace Analysis one can extract the User Settings. Unfortunately they are not allways extracted to the specified location. - The following error can appear in the Error Log: Process : pfwsmgr.exe Procedure : modShellLink.SetLinkAppUserModelID at line 30 Error # : 53 Description: File not found: resfunc.dll - The configured "number of user event logs to keep" in workspace analysis is not allways maintained correctly. - Under cirtain circumstances the system does not logoff before a second logoff attempt is made. This issue has been seen only if all of the following conditions apply: * The RES PowerFuse shell is used. * The session runs on a Windows 2008 (R2) Terminal server with Citrix. * A Folder Sync task is active during logoff. ------------------------------------------------------------ Changes in revision 9.0.2.3: Fixes: - The setting "Do not supppress messages from ICA Seamless Host Agent" does not work. - When running a console outside a RES PowerFuse session with a madatory profile the following issues arise: * User Settings Templates are not available * Desktop sampler files cannot be read in the Workspace Designer - The following errror can appear in the error log when using User Settings with Track Any...... Prog: pwrgrid.exe Procedure: SharedUserPreferences.fysnProcessFileAndFoldersFromTransaction Error: (70) Permission denied ------------------------------------------------------------ Changes in revision 9.0.2.4: Enhancement: - In Locations and Devices, the PowerZone rule 'Hardware Requirement -> Minimum Screen Resolution' has been extended with the following resolutions: 1280x800 1366x768 1440x900 1600x900 1680x1050 Fixes: - Enumerating users sessions in the console was slow when there were many (1000+) active user sessions. - When importing a building block containing an application which had to be published, it was possible that all other applications within the same menu were also (re)published. - Microsoft Excel might crash in the PowerFuse Shell when closing a 'Print Preview' window. - Composed environment variable for thinapp or citrix streaming applicatiosn were not properly removed. Under some circumstances this could cause problems when starting the next thinapp or citrix streaming application. - When the home drive is set by a drive mapping or subst during startup of the workspace manager, the environment variable LCID might not be set correctly. - The maximum instances of an application is not always maintained correctly. - Winword does not start properly when using the "Reference Manager" plugin. This can be solved by setting the following registry value: Key: HKEY_LOCAL_MACHINE\Software\RES\PowerFuse Value (string): KeepTmpDDEMacros Data: yes - The fix for extracting user settings in 9.0.2.2 has been improved. - Asynchronously connected printers are not always available in a subscribed session. - On a Windows 7 or Windows Vista client, when a user issued a 'restart computer, this would always result in a shutdown if there was any folder sync task specified, regardless if the user had access to that task (e.g. based on access control or a powerzone). - Sometimes users receive an error: SharedUserPreferences.ProcessRegGuardMessage at line 1000, Permission Denied. This error is now suppressed for the end-user; an improved solution for this issue will be released in the next service release. - The message box "Please specify Targeted Items" will not longer appear if your Zero Profile mode is "Track specified settings ......" It will only appear if you have checked "Capture targeted items once, than track further changes" in addition. ------------------------------------------------------------ Changes in revision 9.0.2.5: Fixes: - When the application outlook.exe is configured with maximum instances = 1 the following issues can arise * It is not possible to open an .msg file via 'double click' while outlook is already running. * Unmanaged attachments opened by outlook prevent outlook to re-open after a close. - Several applications were set up to allow the user to restore previous user settings. These applications had correctly saved user settings from previous sessions. However, in Workspace Preferences not all applications were show in the 'Restore' list, so it was not possible to restore user settings for those applications. - The application 'CaseWare' does not run properly when using the RES PowerFuse Shell. - The application 'AutoCAD' version 2010 flickers unnecessary in the RES PowerFuse Shell. - When an Administrator presses "View Stored User Settings" the management console has to find the home drive. This will be done according to the following steps: 1) Can the home drive be found in Active Directory. If so, take that. 2) Can the home drive be found in drive mappings and substitutes. If so, that that. 3) If still not found take the current home drive and find a similar one for the actual user.