Preserving Current User Registry - SVS
Hi All,
I’ve just entered the world of SVS and am trying to get my head around application and data layers. I understand that you have data layers for storing user data and that files and directories can be excluded from a layer – but how do you exclude registry data?
For example; PuTTY stores its saved session details in HKCU, when the PuTTY layer is reset this data is lost. How do I separate and exclude the HKCU registry key so that the user data is preserved?
Many thanks,
Charlie
I’ve just entered the world of SVS and am trying to get my head around application and data layers. I understand that you have data layers for storing user data and that files and directories can be excluded from a layer – but how do you exclude registry data?
For example; PuTTY stores its saved session details in HKCU, when the PuTTY layer is reset this data is lost. How do I separate and exclude the HKCU registry key so that the user data is preserved?
Many thanks,
Charlie
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
AngelD
17 years ago
Only directories or file extensions are able to be excluded, so sorry you can't exclude registry entries.
You would have to use an OnPreReset OnEvent action that would run for example a vbscript that backup/save the registry entries you want from the Writeable sublayer. You could launch "reg copy" from the script to save away the registry entry(ies) to example under HKCU and on OnPostReset and/or OnPostImport to restore saved registry.
I think it could be easier to handle this if you store the vbscript in the VZ_LAYER_METADIR directory and is included in the VSA file so the script will follow whenever you import the .VSA.
Here are some links from the Altiris Forum.
http://forums.altiris.com/messageview.aspx?catid=28&threadid=40153
http://forums.altiris.com/messageview.aspx?catid=43&threadid=40085
You would have to use an OnPreReset OnEvent action that would run for example a vbscript that backup/save the registry entries you want from the Writeable sublayer. You could launch "reg copy" from the script to save away the registry entry(ies) to example under HKCU and on OnPostReset and/or OnPostImport to restore saved registry.
I think it could be easier to handle this if you store the vbscript in the VZ_LAYER_METADIR directory and is included in the VSA file so the script will follow whenever you import the .VSA.
Here are some links from the Altiris Forum.
http://forums.altiris.com/messageview.aspx?catid=28&threadid=40153
http://forums.altiris.com/messageview.aspx?catid=43&threadid=40085
Posted by:
fuz_kitten
17 years ago
Phew, ok i'll tackle that tomorow! Thanks for the links, i rated your post.
Fuz
Fuz
Posted by:
AngelD
17 years ago
Here is another post from the Altiris Forum that uses a vbscript that to backup/restore registry using reg copy and the SVS provider.
http://forums.altiris.com/messageview.aspx?catid=28&threadid=35042
http://forums.altiris.com/messageview.aspx?catid=28&threadid=35042
Posted by:
fuz_kitten
17 years ago
What a can of worms! It looks like I've got some learning to do! To be honest I'm a bit daunted by making the jump to SVS. I love the idea of virtualizing things but I’m stating to feel out of my depth.
I guess if I want to keep my job I’m just going to have to pinch my nose and jump…
Thanks for all your help AngelD.
C
I guess if I want to keep my job I’m just going to have to pinch my nose and jump…
Thanks for all your help AngelD.
C
Posted by:
AngelD
17 years ago
As long as you have in mind that resetting or deleting a layer will remove data stored in the Writeable sublayer which is written during usage of the virtual application there should be no problem playing around with SVS.
Another import thing to understand is the Default Priority Order that apply to SVS.
example:
If you launch an executable/process from an application layer and that in turn executes a child process that is outside of that layer anything written by that child process will go into its own layer which could be another layer or base (not layer).
Another good link: Launching Two Versions of an App When Both Are Installed to the Same Location which Scott Jones has written (SVS product manager) that really explains in a nice way how to solve issues with the default priority order when launching the application through a shortcut.
Scott is a really nice fellow and I got to speak with him while my visit to ManageFusion Las Vegas in April.
Another import thing to understand is the Default Priority Order that apply to SVS.
example:
If you launch an executable/process from an application layer and that in turn executes a child process that is outside of that layer anything written by that child process will go into its own layer which could be another layer or base (not layer).
Another good link: Launching Two Versions of an App When Both Are Installed to the Same Location which Scott Jones has written (SVS product manager) that really explains in a nice way how to solve issues with the default priority order when launching the application through a shortcut.
Scott is a really nice fellow and I got to speak with him while my visit to ManageFusion Las Vegas in April.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.