This post describes some random performance tips, triggered by some issues reported at RES Software Support.
When you are busy in maintaining everything for your users, you might ‘forget’ to plan some maintenance within your RES Workspace Manager Console. After changes within your IT infrastructure you probably have to make some cleanup actions within your RES WSM environment.
This blog is based on RES Workspace Manager 2011.
Create a RES Datastore backup and Building Blocks to have a proper fallback scenario.
The next steps can positively influence your RES WSM environment.
These are sorted like the order within the RES Console.
1.1 Clean up Directory Services (Context – Directory Services)
Check for Directory Services or Microsoft Windows domains which became obsolete after a migration for example.
These Directory Services are only needed to give Access Control to objects within the RES Console. Remove Directory Services which are not needed for this purpose.
If your environment does not include trusted domains, uncheck ‘allow query from other domain’ will make sessions start up faster
**Note: It is possible to exclude yourself from access to the console when removing or changing Directory Services. Be sure the correct accounts were added to the Technical Manager role.
2.1 Applications (Composition – Applications)
Microsoft App-V applications.
Since RES Workspace Manager 2011 SR2 + Microsoft App-V 4.6 on Windows 2008R2 multiple sftmime.exe processes can cause server performance degradation.
Check this Knowledge Base article for a resolution: http://support.ressoftware.com/Modules/KnowledgeBase/knowledgebaseTreeView.aspx?id=3190
2.2 User Settings (Composition – User Settings)
- Compress User Settings: New enhancement in RES WSM 2011 SR2
This feature proved itself in production environments, reduced logon times, reduced performance load on file server and network during mass logon/logoff.
**Note: All Agents must run RES WSM 2011 SR2, Compress User Settings is not backwards compatible!
- Check if Folder Redirection and User Settings do not overlap.
When for example redirecting %APPDATA% and saving settings from the
%APPDATA% location with User Settings, settings are being saved twice.
- Windows Metrics registry might be applied slowly by User Settings: http://support.ressoftware.com/Modules/KnowledgeBase/knowledgebaseTreeView.aspx?id=2709
3.1 Security Authorizations (Security – Global Authorized Files)
Quick wins can be achieved here. At logon all rules must be checked and processed by the AppGuard driver, each optimization will be effective immediately.
Check ‘Show all authorized files’, sort by Authorized File and:
- Remove duplicate entries
- Remove rules to non-existing paths and/or servers
- Where possible, apply rules on application level, rather than globally
- Combine rules: When 8 applications are authorized for the same executable, combine to 1 rule
3.2 Security mode (Security – Data)
Check for Security options set to ‘Learning’. Learning mode is a phase between Disabled and Enabled. In Learning mode nothing will be blocked, but you have to maintain the logging and have the goal to enable this option within a short timeframe.
There is no need to run a few months in Learning mode, this will only fill up your database.
4.1 User Eventlog (Diagnostics – Workspace Analysis)
Regularly check the User Eventlog for errors or gaps in timing.
Example: a phased out printserver might not be accessible and cause a logon delay
5.1 Agents vs. Database connection (Setup – Agents)
‘Poll for Database changes’ and ‘Update Agent cache’ are default set to have the most accurate responding RES environment. Obviously this is also the most demanding setting for your environment. Critically decide what the best setting is for your setup.
By default a RES Agent will check each 5 seconds for database changes (Poll for database changes). Changing to 1 minute will reduce the network traffic per RES Agent with approximately 80% for these DB checks.
Likewise increasing the Update Agent Cache will set the frequency with which Agents update their cache. This is randomized to spread out the load on the Database server hosting the RES Datastore. Especially used in environments with thousands of desktop clients.
** Note: Increasing these intervals will cause slower cache updates.
Simplified cache update timing sequence:
5.2 Maintenance Tasks (Setup – Datastore – Maintenance)
Perform Maintenance tasks to cleanup outdated information:
- Check License Lock Info
- Cleanup Logs
- Compact Audit Trail: This reduces the Datastore size and lowers network traffic
- Search for and remove non-existing users
- Verify Database Integrity