RES Workspace Manager 2012 SR3 Release Notes

Contents 1.

New Features

7

Citrix XenApp 6.5: Session Lingering and Session Prelaunch features now supported .......... 7 Locations and Devices: New zone rules based on connected wireless network and nearest access point ................................................................................... 8 Microsoft App-V Integration: Support for App-V 5.0 ................................................... 8 2.

Enhancements and Improvements

9

Actions: Improvement loading packages and programs for Microsoft ConfigMgr ................. 9 Advanced Settings: New option to bypass composer for administrator accounts ................ 9 Agents: Different values for "Poll for changes" intervals ........................................... 10 Agents: New default identification method for Agents in new environments .................. 10 Applications: Administrative note column added to Application List tab ....................... 10 Applications: Enable/Disable added to Quick Edit context menu................................. 11 Applications: Notification when using unsupported characters in menu/application title ... 11 Applications: Option Autolaunch at session start extended........................................ 11 Application User Settings: Default value for Capture mode changed to "After application has ended"........................................................................................ 11 Citrix XenApp: Improved check for a Citrix XenApp server's membership of Citrix Worker Groups ....................................................................................... 12 Citrix XenApp 6: Registry value to make Citrix XenApp server act as Session Host Only server12 Citrix XenApp Publishing: Interface enhancements for Instant Passthrough .................... 12 Console: Column widths customizable ................................................................. 13 Console: Improved performance for environments containing a large number of applications13 Console: Improved reloading of Location and Devices after editing or deleting a Zone ...... 13 Console: Improved startup time for environments containing a lot of applications ........... 13 Console: New icons for Zones and Zone Rules ........................................................ 13 Console: Registry value to resolve Client IP address via DNS ...................................... 14 Console: RES Workspace Manager now works around Microsoft's 15 second timeout during startup ....................................................................................... 14 CPU optimization: Prevent cpushld.exe from running if enabled ................................. 15 Datastore: Variable port for IBM DB2 now supported ............................................... 15 Directory Services: Startup time optimization when using Account SIDs for Processing Access Control ....................................................................................... 15 Drive and Port Mappings: New mapping for RES HyperDrive ....................................... 15 Drivers: New AppGuard, ImgGuard, NetGuard and RegGuard drivers implemented .......... 16 Folder Synchronization: Improvement when synchronizing unmanaged desktop items ....... 16 Folder Synchronization: Several improvements ...................................................... 16 Installation: RES Workspace Manager Agent-only installation ..................................... 17 Locations and Devices: Blast protocol added to Session type rule................................ 17 Lockdown and Behavior: New option to hide desktop icons during session start and refresh 17 Maintenance: Option to search for obsolete Citrix Worker Groups and remove them ........ 18 Microsoft App-V Integration: Improvement for applications pinned to taskbar ................ 18 Microsoft App-V Integration: Support for Microsoft System Center Configuration Manager 2012 SP1 ..................................................................................... 18 Microsoft Windows 8 and Windows Server 2012 compatibility..................................... 19 Network Security: New hidden rule to allow searchprotocolhost.exe ........................... 19 New option "Disable file system redirector on 64-bit systems" for External tasks ............. 19 Performance: Enhancement when determining if active users are within the scope of a security role ................................................................................ 19 Printers: Option to refresh printers on session refresh ............................................. 20 Relay Server: IPv6 now supported for Direct Access connections ................................. 20 ii

Relay Server: MySQL ...................................................................................... 20 Relay Server: Support for configuration through DHCP ............................................. 21 Removable Disks Security: Access Control based on Vendor ID/product ID of USB storage device now possible ....................................................................... 21 RES HyperDrive Integration: Extended RES HyperDrive Client settings .......................... 21 RES IT Store Integration: "Catalog" renamed to "Publication" ..................................... 22 RES VDX Integration: Improved communication with VDX Engine ................................. 22 RES Workspace Manager: Additional parameter for unattended installation ................... 22 RES Workspace Manager Agent: Copy from Clipboard/Import from File buttons on Configure Connection window ........................................................................ 22 Security: Local cache blocked by default ............................................................. 23 Support for Microsoft Office 2013 ...................................................................... 23 Usage Tracking Viewer: Datastore selected in Console now used ................................ 23 User Registry: Open ADM(X) file window changed ................................................... 23 User Settings: Add and Import buttons on Capturing tab combined .............................. 24 User Settings: Basic and Advanced view ............................................................... 24 User Settings: Improvement when adding new Template .......................................... 24 User Settings: New and updated templates ........................................................... 25 User Settings: New wizard to discover User Settings ................................................ 25 Workspace Composer: Detection if a computer comes out of a suspended state improved . 25 Workspace Composer: Microsoft Windows password expiry notification also shown in RES Workspace Manager Shell ................................................................. 26 Workspace Composer: New command line to save settings and User Settings and then restart system........................................................................................ 26 Workspace Composer: Notification message when application is still being installed ........ 26 Workspace Composer: Option to set latency threshold for retrieving context ................. 26 Workspace Composer: Performance improvement when determining Zones based on Chassis type........................................................................................... 26 Workspace Composer: Performance improvement when retrieving information from Active Directory ..................................................................................... 27 Workspace Composer: pwruser.ini setting to prevent unwanted messages when default printer changes ............................................................................. 27 Workspace Composer: Shortcuts manually added to Startup folder now also added to user's pwruser.ini file ............................................................................. 27 Workspace Preferences: Copy to Clipboard button on Diagnostics tab .......................... 27 3.

Fixes

28

Access Control: Location and Devices frame not resizing correctly in read-only mode ...... 28 Access Control: Resolving users with access based on "NOT User/Group" not working correctly ..................................................................................... 28 Agents: Changed identification method not always remembered ................................ 28 Agents: Duplicate Agents in Agent overview when changing identification and connection method at the same time ................................................................ 28 Agents: "Poll for changes" configuration for Workspace Containers not applied until a global change was saved .......................................................................... 29 Agents: Settings for last workspace exception displayed incorrectly in read-only mode ..... 29 Applications: "Bad data" error for data source based on Microsoft Dynamics NAV ODBC driver29 Applications: Environment variables not set for intercepted process ............................ 29 Applications: Linked SCCM actions not visible on Resulting Actions tab ......................... 29 Applications: Process Interception sometimes failed ............................................... 30 Applications: Read-only access Workspace Containers tab not completely read-only ........ 30 Applications: Renamed Workspace Containers not updated ....................................... 30 Applications: Shortcuts sometimes removed from the Start Menu ............................... 30 Applications: Sometimes launching not possible if SCCM linked action was used .............. 31 Applications: White icon if file type 'html' was added to Microsoft Internet Explorer ........ 31 Building Blocks: Different behavior when importing Building Blocks through menu or context menu ......................................................................................... 31

iii

Citrix XenApp: Continuous check for membership of Citrix Worker Groups if no membership existed ....................................................................................... 31 Citrix XenApp 5: Error in Microsoft Windows Event Log after RES Workspace Manager 2012 SR2 was installed ........................................................................... 32 Citrix XenApp 6.5: Errors retrieving Citrix Worker Groups from Citrix XenApp Session Host Only server .................................................................................. 32 Citrix XenApp Publishing: Error importing Building Blocks containing Server Groups ......... 32 Citrix XenApp Publishing: Error publishing applications in multiple folders .................... 33 Citrix XenApp Publishing: Folders not resolved when configured servers contained server group ......................................................................................... 33 Citrix XenApp Publishing: Import Wizard not publishing to Worker Group ...................... 33 Citrix XenApp Publishing: Publishing applications on Citrix XenApp Session Host Only server failed ......................................................................................... 34 Citrix XenApp Publishing: Unable to view certain files in published application .............. 34 Citrix XenApp 5 Publishing: Error publishing application with same name as existing application .................................................................................. 34 Citrix XenApp Streaming: Applications with setting Maximum instances = 1 not started up correctly in user sessions ................................................................. 35 Console: Error when using Microsoft SQL Server 2000 .............................................. 35 Console: Filtering on Workspace Container gave unexpected result ............................. 35 Console: Sorting order of Commands not correct .................................................... 35 Creating folders with path referring to parent "\.." not working properly ...................... 35 Desktop Background: JPG files not shown on Microsoft Windows Server 2003 ................. 35 Drive and Port Mappings: Environment Variables with $ADINFO() not working correctly..... 36 Dynamic Privileges: Drive mappings not always visible ............................................. 36 Dynamic Privileges: Not working correctly in combination with Microsoft's tool SubInACL .. 36 E-mail Settings: Additional mailboxes in Microsoft Outlook sometimes displayed with identifier instead of name................................................................ 36 Environment Variables: Second and third parameter of "$substring" cannot contain another "$substring" .................................................................................. 37 Error message: Sometimes error when server was restarted ...................................... 37 Execute Command: Actions configured with Run using Dynamic Privileges not always executed ..................................................................................... 37 Execute Command: Dynamic Privileges not working ................................................ 37 Execute Command: Executing an external task using a script sometimes not working ....... 37 Folder Synchronization: Not working correctly after upgrade to RES Workspace Manager 2012 SR2 ............................................................................................ 38 Instant Passthrough: Not working with Citrix Worker Groups ..................................... 38 Instant Reports: Incomplete Instant Reports ......................................................... 38 Licensing: License error when new users logged on to laptop for first time .................... 38 Licensing: Reminder for 45 days sometimes not counting down .................................. 39 Locations and Devices: Zone rules based on computer NetBIOS or FQDN name not working properly ...................................................................................... 39 Microsoft App-V: Audit Trail showed a lot of records for "AppvModelIds" for environments containing a large number of applications ............................................ 39 Microsoft App-V: Collection not always removed after executing action with Microsoft System Center Configuration Manager (SCCM) 2007 and 2012 ..................... 40 Microsoft App-V: Multiple Advertisements remained on Microsoft System Center Configuration Manager (SCCM) server after installation finished ................. 40 Network Security: Environment Variables used in Remote address not working correctly ... 40 Printers: Connecting printers could cause Console to hang ........................................ 41 Relay Server: Settings for RES HyperDrive and Microsoft App-V ModelIds not copied to cache41 Removable Disk Security: Unmanaged shares for removable devices (including shared printers) removed from user session ................................................... 41 RES VDX Integration: Concurrent VDX license claimed at every reconnect ..................... 41 RES VDX Integration: Drive Mapping disappeared from client after reconnect ................. 41 RES VDX Integration: Error "All pipe instances are busy" ........................................... 41 RES VDX Integration: Error "ORA-01465 Invalid hex number (INSERT INTO tblLicenses..." ... 42 RES VDX Integration: Local drive mappings did not always reappear after reconnect ........ 42 iv

RES VDX Integration: Local logoff message when online connection state and a specific application were configured ............................................................. 42 RES VDX Integration: Remote Drive mappings not created in local session ..................... 42 RES Workspace Manager Shell: RES VDX setting "Hide client taskbar at session start" not applied on local client .................................................................... 43 Usage Tracking: Sometimes error when creating Example data .................................. 43 Usage Tracking Overview: OU membership not always resolved correctly if OU name contained a slash (/) ...................................................................... 43 Usage Tracking Viewer: Error when using "DailyMaxUsersforApplication" ....................... 43 User Event Log: Error "Microsoft .NET framework version 4.0 or later is missing" ............. 44 User Event Log: Unexpected Microsoft ConfigMgr message ........................................ 44 User Home Directory: Actions defined for pwruser.ini sometimes not working ................ 44 User Home Directory: Compare or copy actions defined for pwruser.ini not working on new profiles if no home drive was defined .................................................. 44 User Home Directory: Global settings applied irrespective of workspace exception settings 45 User Registry: Duplicated "Run Once" registry setting not applied ............................... 45 User Registry: Items in registry file marked for deletion not imported correctly ............. 45 User Registry: "Run Once" setting not taken into account ......................................... 45 User Registry: Scrollbar disappears when resizing window ........................................ 45 User Sessions: Error in User Event Log when using a non-existing cache location ............. 45 User Settings: Central storage location with Full path containing RES Workspace Manager environment variable not properly resolved .......................................... 46 User Settings: Empty strings not captured correctly ................................................ 46 User Settings: Locally cached User Settings sometimes not synchronized ...................... 46 User Settings: Missing templates for desktop icons .................................................. 46 User Settings: Registry keys and values containing Environment Variables not always captured ..................................................................................... 47 User Settings: Sometimes \pwrmenu was not synchronized after system reboot .............. 47 User Settings: Sometimes incorrect error that restoring User Settings failed .................. 47 User Settings: Sometimes not loaded correctly ...................................................... 47 Workspace Composer: 64-bit icon of Microsoft Internet Explorer pinned to taskbar .......... 48 Workspace Composer: Active Setup not always executing .vbs scripts .......................... 48 Workspace Composer: Application focus changed after session reconnect ..................... 48 Workspace Composer: Certain unmanaged icons not stacked properly on taskbar ............ 48 Workspace Composer: Client IP address not always resolved correctly during logon ......... 48 Workspace Composer: Common Startup folder not applied for a user with a new profile ... 48 Workspace Composer: Communication with the WMSync process sometimes not possible .. 49 Workspace Composer: Custom icons not displayed correctly ...................................... 49 Workspace Composer: Default printer removed from pwruser.ini ................................ 49 Workspace Composer: Desktop icons aligned to the left after user workspace was refreshed twice in short period of time ............................................................ 49 Workspace Composer: Dismiss and notify functionality only available in English .............. 49 Workspace Composer: Drive mappings and Drive substitutes not always applied correctly when computer resumed after network change ...................................... 50 Workspace Composer: Drive substitute not shown correctly in Windows Explorer in offline session ....................................................................................... 50 Workspace Composer: Empty Recently Opened Programs list in Start Menu ................... 51 Workspace Composer: Empty Startup folder sometimes shown in Start Menu ................. 51 Workspace Composer: Environment Variables used in path of backup printer not resolved . 51 Workspace Composer: Error opening multiple Microsoft Outlook .msg files .................... 51 Workspace Composer: Force Logoff message shown in shutdownblocker ....................... 51 Workspace Composer: Google Chrome and Lotus Notes icons not stacked properly on taskbar51 Workspace Composer: Icon issues with Microsoft Internet Explorer 10 .......................... 52 Workspace Composer: Icons for managed shortcuts sometimes appeared twice on desktop 52 Workspace Composer: Icons reappeared on desktop after having been deleted............... 52 Workspace Composer: Inetres.adm policy not applied correctly ................................. 52 Workspace Composer: Installation of Microsoft Windows Automatic Updates with insufficient privileges could result in unmanaged session ......................................... 52

v

Workspace Composer: Items in Start Menu or pinned to taskbar sometimes in wrong language ..................................................................................... 52 Workspace Composer: Lock Desktop not working correctly ........................................ 53 Workspace Composer: Microsoft .Net errors in User Event Log ................................... 53 Workspace Composer: Microsoft Windows Active Setup did not work properly if "stubpath" contained white spaces ................................................................... 53 Workspace Composer: Out of memory error when loading User Settings or starting an application .................................................................................. 53 Workspace Composer: PowerShell and Server Manager icon incorrectly pinned to taskbar . 53 Workspace Composer: Prevent unnecessary notification messages about default printer change just after logon ................................................................... 54 Workspace Composer: pwrgate.exe sometimes consumed 100% CPU time ..................... 54 Workspace Composer: Redirecting %AppData% and sub directories not working correctly .. 54 Workspace Composer: Repetitively clicking the splash screen during logon could stop the Workspace Composer from working .................................................... 54 Workspace Composer: Replaced icons for (un)managed shortcuts sometimes disappeared or became blank after logging off and on again ......................................... 54 Workspace Composer: RES Subscriber not working after reconnect ............................. 55 Workspace Composer: "Run as different user" not always working correctly ................... 55 Workspace Composer: ScreenSaveActive containing an empty string could cause error ..... 55 Workspace Composer: Session may hang during workspace refresh .............................. 55 Workspace Composer: Shortcut for Microsoft Internet Explorer not created in new (mandatory) profiles after RES Workspace Manager finished active setup ...... 56 Workspace Composer: Slow startup in environment with multiple domains .................... 56 Workspace Composer: Some registry settings not applied during reconnect ................... 56 Workspace Composer: Startup preferences sometimes disappeared ............................. 56 Workspace Composer: System application not localized in time ................................. 57 Workspace Composer: Taskbar might disappear unexpectedly ................................... 57 Workspace Composer: Unmanaged pinned taskbar items sometimes disappeared ............ 57 Workspace Composer: User defined default mail profile for Microsoft Outlook not saved ... 57 Workspace Composer: Voluntary shortcuts were restored after user removed them ......... 58 Workspace Composer: Wrong protocol assumed when connecting to Citrix XenDesktop session via RDP ............................................................................. 58 Workspace Composer: XML errors when computer name started with a digit (0-9) ........... 58 Workspace Containers: Scrollbar not working in read-only mode ................................ 58

vi

1.

New Features

Citrix XenApp 6.5: Session Lingering and Session Prelaunch features now supported RES Workspace Manager now supports the Session Lingering and Session Prelaunch features of Citrix XenApp 6.5. Session Lingering

If RES Workspace Manager is used in combination with Citrix, and the Session Lingering feature is enabled through Citrix policies, closing the last published Citrix application in a user session no longer causes the Citrix session to log off. Instead, the Citrix session will linger. Please note that lingering Citrix XenApp applications started by RES Workspace Manager will not show the status 'lingering' on the Citrix server. This is caused by the way RES Workspace Manager starts Citrix published applications. Session Prelaunch

Prelaunch applications can be created on the Citrix server for applications that are managed by RES Workspace Manager. If a Citrix Receiver is started on a client, these prelaunch applications are automatically started. When the user starts the actual managed application, the application will start faster, as all logon actions (including pre-fetched User Settings) were already processed when the prelaunch application launched. Please note, for Session Prelaunch to work, the Citrix server needs to be configured to launch the Workspace Composer automatically (Administration > Agents, on the Agents tab, select Automatic for Run Workspace Composer).

Copyright © 1998-2013 RES Software

7

Locations and Devices: New zone rules based on connected wireless network and nearest access point Wireless networks can be excellent indicators of an end user's actual location. At User Context > Location and Devices, new Zone rules have been added for wireless networks: Connected network (SSID) and Nearest access point (BSSID). By creating a Zone rule based on Connected network (SSID), you can configure features (e.g. printers) that are available if a session is running on a device connected to a specific wireless network. A Zone rules based on Nearest access point (BSSID) allows you to configure features to be available if a session detects that a specific access point is the nearest, based on it having the greatest signal strength of all detected access points. In the list of Zone rules, the new rules can be found under Network > Wireless. Due to privacy constraints, detected wireless networks and access points are not logged in the RES Workspace Manager Console. However, during a user session they are shown to the end user on the Diagnostics tab of the Workspace Preferences tool, so end users can provide their administrator with this information upon request. A change in connected wireless network or nearest access point will trigger a session refresh if the change causes a new zone to become active, or causes a currently active zone to become inactive. Otherwise, the session is not refreshed. When refreshing, the advanced setting # seconds to wait before refreshing upon network connectivity change (configured at Setup > Advanced Settings) is taken into account. Notes 

If an access point is configured to hide its SSID, RES Workspace Manager will detect it as an empty SSID (i.e. empty string). If there are multiple access points with a hidden SSID, RES Workspace Manager is not able to distinguish between the networks they belong to. In this case, a rule for the nearest access point, specified for an access point with a hidden SSID, will check the nearest access point of ALL access points that hide their SSID (even if they belong to different networks).



The use of environment variables is not supported for SSID and BSSID names.



Zone rules based on wireless network and nearest access point are not available in RES Workspace Manager Express Edition.

Microsoft App-V Integration: Support for App-V 5.0 RES Workspace Manager now supports Microsoft App-V 5.0. With App-V 5.0 virtual applications work more like installed applications, allowing RES Workspace Manager to interact with the applications directly. Because of this, in user sessions, User Settings Tracking, prefetching User Settings and Process interception can also be done for App-V 5.0 applications.

Copyright © 1998-2013 RES Software

8

2.

Enhancements and Improvements

Actions: Improvement loading packages and programs for Microsoft ConfigMgr The time it takes to load data of large Microsoft System Center Configuration Manager (SCCM) environments has been improved. When creating an Action based on Microsoft ConfigMgr (both on global and application level), and clicking the button for Program, the Select Microsoft ConfigMgr package/program window opens. In this window, all packages and programs that are currently available on the configured Management Server (At Setup > Integration > Microsoft System Center) are shown. To improve the time it takes to load the data about packages and programs that are currently available in large Microsoft System Center Configuration Manager (SCCM) environments, the RES Workspace Manager Console now caches the retrieved package/program information when this window is opened for the first time after the Console was started. This cached data is then loaded into the Select Microsoft ConfigMgr package/program window each subsequent time it is opened. To refresh the packages and programs that are currently available on the configured Management Server, a Refresh cached packages/programs button has been added. Clicking this button will force the Console to flush the cached data and retrieve and load a current list of available packages and programs.

Advanced Settings: New option to bypass composer for administrator accounts At Setup > Advanced Settings the option Bypass composer for accounts matching has been added. With this option you can specify mask(s) of (local) administrator accounts that bypass the Workspace Composer on Agents that start RES Workspace Manager sessions automatically.

Copyright © 1998-2013 RES Software

9

Agents: Different values for "Poll for changes" intervals Poll for changes determines the interval at which Agents check whether they need to download any configuration changes, but also whether they need to execute any tasks. A longer polling interval means that it takes longer before Agents execute tasks such as remote publishing to Citrix XenApp servers, forcing a session refresh, restoring User Settings from the RES Workspace Manager Console, sending messages to users, and disconnect, log off and reset users. Better interval options are now available for selection for the Agent setting Poll for changes. The following additional intervals are now available in order to ensure that tasks are executed within a realistic time frame: 

Every 10 seconds



Every 15 seconds



Every 30 seconds



Every 4 hours

Tasks will time out and fail with an interval longer than 4 hours. The following intervals are therefore no longer available: 

Every 6 hours



Every 12 hours



Every 24 hours

After upgrading to RES Workspace Manager 2012 SR3, intervals that were set to 6, 12 or 24 hours will still be applied, but in the Console the interval value will be shown as Every 4 hours. In these cases, you need to reselect Every 4 hours (or any other interval), to actually change the interval to 4 hours (or any other interval). If, at some point in the future, you downgrade back to RES Workspace Manager 2012 SR2 or older, then Agents set to one of the newly introduced poll intervals (10 seconds, 15 seconds, 30 seconds or 4 hours) will automatically revert to the default of Every 5 seconds. Please note that the polling intervals do not not affect the timing for actually downloading new configuration data, which is determined by the Agent setting Update Agent cache on change.

Agents: New default identification method for Agents in new environments In new installations of RES Workspace Manager, the default identification method for Agents is by Computer domain name and NetBIOS name. In previous versions, the default identification method was by Unique GUID generated by RES Workspace Manager. When upgrading from RES Workspace Manager 2012 SR2 or earlier to RES Workspace Manager 2012 SR3, the configured identification method will not change. The Agent identification method can be configured at Administration > Agents on the Settings tab.

Applications: Administrative note column added to Application List tab The Application List tab (at Composition > Applications), provides information about all applications that RES Workspace Manager controls. Per application, administrators can provide Administrative notes. A column for Administrative notes has been added to the Application List tab to help administrators distinguish and evaluate managed applications more easily. Copyright © 1998-2013 RES Software

10

Applications: Enable/Disable added to Quick Edit context menu It is now possible to enable or disable multiple applications on the Application List tab (at Composition > Applications). The option Enable/Disable has been added to the Quick Edit context menu. On the Application List tab, this options allows you to enable or disable one or multiple applications at once. When disabling multiple applications, the provided Notification message will be applied to the selected applications, overwriting any existing notifications. On the Start Menu tab, this option in the Quick Edit context menu is similar to the Enable and Disable options that were already available.

Applications: Notification when using unsupported characters in menu/application title Microsoft Windows Operating Systems do not support the following characters in a file or folder name: \ / : * ? " < > |. In user sessions, if menu or application titles contain unsupported characters, these are automatically replaced with an underscore ("_"). Now, at Composition > Applications, the RES Workspace Manager Console shows a warning message if you try to save a newly created or edited menu or managed application with unsupported characters in the title. This allows you to change the menu or application title before you save it.

Applications: Option Autolaunch at session start extended At Composition > Applications, when configuring settings for a managed application, the option Autolaunch at session start can now be set to: 

Take no action: The application will not start automatically. The user can change this behavior on the Startup tab of "Workspace Preferences".



Voluntary: Initially, this will start the application automatically, but the user can change this behavior on the Startup tab of "Workspace Preferences".



Mandatory: This will always start the application automatically. The user can not change this behavior.

When set to Voluntary or Mandatory the option Autolaunch by user not allowed is cleared and disabled. The option Disable autolaunch for managed applications (at Composition > Application, on the Settings tab) can override the value specified for Autolaunch at session start.

Application User Settings: Default value for Capture mode changed to "After application has ended" On the Capturing tab, by default, the settings specified in the application's User Settings are preserved at application end: Capture: After application has ended. Optionally, you can set Capture: After session has ended instead, to preserve the settings later. To change the default configuration, you need to switch to the Advanced User Settings view. Before, the default value was Capture: After session has ended. For App-V applications, by default, the settings specified in the application's User Settings are preserved at application end: User package generated by App-V on application end. Before, the default value was User package generated by App-V on session end.

Copyright © 1998-2013 RES Software

11

Citrix XenApp: Improved check for a Citrix XenApp server's membership of Citrix Worker Groups At regular intervals, RES Workspace Manager determines to which Citrix Worker Groups configured Citrix XenApp servers belong. This check runs in the background and has also been optimized. Before, the check was carried out every two hours. This meant that Citrix Worker Group data was out of sync for quite a long time. The check is now performed every minute, so changes are reflected much sooner.

Citrix XenApp 6: Registry value to make Citrix XenApp server act as Session Host Only server A new registry value was added to make a Citrix XenApp server act as a Citrix XenApp Session Host Only server. This can be done by setting the following registry value: Key

Initial installation RES Workspace Manager 2011 / RES Workspace Manager 2012:



HKLM\Software\RES\Workspace Manager (32-bit)



HKLM\Software\Wow6432Node\RES\Workspace Manager (64-bit)

Initial installation RES PowerFuse 2010 and earlier:



HKLM\Software\RES\PowerFuse (32-bit)



HKLM\Software\Wow6432Node\RES\PowerFuse (64-bit)

Value (string)

ActAsSessionHostOnly

Data

Yes

Please note that when setting this registry value, the Citrix XenApp server will be excluded from certain tasks that are not available for Citrix XenApp Session Host Only servers (e.g. application publishing). Citrix XenApp servers acting as Citrix XenApp Session Host Only servers are listed in the Agents overview (at Administration > Agents, on the Agents tab) with "x.x.x (session host only)" in the XenApp version column. "x.x.x (session host only)" can be for instance "6.0.0 (session host only)" or "6.5.0 (session host only)". When using this registry value, it might be desired to set the option Poll for (database) changes to a longer interval than Every 5 seconds for Citrix XenApp servers hosting user sessions (at Administration > Agents, Agents tab, on the Settings tab of the Agent).

Citrix XenApp Publishing: Interface enhancements for Instant Passthrough When configuring Instant Passthrough settings at global and application level, the interface of the forms has been improved. The options have been reordered to match the way in which they are processed by the RES Workspace Composer, and options are greyed out if they cannot be combined with other selected settings. For example, if the Instant Passthrough option Use template ICA file is configured on global level, this file will overrule any ICA files configured at application level. If this global option is selected, the option Use custom ICA file for this application at global level is therefore now greyed out. This reflects the current existing behavior.

Copyright © 1998-2013 RES Software

12

Console: Column widths customizable Throughout the Console it is now possible to adjust the size of the columns as they appear on screen. The customized column width is saved automatically on the user’s home drive or, if not available, in the user’s registry. In every list view in the Console, one column is by default configured to autosize to fill out any remaining screen width. If you adjust the width of an autosizing column, it will no longer autosize and so you may end up with white space to the right of the columns. The option Reset all column properties to defaults in the Options menu, will reset any changes that you made to the order or widths of columns in the Console.

Console: Improved performance for environments containing a large number of applications The time to update the cache after changing an application or menu item has been improved for environments that contain a large number of applications. Cache updates will now take less time.

Console: Improved reloading of Location and Devices after editing or deleting a Zone At User Context > Location and Devices, after editing or removing a zone, the tree is refreshed and reset to the default state. In previous versions, any expanded trees would be collapsed after the refresh. In addition, sometimes the focus also changed to another zone in the tree. After a refresh of the tree, it is now reset to its last custom state and if a zone was edited the focus is reset to this zone. The default state will still be applied if the Location and Devices node is deselected and selected again.

Console: Improved startup time for environments containing a lot of applications The startup of the RES Workspace Manager Console has been improved for environments that contain a large number of applications. The loading of applications will now take less time.

Console: New icons for Zones and Zone Rules In RES Workspace Manager 2012 SR3 the icons for Zones and Zone Rules have been changed to reflect the aspect of location more clearly.

Copyright © 1998-2013 RES Software

13

Console: Registry value to resolve Client IP address via DNS In rare circumstances it may be desirable to resolve the Client IP address via DNS. This can be done by setting the following registry value: Key

Initial installation RES Workspace Manager 2011 / RES Workspace Manager 2012:



HKLM\Software\RES\Workspace Manager (32-bit)



HKLM\Software\Wow6432Node\RES\Workspace Manager (64-bit)



HKCU\Software\RES\Workspace Manager (32-bit)



HKCU\Software\Wow6432Node\RES\Workspace Manager (64-bit)

Initial installation RES PowerFuse 2010 and earlier:



HKLM\Software\RES\PowerFuse (32-bit)



HKLM\Software\Wow6432Node\RES\PowerFuse (64-bit)



HKCU\Software\RES\PowerFuse (32-bit)



HKCU\Software\Wow6432Node\RES\PowerFuse (64-bit)

Value (string)

ClientIPFromDNS

Data

Yes

Console: RES Workspace Manager now works around Microsoft's 15 second timeout during startup RES Workspace Manager is now working around Microsoft's check for revoked certificates which may cause a 15 second timeout during startup (see http://technet.microsoft.com/enus/library/ee619754(v=ws.10).aspx for more information about Microsoft's Certificate Revocation). This enhancement has been specifically introduced for the following situation: 

The RES Workspace Manager Console is configured in an environment with a Relay Server.



The computer running the Console is not directly connected to internet.

Before the enhancement, it appeared that the Console was hanging for 15 seconds before starting or it did not start correctly. Please note, when starting the Console for the first time, there might still be a delay of 15 seconds, but after that it will start correctly.

Copyright © 1998-2013 RES Software

14

CPU optimization: Prevent cpushld.exe from running if enabled At Administration > Performance > CPU Optimization, on the Settings tab, when CPU Optimization was enabled, cpushld.exe would still run on all Agents. To prevent cpushld.exe from running on Agents, the following registry value can be set for each Agent: Key



HKLM\Software\RES\Workspace Manager (32-bit)



HKLM\Software\Wow6432Node\RES\Workspace Manager (64-bit)

Value (string)

runcpushld

Data

No

Note When you want to use the CPU Shield, please enable CPU Optimization (at Administration > Performance > CPU Optimization, on the Settings tab) and remove the registry setting from the Agent.

Datastore: Variable port for IBM DB2 now supported When setting up an IBM DB2 Datastore, a custom port to connect to the RES Workspace Manager Datastore can now be specified after the server name. The notation is "server:port". Previously, this port was hardcoded to 50000. This enhancement is also applicable for Relay Servers and the Reporting Service.

Directory Services: Startup time optimization when using Account SIDs for Processing Access Control At User Context > Directory Services, when Process Access Control based on was set to Account SIDs, the startup and refresh of a RES Workspace Manager session could take a long time. By caching the Account SIDs with the corresponding Account Names, the performance of startup and refresh has been improved for several situations: 

If the same Account Name is used more than once in an Access Control Rule.



If the same Access Control Rule is evaluated more than once during startup/refresh of the user session.

Caching has been implemented for both the Management Console and the Workspace Composer.

Drive and Port Mappings: New mapping for RES HyperDrive Network locations and ports (lpt/com) can be mapped. During logon, connections are made to mapped drives and ports and in user sessions they are treated as one of the system's own disk drives or ports. It is now also possible to set mappings to existing RES HyperDrive Fileservers. This type of mapping is only available if RES HyperDrive integration is enabled (at Setup > Integration > RES Software > RES HyperDrive). Drive and Port Mappings can be found at Composition > Actions By Type > Files and Folders > Drive and Port Mappings.

Copyright © 1998-2013 RES Software

15

Drivers: New AppGuard, ImgGuard, NetGuard and RegGuard drivers implemented New AppGuard, ImgGuard, NetGuard and RegGuard drivers have been implemented. An update of all drivers was necessary to resolve several issues and improve performance. Some of these issues are listed below: 

Process interception failed when a process was started by the svchost.exe process.



In very rare occasions the system could crash (BSOD) when the NetGuard driver could not be initialized. Note

A system reboot is required to activate the new AppGuard, ImgGuard, NetGuard and RegGuard drivers.

Folder Synchronization: Improvement when synchronizing unmanaged desktop items Folder Synchronization has been changed to improve the synchronization of unmanaged desktop items allowing the possibility of roaming these items to different systems and environments. For the synchronization of unmanaged desktop items to work properly, two Folder Synchronizations need to be configured, one to run at logon, one at logoff, with the following settings (other than default settings): Logon



Specify the local desktop folder for Local folder.



Specify a folder on the network to synchronize to for Remote folder.



Direction: Download.



Run at: Logon.



Enable Wait for task to finish before continuing.

Logoff



Specify the local desktop folder for Local folder.



Specify the folder on the network to synchronize to for Remote folder.



Direction: Upload.



Run at: Logoff.



Enable Wait for task to finish before continuing.

Folder Synchronization: Several improvements Several improvements have been made to Folder Synchronization. These improvements include making the Folder Synchronization process more robust, which is especially beneficial in situations where network delays or dropouts happen during this process. For instance, improvements have been made to detect if a remote folder is still reachable after a network change. If the remote folder is not reachable, RES Workspace Manager will now stop the Folder Synchronization.

Copyright © 1998-2013 RES Software

16

Installation: RES Workspace Manager Agent-only installation As of RES Workspace Manager 2012 SR3 it is possible to perform an RES Workspace Manager Agentonly installation. Use Agent-only installations to provide end users with RES Workspace Manager sessions while ensuring that the RES Workspace Manager Console is not available to them. The .msi is RES-WM-2012-Agent-SR3.msi. For Agent-only installations, it is not possible to create a database using a command line (unattended installation). Please note that it is not possible to install a RES Workspace Manager Console-only and an Agentonly installation on the same machine. Instead, a full installation of 2012 is then necessary (after uninstalling the Console-only or Agent-only installation).

Locations and Devices: Blast protocol added to Session type rule At User Context > Locations and Devices, when adding/changing a Session type rule for a Zone, a new Protocol named VMware Blast can now be selected. This protocol enables you to build rules that recognize whether an end user is logging on from a remote desktop using VMWare Blast (as opposed to Citrix ICA, Microsoft RDP, or VMware PCoIP).

Lockdown and Behavior: New option to hide desktop icons during session start and refresh At Composition > Desktop > Lockdown and Behavior, under Microsoft Windows Shell, a new option has been added: Hide desktop icons during session start and session refresh. During session start and refresh, the Workspace Composer determines which icons should be shown on the desktop, and where these icons should be placed. During that process: 

end users can click desktop icons to start unmanaged applications, but not managed applications. (This is only relevant in Merge mode.)



end users may see desktop icons move to different locations.

If the new option Hide desktop icons during session start and session refresh is selected, RES Workspace Manager will show an empty desktop until all icons are in their correct locations. This eliminates the effect of shifting desktop icons, but it also means that end users cannot start any applications from their desktop until the process has finished. This new option will always be evaluated by RES Workspace Manager, even if Lockdown and Behavior is disabled and, if selected, be applied. The new option is cleared by default in existing sites after upgrade. In new installations of RES Workspace Manager, by default, the option is selected.

Copyright © 1998-2013 RES Software

17

Maintenance: Option to search for obsolete Citrix Worker Groups and remove them A new Maintenance action has been added: Search for obsolete Citrix Worker Groups (at Administration > Maintenance). Obsolete Citrix worker groups are worker groups that exist in the RES Workspace Manager Datastore but are from farms for which the RES Workspace Manager site no longer contains any Agents. The list of obsolete worker groups includes information about where in the Management Console the obsolete worker group is being referenced, i.e. for published applications or on the Defaults tab for Citrix XenApp Publishing Integration. If obsolete worker groups are found, the option Remove obsolete Worker Groups becomes available if the Administrator has write access to both the Citrix XenApp Publishing Integration and the Applications nodes. Clicking this option will remove all reference to the obsolete worker groups in the Management Console and Datastore.

Microsoft App-V Integration: Improvement for applications pinned to taskbar In a VDI configuration where users start with a clean environment after each fresh startup, Microsoft App-V applications that are pinned to the taskbar may not stack properly if they are launched for the first time. The stacking of pinned taskbar items is based on the Application User Model IDs, which are known only after an App-V application has been started and cached in the App-V cache for the first time. Improvements have been made to populate Application Model IDs for App-V applications as RES Workspace Manager settings in the settings table in the RES Workspace Manager Datastore. This will allow App-V applications that are pinned to the taskbar to stack properly.

Microsoft App-V Integration: Support for Microsoft System Center Configuration Manager 2012 SP1 Launching managed Microsoft App-V applications using Microsoft System Center Configuration Manager (SCCM) 2012 SP 1 is now possible. With this Service Pack update, SCCM frequently resets the UpdateOSDfile policy to its default value causing the launch of a managed App-V application to fail. By setting the following registry value, a workaround is made available for the automatic SCCM reset, allowing the managed App-V application to launch: Key



HKLM\Software\RES\Workspace Manager (32-bit)



HKLM\Software\Wow6432Node\RES\Workspace Manager (64-bit)

Value (string)

CheckUpdateOSDFile

Data

Yes

Please note, it is still possible that launching a managed App-V application fails. This can be a timing-issue: after the workaround was applied, SCCM resets the UpdateOSDfile policy before the managed App-V application was launched.

Copyright © 1998-2013 RES Software

18

Microsoft Windows 8 and Windows Server 2012 compatibility RES Workspace Manager is now compatible with both x86 and x64 versions of Microsoft Windows 8 and Windows Server 2012. Changes have been implemented in Zone rules and the Desktop Sampler, including Baseline Desktop Analyzer, to achieve this. Notes 

RES Workspace Manager dialog messages that are directly displayed after session logon will not be visible on the Windows 8 Metro Start Screen.



Windows Themes: Custom background images selected by the end user in Windows 8 are not applied in Windows 7, though changes made in Windows 7 are applied in Windows 8.



When publishing a Managed Application from RES Workspace Manager to a Windows Server 2012, the published application is available in RES Workspace Manager sessions, but it does not appear in the list of published applications in the Windows Server Management Console.

Network Security: New hidden rule to allow searchprotocolhost.exe For Network Security, a new default rule has been added to allow searchprotocolhost.exe. This rule is necessary to run the Microsoft Windows search index engine if Network Security is enabled (at Security > Network Connections, on the Settings tab).

New option "Disable file system redirector on 64-bit systems" for External tasks On a 64-bit system, the file system redirector automatically redirects references to certain paths: 

C:\program files\ is redirected to C:\program files (x86)



C:\windows\system32 is redirected to C:\windows\syswow64

Redirecting the paths will affect the start of external tasks if it uses one of these paths. For such external tasks, the option Disable file system redirector on 64-bit systems has been added to ensure that the external task is started from its defined path.

Performance: Enhancement when determining if active users are within the scope of a security role The performance when determining if active users are within the scope of a security role has been enhanced. Before, to determine if active users were in scope of a security role, all access objects (OU/Group/User/Powerzone/Workspace Container) of the active users were compared with the access objects of the security role. This could take quite some time. Now, the comparison of access objects has been limited to the type of the scope. In case the scope is only based on one access object (e.g. OU), determining if an active user is in scope of the security role can be done much quicker. For organizations with a large number of active users or with active users being member of numerous groups, this performance enhancement is very noticeable.

Copyright © 1998-2013 RES Software

19

Printers: Option to refresh printers on session refresh In certain circumstances, refreshing the printers is also desired on session refresh. Refreshing the printers may be necessary, for instance, when an application deleted a printer, there was an error during logon or when access to specific printers is based on Wireless network Zone rules. At Composition > Actions By Type > Printers, on the Settings tab, the new option on session refresh has been added to the Refresh printers section. Selecting this option will cause RES Workspace Manager to reprocess all Network Printers, to determine which printers should be connected when a user session refreshes.

Relay Server: IPv6 now supported for Direct Access connections RES Workspace Manager now supports IPv6 for Direct Access connections to Relay Servers.

Relay Server: MySQL Agents and Relay Servers connecting directly to the Datastore need to have the correct database drivers installed. If your RES Workspace Manager environment runs on a MySQL database and you upgrade the ODBC drivers to version 5.2.4, please note that only the ANSI type of this driver is supported.

Copyright © 1998-2013 RES Software

20

Relay Server: Support for configuration through DHCP RES Workspace Manager now supports configuration of Relay Servers through DHCP making dynamic Relay Server configuration possible. Dynamic Relay Server configuration uses the DHCP servers in your network. To configure dynamic Relay Server configuration, you can store Relay Server connection information in Server options or Scope options on the DHCP servers in your environment. When computers connect to the network, they will receive parameters defined at scope level from the DHCP servers. This allows Relay Server connection information defined in DHCP scope to be transferred to the computer's registry. When the RES Workspace Manager Agent starts up, it will use the information in its registry to connect to the proper Relay Server. You can export Relay Server connection information from RES Workspace Manager to easily add it to the DHCP Scope. To export this data, a new button has been added at Administration > Relay Servers, on the Settings tab. By clicking the button Export Connection string to file, the Relay Server connection string will be exported to a text file. Before this string can be stored on the DHCP servers in your environment, the following information needs to be added manually at the beginning of the string: 

Relay Server name(s).



Optionally, the port number of the Relay Server. If no port number is given, the default port number 1942 will be used automatically by the Agent's service.

Examples of Relay Server names are given in the Relay Server connection string: 

relay1.example.com:2012 (Relay Server name with port number 2012)



relay2 (Relay Server name without port number)

These values should be replaced by your own Relay Server name(s) and optionally port number(s). Notes 

The maximum length of the Relay Server connection string is 255 characters. Please take into account that an encrypted password may consume a lot of characters.



A restart of the Agent service is necessary for the change in connection to take place.

Removable Disks Security: Access Control based on Vendor ID/product ID of USB storage device now possible At Security > Data > Removable Disks, you can secure the use of removable disks in the user workspace by giving only specific users on specific locations specific permissions to use removable disks. Access Control for Removable Disks can be based on Zone rules (Removable Disks window > Access Control tab > Location and Devices section). It is now possible to base Zone rules on the Vendor ID/product ID of a USB storage device. In previous versions, Access Control for Removable Disks could only be based on Zone rules for a USB storage device based on on its Serial number.

RES HyperDrive Integration: Extended RES HyperDrive Client settings On the Settings tab of Setup > Integration > RES Software > RES HyperDrive, the RES HyperDrive Client Settings can be used to override the local RES HyperDrive Client settings in a RES Workspace Manager session. The RES HyperDrive Client settings have been extended with Vault settings. Copyright © 1998-2013 RES Software

21

RES IT Store Integration: "Catalog" renamed to "Publication" At Setup > Integration > RES Software > RES IT Store, the Catalog name and Catalog password fields have been changed to Publication name and Publication password, to be consistent with the naming conventions in RES IT Store.

RES VDX Integration: Improved communication with VDX Engine A new API has been implemented in RES Workspace Manager to improve the communication between the RES Workspace Composer and the RES VDX Engine. Before, if using RES VDX, the communication with the VDX Engine could sometimes fail, resulting in the following error in the error log: "All pipe instances are busy" It could also happen that communication could only be established after a lot of retries. With the implementation of the new API, this unwanted behavior is reduced.

RES Workspace Manager: Additional parameter for unattended installation RES Workspace Manager 2012 SR3 enhances the unattended installation with the possibility to use a RES Workspace Manager Datastore connection string stored in a text file. In a connection string, the database password is encrypted, which prevents password exposure and improves security. Connection string files can be created from the Primary Datastore properties at Setup > Datastore. In the command line for the unattended installation, use the MSI parameter CONNECTFILE=path\file to connect to the Datastore specified in the connection string. This replaces the separate MSI parameters for database server, name, password, etc. Example: Msiexec /i c:\RES-WM-2012-xxxx.msi CONNECTFILE=c:\temp\wmdbconn.txt /qn

RES Workspace Manager Agent: Copy from Clipboard/Import from File buttons on Configure Connection window RES Workspace Manager Agents get configuration data from the Datastore, either directly or through Relay Servers. On an Agent, information on the RES Workspace Manager Agent - Configure Connection window can be used for troubleshooting purposes or making changes to the Agent connection settings. On this RES Workspace Manager Agent - Configure Connection window Copy from clipboard and Import from file buttons have been added. This makes it easier for the user to copy the connection settings of the target Datastore to his local Agent. The Import from file option only supports .txt files. The RES Workspace Manager Agent - Configure Connection window can be opened by running the command %Program Files%\RES Software\Workspace Manager\svc\res.exe /config on every relevant machine. Please note that the Copy to clipboard and Export to file functionalities are not available for the connection settings of Relay Servers.

Copyright © 1998-2013 RES Software

22

Security: Local cache blocked by default All RES Workspace Manager Agents receive a local cache that stores configuration data from the Datastore. Each Agent uses its cached data instead of connecting to the Datastore directly. The local cache also stores user information (log files and monitoring data) that is collected by the Agent. RES Workspace Manager blocks access to the local cache folder by default, even if security is disabled or not available. This enhances security and protects the configuration data from corruption by end users. Notes 

The following folders are excluded from the default protection: 

IconCache



Within Resources: o

custom_resources

o

sft_int

o

ctx_int

o

app_desk

o

app_scr.

Support for Microsoft Office 2013 RES Workspace Manager now fully supports both x86 and x64 versions of Microsoft Office 2013. This includes support for E-mail Templates, User Settings Templates and Outlook signatures.

Usage Tracking Viewer: Datastore selected in Console now used In the Usage Tracking Viewer (available from Setup > Usage Tracking and from Diagnostics > Usage Tracking Overview), the Datastore that was selected in the Console will now be used (Primary/Remote). Previously, the Primary Datastore was used by default. The Datastore connection is shown in the window title.

User Registry: Open ADM(X) file window changed When adding a new User Registry Policy with the same name as a file that already exists in the RES Workspace Manager database, the Open ADM(X) file window opens. Several changes have been made to this window: 

The Cancel option was replaced by a Cancel button that has the standard behavior of RES Workspace Manager cancel buttons.



Descriptions were added for the options Rename and Replace to clarify these options and explain their expected behavior.

User Registry Policies can be configured at global level (at Composition > Actions By Type > User Registry, on the User Registry tab) and at application level (at Composition > Applications, on the Configuration > Actions tab of an application).

Copyright © 1998-2013 RES Software

23

User Settings: Add and Import buttons on Capturing tab combined On the Capturing tab of the New/Edit User Setting window (both on global and application level), the options Templates and Flex Profile Kit were available when clicking the Import button (at the bottom-left of the window). Both options have been moved to the Add button (at the bottom-right of the window) to reduce the number of clicks and improve the flow. When clicking Add, you can now choose between Templates, Custom, and Import > Flex Profile Kit.

User Settings: Basic and Advanced view In RES Workspace Manager 2012 SR3, on the Console you can now choose between a Basic and Advanced view of User Settings (both on global and application level). The Basic view presents the most commonly used options, while the Advanced view offers additional options that may be required for troubleshooting and tweaking. A button at the bottom of the Edit User Settings window (Global) and in the User Settings section of the Edit Application window allows you to switch between Basic User Settings and Advanced User Settings. Choosing Basic User Settings hides the advanced settings that may not be relevant for you. When upgrading from RES Workspace Manager SR2 or earlier to RES Workspace Manager 2012 SR3, existing User Settings on global and application level are shown in Advanced view. The choice for User Settings view can be set as a default for new applications (at Composition > Applications, on the Settings tab).

User Settings: Improvement when adding new Template When editing a managed application's User Settings, adding a User Settings Template no longer opens the New User Setting window. Instead, the items that will be captured with the chosen Template are immediately shown on the Capturing tab for review. This change creates a more efficient flow for adding User Setting Templates on application level, since most administrators do not immediately make changes to the set of captured items proposed in the templates.

Copyright © 1998-2013 RES Software

24

User Settings: New and updated templates You can use User Settings templates when configuring global User Settings at Composition > User Settings or when configuring User Settings for an application at Composition > Applications > Managed Applications > User Settings. New templates have been added for: 

Desktop Content (Control Panel) for Windows XP / 2003 and Vista or later



Microsoft Office 2013





Access



Common



Excel



InfoPath Designer



InfoPath Filler



Lync



OneNote



Outlook



PowerPoint



Publisher



Tools



Word

Internet Explorer 10

Additionally, the following template has been updated for Windows XP / 2003 and Vista or later: 

Desktop Icons (Control Panel): From now on, only .lnk and .url files are saved.

User Settings: New wizard to discover User Settings The User Settings Capture wizard helps you discover which files and registry settings could be relevant as User Settings for an application or process. These can then be tested and optimized. To start the wizard, choose the option Discover User Settings.... This option can be found by clicking Add or New when adding or editing User Settings in Capture mode (at Composition > User Settings, on the User Settings > Capturing tab of a managed application, and on the Capturing tab of a specific User Setting container at application level). Please note that a full installation of RES Workspace Manager is necessary to run the User Settings Capture Wizard as the wizard makes use of the RES Workspace Manager drivers. Also, to avoid conflicting results, no RES Workspace Manager session may be running on the system on which the User Settings Capture Wizard runs.

Workspace Composer: Detection if a computer comes out of a suspended state improved Improvements have been made in RES Workspace Manager to detect if a computer is coming out of a suspended state.

Copyright © 1998-2013 RES Software

25

Workspace Composer: Microsoft Windows password expiry notification also shown in RES Workspace Manager Shell In Microsoft Windows, users get a notification that their password is about to expire. These notifications are now shown in both the RES Workspace Manager Shell and the Microsoft Windows Shell. Previously, these notifications were shown only in the Microsoft Windows Shell. In the RES Workspace Manager Shell, password expiry notifications include a link to open the Workspace Preferences tool, where the password can be changed. If the change password option is hidden from the user's Workspace Preferences tool, then the link in the password expiry notification is replaced by text instructing the user to press CTRL+ALT+DEL to change it.

Workspace Composer: New command line to save settings and User Settings and then restart system Installation packages initiated by Microsoft System Center Configuration Manager (SCCM) sometimes need a reboot. In a regular reboot initiated by this system, settings and User Settings are not saved. For these situations, it is now possible to initiate a restart of the system with the following command line option: Command line parameters for %respfdir%\pwrgate.exe -55

Save settings and User Settings and then initiate a restart

Please note, with this command line option, a user will NOT be prompted to save any open/unsaved documents before his system is restarted.

Workspace Composer: Notification message when application is still being installed At Composition > Applications, on the Configuration > Actions tab of an application, an RES Automation Manager or Microsoft ConfigMgr action can be configured to install an application when a user clicks the application shortcut. In a user session, if the user clicks the application shortcut again before the installation is finished, he will now receive a notification message that the installation is still running.

Workspace Composer: Option to set latency threshold for retrieving context Under certain circumstances high latency networks could cause long delays at logon or session refresh. This was due to the retrieval of the user context from Active Directory. This has been fixed. At Setup > Advanced Settings the new option Use cached credentials if latency to AD is above: (in milliseconds) has been added. The threshold for the Active Directory latency can be set when the option is activated. If at user logon the network latency to the domain controller is above the specified threshold, the RES Workspace Composer will use the local cached user context. A background process will retrieve the actual user context from the domain controller and update the cached credentials if necessary. The user may experience a session refresh due to changes in the context.

Workspace Composer: Performance improvement when determining Zones based on Chassis type In user sessions, determining a Zone that was based on Chassis type could take several seconds to complete. This has been improved. Copyright © 1998-2013 RES Software

26

Workspace Composer: Performance improvement when retrieving information from Active Directory In user sessions, the performance of retrieving information from Active Directory has been improved. This enhancement reduces the number of Active Directory queries during session startup and session refresh.

Workspace Composer: pwruser.ini setting to prevent unwanted messages when default printer changes When the default printer is changed, a notification message is displayed to inform the end user. To suppress these messages, the entry NotifyDefaultPrinterChange in the pwruser.ini file can be set: Setting

Description

NotifyDefaultPrinterChange=No

The notification message will never be displayed when the default printer changes.

NotifyDefaultPrinterChange=OncePerLocation The notification message is only displayed if the new default printer differs from the default printer that has already been set for this location.

Workspace Composer: Shortcuts manually added to Startup folder now also added to user's pwruser.ini file In a user session, a user may be able to manually add or delete managed shortcuts to the Microsoft Windows Startup folder. These shortcuts will now also be added to the user's pwruser.ini file, allowing them to be applied in future user sessions. Please note that this only works if: 

At Composition > Desktop > Shell, Use Microsoft Windows Shell as the default shell was selected.



At Composition > Applications, on the Settings tab, Merge with unmanaged shortcuts was selected.

N.B. If the RES Workspace Manager shell is selected, the startup items can only be changed in user sessions in the Workspace Preferences, on the Startup tab.

Workspace Preferences: Copy to Clipboard button on Diagnostics tab Workspace Preferences is the users' desktop management system. On the Diagnostics tab of the Workspace Preferences, a Copy to Clipboard button has been added. This makes it easier for the user to provide the administrator with Diagnostics information for troubleshooting purposes.

Copyright © 1998-2013 RES Software

27

3.

Fixes

Access Control: Location and Devices frame not resizing correctly in read-only mode In the RES Workspace Manager Console, a lot of the New/Edit windows have an Access Control tab (e.g. at Composition > User Settings when adding a new or editing an existing User Setting). If such a New/Edit window was opened in read-only mode (because of your security role), the Location and Devices frame on the Access Control tab would not resize together with the rest of the window. This has been fixed.

Access Control: Resolving users with access based on "NOT User/Group" not working correctly If objects were configured with NOT User/Group for Access Control, resolving users should display a list with all Active Directory users except those users configured as "Not User" in the RES Workspace Manager Console. Instead, a list was displayed containing only users that, at a minimum, were member of the "Domain Users" group and were not configured as "Not User" in the Console. This has been fixed.

Agents: Changed identification method not always remembered At Administration > Agents, on the Settings tab, if the setting Identify Agents by was changed, the changed setting would not be remembered if a different tab was selected without clicking Save Settings first. This has been fixed.

Agents: Duplicate Agents in Agent overview when changing identification and connection method at the same time Consider the following scenario: 

At Administration > Agents, exceptions for Workspace Containers were configured.



At Administration > Agents, on the Settings tab, Datastore connection was set to Connect directly to the Datastore.



At Administration > Agents, for two Workspace Containers, Datastore connection was set to Connect through Relay Server with two different Relay Servers configured.



At Administration > Agents, one of these Workspace Containers was disabled and the other was enabled.



The two Workspace Containers applied to one or more identical Agents.



At Administration > Agents, on the Settings tab, the option Identify Agents by was changed.



At Administration > Agents, the disabled Workspace Container was enabled and the enabled Workspace Container was disabled.



All changes were saved by clicking Save Settings.

In this scenario, it could happen that duplicate Agents were listed in the Agents overview (on the Agents tab). This has been fixed.

Copyright © 1998-2013 RES Software

28

Agents: "Poll for changes" configuration for Workspace Containers not applied until a global change was saved At Administration > Agents, if the option Poll for changes was configured for a specific Workspace Container, this change was only applied after a change was saved on global level (at Administration > Agents, on the Settings tab). This has been fixed.

Agents: Settings for last workspace exception displayed incorrectly in read-only mode Consider the following scenario: 

At Administration > Agents, one or more Workspace Containers were configured.



The Console user only had read-only access to this node.

In this scenario, the tab of the last (most right) Workspace Container always displayed the same settings as those of the Workspace Container next to it. This has been fixed.

Applications: "Bad data" error for data source based on Microsoft Dynamics NAV ODBC driver Consider the following scenario: 

At Composition > Applications > Data Sources, a Data Source was configured for the Microsoft Dynamics NAV Driver.



In the Dynamics NAV ODBC Setup window, any ODBC setting other than the Data Source Name was configured.

In this scenario, a "Bad data" error occurred each time you opened the data source in the RES Workspace Manager Console and viewed its Settings by clicking the Change button. This has been fixed.

Applications: Environment variables not set for intercepted process If a process was intercepted (due to the application-level option Intercept new process and apply configuration), Environment Variable actions configured for the matching Managed Application were not set. This has been fixed. A new service, RESPESVC, has been introduced for this. Other configurations and Actions were implemented correctly.

Applications: Linked SCCM actions not visible on Resulting Actions tab Consider the following scenario: 

At Setup > Integration > Microsoft System Center, on the Settings tab, Microsoft System Center ConfigMgr Integration was enabled.



At Setup > Integration > Application Virtualization > Microsoft App-V, Microsoft App-V Integration was enabled.



At Composition > Applications, an App-V application was added with the option Use SCCM to deploy App-V application enabled (on the application's Properties > General tab).



At Composition > Applications, on the Configuration > Actions tab of an application, a linked action was defined with Perform Actions from application pointing to the App-V application with the option Use SCCM to deploy App-V application enabled.

In this scenario, in the Edit Linked Actions window, the actions were not visible on the Resulting Actions tab, but they were applied when the application was started. This has been fixed. Copyright © 1998-2013 RES Software

29

Applications: Process Interception sometimes failed At Composition > Applications, when Process Interception was enabled for an application, in user sessions Process Interception failed if the process was started by svchost. This has been fixed.

Applications: Read-only access Workspace Containers tab not completely read-only At Composition > Applications, if a Console user had read-only access to an application, some properties on the application's Workspace Containers tab (Access Control > Workspace Containers tab) were still editable. This has been fixed.

Applications: Renamed Workspace Containers not updated Consider the following scenario: 

At Composition > Applications, exceptions for Workspace Containers were configured OR At Composition > Applications, on the Access Control > Workspace Containers tab of an application, specific Workspace Containers were configured.



The Workspace Container was renamed.

In this scenario, the new name of the Workspace Container was not shown in the following places: 

At Composition > Applications in the tab caption of the Workspace Container.



At Composition > Applications, on the Application List tab in the Workspace Control column.

This has been fixed.

Applications: Shortcuts sometimes removed from the Start Menu Consider the following scenario: 

At Composition > Applications, on the Settings tab, the Windows Shell shortcut creation was set to Merge with unmanaged shortcuts.



At Composition > Applications, on the Properties tab of an application, Replace existing unmanaged shortcuts and Create Start Menu shortcut were selected.

In this scenario, if the application indeed replaced an unmanaged shortcut, the shortcut would also disappear from other menus in the user's Start Menu. This has been fixed. 

If the option Replace existing unmanaged shortcuts is selected and Create Start Menu shortcut is not selected, the application's shortcut will be removed from any Start Menu folder.



If the options Replace existing unmanaged shortcuts and Create Start Menu shortcut are both selected, the application's shortcut will no longer be removed from the Start Menu folder.

Copyright © 1998-2013 RES Software

30

Applications: Sometimes launching not possible if SCCM linked action was used Consider the following scenario: 

At Setup > Integration > Microsoft System Center, on the Settings tab, Microsoft System Center ConfigMgr Integration was enabled.



At Composition > Applications, an application was added:





On the application's Properties > General tab, for the Command line field "c:\program files\prog\prog.exe" was filled in.



On the application's Configuration > Actions tab, the action Microsoft ConfigMgr was configured to use SCCM installation of "prog" in case prog.exe could not be found.

At Composition > Applications, a second application was added: 

On the application's Properties > General tab, for the Command line field "c:\program files\prog\prog.exe" was filled in.



On the application's Configuration > Actions tab, a Linked Action was configured with Perform Actions from application pointing to the first application.

In this scenario, if the first application "prog" was not installed and the second application "prog" was started, "prog" would first be installed before it was started. After "prog" was installed, the SCCM installation would give a notification that the installation was "successfully finished" seconds before "prog" would be visible under "c:\program files". As a result, launching "prog" would fail. This has been fixed.

Applications: White icon if file type 'html' was added to Microsoft Internet Explorer At Composition > Applications, when configuring the application Microsoft Internet Explorer and the file type html was added on the Properties > File Types tab, files with this extension would have a white icon in user sessions. This has been fixed.

Building Blocks: Different behavior when importing Building Blocks through menu or context menu There was a difference in behavior when Building Blocks were imported via Action > Import Building Blocks or Action > Applications > Building Blocks > Add/Update Applications. This has been fixed.

Citrix XenApp: Continuous check for membership of Citrix Worker Groups if no membership existed At regular intervals, RES Workspace Manager determines to which Citrix Worker Groups configured Citrix XenApp servers belong. If the Citrix XenApp servers initially were not a member of any Citrix Worker Groups, this check was still carried out every minute. This has been fixed.

Copyright © 1998-2013 RES Software

31

Citrix XenApp 5: Error in Microsoft Windows Event Log after RES Workspace Manager 2012 SR2 was installed After installing RES Workspace Manager 2012 SR2 on a Citrix XenApp 5 server, the following error could be logged every minute in the Microsoft Windows Event Log: "PFXA6: Could not load file or assembly..." This has been fixed.

Citrix XenApp 6.5: Errors retrieving Citrix Worker Groups from Citrix XenApp Session Host Only server Errors could be reported in the Windows Event Log for applications when RES Workspace Manager tried to retrieve Citrix Worker Groups from a Citrix XenApp Session Host Only server (Worker). This has been fixed. If you have Citrix XenApp 6.5 Session Host Only servers (Worker) configured in your environment, consider the following requirements: 



RES Workspace Manager must be installed on one or more Citrix XenApp Controllers (Zone Data Controllers). For redundancy purposes it is preferred to have RES Workspace Manager installed on two or more Citrix XenApp Controllers. This is required for the following: 

To retrieve available Citrix XenApp Worker Groups and make them available in the RES Workspace Manager environment.



Execute Citrix application publishing in case applications are published from a RES Workspace Manager Console that is running on a Citrix XenApp Session Host Only server.

For Agents running on a Citrix XenApp Controller, the option Poll for changes must be set to Every 5 seconds (at Administration > Agents, on the Settings tab). Note



If you are using a Relay Server for your Citrix XenApp 6.5 Host Only servers, it is necessary to upgrade to Relay Server 2012 SR3 for this fix to work.



Refreshing Citrix Worker Groups from the RES Workspace Manager Console is not available for Citrix XenApp 6.5 Host Only servers.

Citrix XenApp Publishing: Error importing Building Blocks containing Server Groups When importing a Building Block containing Citrix XenApp Server Groups, the following error could occur: "Procedure: frmCTXSet.LoadServerGroups, Error: (91) Object variable or With block variable not set" This has been fixed.

Copyright © 1998-2013 RES Software

32

Citrix XenApp Publishing: Error publishing applications in multiple folders Consider the following scenario: 

At Composition > Applications, on the Start Menu tab, a menu folder including subfolders and applications was present.



At Composition > Applications, on the Start Menu tab, that menu folder was Published/Unpublished using the Quick Edit context menu (select the folder and right-click the mouse) (Quick Edit > Publishing > Publish/Unpublish).

In this scenario, each first application in the menu folder and its subfolders was skipped and would not be published or unpublished. This has been fixed.

Citrix XenApp Publishing: Folders not resolved when configured servers contained server group At Setup > Integration > Application Virtualization > Citrix XenApp Publishing, on the Defaults > Published Application tab, if the Citrix XenApp Servers that were added to Configured Servers contained a server group, Citrix folders were not resolved for the applications at Composition > Applications. This has been fixed.

Citrix XenApp Publishing: Import Wizard not publishing to Worker Group At Composition > Applications, when importing an application, the Import Wizard would by default use the server that was globally configured for Citrix XenApp Publishing (at Setup > Integration > Application Virtualization, on the Settings tab). If you would select a Citrix Worker Group in the Import Wizard, the wizard would still publish the application to the default server. And if you would select a Citrix Worker Group, but no default server was configured, the application was not published. This has been fixed.

Copyright © 1998-2013 RES Software

33

Citrix XenApp Publishing: Publishing applications on Citrix XenApp Session Host Only server failed Publishing applications failed in the following circumstances: 

When publishing applications from the RES Workspace Manager Console on a Citrix XenApp Session Host Only server.



When publishing applications using Remote Publishing and the server that would do the actual publishing was a Citrix XenApp Session Host Only server.

This has been fixed. Applications are now published and available as a Citrix published application. Please note that the ICA file is not created when publishing applications from a Citrix XenApp Session Host Only server. If you have Citrix XenApp 6.5 Session Host Only servers (Worker) configured in your environment, please consider the following requirements: 



RES Workspace Manager must be installed on one or more Citrix XenApp Controllers (Zone Data Controllers). For redundancy purposes it is preferred to have RES Workspace Manager installed on two or more Citrix XenApp Controllers. This is required for the following: 

To retrieve available Citrix XenApp Worker Groups and make them available in the RES Workspace Manager environment.



Execute Citrix application publishing in case applications are published from a RES Workspace Manager Console that is running on a Citrix XenApp Session Host Only server.

For Agents running on a Citrix XenApp Controller, the option Poll for changes must be set to Every 5 seconds (at Administration > Agents, Agents tab, on the Settings tab of the Agent). Note

If you are using a Relay Server for your Citrix XenApp 6.5 Host Only servers, it is necessary to upgrade to Relay Server 2012 SR3 for this fix to work.

Citrix XenApp Publishing: Unable to view certain files in published application At Composition > Applications, on the application's Properties > File Types tab, when a file type association was configured for a published application and the file name or path contained a space, the application could fail to start in a user session when it was started by clicking on a file associated with that application. This has been fixed.

Citrix XenApp 5 Publishing: Error publishing application with same name as existing application At Composition > Applications, if an application was published that had the same name as an application that already existed, the application name (browser name) was not properly set. As a result, it was not possible to start that published application in a user session. This has been fixed.

Copyright © 1998-2013 RES Software

34

Citrix XenApp Streaming: Applications with setting Maximum instances = 1 not started up correctly in user sessions When a Citrix XenApp Streamed Application was published with the option Maximum instances set to "1" (at Composition > Applications, on the Properties > Settings tab of the application), the application sometimes did not start up correctly in user sessions. The following error would then be displayed: 'Application is already running in the system tray and cannot be started a second time.' This has been fixed.

Console: Error when using Microsoft SQL Server 2000 When using Microsoft SQL Server 2000, the following SQL error could appear in the common error log: The NOLOCK, READUNCOMMITTED, and READPAST lock hints are only allowed in a SELECT statement. (DELETE FROM tblLicenses WITH (ROWLOCK READPAST) WHERE AppGUID = ? AND strLastUpdateUTC < ?) This has been fixed.

Console: Filtering on Workspace Container gave unexpected result At User Context > Workspace Containers, when filtering on the Workspace Containers, an unexpected result was shown. The objects that complied to a filter were not shown, whereas nothing was shown when an exclusive filter was used. This has been fixed.

Console: Sorting order of Commands not correct At Composition > Actions By Type > Execute Command, on the Commands tab, if the list contained 10 or more commands and the user clicked on the Order column, the list was sometimes sorted incorrectly. Instead of the order "1, ..., 9, 10, 11, 12", the commands would be shown in the order "1, 10, 11, 12, 2, ..., 9". This has been fixed.

Creating folders with path referring to parent "\..\" not working properly Creating folders with a path referring to a parent such as "\..\" did not work properly. For instance, at Composition > User Settings, on the Settings tab, for Central storage location, a Full path referring to a parent such as "\..\" did not work properly. This has been fixed.

Desktop Background: JPG files not shown on Microsoft Windows Server 2003 At Composition > Desktop > Background, when a .jpg file was selected for Desktop background picture, the background picture was not shown on computers running Microsoft Windows Server 2003. This has been fixed.

Copyright © 1998-2013 RES Software

35

Drive and Port Mappings: Environment Variables with $ADINFO() not working correctly At Composition > Actions By Type > Files and Folders > Drive and Port Mappings, if a Drive mapping was configured for the home drive based on an environment variable that used the $ADINFO() function, the drive mapping would not be performed correctly. The $ADINFO() function was not properly parsed. This has been fixed.

Dynamic Privileges: Drive mappings not always visible Consider the following scenario: 

At Composition > Applications, dynamic privileges for an application were configured on the tab Managed Applications > Security > Dynamic Privileges.



The field Access token was set to Add administrator rights.



At Composition > Files and Folders > Drive and Port Mappings, Drive mappings were configured.



The user was logged on with Administrator privileges.



User Account Control (UAC) was enabled on the user's computer.

In this scenario, the drive mappings made by RES Workspace Manager were not visible from the application that was started with Dynamic privileges. This has been fixed.

Dynamic Privileges: Not working correctly in combination with Microsoft's tool SubInACL Consider the following scenario: 

At Composition > Applications, 'SubInACL', a Microsoft command-line tool, was configured as a managed application.



On the Security > Dynamic Privileges tab of the managed application 'SubInACL', the Access token was set to Add administrator rights.

In this scenario, the application reported the following error: 'insufficient or missing privileges' This has been fixed.

E-mail Settings: Additional mailboxes in Microsoft Outlook sometimes displayed with identifier instead of name At Composition > Applications > E-mail Settings, if an additional mailbox for Microsoft Exchange Server was created, this mailbox would sometimes be shown in Microsoft Outlook with a Globally Unique Identifier (GUID) as its name instead of its proper name. This has been fixed.

Copyright © 1998-2013 RES Software

36

Environment Variables: Second and third parameter of "$substring" cannot contain another "$substring" Consider the following scenario: 

At Composition > Actions By Type > Environment Variables, on the Environment Variables tab, a new environment variable was configured with the function $substring specified for Value (Properties tab) where the starting point and the number of characters to be selected were both defined by separate $substrings.

In this scenario, the environment variable did not work correctly, as the second and third parameter could not contain another $substring. This has been fixed.

Error message: Sometimes error when server was restarted When a server was restarted, an error such as "New connection settings not valid (database->@\)......" could appear in the common error log (at Diagnostics > Errors). This has been fixed.

Execute Command: Actions configured with Run using Dynamic Privileges not always executed Consider the following: 

At Composition > Execute Command, on the Properties tab of a Command, Run using Dynamic Privileges was enabled.



At Composition > Execute Command, on the Script tab a script was defined with vsb as File extension of script.

On Microsoft Windows Vista or higher, the script would fail to be executed. This has been fixed.

Execute Command: Dynamic Privileges not working At Composition > Action By Type > Execute Command, when a Command was configured with Run using Dynamic Privileges enabled, the task in the Command line would fail to start if the Command line contained one or more parameters. This has been fixed.

Execute Command: Executing an external task using a script sometimes not working At Composition > Actions By Type > Execute Command, on the Properties tab of a Command, if Wait for task to finish before continuing was NOT enabled and a script was defined on the Script tab, this could result in the following error: "Cannot find script file" This has been fixed.

Copyright © 1998-2013 RES Software

37

Folder Synchronization: Not working correctly after upgrade to RES Workspace Manager 2012 SR2 Consider the following scenario: 

At Composition > Actions By Type > Files and Folders > Folder Synchronization, on the Settings tab, Folder Synchronization was enabled.



At Composition > Actions By Type > Files and Folders > Folder Synchronization, on the Synchronizations tab, a folder synchronization was configured.



On the Filters tab of the New/Edit folder synchronization window, Files to include were configured.

In this scenario, after upgrading to RES Workspace Manager 2012 SR2, the files that were synchronized were not restricted to the files that were configured to be included in the synchronization. This has been fixed.

Instant Passthrough: Not working with Citrix Worker Groups At Setup > Integration > Application Virtualization > Citrix XenApp Publishing, on the Defaults > Published Application tab, if Citrix Worker Groups were selected as Configured Servers, Instant Passthrough did not work. This has been fixed. Note 

If you are using a Relay Server for your Citrix XenApp 6.5 Host Only servers, it is necessary to upgrade to Relay Server 2012 SR3 for this fix to work.



Refreshing Citrix Worker Groups from the RES Workspace Manager Console is not available for Citrix XenApp 6.5 Host Only servers.

Instant Reports: Incomplete Instant Reports Instant Reports generated via Action > Create Instant Report were incomplete for several features: 

Agents (at Administration > Agents): the Instant Report would miss the setting Datastore Connection (including its sub settings) for any configured Workspace Exception.



Website Security (at Security > Applications > Websites): the Instant Report would miss the setting Security method.



Microsoft TS RemoteApp integration (at Setup > Integration > Microsoft TS RemoteApp): the Instant Report would miss the setting Enable "Microsoft TS RemoteApp Publishing" by default.

These issues have been fixed.

Licensing: License error when new users logged on to laptop for first time Consider the following scenario: 

A new user logged on to a RES Workspace Manager managed laptop for the first time.



At logon, the database could not be reached to obtain a RES Workspace Manager license and no license was reserved for this user.

In this scenario, the user would immediately receive a message that no license was available. This has been fixed. Now, the message that no license is available will only appear if no license could be obtained within 10 minutes after logon.

Copyright © 1998-2013 RES Software

38

Licensing: Reminder for 45 days sometimes not counting down Consider the following scenario: 

At Setup > Licensing, on the Licenses tab, Continue with reminder for 45 days was selected for If no license available at logon.



CLSID code pages were used within the organization.



No RES Workspace Manager license was activated.

In this scenario, the Status of RES Workspace Manager would not count down from 45 days. This has been fixed.

Locations and Devices: Zone rules based on computer NetBIOS or FQDN name not working properly At User Context > Locations and Devices, when adding or changing a Zone rule based on Computer name, clicking for Filter in the Add/Change Rule window, opens the User Sessions window. In this window, the user can select an existing TS Client name, computer NetBIOS name or computer FQDN name. However, if in the Add/Change Rule window, Computer (NetBIOS) was selected for Type (name), the Filter option was sometimes filled with the computer FQDN name. And when Computer (FQDN) name was selected for Type (name), the Filter option was always filled with the TS Client name. These issues have been fixed.

Microsoft App-V: Audit Trail showed a lot of records for "AppvModelIds" for environments containing a large number of applications At Diagnostics > Audit Trail, the Audit Trail may show a lot of "Edit" and "Delete" records for class "AppvModelIds" for environments containing a large number of Microsoft App-V applications. This has been fixed.

Copyright © 1998-2013 RES Software

39

Microsoft App-V: Collection not always removed after executing action with Microsoft System Center Configuration Manager (SCCM) 2007 and 2012 Consider the following scenario: 

At Setup > Integration > Microsoft System Center, on the Settings tab, Microsoft System Center ConfigMgr Integration was enabled.



At Setup > Integration > Application Virtualization > Microsoft App-V, Microsoft App-V Integration was enabled.



At Composition > Applications, an App-V application was added with the option Use SCCM to deploy App-V application enabled (on the application's Properties > General tab).



In the user session, the user selected Dismiss and notify me when done.



When the user was notified that the application was ready for use, he decided not to run it.

When the user started the application, RES Workspace Manager created a collection on the Microsoft System Center Configuration Manager server to enable the use of SCCM to deploy the AppV application. In this scenario, after the Microsoft System Center Configuration Manager finished the deployment of the App-V application, the collection was not removed. Also, if a reboot was required after the installation of the application was finished, the collection was not removed. Both issues have been fixed.

Microsoft App-V: Multiple Advertisements remained on Microsoft System Center Configuration Manager (SCCM) server after installation finished Consider the following scenario: 

At Setup > Integration > Microsoft System Center, on the Settings tab, Microsoft System Center ConfigMgr Integration was enabled.



An application was configured to be installed and configured when a user would click the application shortcut.

In this scenario, if a user clicked the application shortcut multiple times before the installation was finished, multiple Advertisements were created on the SCCM server, but not all were removed after the installation of the application was finished. This has been fixed.

Network Security: Environment Variables used in Remote address not working correctly Consider the following scenario: 

At Composition > Actions By Type > Environment Variables, on the Settings tab, Environment Variables were enabled.



At Composition > Actions By Type > Environment Variables, on the Environment Variables tab, Environment Variables were set.



At Security > Network Connections, Environment Variables were used in the Remote address (on the Settings tab of the Authorized/Blocked Connection window).

In this scenario, the Environment Variables used in the Remote address did not work correctly. This has been fixed.

Copyright © 1998-2013 RES Software

40

Printers: Connecting printers could cause Console to hang In rare circumstances, connecting printers from the RES Workspace Manager Console could cause the Console to hang. This has been fixed.

Relay Server: Settings for RES HyperDrive and Microsoft App-V ModelIds not copied to cache Settings for RES HyperDrive and Microsoft App-V ModelIds related to the stacking of application icons on the taskbar, were not copied to the cache of the Relay Server. This has been fixed.

Removable Disk Security: Unmanaged shares for removable devices (including shared printers) removed from user session If Removable Disk Security was configured (at Security > Data > Removable Disks), all unmanaged shares for removable devices in a RES Workspace Manager session, including shared USB printers and communication devices, were removed. This has been fixed. Now, instead of the shares for all removable devices, only the shares for removable disks are removed.

RES VDX Integration: Concurrent VDX license claimed at every reconnect Consider the following scenario: 

At Setup > Integration > RES Software > RES VDX, on the Settings tab, RES Virtual Desktop Extender (VDX) integration was enabled.



At Setup > Licensing, on the Licenses tab, no named RES VDX licenses were available, only concurrent licenses.

In this scenario, a concurrent RES VDX license was claimed at every reconnect of a user session. This has been fixed.

RES VDX Integration: Drive Mapping disappeared from client after reconnect Consider the following scenario: 

At Setup > Integration > RES Software > RES VDX, RES Virtual Desktop Extender (VDX) integration was enabled.



At Composition > Actions By Type > Files and Folders > Drive and Port Mappings, drive mappings were configured and the option Also connect all network drives using VDX plugin was enabled (on the Settings tab).

After a reconnect to a remote session, the local drive mappings would not be created. This has been fixed.

RES VDX Integration: Error "All pipe instances are busy" If using RES Workspace Manager in combination with RES VDX, the communication with the VDX Engine could sometimes fail, resulting in the following error in the common error log: "Error 231, All pipe instances are busy" This has been fixed.

Copyright © 1998-2013 RES Software

41

RES VDX Integration: Error "ORA-01465 Invalid hex number (INSERT INTO tblLicenses..." At Setup > Integration > RES Software > RES VDX, on the Settings tab, RES Virtual Desktop Extender (VDX) integration, when RES VDX integration was enabled in a configuration with an Oracle Database, the following error might appear in the common error log: ORA-01465 Invalid hex number (INSERT INTO tblLicenses... This has been fixed.

RES VDX Integration: Local drive mappings did not always reappear after reconnect Consider the following scenario: 

At Setup > Integration > RES Software > RES VDX, on the Settings tab, RES Virtual Desktop Extender (VDX) integration was enabled.



At Composition > Actions By Type > Files and Folders > Drive and Port Mappings, on the Mappings tab, local drive mappings were configured.

In this scenario, the local drive mappings that were managed via RES VDX, did not always reappear after a session reconnect. This has been fixed.

RES VDX Integration: Local logoff message when online connection state and a specific application were configured Consider the following scenario: 

At Setup > Integration > RES Software > RES VDX, RES Virtual Desktop Extender (VDX) integration was enabled and the option End running client applications at log off was selected.



At Composition > Applications, on the Settings tab, When online, start a specific application () instead of a full desktop was selected. 

In the Online Application Properties window, Launch before other actions was selected.

In this scenario, a local logoff dialog window could appear in a user session if an application was closed. This has been fixed.

RES VDX Integration: Remote Drive mappings not created in local session Consider the following scenario: 

At Setup > Integration > RES Software > RES VDX, RES Virtual Desktop Extender (VDX) integration was enabled.



PCoIP technology was used.



At Composition > Actions By Type > Files and Folders > Drive and Port Mappings, remote drive mappings were configured.

In this scenario, the remote drive mappings were not connected in local RES Workspace Manager sessions. This has been fixed. Note For this fix to work correctly, RES VDX 2011 SR4 Revision 9.5.4.4 or higher must be installed.

Copyright © 1998-2013 RES Software

42

RES Workspace Manager Shell: RES VDX setting "Hide client taskbar at session start" not applied on local client Consider the following scenario: 

RES Workspace Manager was used both on a local client and in a remote session.



At Composition > Desktop > Shell, Use RES Workspace Manager Shell as the default shell was selected.



At Setup > Integration > RES Software > RES VDX, Hide client taskbar at session start was set to Yes.

In this scenario, the RES VDX setting Hide client taskbar at session start was not applied on the local client. This has been fixed. Note For this fix to work correctly, RES VDX 2011 SR4 Revision 9.5.4.3 or higher must be installed.

Usage Tracking: Sometimes error when creating Example data Consider the following scenario: 

One OU was defined for an Active Directory domain.



At Setup > Usage Tracking, Example data was created.

In this scenario, the following error could occur: 'Procedure: fysnInitializeDummyOUDataset, Error: (91) Object variable or With block variable not set' This has been fixed.

Usage Tracking Overview: OU membership not always resolved correctly if OU name contained a slash (/) If a user was member of an OU that had a slash (/) in its name, the user's OU membership was not always resolved correctly. At Diagnostics > Usage Tracking Overview, when running the Usage Tracking Viewer, in the OU column on the Sessions tab, the OU was displayed as a GUID instead of its actual path. This has been fixed.

Usage Tracking Viewer: Error when using "DailyMaxUsersforApplication" At Setup > Usage Tracking, on the Application tab of the Usage Tracking Viewer, if the method DailyMaxUsersforApplication was used to get the report Daily maximum users for application, the following error could be shown: "Index was outside the bounds of the array" This has been fixed.

Copyright © 1998-2013 RES Software

43

User Event Log: Error "Microsoft .NET framework version 4.0 or later is missing" Consider the following scenario: 

At Composition > Applications, on the Configuration > Actions tab of an application, an action (e.g. Execute Command) was defined.



In a user session, the application was started or it was closed.

In this scenario, in the User Event Log the following error was logged: "Microsoft .NET framework version 4.0 or later is missing" This has been fixed. RES Workspace Manager checks for the .NET framework as a prerequisite for running Folder Synchronization tasks (i.e. Actions), but if Folder Synchronization is disabled for an environment, errors are no longer logged.

User Event Log: Unexpected Microsoft ConfigMgr message At Diagnostics > User Sessions, the User Event Log could contain the message "Microsoft ConfigMgr software installations finished" although software distribution was disabled (at Composition > Actions By Type > Microsoft ConfigMgr, on the Settings tab). This has been fixed.

User Home Directory: Actions defined for pwruser.ini sometimes not working Consider the following scenario: 

At Composition > Actions By Type > Files and Folders > User Home Directory, on the Actions tab, actions were defined for pwruser.ini.



At Composition > Actions By Type > Files and Folders > Drive and Port Mappings, on the Mappings tab, NO drive mapping existed for the home drive that was defined on the Settings tab of the User Home Directory node.

In this scenario, the actions defined for pwruser.ini, which stores certain user-related settings, would not be performed. This has been fixed.

User Home Directory: Compare or copy actions defined for pwruser.ini not working on new profiles if no home drive was defined Consider the following scenario: 

At Composition > Actions By Type > Files and Folders > User Home Directory, on the Actions tab, a copy or compare action was defined for pwruser.ini.



At Composition > Actions By Type > Files and Folders > Drive and Port Mappings, on the Mappings tab, NO drive mapping existed for the home drive that was defined on the Settings tab of the User Home Directory node.

In this scenario, the actions defined for pwruser.ini, which stores certain user-related settings, would not be performed on a new profile that did not yet contain the pwruser.ini file. This has been fixed.

Copyright © 1998-2013 RES Software

44

User Home Directory: Global settings applied irrespective of workspace exception settings Consider the following scenario: 

At Composition > Actions By Type > Files and Folders > User Home Directory, on the Settings tab, User Home Directory was Disabled.



For a workspace exception User Home Directory was Enabled.

In this scenario, the global settings were always applied, irrespective of the settings of the workspace exception. This has been fixed.

User Registry: Duplicated "Run Once" registry setting not applied At Composition > Actions By Type > User Registry, on the User Registry tab, when a registry setting with the option Run once enabled (Properties tab) was duplicated, the duplicated registry setting was not applied in user sessions. This has been fixed.

User Registry: Items in registry file marked for deletion not imported correctly At Composition > Actions By Type > User Registry, when importing a registry file into RES Workspace Manager, items that were marked for deletion were not imported correctly. This has been fixed.

User Registry: "Run Once" setting not taken into account At Composition > Actions By Type > User Registry, on the User Registry tab, when a registry policy setting with the option Run once enabled (Properties tab) was configured, the policy tasks were reapplied in user sessions after every change. This has been fixed.

User Registry: Scrollbar disappears when resizing window At Composition > Actions By Type > User Registry, when editing a policy, the vertical scrollbar for the tree on the Properties tab would not allow the user to scroll all the way down to the last entry. This has been fixed.

User Sessions: Error in User Event Log when using a non-existing cache location Consider the following scenario: 

At Composition > User Settings, User Setting caching was set to Cache locally at logon and logoff, unless otherwise specified



A non-existing location was given for Cache location (e.g. for clean user profiles)

When a user started a session, the error message "User settings location not available" was logged in the User Event Log (at Diagnostics > User Sessions). This has been fixed.

Copyright © 1998-2013 RES Software

45

User Settings: Central storage location with Full path containing RES Workspace Manager environment variable not properly resolved Consider the following scenario: 

At Composition > Actions By Type > Environment Variables, on the Environment Variables tab, an environment variable was created.



At Composition > User Settings, on the Settings tab, for Central storage location, a Full path was configured containing the environment variable that was created before.

In this scenario, the full path was not properly resolved due to a timing issue. This has been fixed.

User Settings: Empty strings not captured correctly User Settings (both at global level and at application level) can be configured to capture Registry settings. 

On the Properties tab of a User Setting (both at global level (Composition > User Settings) and at application level (Composition > Applications), the Zero Profile mode was set to Capture.



On the Capturing tab of the User Setting, for Targeted items to capture, Registry keys and/or Registry trees and/or Registry values were defined as Targeted items to capture.

It is possible that these captured registry settings included one or more default values whose data was an empty string. When restoring, RES Workspace Manager would change the empty string data to '(value not set)' and an error message could occur in case an application depended on the empty string value. This has been fixed. Default values with an empty string as its data will now be restored as such.

User Settings: Locally cached User Settings sometimes not synchronized At Composition > User Settings, on the Settings tab, when the option User Settings caching was set to Cache locally at logon and logoff, unless otherwise specified, synchronizing User Settings or the user's personal settings folder could sometimes fail with the following error: "Error 231, All pipe instances are busy" This has been fixed.

User Settings: Missing templates for desktop icons At Composition > User Settings, the templates for desktop icons for Microsoft Windows XP, Windows 2003, Windows Vista and Windows 7 that became available in RES Workspace Manager 2012 SR1 Fixpack 9.7.1.1 were missing in the RES Workspace Manager 2012 SR2 release. This has been fixed. These templates can be found as a global User Setting under Windows > Vista or later > Control Panel > Desktop Icons and Windows > XP/2003 > Control Panel > Desktop Icons and only applies to sessions using the Microsoft Windows Shell. In addition, some of the User Settings template names were not translated in the context menus. This has also been fixed.

Copyright © 1998-2013 RES Software

46

User Settings: Registry keys and values containing Environment Variables not always captured Consider the following scenario: 

On the Properties tab of a User Setting (both at global level (at Composition > User Settings) and at application level (at Composition > Applications)), the Zero Profile mode was set to Captured targeted items on application/session end.



On the Capturing tab of the User Setting, for Targeted items to capture, Registry keys and/or Registry values were defined containing Environment Variables.

In this scenario, the capturing of User Settings did not work properly. This has been fixed.

User Settings: Sometimes \pwrmenu was not synchronized after system reboot Consider the following scenario: 

At Composition > User Settings > Settings, User Settings caching was configured.



The user's system was rebooted.

Sometimes, the \pwrmenu folder was not synchronized. This has been fixed.

User Settings: Sometimes incorrect error that restoring User Settings failed At Diagnostics > User Sessions, when restoring User Settings, sometimes an error was given that restoring the User Settings failed, although it had been successful. This incorrect error was caused by a timeout that was set to 1 second for communication between pwrcache.exe and resop.exe. This has been fixed. The timeout has been increased to 5 seconds.

User Settings: Sometimes not loaded correctly Consider the following scenario: 

At Composition > User Settings, on the Properties tab of a User Setting, Load in background after session started was set for Apply.



At Composition > Applications, on the User Settings > Properties tab of an application, Prefetch in background, check on application start was set for Apply.

In this scenario, the application or global User Settings were sometimes missing or not loaded correctly. This has been fixed.

Copyright © 1998-2013 RES Software

47

Workspace Composer: 64-bit icon of Microsoft Internet Explorer pinned to taskbar Consider the following scenario: 



At Composition > Applications, on the Settings tab: 

Windows Shell shortcut creation was set to Merge with unmanaged shortcuts.



Active Setup was enabled.

A user with a new or mandatory user profile logged on to a 64-bit Operating System with Microsoft Internet Explorer 9 or earlier installed.

In this scenario, in user sessions with RES Workspace Manager SR2 Fixpack 5 or later, a default Microsoft Internet Explorer icon was pinned to the taskbar, pointing to the 64-bit version of the application. After upgrading to RES Workspace Manager SR3, a default Microsoft Internet Explorer icon will be pinned to the taskbar, pointing to the 32-bit version of the application. This is default behavior of Microsoft Windows.

Workspace Composer: Active Setup not always executing .vbs scripts At the startup of user sessions, .vbs scripts that should run during Active Setup were not always running. This has been fixed.

Workspace Composer: Application focus changed after session reconnect After a session reconnect, application focus could switch to another application while the user was working in the first application. This has been fixed.

Workspace Composer: Certain unmanaged icons not stacked properly on taskbar If a user pinned the unmanaged application Microsoft Windows Explorer to the taskbar and started the application from there, the windows on the taskbar icon were not stacked correctly. This has been fixed.

Workspace Composer: Client IP address not always resolved correctly during logon Under rare circumstances the client IP address was not resolved correctly during logon. This has been fixed.

Workspace Composer: Common Startup folder not applied for a user with a new profile Consider the following scenario: 

At Composition > Applications, on the Settings tab, Disable Active Setup (skips first-time shell init) was not selected.



At Composition > Desktop > Shell, Use Microsoft Windows Shell as the default shell was selected.

If a user with a new profile logs on to the RES Workspace Composer, Active Setup will be executed. In this scenario, the startup items that are stored in the common Startup folder were not applied for that user. This has been fixed.

Copyright © 1998-2013 RES Software

48

Workspace Composer: Communication with the WMSync process sometimes not possible Under rare circumstances, the following error was reported in the Windows Event Log for the WMSync process: "Pipe is being closed" This error was reported regardless of whether local User Setting caching was enabled or disabled (globally at Composition > User Settings > Settings or per application at Composition > Applications, on the User Settings > Properties tab of the application). This has been fixed.

Workspace Composer: Custom icons not displayed correctly Consider the following scenario: 

At Composition > Applications, an application was added with a custom icon.



The end user worked on a machine running Microsoft Windows 7 or higher.



In Microsoft Windows, in the Taskbar and Start Menu Properties, on the Taskbar tab, Use small icons was selected.

In this scenario, the application icons were not displayed correctly. This has been fixed.

Workspace Composer: Default printer removed from pwruser.ini Under some circumstances, the default printer value in the pwruser.ini file was cleared. This could particularly happen when a fresh pwruser.ini file (including a default printer) was recently copied at Composition > Action by Type > Files and Folders > User Home Directory. This has been fixed.

Workspace Composer: Desktop icons aligned to the left after user workspace was refreshed twice in short period of time If a user workspace was refreshed twice in a short period of time, all desktop icons could be aligned to the left of the screen. This could happen, for instance, when a laptop resumed from a hibernate state and reconnected to the network. This has been fixed.

Workspace Composer: Dismiss and notify functionality only available in English If a user selects a new application, the application first needs to be installed before the user can start using the application. The Dismiss and notify me when done functionality allows users to continue working with other applications during the installation of the new application. The Dismiss and notify me when done functionality is now available in all languages that are supported by RES Workspace Manager. Previously this functionality was only available in English.

Copyright © 1998-2013 RES Software

49

Workspace Composer: Drive mappings and Drive substitutes not always applied correctly when computer resumed after network change Consider the following scenario: 

A Drive mapping (at Composition > Files and Folders > Drive and Port Mappings) and/or a Drive substitute (at Composition > Files and Folders > Drive Substitutes) was configured with a dependency on connection state.



A computer went into standby mode.



The computer's connection state changed.

In this scenario, the Drive mapping and/or Drive substitute were not always applied correctly in a user session when the computer resumed after being in standby mode. This has been fixed. Please note, for this fix to work properly, the following option needs to be set: 

At Setup > Advanced Settings, fill in a delay for # seconds to wait before refreshing after network change or resume.

This delay will allow RES Workspace Manager to retrieve the connection state before a refresh occurs, allowing Drive mappings and Drive substitutes to be applied correctly in a user session.

Workspace Composer: Drive substitute not shown correctly in Windows Explorer in offline session Consider the following scenario: 



A Drive mapping (at Composition > Files and Folders > Drive and Port Mappings) was configured: 

Device was set to X:.



Share name was set to a network drive (e.g. \\serverX\pathX).



Required connection state was set to Online connection.

A Drive substitute (at Composition > Files and Folders > Drive Substitutes) was configured: 

Virtual drive was set to X:.



Physical drive and path was set to C:\Temp.



Required connection state set to Offline connection.



At Composition > Files and Folders > Drive and Port Mappings, on the Settings tab, Refresh Drive and Port Mappings when network connectivity changes was selected.



At Composition > Files and Folders > Drive Substitutes, on the Settings tab, Refresh Drive Substitutes when network connectivity changes was selected.



At Composition > Desktop > Lockdown and Behavior, in the section Workspace Composer, the setting Do not refresh Workspace when network connectivity changes was NOT selected.

In this scenario, in a user session, in Windows Explorer, X: was shown as a network location. Unplugging the network cable caused the user session to be refreshed. After this refresh, in Windows Explorer, X: was still shown as a network location, but one that was disconnected. Clicking the network location X: would open the local path as it was configured in the Drive substitute. This has been fixed. The Drive substitute is now shown correctly in Windows Explorer after a network connectivity change.

Copyright © 1998-2013 RES Software

50

Workspace Composer: Empty Recently Opened Programs list in Start Menu Consider the following scenario: 

A new user profile was created



At Composition > Applications > Settings, the Windows Shell shortcut creation was set to Merge with unmanaged shortcuts.



A new RES Workspace Manager user session was started

The Recently Opened Programs list in the user's Start Menu would be empty. This has been fixed.

Workspace Composer: Empty Startup folder sometimes shown in Start Menu At Composition > Applications, on the Settings tab, when the option Remove empty menus was selected, an empty Startup folder could still be shown in the user's Start Menu. This has been fixed.

Workspace Composer: Environment Variables used in path of backup printer not resolved At Composition > Actions By Type > Printers, if a printer was configured as a backup printer (by selecting the Failover option) and Environment Variables were used in the path, the Environment Variables were not resolved in the user session. This has been fixed.

Workspace Composer: Error opening multiple Microsoft Outlook .msg files If a user opened multiple Microsoft Outlook .msg files one after the other, this could result in the following error: "(67) Too many files" This has been fixed.

Workspace Composer: Force Logoff message shown in shutdownblocker Consider the following scenario: 

At Composition > Desktop > Shell, Use Microsoft Windows Shell as the default shell was selected.



The end user worked on a machine running Microsoft Windows Vista or Microsoft Windows 7 (64bit).

In this scenario, a "Force Logoff" message was shown in the shutdownblocker. This has been fixed.

Workspace Composer: Google Chrome and Lotus Notes icons not stacked properly on taskbar If the applications Google Chrome or IBM Lotus Notes were started from their corresponding pinned taskbar item, the application did not stack correctly onto its pinned taskbar icon in Microsoft Windows 7 and 2008 R2. This has been fixed.

Copyright © 1998-2013 RES Software

51

Workspace Composer: Icon issues with Microsoft Internet Explorer 10 The following issues regarding Microsoft Internet Explorer 10 have been fixed: 

After installation, two Microsoft Internet Explorer icons could be pinned to the taskbar.



When clicking the Microsoft Internet Explorer icon, the application sometimes did not stack properly onto its pinned taskbar icon.

Workspace Composer: Icons for managed shortcuts sometimes appeared twice on desktop Under certain circumstances, the icon for a managed application appeared twice on the desktop. This has been fixed.

Workspace Composer: Icons reappeared on desktop after having been deleted Consider the following scenario: 

At Composition > Applications > Settings, the Windows Shell shortcut mode was set to Merge with unmanaged shortcuts.



An end user manually deleted a managed shortcut from the desktop (not via Workspace Preferences).

In this scenario, the deleted shortcut reappeared on the end user's desktop when the end user logged off and on again. This has been fixed.

Workspace Composer: Inetres.adm policy not applied correctly If the Microsoft Internet Explorer policy setting Site To Zone Assignment List in the Inetres.adm policy file was configured in the RES Workspace Manager Console, it was not applied correctly in user sessions. This has been fixed.

Workspace Composer: Installation of Microsoft Windows Automatic Updates with insufficient privileges could result in unmanaged session To install Microsoft Windows Automatic Updates in a user session, a user needs local administrator rights. If the user did not have sufficient privileges, and Automatic Updates were installed, after which RES Workspace Manager wanted to restart the system to complete the updating process, Microsoft Windows would stop the shutdown. This resulted in an unmanaged user session. This has been fixed. Now, RES Workspace Manager will ignore Automatic Updates if the user has insufficient privileges.

Workspace Composer: Items in Start Menu or pinned to taskbar sometimes in wrong language Consider the following scenario: 

At Composition > Applications, on the Settings tab, the Windows Shell shortcut creation was set to Merge with unmanaged shortcuts.



On a workstation running Microsoft Windows 7, the display language differed from the installed language.

In this scenario, the items in the user's Start Menu or pinned to taskbar items sometimes did not show titles in the proper display language. This has been fixed. Copyright © 1998-2013 RES Software

52

Workspace Composer: Lock Desktop not working correctly Consider the following scenario: 

At Composition > Applications, on the Settings tab, Replace all unmanaged shortcuts was selected for Windows Shell shortcut creation.



At Composition > Desktop > Screensaver, Screensaver Composition was Disabled.

In this scenario, if a user selected the Lock Desktop icon, this could give unpredictable results. This has been fixed.

Workspace Composer: Microsoft .Net errors in User Event Log On a Terminal Server, the following error could be logged in the User Event Log of every user session: "Microsoft .NET Framework version 4.0 or later is missing" This has been fixed.

Workspace Composer: Microsoft Windows Active Setup did not work properly if "stubpath" contained white spaces If customers implemented their own Active Setup of Microsoft Windows components, this did not always work properly with RES Workspace Manager 2012 SR2. This problem occurred if the "stubpath" definition contained white spaces (e.g. due to the use of command line parameters) that were not enclosed in quotes. This has been fixed.

Workspace Composer: Out of memory error when loading User Settings or starting an application In RES Workspace Manager sessions, the error "Input past end of file" (#62) could appear in the common error log at the startup of the Workspace Composer when loading User Settings or when an application was started. This has been fixed.

Workspace Composer: PowerShell and Server Manager icon incorrectly pinned to taskbar Consider the following scenario: 

At Composition > Applications, on the Settings tab, Windows Shell shortcut creation was set to Replace all unmanaged shortcuts and the option Disable Active Setup (skips first-time shell init) was selected.



A user session was started on a Terminal Server with a new or mandatory profile.

In this scenario, a PowerShell and Server Manager icon would be pinned to the taskbar. This has been fixed.

Copyright © 1998-2013 RES Software

53

Workspace Composer: Prevent unnecessary notification messages about default printer change just after logon Shortly after logon, if printers were connected asynchronously, one or more notification messages regarding changing the default printer were shown in the user session. This has been fixed.

Workspace Composer: pwrgate.exe sometimes consumed 100% CPU time Under rare circumstances, pwrgate.exe consumed 100% CPU time. This has been fixed.

Workspace Composer: Redirecting %AppData% and sub directories not working correctly Consider the following scenario: 

In the RES Workspace Manager Console at Composition > Actions by Type > Files and Folders > Folder Redirection, on the Redirections tab, the Windows folder AppData was redirected.



The end user worked on a machine running Microsoft Windows Vista or higher.



Folder Redirection on %AppData% failed.

When Folder Redirection on a redirected folder fails, RES Workspace Manager has the fallback to set registry keys for the redirected folder and its sub directories. In this scenario, the following sub directories were missing in the fallback routine: 

Recent



PrintHood



Templates



AdminTools

This has been fixed.

Workspace Composer: Repetitively clicking the splash screen during logon could stop the Workspace Composer from working During logon, if a large number of User Settings needed to be loaded, the user could stop the Workspace Composer by repetitively clicking the RES Workspace Manager splash screen. Several improvements have been made to reduce the chance of this behavior reoccurring.

Workspace Composer: Replaced icons for (un)managed shortcuts sometimes disappeared or became blank after logging off and on again At Composition > Applications > Settings, if the Windows Shell shortcut creation was set to Merge with unmanaged shortcuts, some unmanaged applications (e.g. the Microsoft Windows applications Sticky Notes and Snipping Tool) that were pinned to the taskbar were no longer available or became blank icons after logging off and on again. Also, when the user manually pinned managed applications to the Start Menu, these icons could also become blank after logging off and on again. Both issues have been fixed. Note To resolve the issue of blank icons, after installing the Fixpack, all blank icons must once be manually unpinned and repinned to the taskbar/Start Menu. Copyright © 1998-2013 RES Software

54

Workspace Composer: RES Subscriber not working after reconnect When RES Subscriber 2010 SR2 was installed, the RES Subscriber icon in the system tray stayed red after a RES Workspace Manager session reconnected from the same client. This has been fixed.

Workspace Composer: "Run as different user" not always working correctly Consider the following scenario: 

At Composition > Desktop > Shell, Use Microsoft Windows Shell as the default shell was selected.



In the Workspace Composer, an application was started with Run as different user.

In this scenario, the credentials specified for Run as different user were not used when the application was started. Instead, the credentials of the logged on user were used. This has been fixed. Note When an application is started using Run as different user, only the settings that are related to the start of the application (configured on the Properties > Settings tab of the application), are applied. These settings are: 

Startup style of application



Process priority of application



Disable file system redirector on 64-bit systems

Actions configured for the application (on the Configuration > Actions tab of the application) will not be applied.

Workspace Composer: ScreenSaveActive containing an empty string could cause error When the registry value ScreenSaveActive was set in a user session and it contained an empty string, the following error could appear in the common error log (in the Console at Diagnostics > Errors): Procedure

SetScreenSaveTimeout

Error #

13

Error description

Type mismatch

This has been fixed.

Workspace Composer: Session may hang during workspace refresh Consider the following scenario: 

In a RES Workspace Manager session, Imprivata solutions were used.



The RES Workspace Manager session was running for several days.

In this scenario, when the session would be refreshed, it could hang for several minutes. This has been fixed.

Copyright © 1998-2013 RES Software

55

Workspace Composer: Shortcut for Microsoft Internet Explorer not created in new (mandatory) profiles after RES Workspace Manager finished active setup At Composition > Applications, on the Settings tab, if Disable Active Setup (skips first-time shell init) was not selected, after RES Workspace Manager finished the active setup, no shortcut was created on the taskbar for Microsoft Internet Explorer in user sessions with a new (mandatory) profile. This has been fixed.

Workspace Composer: Slow startup in environment with multiple domains If multiple NT or Active Directory domains were configured in an environment, the startup of the Workspace Composer could be very slow. This has been fixed.

Workspace Composer: Some registry settings not applied during reconnect Consider the following scenario: 

At Composition > Action By Type > Execute Command, commands were configured to execute registry settings such as ForceDisconnectOnIdle.



The command was configured to run the task At reconnect session.

In this scenario, these registry settings were not applied during a reconnect. The current settings were applied in the Workspace Composer before the scheduled Task had run. This has been fixed. Note For this fix to work correctly, the setting Wait for task to finish before continuing must be selected for these commands.

Workspace Composer: Startup preferences sometimes disappeared Consider the following scenario: 

In Workspace Preferences, on the Startup tab, applications were configured to be started at startup.



At Composition > Applications, in the Access Control section of the application, access to some of the applications the user configured to be started at startup were made dependent on context (e.g. only access when user session is online, no access if user session is offline).

In this scenario, when the user session changed context and changed back again (e.g. the user session went from online to offline and back again), the items that were configured on the Startup tab of the Workspace Preferences could have disappeared. This has been fixed.

Copyright © 1998-2013 RES Software

56

Workspace Composer: System application not localized in time Consider the following scenario: 

At Composition > Desktop > Lockdown and Behavior, Always hide "Workspace Preferences" in menu was selected.



At Composition > Applications, an application was added to the Start Menu with: 

the Command line C:\Program Files (x86)\RES Software\Workspace Manager\pwrgate.exe.



Parameters was "8".

In this scenario, this system application was not localized in time. As a result, in Workspace Preferences, at Available applications on the Start Menu tab, the application description "3" was shown. This has been fixed.

Workspace Composer: Taskbar might disappear unexpectedly Consider the following scenario: 

At Composition > Desktop > Shell, Use RES Workspace Manager Shell as the default shell was selected.



In a RES Workspace Manager session, Imprivata solutions were used.

In this scenario, the taskbar sometimes disappeared unexpectedly. This has been fixed.

Workspace Composer: Unmanaged pinned taskbar items sometimes disappeared At Composition > Actions By Type > Files and Folders > User Home Directory, on the Settings tab, if a new Default home drive was configured (in this case no pwruser.ini file would exist for the user), unmanaged pinned taskbar items could disappear after the user started a RES Workspace Manager session for the first time. This has been fixed.

Workspace Composer: User defined default mail profile for Microsoft Outlook not saved In a user session, if the user added a new default mail profile in Microsoft Outlook, this new default profile was not saved. When closing and starting up Microsoft Outlook again, the old default profile would be loaded. This has been fixed.

Copyright © 1998-2013 RES Software

57

Workspace Composer: Voluntary shortcuts were restored after user removed them Consider the following scenario: 

In the Console, at Composition > Applications, on the Properties > General tab of application "A", the Automatic Shortcut option for Desktop was configured as Set voluntary shortcut.



In a RES Workspace Manager session, in the Workspace Preferences, on the Start Menu tab:





the option Display all available applications in Start Menu was not selected.



application "A" was selected to be displayed in the Start Menu.

In the RES Workspace Manager session, the user removed the voluntary shortcut from the desktop.

In this scenario, in the user session, if a user added or removed any application to/from the Start Menu and the workspace was refreshed, the application icon that was removed before would automatically be added to the desktop again. This has been fixed.

Workspace Composer: Wrong protocol assumed when connecting to Citrix XenDesktop session via RDP When connecting to a Citrix XenDesktop session, RES Workspace Manager assumes the protocol is ICA. When connecting to a Citrix XenDesktop session via RDP, this assumed protocol is wrong. In that case, for instance, RES VDX did not work. This has been fixed. RES Workspace Manager now checks the protocol for Remote Sessions.

Workspace Composer: XML errors when computer name started with a digit (0-9) When a computer name started with a digit (0-9), logging on or off an RES Workspace Manager session could result in XML errors when reading or writing to the pwruser.xml file. This has been fixed.

Workspace Containers: Scrollbar not working in read-only mode Consider the following scenario: 

Throughout the Console, the Access Control > Workspace Containers window was opened in read-only mode.



In that window, Specific workspace containers was selected.

In this scenario, the scrollbar to scroll through the list of Workspace Containers was not working. For instance, if there were a large number of Workspace Containers configured, and a Workspace Container at the bottom of the list was selected, it was not possible to scroll to this Workspace Container. This has been fixed.

Copyright © 1998-2013 RES Software

58

Disclaimer Whilst every care has been taken by RES Software to ensure that the information contained in this publication is correct and complete, it is possible that this is not the case. RES Software provides the publication "as is", without any warranty for its soundness, suitability for a different purpose or otherwise. RES Software is not liable for any damage which has occurred or may occur as a result of or in any respect related to the use of this publication. RES Software may change or terminate this publication at any time without further notice and shall not be responsible for any consequence(s) arising there from. Subject to this disclaimer, RES Software is not responsible for any contributions by third parties to this publication. Copyright Notice Copyright © on software and all Materials 1998-2013 Real Enterprise Solutions Development BV, P.O. Box 33, 5201 AA `sHertogenbosch, The Netherlands. RES and the RES Software Logo are either registered trademarks or service marks of Real Enterprise Solutions Nederland B.V. in Europe, the United States and other countries. RES Automation Manager, RES Workspace Manager, Dynamic Desktop Studio, Virtual Desktop Extender and RES VDX are trade names of Real Enterprise Solutions Nederland B.V. in Europe, the United States and other countries. All other product and company names mentioned may be trademarks and/or service marks of their respective owners. Real Enterprise Solutions Development BV, The Netherlands has the following patents: U.S. Pat. "US 7,433,962", "US 7,565,652", "US 7,725,527", other patents pending or granted.

lix