RG02B – Guide to Workspace Manager registry

 

By Max Ranzau

 

regedit-supericonThis article is based on the old article RG005 PowerFuse Tips and Tricks, which was published back in 2009. Plenty has happened since then, so it seemed like a good idea to move the registry settings to a  seperate dedicated technote. I have plowed through tonnes of releasenotes and available documentation to compile this list. Here you can learn how to tweak the behavior of RES Workspace Manager.  Where possible I will try to include what release/version the registry settings are valid from.

Note1: You are likely to see a setting available from a given service release and update pack. If you are running the next service release or a newer product version, you likely already have the given functionality as the service releases are cumulative, i.e. they contain all the previous update packs which also have been regression tested together. Only exception is if for one reason or another it has been decided to remove the feature.

Note2: Required values below may be marked with a hashmark (#) or a percentage sign (%). The hashmark indicates that the required value is a numeric value, regardless of the value’s datatype. Percent indicates a string value. If nothing else is specified, the value is simply just the stringvalue Yes.

Use the jump-links provided below to skip to the section you’re interested in. Newer registry tweaks will be tend to be towards the top. Clicking an up-arrow ( ^ ) will return you to the top of the index.


 

Update Nov 21st 2014:

095 – Relay Server, configure custom certificates

094 – Relay Server, set duration window for datastore cleanup

093 – Fix for problem with opening unicode char filenames

092 – Lower connection timeout to Relay Server

091 – Fix multiple IE instance problem on Win 8.1

090 – Fix overlapping desktop icons

089 – Revert to old drive-refresh method

088 – Always show search field in Application List

087 – Citrix XenApp 7.x: bring back Session Lingering

086 – Relay Server, prevent daily obsolete log cleanup

085 – VDI: Store update-GUID’s on disk instead of registry

084 – SCCM App, configure startup delay

083 – Relay Server, enable additional encryption.

082 – Prevent SCCM App-V OSD reset

081 – Enable Process intercepting for Citrix XenDesktop 7

Update: Dec 3rd 2013

080 – Stop WM from creating pwrgate based shortcuts

079 – Prevent WM Sync from launching

078 – Fix save problem with saving Outlook MAPI profile

077 – Force Citrix XA server into Host-Only mode

076 – Resolve client IP address from DNS

075 – Workaround for SCCM launch of App-V

074 – Disable CPUshield process completely

073 – Speed up console access to certain apps

072 – Fix problem at logoff from Citrix server

071 – Fix Outlook’s NewMail Desktop Alert / Languages

070 – Auto-correction list of Word user setting fix

069 – Remote control fix

068 – Fix for published system-tray apps

067 – Citrix XenApp Publishing – Session sharing fix

066 – Boost performance starting an offline WM user session

065 – Prevent memoryleak when “CheckShutdown” used

064 – Connect printers restored from User Settings

063 – Suppress taskbar icons of Workspace Extended apps

062 – Change default AppID for PWRGATE.EXE

061 – Suppress Show/Hides Desktop button on taskbar

060 – Configure delay before Workspace Composer starts

059 – Disable shell folders created when User Settings enabled

058 – Extend Active Directory enumeration timeout

057 – Fix blank icons for active App-V apps

056 – Change Webguard message settings

055 – Tweak Oracle DB size check behavior

054 – Modify ActiveSetup timeout

053 – Change default AppID for PWRgate.exe

052 – Configure silent refresh

051 – Fix problem opening .CSV files from Internet Explorer

050 – Enable process to be started, called as a process.

049 – Prevent apps from changing size of workarea in RES Shell

048 – Change how Desktop Sampler reads computer/client name

047 – Fix Win7 Recent Docs not working after upgrade

046 – Fix ‘From’ field in Outlook 2010

045 – Locate printers by subnet for workstations

044 – Fix issue with starting Winword from within Navision

043 – Fix issue with opening UNC path from an app in PFshell

042 – Do not preceed RES published apps with a backslash

041 – Fix for Winword/Reference Manager problem

040 – Change local taskbar behavior of VDX

039 – Allow Desktop shortcuts to unmanaged applications

038 – Enable WM performance analysis dump file

037 – Disable connection string pickup via DCHP option

036 – Force enumeration of redirected folders from registry

035 – Correct behavior of dl-manager launched pub apps

034 – Fix Thinapp runtime error in a XenDesktop env.

033 – Folder Synchronization: Ability to use network drives

032 – Preserve QuickLaunch shortcuts on Win 7

031 – Fix slow logons due to SRS files in Outlook Folder

030 – User Settings: Configure compression interval

029 – Change timeout for password change in Workspace Prefs

028 – Fix low-resolution icons pinned on Start Menu

027 – Enable console legacy application mode

026 – Enable classic blanking splash screen on refresh

025 – Settings for Desktop Sampler

024 – Configure Agents to force shutdown

023 – Configure behavior of ALLUSERSPROFILE variable

022 – VDX: Set wait time before establishing connection

021 – Prevent Outlook 2k3 from launching Word 2k3 embedded

020 – Allow Windows Run keys to execute

019 – Only hide splashscreen

018 – Force DISCONNECT after idle-timeout

017 – Enable asyncronous build of the start menu

016 – Force LOGOFF after idle-timeout

015 – Avoid privacy issues displaying concurrent license usage

014 – Read-only-Blanketing: Do not remove admin shares

013 – Display the taskbar only on the primary display

012 – Override the alteration of the Citrix Explorer Hook

011 – Change location of the Workspace Manager cache

010 – Force rebuild the Workspace Manager cache

009 – Managing global WM settings on an individual computer

008 – Database connection settings

007 – Configure cache update interval

006 – Disable screensaver when VDX is active

005 – Force LogOff of disconnected sessions after timeout

004 – Silently refresh RES Workspace Manager sessions

003 – Tweak how Memoryshield counts application instances

002 – Make WM use AD “displayname” instead of “fullname”

001 – Tweak how User Installed Applications authorizes

000 – Enable Workspace Manager trace mode

 


 

095 – Relay Server, configure custom certificates

HKLM\Software\RES\Workspace Manager\RelayServer\CustomCertificate (REG_SZ) = identifier*
HKLM\Software\RES\Workspace Manager\RelayServer\CustomCertificateStoreFindBy(REG_SZ) = Thumbprint|SerialNumber

HKLM\Software\RES\Workspace Manager\RelayServer\CustomCertificateStore(REG_SZ) = folder*

Posted Nov 20th 2014. Valid from RES Workspace Manager 2014 SR2 (9.9.2.0) As of this release, RES Workspace Manager supports the use of custom certificates for the connection between an RES Agent (RES service) and a Relay Server, and between Relay Servers. With the use of custom certificates, RES Workspace Manager offers enhanced authentication. Previously only self-signed certificates were used for these connections. Use the directions below to fill in the above registry settings correctly

CustomCertificate: By default, the field “Subject name” will be used to identify the custom certificate in the certificate store. Use this value for identifier*. With the registry value CustomCertificateStoreFindBy the certificate’s Thumbprint or SerialNumber can also be used to identify it in the certificate store. See entry below:

CustomCertificateStoreFindBy: As mentioned above, by default, the “Subject name” field will be used to identify the custom certificate in the certificate store. However, with the registry value CustomCertificateStoreFindBy, the custom certificate can alternatively be identified by its Thumbprint or SerialNumber. When setting this registry value to either of these two values, make sure to specify the correct data for the registry value CustomCertificate above.

CustomCertificateStore: By default, the Relay Server will look for the custom certificate in the “Personal” folder in the local certificate store. With the registry value CustomCertificateStore, a different folder* in the certificate store can be specified. In case a non-English version of Microsoft Windows is being used, the Microsoft Windows internal folder names must be specified for certificate data. The supported Windows internal certificate store folder names are specified below: ^

Windows internal folder name
Foldername, Windows, English
Root Trusted Root Certification Authorities
CertificateAuthority Intermediate Certification Authorities
TrustedPublisher Trusted Publishers
Disallowed Untrusted Certificates
AuthRoot Third-Party Root Certification Authorities
TrustedPeople Trusted People
AddressBook Other People

 

094 – Relay Server, set duration window for datastore cleanup

HKLM\Software\RES\Workspace Manager\RelayServer\DBCleanupDuration(REG_DWORD) = 0..24 (hours)

Posted Nov 20th 2014. Valid from RES Workspace Manager 2014 SR2 (9.9.2.0) Obsolete log files and obsolete Usage Tracking data are cleaned up on a daily basis. RES Workspace Manager will start (or continue) with the daily cleanup of the Datastore at the time configured at Setup|Advanced Settings (obsolete log files) and Setup|Usage Tracking (obsolete Usage Tracking data).
For Relay Servers that are connected directly to the Datastore, the duration of the daily cleanup can now be specified, or more to the point: limited. This can be done by setting the above registry value to limit the amount of time where cleanup may occur. If the duration is not specified, the daily cleanup is not time limited (default behavior) and will continue until finished.  ^

 

093 – Fix for problem with opening unicode char filenames

x86: HKLM|HKCU\Software\RES\Workspace Manager\KeepUnicodePath (REG_SZ) = Yes
x64: HKLM|HKCU\Software\Wow6432Node\RES\Workspace Manager\KeepUnicodePath(REG_SZ) = Yes

Posted Nov 20th 2014. Valid from RES Workspace Manager 2014 SR2 (9.9.2.0) Under certain circumstances, when opening a Microsoft Word document that contained a lot or special Unicode characters, the document would open with an 8.3 file name (also called short filename or SFN). This might result in Microsoft Word interpreting the file as a .doc file instead of the original format, for instance .docx. This has been fixed, but to make it work you’ll have to implement the above regsetting for some reason. By doing that, the original file name will be kept and an 8.3 file name will never be applied in an Workspace Manager session. ^

 

092 – Lower connection timeout to Relay Server

x86: HKLM\Software\RES\Workspace Manager\RSConnectTimeout (REG_SZ) = 1..9 (sec)
x64: HKLM\Software\Wow6432Node\RES\Workspace Manager\RSConnectTimeout(REG_SZ) = 1..9 (sec)

Posted Nov 20th 2014. Valid from RES Workspace Manager 2014 SR2 (9.9.2.0) In situations where a user logged on to a session and the connection to a Relay Server was not available, the user could experience slow logon times. This has been resolved. Every Relay Server that is not available will cause a 10-second delay, because the default connection wait time is 10 seconds. To lower the number of seconds of this delay, the above registry value can be set.  ^

 

091 – Fix multiple IE instance problem on Win 8.1

x86: HKLM\Software\RES\Workspace Manager\EnableMultipleIE (REG_SZ) = Yes
x64: HKLM\Software\Wow6432Node\RES\Workspace Manager\EnableMultipleIE(REG_SZ) = Yes

Posted Nov 20th 2014. Valid from RES Workspace Manager 2014 SR2 (9.9.2.0) Consider the following scenario: Several managed Internet Explorer applications were configured with the following settings on the Properties.General tab of the app: 1) For each IE, a different Parameter was configured. 2) Under automatic shortcuts, Create Start Menu shortcut was selected. 3) A user session was running on Windows 8.1. In this scenario, only one application shortcut for IE was displayed on the Win8.1 Apps screen. This has been fixed, but for some reason you’ll need to set the above registry key to make it work.  ^

 

090 – Fix overlapping desktop icons

x86: HKLM\Software\RES\Workspace Manager\DoNotAllowOverlappedDesktopItems (REG_SZ) = Yes
x64: HKLM\Software\Wow6432Node\RES\Workspace Manager\DoNotAllowOverlappedDesktopItems(REG_SZ) = Yes

Posted Nov 20th 2014. Valid from RES Workspace Manager 2014 SR2 (9.9.2.0) Scenario: You are running WM in Shortcut Merge mode, and in the user session the desktop contain managed and unmanaged shortcuts, which do not overlap. Second, in the Windows desktop context menu, under View, the option Align icons to grid was not selected. In this scenario, after a workspace refresh, the desktop shortcuts could sometimes be placed on top of each other. This has been resolved. For this fix to work, for some reason you have to set the above registry value. ^

 

089 – Revert to old drive-refresh method

x86: HKLM|HKCU\Software\RES\Workspace Manager\RefreshAllMappedDrives (REG_SZ) = Yes
x64: HKLM|HKCU\Software\Wow6432Node\RES\Workspace Manager\RefreshAllMappedDrives(REG_SZ) = Yes

Posted Nov 20th 2014. Valid from RES Workspace Manager 2014 SR2 (9.9.2.0) Improvements have been made to speed up the refresh of a user workspace. In addition, only the drives that need to be added or removed because of a context change, are part of the workspace refresh. Before SR2, during a workspace refresh, all drives were first removed and then those drives that were valid for the user session were remapped. Set the above value if you for some reason want to go back to the old ways as in first removing all drives and then remapping only those drives that are valid for the user session.  ^

 

088 – Always show search field in Application List

x86: HKLM|HKCU\Software\RES\Workspace Manager\ShowSearchFieldAlways (REG_SZ) = Yes
x64: HKLM|HKCU\Software\Wow6432Node\RES\Workspace Manager\ShowSearchFieldAlways(REG_SZ) = Yes

Posted Nov 20th 2014. Valid from RES Workspace Manager 2014 SR2 (9.9.2.0) This is one of those reghacks you wonder why isn’t enabled per default out of the box, thus you should make it part of your best practice set. There was no bloody reason to hide this searchbar in the first place. Anyway, at Composition | Applications, on the Application List tab, when entering data to search for an application, a Search field automatically appears (and automatically disappears once the data has been deleted or the application was opened). To always show the Search field on the Application List tab, set the above registry value. Setting this registry value will solve the following issue: When searching in the application list (at Composition > Applications, on the Application List tab) the first two letters that were typed might be switched. Note: The release-notes incorrectly states it’s a REG_DWORD. Ignore that. Trust the RESguru. ^

 

087 – Citrix XenApp 7.x: bring back Session Lingering

x86: HKLM|HKCU\Software\RES\Workspace Manager\LingerDisconnectTimerInterval (REG_DWORD) = 1-999 (secs)
x64: HKLM|HKCU\Software\Wow6432Node\RES\Workspace Manager\LingerDisconnectTimerInterval(REG_DWORD) = 1-999 (secs)

x86: HKLM|HKCU\Software\RES\Workspace Manager\LingerTerminateTimerInterval (REG_DWORD) = 1-999 (secs)
x64: HKLM|HKCU\Software\Wow6432Node\RES\Workspace Manager\LingerTerminateTimerInterval(REG_DWORD) = 1-999 (secs)

Posted Nov 20th 2014. Valid from RES Workspace Manager 2014 SR2 (9.9.2.0) With this release, the Citrix functionality Session Lingering is, via RES Workspace Manager, still made possible for Citrix XenApp 7.5. It’s not necessary to use this reghack for XA 7.6 as Citrix brought this feature back. To enable Session Lingering for these XenDesktop/XenApp up to 7.5, two registry values can be set: LingerTerminateTimerInterval and LingerDisconnectTimerInterval. When setting the registry value LingerTerminateTimerInterval, RES Workspace Manager will make sure that the Citrix session will linger for the specified number of minutes after having closed the last published Citrix application in a user session. After this time, the Citrix session will be terminated. When setting the registry value LingerDisconnectTimerInterval, the Citrix session will linger for the specified number of minutes after having closed the last published Citrix application in a user session. After this time, the Citrix session will be disconnected. NOTE: 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.

 

086 – Relay Server, prevent daily obsolete log cleanup

HKLM\Software\RES\Workspace Manager\RelayServer\RemoveObsoleteLogFiles(REG_DWORD) = 0

Posted Nov 20th 2014. Valid from RES Workspace Manager 2014 SR1 (9.9.1.0) Obsolete log files are cleaned up on a daily basis. The time at which this cleanup should occur can be specified in Setup | Advanced Settings. To configure a Relay Server that is connected to the Datastore, to not perform this daily cleanup, the above registry value can be set. In environments where no Agents, but only Relay Servers are connected to the Datastore, please note that by setting this registry value on all Relay Servers, obsolete log files will not be deleted anymore. This may cause an unexpected growth of the Datastore resulting in performance degradation.  ^

 

085 – VDI: Store update-GUID’s on disk instead of registry

x86: HKLM\Software\RES\Workspace Manager\LocalCacheOnDisk (REG_SZ) = Yes
x64: HKLM\Software\Wow6432Node\RES\Workspace Manager\LocalCacheOnDisk(REG_SZ) = Yes

Posted Nov 20th 2014. Valid from RES Workspace Manager 2014 SR1 (9.9.1.0) The RES Workspace Manager Agent cache uses UpdateGUIDs to determine which parts of the cache need to be updated. Together with the RES Workspace Manager policy settings, these UpdateGUIDs are stored in the registry. When the UpdateGUIDs in the registry are different from the UpdateGUIDs in the Datastore/Relay Server, the relevant items are updated.

In VDI environments that use a non-persistent/pooled model, and where the RES Workspace Manager Agent cache is stored on a persistent disk, most likely the latest versions of the UpdateGUIDs and RES Workspace Manager policy settings are not in the registry of the golden image/template. Therefore, the cache will be updated with information from the Datastore or Relay Server, even though the most recent versions of the cache files are already present in the RES Workspace Manager cache on the persistent disk. The update causes I/O load and network traffic.

With this setting it is possible to make the cache independent of the Operating System’s (OS) registry. Setting this registry value will convert the UpdateGUIDs and policy settings automatically from the OS’ registry to two new XML files in the RES Workspace Manager DBcache folder on the persistent disk: UpdateGUIDs.xml and Settings.xml.
To store the UpdateGUIDs and RES Workspace Manager policy settings in the RES Workspace Manager DBcache folder, set the registry setting above.

After having set this registry value, when changing the Data to “No” or removing the registry value from the Agent, the cache will automatically convert UpdateGUIDs.xml and Settings.xml back into the OS’ registry and the files will be deleted from the DBCache folder. Setting this registry value will prevent unnecessary network traffic caused by the initial cache update, but may cause some additional disk I/O load on the RES Workspace Manager cache folder when processing changes in the Datastore throughout the day. ^

 

084 – SCCM App, configure startup delay

x86: HKLM|HKCU\Software\RES\Workspace Manager\SCCMDelayBeforeRunningProgram (REG_DWORD) = 1-999 (secs)
x64: HKLM|HKCU\Software\Wow6432Node\RES\Workspace Manager\SCCMDelayBeforeRunningProgram(REG_DWORD) = 1-999 (secs)

Posted Nov 20th 2014. Valid from RES Workspace Manager 2014 (9.9.0.0) In a user session, when an SCCM application was installed successfully, there is a default delay of 3 seconds before the application will be started. For some environments this default delay might not be long enough, resulting in an error message that the application cannot be started. In these situations you may want to change the default delay between successful installation and starting the application. This can be done by setting the registry value above ^

 

083 – Relay Server, enable additional encryption.

 

x86: HKLM\Software\RES\Workspace Manager\Relay Server\CertificateAlgorithm (REG_SZ) = x
x = SHA256RSA or SHA384RSA or SHA512RSA

Posted Nov 20th 2014. Valid from RES Workspace Manager 2014 (9.9.0.0) It is possible to use SHA256RSA, SHA384RSA or SHA512RSA encryption for the Self Signed Certificate of the WM Relay Server. A Self Signed Certificate is used for the SSL (Secure Sockets Layer) connection between the Relay Server and RES Workspace Manager Agents. The default encryption algorithm used is SHA1RSA, but this can be changed. This can be done by setting the registry value above.

IMPORTANT: After setting this registry value, the Relay Server might not start properly after a reboot. To resolve this, execute the following actions: 1) Open a command prompt with Administrative rights (cmd.exe). 2) Enter the following command: “sc config ResRls depend= KeyIso”. You may also consider creating an Automation Manager job for this  ^

 

082 – Prevent SCCM App-V OSD reset

x86: HKLM\Software\RES\Workspace Manager\CheckUpdateOSDFile (REG_SZ) = Yes
x64: HKLM\Software\Wow6432Node\RES\Workspace Manager\CheckUpdateOSDFile(REG_SZ) = Yes

Posted Nov 20th 2014. Valid from RES Workspace Manager 2014 (9.9.0.0) Launching managed Microsoft App-V applications using Microsoft System Center Configuration Manager (SCCM) 2012 SP 1 is 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 above registry value, a workaround is made available for the automatic SCCM reset, allowing the managed App-V application to launch. 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.  ^

 

081 – Enable Process intercepting for Citrix XenDesktop 7

x86: HKLM\Software\RES\Workspace Manager\XenDesktop7Intercept (REG_SZ) = Yes
x64: HKLM\Software\Wow6432Node\RES\Workspace Manager\XenDesktop7Intercept(REG_SZ) = Yes

Posted Nov 20th 2014. Valid from RES Workspace Manager 2014 (9.9.0.0). Obsolete as of SR2 (9.9.2.0) RES Workspace Manager supports process intercepting for Citrix XenDesktop 7 delivered applications (known as published applications on Citrix XenApp 6.5). In combination with a registry value on the Agent, this mechanism can be used to ensure that Citrix XenDesktop 7 deliverd applications are started in a managed workspace, instead of being RES-unmanaged. To use Process interception for Citrix XenApp 6.5 published applications, set the option Run RES Workspace Composer to Automatic for servers running XenApp (at Administration | Agents). If an unmanaged Citrix published application is started on these servers, it will always be launched by the RES Workspace Composer. If there is a managed application that uses the same process and that is configured with If managed shortcut was not used: Intercept new process and apply configuration, it will be intercepted.  ^

 

080 – Stop WM Sync from creating PwrGate based shortcuts

x86: HKLM\Software\RES\Workspace Manager\InterceptManagedApps (REG_SZ) = Yes
x64: HKLM\Software\Wow6432Node\RES\Workspace Manager\InterceptManagedApps (REG_SZ) = Yes

Posted Dec 3rd 2013. Valid from RES Workspace Manager 2012 SR4 (9.7.4.0)  This registry setting enables a new feature to completely stop WM from creating managed application shortcuts based on pwrgate.exe. Note, there are more value options for this registry hack. This feature is described in more detail in this article. ^

 

079 – Prevent WM Sync from launching

x86: HKCU|HKLM\Software\RES\Workspace Manager\RunWMSync (REG_SZ) = No
x64: HKCU|HKLM\Software\Wow6432Node\RES\Workspace Manager\RunWMSync (REG_SZ) = No

Posted Nov 30th 2013. Valid from RES Workspace Manager 2012 SR4 (9.7.4.0)  To improve local caching of User Settings, the WMSync process is started immediately at the start of the Workspace Composer. WMSync will also be started if local caching is not used. Preventing the WMSync process from being started immediately at the start of the Workspace Composer can be realized by setting the following registry value by setting the registry value above. Warning: Setting this registry value will prevent local caching from working. ^

 

078 – Fix save problem with saving Outlook MAPI profile

x86: HKLM\Software\RES\Workspace Manager\KeepUserDefaultMAPIProfile (REG_SZ) = Yes
x64: HKLM\Software\Wow6432Node\RES\Workspace Manager\KeepUserDefaultMAPIProfile (REG_SZ) = Yes

Posted Aug 23rd 2013. Valid from RES Workspace Manager 2012 SR3 Update 2 (9.7.3.2)  In a user session, if multiple mail profiles were attached to Microsoft Outlook, and the user made one of these profiles his default profile (at Microsoft Windows Control Panel | Mail | Show profiles | Always use this profile), the new default profile was not saved. When closing and starting up Microsoft Outlook again, the old default profile would be loaded. In a user session, if the user created an additional unmanaged mail profile and made this profile his default profile, the new default profile was not saved. When closing and starting up Microsoft Outlook again, the old default profile would be loaded. Both of these issues can be fixed by setting the registry value above. ^

 

077 – Force Citrix XA server into Host-Only mode

x86: HKLM\Software\RES\Workspace Manager\ActAsSessionHostOnly (REG_SZ) = Yes
x64: HKLM\Software\Wow6432Node\RES\Workspace Manager\ActAsSessionHostOnly (REG_SZ) = Yes

Posted May 23rd 2013. Valid from RES Workspace Manager 2012 SR2 Update 6 (9.7.2.6)  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 registry value above.  NOTE1: 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 (Administration|Agents, 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) NOTE2: According to the releasenotes, this setting somehow also applies to PowerFuse 2010 and earlier. The correct registry paths for these platforms are HKCU|HKLM\Software\RES\PowerFuse (x86) and HKCU|HKLM\Software\Wow6432Node\RES\PowerFuse (x64). ^

 

076 – Resolve client IP address from DNS

x86: HKCU|HKLM\Software\RES\Workspace Manager\ClientIPFromDNS (REG_SZ) = Yes
x64: HKCU|HKLM\Software\Wow6432Node\RES\Workspace Manager\ClientIPFromDNS (REG_SZ) = Yes

Posted May 23rd 2013. Valid from RES Workspace Manager 2012 SR2 Update 5 (9.7.2.5)  In rare circumstances it may be desirable to resolve the Client IP address via DNS. This can be done by setting the registry value above. NOTE: According to the releasenotes, this setting somhow also applies to PowerFuse 2010 and earlier. The correct registry paths for these platforms are HKCU|HKLM\Software\RES\PowerFuse (x86) and HKCU|HKLM\Software\Wow6432Node\RES\PowerFuse (x64) ^

 

075 – Workaround for SCCM launch of App-V

x86: HKLM\Software\RES\Workspace Manager\CheckUpdateOSDFile (REG_SZ) = Yes
x64: HKLM\Software\Wow6432Node\RES\Workspace Manager\CheckUpdateOSDFile (REG_SZ) = Yes

Posted May 23rd 2013. Valid from RES Workspace Manager 2012 SR2 Update 3 (9.7.2.3)  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 registry value above, a workaround is made available for the automatic SCCM reset, allowing the managed App-V application to launch.
NOTE: It’s still possible that launching a managed App-V application may fail. This can be a timing-issue: After the workaround is applied, SCCM resets the UpdateOSDfile policy before the managed App-V application is launched.. ^

 

074 – Disable CPUshield process completely

x86: HKLM\Software\RES\Workspace Manager\runcpushld (REG_SZ) = No
x64: HKLM\Software\Wow6432Node\RES\Workspace Manager\runcpushld (REG_SZ) = No

Posted May 23rd 2013. Valid from RES Workspace Manager 2012 SR2 Update 1 (9.7.2.1)  In the Administration | Performance | CPU Optimization node, on the Settings tab, when CPU Optimization was disabled, cpushld.exe would still run on all Agents. To prevent cpushld.exe from running on Agents, the registry value above can be set for each Agent.

 

073 – Speed up console access to certain apps

x86: HKLM\Software\RES\Workspace Manager\SkipFullNames (REG_SZ) = Yes
x64: HKLM\Software\Wow6432Node\RES\Workspace Manager\SkipFullNames (REG_SZ) = Yes

Valid from RES Workspace Manager 2012 SR2 (9.7.2.0)  This tweak improves the Managed Application editwindow load time, when users/groups are in multiple domains: Sometimes, Access Control for managed applications may be based on groups whose members are users and/or groups from multiple domains. In such situations, determining the full user name may take a long time. To speed up accessing to these applications in the Management Console, the administrator can choose to skip the resolving of full user names. This can be done by adding the registry setting above. ^

 

072 – Fix problem at logoff from Citrix server

x86: HK*\Software\RES\Workspace Manager\SkipCloseWFShell (REG_SZ) = Yes
x64: HK*\Software\Wow6432Node\RES\Workspace Manager\SkipCloseWFShell (REG_SZ) = Yes

Valid from RES Workspace Manager 2012 SR2 (9.7.2.0) *Valid entry in both HKCU and HKLM. Sometimes the Workspace Composer would yield unexpected results during logoff from a Citrix server (it’s not specified in the releasenotes if this is XA or XD) Anyway, at logoff RES Workspace Manager terminates the WFShell.exe in order to speed up the logoff process. Sometimes this termination gave unexpected results. To prevent this situation, the registry value above can be set. ^

 

071 – Fix Outlook’s NewMail Desktop Alert / Languages

x86: HK*\Software\RES\Workspace Manager\OutlookNotificationCheck (REG_SZ) = Yes
x64: HK*\Software\Wow6432Node\RES\Workspace Manager\OutlookNotificationCheck (REG_SZ) = Yes

Valid from RES Workspace Manager 2012 SR2 (9.7.2.0) *Valid entry in both HKCU and HKLM. Microsoft Outlook’s New Mail Desktop Alert seems not to show up in some languages. In Composition|Desktop|Shell, if “Use RES Workspace Manager Shell as the default shell” was selected, the Workspace Composer did not show New Mail Desktop Alerts for several Microsoft Outlook languages. To always show New Mail Desktop Alerts from Microsoft Outlook, set the registry setting above. ^

 

070 – Auto-correction list of Word user setting fix

x86: HK*\Software\RES\Workspace Manager\KeepWordRunning (REG_SZ) = <see description>
x64: HK*\Software\Wow6432Node\RES\Workspace Manager\KeepWordRunning (REG_SZ) = <see description>

Valid from RES Workspace Manager 2012 SR2 (9.7.2.0) *Valid entry in both HKCU and HKLM. This reghack is an update of an older one (see #044). As it turns out later, auto-correction list of Microsoft Word was not restored properly with WM’s User Settings, when the registry key above was set to Yes. This can now be resolved by setting the registry key to the value; Delayed. Please note that for this fix to work, the User Settings configured on application level for Microsoft Word should now be set at global level. ^

 

069 – Remote control fix

x86: HK*\Software\RES\Workspace Manager\UseOnlyComputerNameForShadow (REG_SZ) = Yes
x64: HK*\Software\Wow6432Node\RES\Workspace Manager\UseOnlyComputerNameForShadow (REG_SZ) = Yes

Valid from RES Workspace Manager 2012 SR2 (9.7.2.0) *Valid entry in both HKCU and HKLM. In the WM console under Diagnostics|User Sessions, Remote Control on a user session didn’t seem to always work. When trying to remote a user session, the following error could appear: Message Remote Control failed, Error #87, Error description: The parameter is incorrect. To prevent this error, add the registry value above. ^

 

068 – Fix for published system-tray apps

x86: HK*\Software\RES\Workspace Manager\IncludeProcesses (REG_SZ) = p1.exe,p2.exe,p..
x64: HK*\Software\Wow6432Node\RES\Workspace Manager\IncludeProcesses (REG_SZ) = p1.exe,p2.exe,p..

Valid from RES Workspace Manager 2012 SR2 (9.7.2.0) *Valid entry in both HKCU and HKLM. Sometimes SystemTray-only applications were not launched properly as Citrix published applications. Applications that were not visible in the taskbar, for example the Lync Client, did not launch properly as a published  application. If such a system-tray-only application was launched and it was the only application within the user’s session on the Citrix XenApp server, the Workspace Composer did not pick up on the process and immediately logged off the session. To prevent this error, add the name of the application executable to the registry key above. The value of the key is a comma separated list of processes, preventing the session to close as long as these processes are running. ^
067 – Citrix XenApp Publishing – Session sharing fix

x86: HK*\Software\RES\Workspace Manager\KeepSeamlessHostAgent (REG_SZ) = Yes
x64: HK*\Software\Wow6432Node\RES\Workspace Manager\KeepSeamlessHostAgent (REG_SZ) = Yes

Valid from RES Workspace Manager 2012 SR2 (9.7.2.0) *Valid entry in both HKCU and HKLM. Session sharing was not always possible when starting published application from Citrix Published Desktop. If a published application was started from a Citrix Published Desktop, session sharing might not work. To solve this problem, add the registry setting above. ^

 

066 – Boost performance starting an offline WM user session.

x86: HK*\Software\RES\Workspace Manager\SkipDSWhenOffline (REG_SZ) = Yes
x64: HK*\Software\Wow6432Node\RES\Workspace Manager\SkipDSWhenOffline (REG_SZ) = Yes

Valid from RES Workspace Manager 2012 SR2 (9.7.2.0) *Valid entry in both HKCU and HKLM. When a user started a RES Workspace Manager session on a device that was offline, the session startup could take a very long time. This was caused by the system querying for a domain controller. The long logon time can be decreased by setting the registry value above. ^

 

065 – Prevent memoryleak in pwrcache.exe when “CheckShutdown” hook is set.

x86: HKLM\Software\RES\Workspace Manager\CheckShutdown (REG_SZ) = yes
x64: HKLM\Software\Wow6432Node\RES\Workspace Manager\CheckShutdown (REG_SZ) = yes

Valid from RES Workspace Manager 2012 Fixpack 4 (9.7.0.4) When using the Citrix XenApp Advanced Configuration tool to create a reboot schedule for Citrix Provisioned XenApp servers, the corresponding server sometimes freezes during the reboot. If this occurs, the server no longer responds to any requests and only a hard reset can solve the issue. To prevent these situations, you can implement the setting above. ^

 

064 – Connect printers restored from User Settings

x86: HKLM\Software\RES\Workspace Manager\ForcePrinterConnections (REG_SZ) = yes
x64: HKLM\Software\Wow6432Node\RES\Workspace Manager\ForcePrinterConnections (REG_SZ) = yes

Valid from RES Workspace Manager 2012 Fixpack 1 (9.7.0.1). Printers that are restored in a user session via User Settings in HKCU\Printers\Connections are correctly restored, but are not connected per default. If this is required, set the registry key above. ^

 

063 – Suppress taskbar icons of Workspace Extended apps

x86: HKLM\Software\RES\Workspace Manager\ExcludeSubscribedTasks (REG_SZ) = see below
x64: HKLM\Software\Wow6432Node\RES\Workspace Manager\ExcludeSubscribedTasks (REG_SZ) = see below

Valid from RES Workspace Manager 2012 Fixpack 1 (9.7.0.2). Managed applications that run as a workspace extension in a RES Workspace Manager session (“subscribed” tasks) appear with their own icon in the taskbar. In certain circumstances, this may lead to situations in which the application icon is still shown in the taskbar, but the application is no longer active. As a result, the taskbar icon no longer works. For example, this behavior may occur when tasks with a relative short duration are executed (e.g. 500 ms), such as the windows captions in a RES Workspace Manager session. It is now possible to suppress this behavior by setting the above registry key.

The data of this value is formatted as: <window caption of task1 to be excluded>,<window caption of task2 to be excluded>, <etc.>^

 

062 – Change default AppID for PWRGATE.EXE

x86: HKLM\Software\RES\Workspace Manager\PwrGateAppId (REG_SZ) = #AppID number
x64: HKLM\Software\Wow6432Node\RES\Workspace Manager\PwrGateAppId (REG_SZ) = #AppID number

Valid from RES Workspace Manager 2012 Fixpack 1 (9.7.0.1). In certain situations, a specific managed application doesn’t start correctly in the user workspace. If this behavior is caused by the fact that a 3rd party application starts pwrgate.exe without any arguments, setting the above may help. ^

 

061 – Suppress Show/Hides Desktop button on taskbar

x86: HKLM\Software\RES\Workspace Manager\SuppressShowDesktopButton (REG_SZ) = yes
x64: HKLM\Software\Wow6432Node\RES\Workspace Manager\SuppressShowDesktopButton (REG_SZ) = #Secs

Valid from RES Workspace Manager 2012 Fixpack 2 (9.7.0.2). You can now use the registry key above to suppress the Show/Hide Desktop button on the taskbar of users for whom, at Composition > Desktop > Shell, it has been specified that they should be given the RES Workspace Manager shell. ^

 

060 – Configure delay before Workspace Composer starts

x86: HKLM\Software\RES\Workspace Manager\WaitBeforeStart (REG_DWORD) = #Secs
x64: HKLM\Software\Wow6432Node\RES\Workspace Manager\WaitBeforeStart (REG_DWORD) = #Secs

Valid from RES Workspace Manager 2011 SR4 (9.5.4.0). In certain situations, it’s desirable to have the Workspace Composer wait a few seconds before starting. This can be done by adding the registry key above. Maximum for #secs is 3600 seconds (1 hour) ^

059 – Disable shell folders created when User Settings enabled

HKLM\Software\RES\Workspace Manager\CheckDisabledFolders (REG_SZ) = Yes

Valid from RES Workspace Manager 2011 SR2 (9.5.2.0). When User Settings is enabled in Composition | User Settings, the default shell folders might be created although they are disabled by the “disable known folders” policy. RES Workspace Manager will no longer create disabled known folders if the registry key above is configured. ^

 

058 – Extend Active Directory enumeration timeout

x86: HKLM\Software\RES\Workspace Manager\DirectoryServiceRetryLimit (REG_SZ) = #Secs
x64: HKLM\Software\Wow6432Node\RES\Workspace Manager\DirectoryServiceRetryLimit (REG_SZ) = #Secs

Valid from RES Workspace Manager 2011 SR3 (9.5.3.0). In rare circumstances, the RES Workspace Manager Composer reported online, while the Microsoft Windows Directory Service was not yet fully available. This could happen for example when connecting over a VPN connection. The default value is 15 seconds. The registry key above can be added to increase the waiting time for the Directory Service to become available. ^

 

057 – Fix blank icons for active App-V apps

x86: HKLM\Software\RES\Workspace Manager\DisableIconRefresh (REG_SZ) = Yes
x64: HKLM\Software\Wow6432Node\RES\Workspace Manager\DisableIconRefresh (REG_SZ) = Yes

Valid from RES Workspace Manager 2011 SR3 (9.5.3.0). Under certain circumstances, icons for active Microsoft App-V applications on the taskbar become blank after a user refreshes the workspace. When the user refreshes the workspace again, the icons return to normal. Use this registry hack to mitigate this behavior. ^

 

056 – Change Webguard message settings

HKCU\Software\Policies\RES\WebGuardIE\UseMsgBox (REG_DWORD) = 1 or 0
HKCU\Software\Policies\RES\WebGuardIE\MsgTimeout (REG_DWORD) = #Secs

Valid from RES Workspace Manager 2011 SR3 (9.5.3.0). WebGuard now has the option to show a message pop-up boxm instead of just the default in-browser message, when an url is blocked. The message box can be configured to disappear automatically after an adjustable timeout. Set UseMsgBox=1 to turn on, 0 to turn off. ^

 

055 – Tweak Oracle DB sizecheck behavior

x86: HKLM\Software\RES\Workspace Manager\DoNotAnalyseDB (REG_DWORD) = 1
x64: HKLM\Software\Wow6432Node\RES\Workspace Manager\DoNotAnalyseDB (REG_DWORD) = 1

Valid from RES Workspace Manager 2011 SR3 (9.5.3.0). When using an Oracle Database, retrieving the Database size from the RES Workspace Manager Console in Setup | Datastore can sometimes be observed to take a long time or could even cause the Console to hang. In order to resolve this issue, the registry entry above can be set to resolve the situation. ^

054 – Modify ActiveSetup timeout

x86: HKLM\Software\RES\Workspace Manager\ActiveSetupTimeout (REG_SZ) = #Secs
x64: HKLM\Software\Wow6432Node\RES\Workspace Manager\ActiveSetupTimeout = #Secs

Valid from RES Workspace Manager 2011 SR3 (9.5.3.0) In rare circumstances, Active Setup (which is used to execute an application that is not registered or if the version in the Current User registry is lower than in the Local Machine registry) takes more than 60 seconds to complete. This could result in a timeout at logon. With the above registry value the Active Setup Timeout can be configured. Note: #Secs is number of seconds to wait.  ^

 

053 – Change default AppID for PWRgate.exe

x86: HKLM\Software\RES\Workspace Manager\PwrGateAppId (REG_SZ) = #AppId
x64: HKLM\Software\Wow6432Node\RES\Workspace Manager\PwrGateAppId (REG_SZ) = #AppId

Valid from RES Workspace Manager 2011 SR3 (9.5.3.0) In certain situations (e.g. when using the Datatrac application), Managed Applications did not start correctly because pwrgate.exe was started without any arguments. To solve this issue, set the registry entry above. Note #appid is a number in a REG_SZ  ^

 

052 – Configure Silent Refresh

SOFTWARE\RES\Workspace Manager\SilentRefresh (REG_SZ) = Yes

Valid from RES PowerFuse 2008. Can be configured in either HKCU or HKLM.A silent refresh does not show a splash screen during a refresh of the Workspace Manager, which in some cases is less intrusive for the user. This type of refresh is only used when the refresh is a result of a display change, a USB device change or when reconnecting to a disconnected session. If you are challenged with speeding up perceived logon time, setting this one could help. For legacy PowerFuse the registry key instead is SOFTWARE\RES\PowerFuse. Added by Rob Aarts. ^

 

051 – Fix problem opening .CSV files from Internet Explorer

HKLM\SOFTWARE\RES\Workspace Manager\SkipCLSID (REG_SZ) = Yes

Valid from RES Workspace Manager 2011 SR1, UpdatePack 5 (9.5.1.5) Opening a .CSV file from the Internet Explorer could fail. This problem can be solved by adding the registry entry above. ^

 

050 – Enable process to be started, called as a process.

HKLM\SOFTWARE\RES\Workspace Manager\PwrGateFileMapping (REG_SZ) = Yes

Valid from RES Workspace Manager 2011 SR1, UpdatePack 5 (9.5.1.5) In very rare circumstances Managed Applications will not start if that application is called as a process, e.g. by pressing a specific button in a third-party application. If this is the case, the registry entry above solves the issue. ^

 

049 – Prevent apps from changing size of workarea in RES Shell

SOFTWARE\RES\Workspace Manager\CorrectWorkArea (REG_SZ) = Yes

Valid from RES Workspace Manager 2011 SR1, UpdatePack 6 (9.5.1.6). In exceptional circumstances, when using the RES Workspace Manager Shell (aka RES Shell), applications incorrectly change the size of the work area (not sure what the Work Area is – The desktop?). Anyway, this behavior can be detected and corrected by setting the above registry key in either HKLM or HKCU. ^

 

048 – Change the way Desktop Sampler reads computer/client names

HKLM\Software\RES\Desktop Sampler\ForceComputername (REG_SZ) = Yes

Valid from (not really sure, a post release to WM2011 SR1). A new registry setting has been added to the Desktop Sampler. This fix changes how the desktop sampler reads the computer name. On a VDI/TS environment the, desktop sampler will per default look for the computername of the client connecting to the session. The reghack above changes the behavior to look for the hostname of the TS/VM itself. ^

 

047 – Fix Win7 Recent Docs not working after upgrade

HKLM\SOFTWARE\RES\ PowerFuse\UseOldRecentDocsMethod (REG_SZ) = Yes

Valid from RES Workspace Manager 2011 SR1  (9.5.1.1). On Windows 7, users may have Recent documents accessible from the start menu. When you upgrade from PowerFuse 2010 to Workspace Manager 2011, Recent documents may no longer work. Applying the above registry setting should this . ^

 

046 – Fix ‘From’ field in Outlook 2010

HKLM\SOFTWARE\RES\Workspace Manager\ConnectFromOL2010 (REG_SZ) = Yes

Valid from RES Workspace Manager 2011 SR1  (9.5.1.1). Sometimes the ‘From’ field in Outlook 2010 can display ‘Microsoft Exchange’ or ‘Microsoft Exchange Server’. This behavior can be fixed by using the above registry setting. ^

 

045 – Locate printers by subnet for workstations

SOFTWARE\RES\PowerFuse\LocatePrintersByIP (REG_SZ) = Yes

Valid from RES PowerFuse 2010 SR3 UpdatePack 7 (9.0.3.7). With this setting, the default printer configured on a laptop is remembered, based on ip address. This functionality is not available for terminal servers. For customers who want this functionality, the registry setting above can be set in either HKLM or HKCU.. ^

 

044 – Fix issue with starting Winword from Navision

HKLM\SOFTWARE\RES\PowerFuse\KeepWordRunning (REG_SZ) = Yes

Valid from PowerFuse 2010 SR3 UpdatePack 6 (9.0.3.6). Starting winword.exe from within Navision might result in an error message like: Faulting application fin.exe, version 6.0.29626.0, time stamp 0x4a849450, faulting module OLHandler.dll,…. This behaviour can be prevented by setting this registry key. NOTE: This reghack has been updated per Workspace Manager 2012 SR2. See Reghack #070 above for details. ^

 

043 – Fix issue with opening UNC path from an app in PFshell

HKLM\SOFTWARE\RES\PowerFuse\StartHiddenPexplorer (REG_SZ) = Yes

Valid from Workspace Manager 2010 SR2 UpdatePack 11 (9.0.2.11) and Workspace Manager 2008 SR9 UpdatePack 12 (8.0.9.12). In rare circumstances it is not possible to open an UNC path in the RES PowerFuse Shell from another application, such as MS Outlook. The registry setting above may very well solve the problem. ^

 

042 – Do not preceed RES published apps with a backslash

HKLM\SOFTWARE\RES\PowerFuse\NoPrecedingSlashInPNFolder (REG_SZ) = Yes

Valid from Workspace Manager 2010 (9.0.2.7) When publishing an application via RES Workspace Manager the PN root folder is always prefixed with a backslash “\”.   This “\” will not appear if the registry entry above is configured. ^

 

041 – Fix for Winword/Reference Manager problem

HKLM\SOFTWARE\RES\PowerFuse\TmpDDEMacros (REG_SZ) = Yes

Valid from Workspace Manager 2008 (8.0.9.5) and Workspace Manager 2010 (9.0.2.4) For some reason Winword doesn’t start properly when using the Reference Manager plugin. This can be solved by setting the registry value above. ^

 

040 – Change local taskbar behavior of Worspace Extender

HKLM\SOFTWARE\RES\PFWSExt\AutoExtendWorkspace (REG_DWORD) = 0

Per default, the Workspace extender will kill the local explorer.exe process and thereby also the local taskbar The default value for AutoExtendWorkSpace = 1). This behavior can be prevented by changing the value above to 0 (zero). ^

 

039 – Allow Desktop shortcuts to unmanaged applications

SOFTWARE\RES\PowerFuse\AllowExeLinkOnDesktop (REG_SZ) = Yes

Valid from RES Workspace Manager 2008 SR5. Note: This reghack has no use (if implemented at all) in Workspace Manager 2010, as this version offers the ability to mix managed and unmanaged applications in the console by default. Anyway, RES changed the mechanism for handling the desktop in the windows shell in PF2008 SR5. One of the results of this change is that user-made desktop shortcuts to executable files are now hidden in RES Workspace Manager sessions, because they are shortcuts to unmanaged applications.  If users should still have access to any desktop shortcuts to executables, you can allow this by setting the key as specified above in either HKLM or HKCU. ^

 

038 – Enable Workspace Manager performance analysis dump file

HKLM\Software\RES\PowerFuse\Instrumentation (REG_SZ) = Yes

Valid from Workspace Manager 2008 SR4 (8.0.4.0). When you create this key a dumpfile will be created which can help RES Software support troubleshoot performance issues. Two logfiles will be generated in seperate locations:

  • The logfile for the performance of the RES Workspace Manager Workspace Composer will be generated when a Workspace Manager session is logged off and can be found as “\pwrmenu\perfdump_%computername%.txt” folder in the users homedrive.
  • The logfile for the performance of the RES Service and components will be generated when the RES Service is restarted and can be found as “%programFolder%\RES PowerFuse\perfdump_pwrcache_up_%computername%.txt.

I have generated a couple of samples, so you can see what they look like. Only RES will be able to make heads or tails out of them anyway. The performance logfile for the RES service look like this. The per-user performance logfile looks like this. ^

 

037 – Disable connection string pickup via DCHP option

SOFTWARE\RES\PowerFuse\DisableDHCP (REG_SZ) = Yes

Valid from Workspace Manager 2010 (9.0.0.1) Per default, Workspace Manager will look for a connection string in the DCHP options pulled from the DCHP server when TCP/IP initialized. See this article on how to set it up. If you haven’t defined a PoweFuse option on your DHCP server, you don’t need this setting, however if you do have it and you want to prevent some machines from picking it up, use the setting above. ^

 

036 – Force Workspace Manager to enumerate redirected folders from registry

SOFTWARE\RES\PowerFuse\SpecialFoldersFromRegistry (REG_SZ) = Yes

Valid from Workspace Manager 2010 SR1, update pack 12 (9.0.1.2) Under some circumstances folder redirection was properly configured, but not recognized at the time Workspace Manager is building up the desktop, start menu and so on. As a workaround, it is now possible to force Workspace Manager to resolve the special folders from the registry by creating the registry value above in either HKLM or HKCU. ^

 

035 – Ensuring correct behavior of download-manager launched published apps

HKLM\SOFTWARE\RES\PowerFuse\ExcludeProcesses (REG_SZ) = %launchprocess|%childprocess

Valid from Workspace Manager 2010 SR1, update pack 11 (9.0.1.11). Sometimes a published aplication uses a download manager (such as DFSVC.EXE found in Windows) to download and start an application. Because the DFSVC.EXE process doesn’t stop, the published Workspace Manager application will not stop even if the user ends the  downloaded application. This has been fixed, but to work properly the above registry value must also be created. For example if the downloaded application is process xyz.exe, the data of the registry key must be “dfsvc.exe|xyz.exe”. See also RES KB article 201983 as the specification for the keyvalue was different in Workspace Manager 2008 SR3. ^

 

034 – Fix Thinapp runtime error in a XenDesktop environment

HKLM\SOFTWARE\RES\PowerFuse\BlockPicaSvcFix (REG_SZ) = Yes

Valid from Workspace Manager 2010 SR1, update pack 11 (9.0.1.11) Starting a Thinapp application on a XenDesktop environment might result in a runtime error generated by picasvc.exe. This behaviour can be blocked by configuring the registry value above. ^

 

033 – Folder Synchronization: Ability to use network drives

SOFTWARE\RES\PowerFuse\DisableFolderSyncLocalCheck (REG_SZ) = Yes

Valid from Workspace Manager 2010 SR1, updatepack 9 (9.0.1.9) A registry tweak allows you to use network drives in Composition > Files and Folders > Folder Synchronization where normally only local drives are allowed. You can configure this registry settings in either HKLM or HKCU. ^

 

032 – Preserve QuickLaunch shortcuts on Microsoft Windows 7

HKLM\SOFTWARE\RES\PowerFuse\ KeepQL (REG_SZ) = Yes

Valid from Workspace Manager 2010 SR1, updatepack 5 (9.0.1.5) On Microsoft Windows 7 and Microsoft Windows 2008 R2 QuickLaunch items were no longer managed. During logoff all Managed shortcuts in the QuickLaunch folder (which the user might have put there) were deleted. This deletion can be prevented with this key. ^

 

031 – Fix for slow logons due to large amount of SRS files in Outlook Folder

HKLM\SOFTWARE\RES\PowerFuse\CleanupSRS (REG_SZ) = Yes

Valid from Workspace Manager 2010 SR1, updatepack 4 (9.0.1.4) The *.SRS (Send and Receive Settings) files created in C:\Documents and Settings\%name%\Application Data\Microsoft\Outlook, by outlook are not always correctly removed. This registry setting for RES Workspace Manager ensures a nice and tidy cleanup. ^

 

030 – User Settings: Configure compression interval

HKLM\SOFTWARE\RES\PowerFuse\ZPCompressInterval (REG_SZ) = #days

Valid from Workspace Manager 2010 SR1, updatepack 3 (9.0.1.3) The User Settings Files *.upf2 and *.upr2 are now compressed during logoff approximately once per month. In addition the ‘compression interval’ for these files can be configured via this value. The #days is the number of days between each compression interval. If you set the value to 0 (zero) the files will be shrunk during each logoff. ^

 

029 – Change default timeout for changing password in Workspace Preferences

HKLM\SOFTWARE\RES\PowerFuse\ChangePasswordTimeout (REG_SZ) = #secs

Valid from Workspace Manager 2010 SR1 (9.0.1.0). It is possible to change the default timeout for changing the user’s password in the Workspace Preferences tool. The default timeout is 5 seconds, which btw is the minimum value. To change the default timeout create the registry value as specified above. This timeout occurs if your network connection is very slow.  You can experience it on a Win7 machine by blocking tcp ports 445 and 88 and enabling the rest. If you try to change the password you should receive a “the specified network password is not correct” message after approx. 8 seconds. By setting the registry value, you can manipulate that particular timeout. ^

 

028 – Fix low-resolution icons pinned on Start Menu

HKLM\SOFTWARE\RES\PowerFuse\MultiIconSupport (REG_SZ) = Yes

Valid from Workspace Manager 2010, updatepack 10 (9.0.0.10). By default, the Workspace Manager doesn’t use Multi Icon Support (aka High quality icons) when pining icons to the startmenu. The result is funny looking stretched out icons. Apply this registry setting, then go to the Setup|Agents node in the console. Select and rightclick on the agents you want to update now, and select ‘Force Cache Update’. Next time you pin something to the startmenu, things should look better. ^

 

027 – Enable console legacy application mode

x86: HKLM\SOFTWARE\RES\PowerFuse\ConsoleNoAppIcons (REG_SZ) = Yesx64: HKLM\SOFTWARE\Wow6432Node\RES\PowerFuse\ConsoleNoAppIcons (REG_SZ) = Yes

Valid from Workspace Manager 2010, update pack 7 (9.0.0.7). With this registry setting it is possible to force the Workspace Manager 2010 console NOT to display the real application icons in the Managed Application node. This may be useful if you’ve got a ridiculous high number of applications, and the console seems somewhat sluggish to work with. See RES KB article Q202499 for more information. ^

 

026 – Enable classic blanking splash screen on refresh

SOFTWARE\RES\PowerFuse\ClassicSplash (REG_SZ) = Yes

Valid from Workspace Manager 2010 (9.0.0.0). If you for one reason or another would like to blank the screen while the refresh is taking place and show only the splash screen loader –  just like in the old pre 2010 days, then this registry is for you. This is also a temporary workaround if your icons aren’t being built correctly. The setting can be applied both in HKLM and HKCU. ^

 

025 – Settings for Desktop Sampler

HKLM\SOFTWARE\RES\Desktop Sampler\Delay (REG_SZ) = #secondsHKLM\SOFTWARE\RES\Desktop Sampler\ExpireDays (REG_SZ) = #daysHKLM\SOFTWARE\RES\Desktop Sampler\InstallDate (REG_SZ) = %dd-mm-yyyHKLM\SOFTWARE\RES\Desktop Sampler\SamplePath = path (\\UNC or local)HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\DTSampler (REG_SZ) = "dtsampler.exe"

Valid from Workspace Manager 2010 (9.0.0.0) These settings specify how the Desktop Sampler behaves. The setting Delay will determine how many seconds after execution the sampler will create it’s snapshot, 30 seconds is default if not specified. This is usefull if you have a longer-than-average loginscript or just a plain slow environment at the moment. Expiredays will cleanly uninstall the Desktop Sampler from the target environment #days after the date specified in Installdate. This value is set automagically if you use the Desktop Sampler MSI package to deploy it with. Finally the SamplePath allows you to specify where the Desktop Sampler should store it’s DTS files. If not specifed, the files will be stored locally in the same path as where the Sampler’s binary (dtsampler.exe) is found. The path can be an UNC path to a \\server\share, or just another local path on the target computer. Note, from Workspace Manager 2010 SR1, the samplepath can be overridden by specifying a /SAMPLEPATH= on the commandline of dtsampler.ex.

Note: the Windows..Run key above, is where the Desktop Sampler installs itself into the registry, so it runs automatically and takes a snapshot of the environment after the user has logged in. ^

 

024 – Configure Agents to force shutdown

SOFTWARE\RES\PowerFuse\ForceShutdown (REG_SZ) = %option

Valid from Workspace Manager 2010 (9.0.0.0). It is possible to force a shutdown on workstations when users log off. This can be enabled by setting the above registry string in either HKLM or HKCU, with one of the values for % option as specified below:

shutdown = Initiates a normal shutdown
poweroff = Initiates a shutdown + poweroff
restart = Initiates a shutdown + restart              ^

 

023 – Configure behavior of ALLUSERSPROFILE variable

HKLM\SOFTWARE\RES\PowerFuse\DisableWDSFix (REG_SZ) = Yes OR New

Valid from Workspace Manager 2008 SR8, updatepack 1 (8.0.8.0) When starting a RES Workspace Manager session with the Windows Explorer, the ALLUSERSPROFILE variable in the Explorer will be set to the User’s profile folder. Under some circumstances this may result in unwanted behavior. Therefore in RES Workspace Manager 2008 SR8 the registry setting above was added. The caveat of this method was that Windows Desktop Search would not work properly. Therefore it is now possible to set this registry value to ‘New’ which will cause the ALLUSERSPROFILE variable to point to the All Users Profile folder.  Note that this should only be used if DisableWDSFix = Yes does not work in your environment.

Note: In Workspace Manager 2008 SR7 another registry fix; HKLM\Software\RES\PowerFuse\EnableWDSFix was introduced. That key is now obsolete and thus should no longer be used. ^

 

022 – Extender/ Subscriber: Set wait time before establishing connection

x86: HKLM\SOFTWARE\RES\PowerFuse\WaitTimeForExtender (REG_DWORD) = #minutes [2..120]x64: HKLM\SOFTWARE\Wow6432Node\RES\PowerFuse (REG_DWORD) = #minutes [2..120]

Valid from Workspace Manager 2008 SR8 (8.0.8.0) Occasionally, the connection between the RES Workspace Manager Workspace Manager and the RES Subscriber/Workspace Extender cannot be established. If this occurs, you can solve this by enhancing the wait time for this connection during startup of the Workspace Composer component. The default wait time is 2 seconds. You can set longer wait times with the registry setting above. ^

 

021 – Prevent Outlook 2003 from launching Word 2003 embedded

SOFTWARE\RES\PowerFuse\StartWordForOutlook (REG_SZ) = No

Valid from Workspace Manager 2008 SR7 (8.0.7.16). If you have a managed and a unmanaged instance of Outlook running, you can potentially run into conflicting Normal.dot problems. To prevent embedded autolaunch of Microsoft Word 2003 when Microsoft Outlook 2003 is launched, create the registry key above in either HKLM or HKCU. See RES KB article Q202617 for more information on this setting. ^

 

020 – Allow Windows Run keys to execute

HKLM\SOFTWARE\RES\PowerFuse\DoNotRemoveRunKeys (REG_SZ) = Yes

Valid from RES Workspace Manager 2008 SR7 (8.0.7.0) Sometimes you may actually want to allow items registered under the HKLM…\Windows\Currentversion\Run key to execute at login. Workspace Manager disables this per default by tempoarily renaming the  key to run.org within a Workspace Manager session. By using this registry setting you can block this behavior. Note however that it’s way more structured to create external tasks with the Run-Hidden option enabled than doing this reghack. Note: In Workspace Manager 2010 SR1, this option is now included in the console Go to Setup|Datastore|Advanced Settings. Here you will find a setting called “Do not prevent applications in the Run key or RunOnce key from starting”. ^

 

019 – Only hide splashscreen

HKLM\SOFTWARE\Policies\RES\PowerFuse\Settings\ApplicationSettings\NoSplash (REG_SZ) = Yes

Valid from Workspace Manager 2008 SR3 (8.0.3.0) In certain circumstances, some customers wanted to hide the splash screen at logon, yet retaining the splash when refreshing. The above registry hack should do the trick. Note that the AdvancedConfig key above prior to 2008 SR3 was called AdvancedConfig. ^

 

018 – Force DISCONNECT after idle-timeout

SOFTWARE\RES\PowerFuse\ForceDisconnectOnIdle (REG_DWORD) = #minutes

Valid from Workspace Manager 2010 (9.0.0.1). It is possible to force a RES Workspace Manager session to disconnect after “n” minutes, by setting the key above in either HKLM or HKCU. The #minutes value must be at least 1. ^

 

017 – Enable asyncronous build of the start menu

SOFTWARE\RES\PowerFuse\AsyncStartMenu (REG_SZ) = Yes

Valid from Workspace Manager 2008 SR6, updatepack 1 (8.0.6.1) Some improvements were made in this release, due to that reading of the icons from disk and the creation of the Start Menu during the first logon could sometimes slow things down. To enable to faster async creation of the Start Menu, try setting this registry key. ^

 

016 – Force LOGOFF after idle-timeout

SOFTWARE\RES\PowerFuse\ForceLogOffEnabled (REG_SZ) = Yes or No
SOFTWARE\RES\PowerFuse\ForceLogOffTimeout (REG_SZ) = #minutes
SOFTWARE\RES\PowerFuse\ForceLogOffOnIdle (REG_SZ) = Yes or No

Valid since Workspace Manager 2008 SR4, updatepack 5 (8.0.4.5). Forcing a logoff event is typically used for computers that run in some sort of kiosk environment or say for service stations. You can configure this behavior by configuring the following registry settings in either HKLM or HKCU:

If ForceLogOffOnIdle has been configured as Yes, the timeout will start when the idle timer starts. If ForceLogOffOnIdle has not been configured or has been configured as No, the timeout will start when the screensaver starts or when the session is locked. When the timeout expires, the user session will be forced to log off (any unsaved data will be lost). See RES KB article Q201739 for further information. ^

 

015 – Avoid privacy issues with display of concurrent license usage

SOFTWARE\RES\PowerFuse\NoListConcurrentUsers (REG_SZ) = Yes

Valid from Workspace Manager 2008 SR4 (8.0.4.0). If an application has concurrent user licensing, and the number of licenses is exceeded, a new attempt to start the application will show a warning form, with a list of users currrently using this application. Showing this list may conflict with security or privavcy policies. As a workaround the registry setting above may be configured to prevent the list being shown to the users.  This value can be set in either HKLM or HKCU.

Perhaps it would be a good thing to configure this registry value as global PowerLaunch registry setting when needed, where you can apply Access Control to it. The setting is especially useful for shared environments such as MSP’s or perhaps financial institutions. ^

 

014 – Read-only-Blanketing: Do not remove administrative shares

HKLM\SOFTWARE\RES\PowerFuse\KeepSharesWithROB (REG_SZ) = Yes

Valid from Workspace Manager 2008 SR4 (8.0.4.0). Setting this item will prevent the Read-only-Blanketing subsustem from removing the administrative shares (\\computer\c$, d$ etc). This happens even if RoB is in LearningMode. Even though this constitures a reduction of overall security, this is useful if there is such a need on a given machine. ^

 

013 – Display the taskbar only on the primary display

HKLM\SOFTWARE\RES\PowerFuse\CorrectTaskbar (REG_SZ) = Yes

Valid from PoweFuse SR3, updatepack 7 (8.0.3.7). This reghack may be useful in situations where for some reason the taskbar is not visible or your application is displayed behind the taskbar. You may also experience that the taskbar is stretched across multiple monitors if you have such a setup. This behavior has been observed on Citrix platforms primarily. For this fix to work, you need at least an ICA Client 11 or higher. ^

 

012 – Override the alteration of the Citrix Explorer Hook

x86: HKLM\SOFTWARE\RES\PowerFuse\ResetCitrixExplorerHook (REG_SZ) = Nox64: HKLM\SOFTWARE\Wow6432Node\RES\PowerFuse\ResetCitrixExplorerHook (REG_SZ) = No

Valid since after Workspace Manager 2008 SR3 (8.0.3.0). RES introduced a change which disables the Citrix Explorer Hook. The explorer hook  is what in a plain-vanilla Citrix environment would prevents a user running a published app from getting access to an explorer desktop. However since PowerFuse is wrangeling the desktop environment, we really want to get rid of said explorer hook as it can complicate things unnecessarily. Security is not comprimised as PowerFuse’s AppGuard takes over from there.

In short, disabeling the Citrix Explorer Hook – and keeping it that way, is a good thing to do. Even so, there might be special situations where you do not want this to happen. For more information about these keys, refer to RES KB article Q202199. Login required. ^

 

011 – Change location of the Workspace Manager cache

HKLM\Software\RES\PowerFuse\LocalCachePath (REG_SZ) = %folderpath 

Valid from Workspace Manager 2008. In some instances you would prefer not to have the cached copy of the Workspace Manager datastore in the default location of %programfiles%\RES PowerFuse\Data\DBcache. If you use this regsetting, you can provide an alternate local %folderpath like “D:\Somefolder\PFLocalCache” (NO! don’t even think of UNC’s, it’s supposed to be local!). Note: you must do two things to complete the move: 1) Delete all values and keys beneath HKLM\Software\RES\PowerFuse\UpdateGUIDs. 2) Restart the RES service. Once this is done, the IconCache, Objects, etc folders will be created and populated with the current values from the Workspace Manager datastore. ^

 

010 – Force rebuild the Workspace Manager cache

x86: HKLM\SOFTWARE\RES\PowerFuse\UpdateGUIDs <- delete this keyx64: HKLM\Wow6432Node\RES\PowerFuse\UpdateGUIDs <-delete this key

If for some reason you need to completely re-initialize the local cache of RES Workspace Manager, this is accomplished by deleting the key above. After you’ve done this, you will need to restart the RES service, which in turn will rebuild the cache. The key holds the GUID’s for the different objects in Workspace Manager. The GUIDS are used to verify if the local cache is in sync with the datastore. If an object has changed, the Update GUID will change, hence all agents will update just the difference/delta instead of the complete configuration set in the database. This operation is harmless as the UpdateGUIDs key can be removed without causing any problem with Workspace Manager. As soon as the RES service determines there is no local cache, it will proceed to transfer a copy of the entire configuration set in the datastore. ^

 

 

009 – Managing global Workspace Manager settings on an individual computer

SOFTWARE\Policies\RES\PowerFuse\Settings - and below

Valid from Workspace Manager 2008 but mostly obsolete after version 2010. This registry tree holds the RES Workspace Manager global configuration data and may exist in both HKLM and HKU. Note per default it does not exist in HKCU. There are MANY registry settings in here, which are largely self explanitory. Perhaps in a future article I may detail these further. The settings found here concerns configuration items that can only have a Yes/No value (Boolean) or a numeric value (Integer) .  An example of a Boolean setting is “CPU Shield Enabled”: the value of the setting can only be “Yes” or “No”. An example of an Integer is the maximum number of simultaneous logons: the value of the setting can only be a number.

Another side to using the registry settings found here, is that you can use policies to customize these settings per user or per server. These policies can be applied using RES Wisdom or importing an ADM file found in this article.

An important change from Workspace Manager 2008 SR3 and up: Prior to this the Advanced Configuration settings resided below HKLM\Software\Policies\RES\Powerfuse\Settings\AdvancedConfig. From RES Workspace Manager 2008 IR3 and up the AdvancedConfig keyname has changed to ApplicationSettings, so the full path is: HKLM\Software\Policies\RES\Powerfuse\Settings\ApplicationSettings.

warning, yellowNotice: Using these registry settings is largely a moot point since Workspace Manager 2010, as we now have the ability to configure most of these items from within Workspace Models. See article RG02A for more information on this topic. Second, the decision should be weighed carefully whether to roll out policies using Active Directory or using RES Workspace Manager. It is advisable to choose one method or the other, and it is inadvisable to attempt to combining them. Reason is that Microsoft applies policy based settings at logon and at 90 minute intervals per default after that, where as Workspace Manager may apply settings at any time in a dynamic environment. ^

 

008 – Database connection settings

HKLM\SOFTWARE\RES\PowerFuse\DB*

Valid from Workspace Manager 2008. Database connectivity settings can be found in this key. Do not modify these directly unless you have a very specific reason to do so, as per Workspace Manager 2010, you now have the ability to import/export a connection string, even obtain it via DHCP from Workspace Manager 2010 and up. See this article for further info on DHCP and the connection string. While thus obsolete, you can however still copy this registry key from another computer to ensure the two computers connect with the same username, password and other database connectivity options. The database password is ofcourse encrypted properly. The keys you would need are the ones that begin with DB* as shown above. ^

 

007 – Configure cache update interval

SOFTWARE\RES\PowerFuse\CacheTimerInterval (REG_SZ) = #seconds

Valid from Workspace Manager 2008 SR4 (8.0.4.5). The described method here is obsolete as it’s now possible in the Workspace Manager 2010 console to configure this behavior more detailed. Look in the Setup|Agents node for the Agent update cache dropdown. The #seconds interval (valid range is 5-60 seconds) determines how often the RES service  checks for changes in the database or for new transactions locally that needs to be uploaded. The default for this interval is 5 seconds. This interval can be changed only in HKLM.

warning, yellowNotice: Changing the default of 5 seconds should only be done in special cases, such as if you anticipate heavy load on the database server. ^

 

006 – Disable screensaver when VDX is active

SOFTWARE\RES\PowerFuse\NoAgentScreensaver (REG_SZ) = Yes

Valid from Workspace Manager 2008 SR4 (8.0.4.5). When a RES Workspace Manager session is started from a workstation with the VDX component aka RES Subscriber Agent installed, the RES Workspace Manager session will enable a Screensaver by default. It is now possible to change this behavior, by setting the following registry string value in either HKLM or HKCU. ^

 

005 – Force LogOff of disconnected sessions after timeout

SOFTWARE\RES\PowerFuse\ForceLogoffEnabled (REG_SZ) = Yes OR NoSOFTWARE\RES\PowerFuse\ForceLogoffTimeout (REG_SZ) = #minutesSOFTWARE\RES\PowerFuse\ForceLogoffTimeoutOnDisconnect (REG_SZ) = #minutesSOFTWARE\RES\PowerFuse\ForceLogoffOnDisconnect (REG_SZ) = Yes OR No

Valid from Workspace Manager 2008 SR4 (8.0.4.5). It is possible from to force a logoff of disconnectd sessions after a specified timeout expires. This can be enabled by setting the following registry keys in either HKLM or HKCU. If you are already using the ForceLogoffOnIdle mechanism, the timeout in ForceLogoffTimeout can be used to use the same timeout for both mechanisms, or you can use a different timeout to disconnect by setting a value in ForceLogoffTimeoutOnDisconnect. ^

 

004 – Silently refresh RES Workspace Manager sessions

SOFTWARE\RES\PowerFuse\SilentRefresh (REG_SZ) = Yes

Valid since Workspace Manager 2008 SR5. This setting is somewhat obsolete since Workspace Manager 2010 as you can configure this behavior in the console in the Composition|Desktop|Lockdown and Behavior node. Look for the Hide Splash scren option. A silent refresh of RES Workspace Manager will not show a splash screen during load or refresh of the Workspace Composer, which may be perceived as less intrusive on the ser. A silent refresh will only be used when the refresh is a result of a display change, a USB device change or a reconnect of a disconnected session. Note: In the Workspace Manager 2010 console this is only available as a global option, i.e. you cannot have the splashscren turned on for some users and off for others. The setting can be configured in HKLM or HKCU and is not created per default. ^

 

003 – Tweak how Memoryshield counts application instances

SOFTWARE\RES\PowerFuse\MSLimitOnProcIDs (REG_SZ) = Yes OR No

Valid from Workspace Manager 2008 SR5. With MemoryShield, you can limit the number of running applications per session. This limits the number of tasks on the taskbar, which is not always equal to the number of running applications. For example, 3 open e-mails in Microsoft Office Outlook count for 3 tasks, whereas there is only one running application. You can now set one of the following registry settings to ensure that tasks belonging to the same running application are counted only once by MemoryShield. You can set the registry key in either HKLM or HKCU. ^

 

002 – Make Workspace Manager use AD “displayname” instead of “fullname”

HKLM\SOFTWARE\RES\PowerFuse\UseDisplaynameasFullname (REG_SZ) = Yes

Valid and working from Workspace Manager 2008 SR6. It is possible to use and show the Active Directory property “displayname” instead of “fullname”. When using the “displayname” property, it will be shown in the Full name column in the Workspace Sessions and Workspace Analysis nodes. It will also influence the full name that is shown to the user in a RES Workspace Manager session (for example in the PowerPanel’s User tab). This can be enabled by setting the following registry key only in HKLM. Note: This feature only works in an Active Directory environment. ^

 

001 – Tweak how User Installed Applications authorizes non-managed applications

SOFTWARE\RES\PowerFuse\PMWAutoAllowFolders (REG_SZ) = Yes

Valid from Workspace Manager 2008 SR5. In order to allow more complex apps with multiple executables and other unknowns to be installed by a user trusted with the User Installed Application right,  in an environment where both AppGuard and Read-Only Blanketing are enabled, set the registry key to “Yes” in either HKLM or HKCU. This will automatically authorize all executables found in the folder where the executable specified in the PMWS wizard was found. Note from Workspace Manager 2010 SR2, this feature is now a checkbox in the console, found under Composition|Applications|User Installed Applications. ^

 

000 – Enable Workspace Manager trace mode

Valid from Workspace Manager 2008 (8.0.0.0) Trace mode enables a detailed diagnostics logging mode built into Workspace Manager. This is very useful if you are experiencing technical difficulties with the product. When you enable tracing, a continuous 2MB logfile will be created, i.e the log will never grow bigger than 2 Meg.  If you decide to open a support ticket with RES Support, they are likely to be happy if you have this trace logfile at hand. It includes detailed information of what’s going on inside, enabeling RES Software’s engineers to better and quicker figure out what’s going on.There is a seperate article RG015 which discusses tracemode and other tools of the trade. Click here to read.

 

^

force LogOff of disconnected sessions after timeout

No Comments

No comments yet.

RSS feed for comments on this post.

Leave a comment

Comments are welcome as always. Just do the math below. * Time limit is exhausted. Please reload the CAPTCHA.