Video Screencast Help
Scheduled Maintenance: Symantec Connect is scheduled to be down Saturday, April 19 from 10am to 2pm Pacific Standard Time (GMT: 5pm to 9pm) for server migration and upgrade.
Please accept our apologies in advance for any inconvenience this might cause.

SVS Cleaner

Created: 17 Nov 2006 • Updated: 29 Jul 2010 | 9 comments
CondorMan's picture
+1 1 Vote
Login to vote

SVS Cleaner is a handy utility that will organize and optimize the registry and files in your layers.

After creating a new layer and before exporting it, run SVS Cleaner to do the following:

  1. Organize registry and file structure of layers. This ensures that your layers are completely portable.
  2. Remove uninstall information from layers (optionally). Generally, you will not want uninstall information in your layers, because if you have any problems you will either remove or reset the layer.
  3. Clean registry settings and files of layers. This will remove registry settings and files that should not be part of the layer. This will increase performance and reliability. This also keeps the size of your vsa's as small as possible.

Updates:
17 Nov 06 Uninstall information is no longer removed by default because some software requires it. You can still enable the removal of uninstall information by enabling the check box.

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.

Comments 9 CommentsJump to latest comment

StevieMcR's picture

Be aware of Adobe products.

License info is in the uninstall information so if you remove this your app won't work anymore.

0
Login to vote
icecycle's picture

(0xc0000135)

winxpsp2

0
Login to vote
macten's picture

I'm getting the same error. Any resolution?

0
Login to vote
dbunten's picture

You need to have .NET 2.0 installed for SVSClean to work. This should probably be documented somewhere as a dependency.

0
Login to vote
Scott Hardie's picture

This is not something you will always want to do because the uninstall not only contains the license information but -- if you have plans to use SVS in future revisions to write permanently to the base line -- you have the potential to lose the local self-healing capabilities of .msi based applications. Unless, of course, you plan to use Application Management Solution to redirect self healing source paths.

For a laptop user this is important because the remote source path may not be available when they're not on the corporate network or VPN.

Just food for thought. If you plan on doing so and do not want to have to recreate your layers at a later point.

James "Scott" Hardie
Vice President of Technology Services
shardie@xcendgroup.com
http://www.xcendgroup.com

James "Scott" Hardie
Security Architect
Security Business Practice
Symantec Corporation
www.symantec.com
__________________________________
Office: (810) 588 9464
Mobile: (810) 588 9464<

0
Login to vote
Wm Jesse Foster's picture

CondorMan thought ahead. By modifying the .csv file, you can control what gets removed.This feature makes the tool flexible. I think that is just good design.

0
Login to vote
Scott Jones's picture

Adam, ref: "future revisions to write permanently to the base line" -- SVS will never give you the ability to "merge" (the official term) an application layer to the base. (At least, not as a product feature -- tho you are invited to write your own tool!) Read my post in this thread for the reason why.

Regardless, today SVS depends on the source .MSI being in the layer in order to correctly handle self-healing and updates (including Office Update!). As long as the source .MSI is in the layer, SVS will correctly apply these changes to the writable sublayer of the application. If the source .MSI is outside the layer, the result of changes to the app made by the MSI Service will end up in the base.

So, CondorMan, it's rather critical that the source .MSI not be removed from the layer by default in your tool.

In the future, we may get more sophisticated and support .MSI source paths that point anywhere, but for the first release this was quick, simple and effective design.

Scott Jones
Business Critical Engineer, Endpoint Virtualization
Symantec Corporation
www.symantec.com
 

0
Login to vote
CondorMan's picture

Thank you for all of your feedback. I have submitted an updated version that has the removal of uninstall information disabled by default. You can still remove uninstall information by enabling the check box.

Remember, you can always customize which rules to use in the Advanced tab. You can also remove rules from and add rules to the SVSClean.csv file.

0
Login to vote
FrankB's picture

Is it possible to that you create a way to choose the layer that has to be cleaned?

I've tested your tool in a VM but I wasn't able to choose, if I do that on a live machine, which has already several clean layers, I wouldn't like them to be checked also.

Could that be possible you think?

Kind Regards, Starf0x.

PS, I think you expected this question :)

______________________________________________
Frank Bastiaens
Senior Technical Consultant
Vanderlet B.V.

0
Login to vote