RG005 RES Workspace Manager, Tips & Tricks

By Max Ranzau

 

This article is a collection of obscure things, of what is possible to do with Workspace Manager behind the scenes. There is no particular order to the items. All information below has been collected from the releasenotes, helpfiles and other available sources. Otherwise the information has been derived simply by playing around with Workspace Manager.

Inside the Workspace Manager Management Console

Mapping to WebDAV folders in PowerLauch

PowerLaunch driveletter mappings allow mapping driveletters to virtual directories on IIS. This is refered to as WebDAV (Web Distributed Authoring and Versioning) folders, which start with “http://” or “https://” instead of servershare. For additional information on how to configure WebDAV folders on IIS, go here and here.

This trick will enable you to map a network drive, say T: -> http://yoursharepointserver/somefolder

Using PowerLaunch to unmap existing network drives

You can unmap a mapping on a given level by using the dummy share name “unmap“ (without quotes) in the Share name field when editing the mapping. This is usefull if you are in a transition phase where you’re still mapping some drives from a loginscript and you want Workspace Manager to take over as you get everything implemented.

Update: This feature is obsolete in Workspace Manager 2010 SR1, as the drivemapping feature now has an Action setting, where you can select to Disconnect network drive, directly in the GUI.

Seat licensing versus file extensions:

If you chose per seat licensing for an application, Workspace Manager will automatically set the option “Only RES Workspace Manager is allowed to launch this application”. The effect of this is that file associations registered in the OS will no longer take effect. If you for an example set per seat licensing on Notepad.exe, you will no longer be able to edit .ini and .txt files just by doubleclicking or rightclicking on them. If you do, appguard will intercept you and notepad will be blocked.

The reason why this is happening is that Workspace Manager needs to be in control of when the target  application is launched. If we simply let explorer.exe start notepad, we would be unable to record the license usage.

In order to avoid this issue. you will need to configure instant file associations for the filetypes normally associated with notepad, such as .txt, .ini, .log etc.

Registry settings of RES Workspace Manager

Per August 30th 2010, all registry settings have been moved to a new seperate article RG02B, which is available right here.

| datetime January 17, 2009 12:43

2 Comments

Other Links to this Post

  1. RES Software User Group | SR5 PowerFuse update — May 20, 2009 @ 17:47

  2. » Powerfuse 2008 issues encountered — May 27, 2009 @ 18:22

RSS feed for comments on this post.

Leave a comment


three − = 2