Video Screencast Help
Endpoint Virtualization Community Blog

Symantec Workspace Virtualization - Setting File & Registry Permissions

Created: 28 Nov 2010 • Updated: 23 Feb 2011 • 3 comments
Scot Curry's picture
+1 1 Vote
Login to vote

I was working on an update to my Packaging Best Practices document.  I was beginning to write the section on selecting the operating system.  One of the issues with using Windows 7 or Windows Vista is that these OS's don't allow applications to write to protected areas.  Using Workspace Virtualization it is possible to set permissions on both files and registry.

Once a layer has been captured you can set permissions on the folders and files using the same tools you would for a physically installed application. The one difference is that you will need to set the permissions on folder in the redirection directory (usually C:\fslrdr\#) before exporting the layer. You will need to find the layers read only number.  You can find this in the Workspace Virtualization Admin tool by selecting View -> Details. 

Setting permissions on the registry requires a couple of special steps.  You will need to find the layers read only number as you did with the file permissions above. Make note of the number you want to modify, then use the following steps:

  • Activate the layer on which you want to set permissions (you can also just view the layer properties and the registry will be mounted).
  • Open regedit and navigate to HKEY_LOCAL_MACHINE\_SWV_LAYER_# (where # is the number of the read only layer).
  • Navigate to the registry key that needs to be modified
  • Modify the permissions on the key by right clicking on the key and selecting Permissions...
  • Set the permissions for the keys you want to modify, deactivate and export the layer.

The permissions for the registry key will become part of the layer, and will be applied when the layer is imported to another machine.

Comments 3 CommentsJump to latest comment

MikeWoodd's picture

Scott, thanks for the article.

I can't wait for your updated Packaging Best Practices doc... really, I mean that, I have a project underway that could really use it. :)

Login to vote
murphmf's picture

Along the lines of file permissions. I would like to be able to edit a config .dll in a captured program's directory. The file in question is automatically placed into the read-only redirect path. I can edit this file and save the changes while the application is Activated on Windows XP, but not on Windows 7. I have set full permissions on both the C:\Program Files and C:\fslrdr directories and still can not save changes made in a text editor to this file. Trying to save the text file produces a Save As prompt and the process results in a "Access is denied" error. Any suggestions? 

Login to vote
murphmf's picture

Just to close the loop on this before anyone responds. Turned out to be a Windows 7 permissions bug and I solved it by following this thread:

Login to vote