Video Screencast Help

SVS package for Win 7

Created: 16 Aug 2010 • Updated: 12 Oct 2010 | 9 comments
This issue has been solved. See solution.

Hello to everyone,

I have a problem with SVS packages. I created Office 2003 package for Win XP - it works fine, no problems. But when I deploy the same svs package to Win 7 it is not working.
I tried to create a package on Win 7 machine but I am having problems - installation starts and finishes after a second and the SVS admin closes the layer.

Is it possible to create a SVS packages on Win XP and then deploy to Win 7?

What is best practise for 'global excludes'? Shall I exclude whole "documents and settings" directory?

Thanks.

Comments 9 CommentsJump to latest comment

Jordan's picture

What version of SWV are you using and is the win7 64-bit?

If a forum post solves your problem please flag is as the solution

corso's picture

Hello Jordan,

I use the SVS 2.1.3066, and it is Windows 7 - 32bit - I have not tried 64bit yet...

Thanks.

Jordan's picture

SVS 2.1 does not support Win7, you'll need to upgrade to at least SWV 6.1 SP1 for Win7 support.

If a forum post solves your problem please flag is as the solution

SOLUTION
corso's picture

I used SVS agent which comes with CMS 7 - latest release. Could you please let me know where I can download latest SVS? Is it the case of adding a software release to Software Catalog and creation of a software deployment policy?

Thank you for your help

corso's picture

Jordan,

I've just had a look at the console and there is SWV agent 6.1.5126 in the Software Catalog - I did not notice it earlier and I did not know that it replaced SVS agent. I just set CMS 7 up so I do not have many managed PCs yet. What do you suggest:
1. Replace SVS agent on all Win XP machines with SWV agent> (it's only few machines so it won't be a problem).
2. Use SWV for Win 7 machines and stick to SVS on XP? - it does not seem to be a good idea because I will have to create 2 virtual packages - one for SVS one for SWV.
4. Are SVS packages compatibile with SWV? in such case I will not have to create a new packages...

Please advise.

Thanks.

Jordan's picture

I would upgrade all to SWV which is just the next version of SVS, the releases go from SVS 2.1 -> SWV 6.1, and because of that all packages are forward compatible meaning anything made by SVS will work with SWV but not the other way around.

If a forum post solves your problem please flag is as the solution

corso's picture

Thanks for your help. I did some testing today and it worked well. Thanks.

Jordan's picture

No problem.

If a forum post solves your problem please flag is as the solution