SVS Layer Settings Migration Utility
As with any application, sometimes SVS layers need to be 'reinstalled' or updated. Of course, with SVS this is done by resetting a layer, or deleting the layer and importing a new one. When you perform either of these actions, you generally lose all of the personal settings configured on the layer before it is reset or deleted and re-imported.
This issue is addressed in the article here: http://www.symantec.com/community/tip/3132/even-le... which outlines a process whereby the settings for a layer may be backed up and then restored after the reset or delete/import occurs. The article focuses on MS office products, but I found that this process was effective with most all of the applications we have virtualized. Once more, going from one version of a layer to a newer one (sometimes even when the app version was newer), I found this procedure effectively restored personal settings.
The biggest hurdle in my environment is that with several thousand machines, there is no way we could deploy a new version of a layer and retain the settings in this way given the amount of time and effort it would take to manually perform the backup/restore.
So then, I created a command line utility that does it for me. It takes in as arguments: the old layer name, the new layer name, and either the path to the new layer or a switch indicating you just want to reset the layer. It can be run from a flash drive, network drive, or can be built into an NS or DS job. Running it without any arguments will bring up the help window, and it has a verbose mode as well. As of this writing, I have not yet built in return codes for the executable.
Obviously, you will want to test it with any layer or layers to be sure it is migrating the settings over correctly before a production roll out. Generally, if ANY of the settings are restored you can assume that all that can be have been. Keep in mind though, that it does not (could not) test for settings compatibility between layers. You could conceivably mis-match a new layer - e.g save the settings from MS outlook, and restore them to a layer of adobe acrobat if you gave it the parameters to do so. Not sure what would happen there, but as you can imagine, probably not what you want. And while resetting the new layer would resolve the issue(s), the settings you were hoping to restore would be gone.
Some apps have additional settings that are stored in different places, so they can't always all be restored via the method this utility currently uses (see article above). However, I'd be happy to modify it to include other methods if anyone knows of other common places SVS app settings are stored. I've tried to create a universal utility that can be used with any layer, but I'm open to creating specialized versions if there is a need...
| License: | AJSL By clicking the download link below, you agree to the terms and conditions in the Altiris Juice Software License |
| Support: | User-contributed tools on the Juice are not supported by Altiris Technical Support. If you have questions about a tool, please communicate directly with the author by visiting their profile page and clicking the 'contact' tab. |
| Attachment | Size |
|---|---|
| SVS_Migrate_Settings.zip | 276.87 KB |
- Login or register to post comments
- 3573 reads
- Printer-friendly version















Good job
Good job,
We do this by using flexprfl.exe from Microsoft.
Flex is in the Office resource kit for Office 2000, and can be downloaded form the Microsoft website.
And it is not only for Office, but you can use it for all software you want.
Creating a command line in the package with a prereset to save, and a post reset to restore.
i posted a article about this already.
Regards
Erik
www.dvs4sbc.nl
I can't believe that this
I can't believe that this wasn't thought of before. It's great to see this tool. We've been debating on how to handle a particular family of products from a specific manufacturer that has quarterly service pack updates.
One of the best things about SVS was the thought that you could make quick switches on SVS Layers to reset things after a disaster, but losing all of the settings so frequently for this particular manufacter's product was too much of a hinderance to use SVS.
I'm going to test it out.
Thanks.
Best implementation practice
Skakid,
SVS is a great program with great purposes. One of the best things is that you are able to run a applikation with and without a specific service pack at once.
But the best implementations are doen with additionel tools.
Use SVS with CACLS, and you bring in Rights management.
Use SVS with Flex, and you bring in registry and file import and export functionality.
Read the Juice at least once a week, and keep you're knowledge updated with the best knowledge there is.
But you have one pitfall.
SVS implementations can only be succesfull if you are able to build good and stable packages.
I gie trainings all over europe, and even good packagers are stunishd of what possibility's there are to build better packages.
Regards
Erik
www.dvs4sbc.nl
Scott's solution is really
Scott's solution is really stupid simple which is why none of us probably ever thought of it before, we're trying to over complicate something that wasn't.
Good to see someone make this tool chaotech, I've got something planned to do this but haven't gotten to it yet.
Source Code?
I am curious what you created the exe with and if you would be willing to share the source code? I see some real practical purposes for both features but I am most interested on retaining users settings through a reset. Are the commands svscmd based? Ultimately I think it would be most useful if this was something that could be added as an Event Pre Reset wisescript that was dynamic enough that it could be added to every package.