Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Virtualization Community Blog

Command Line Switches for New SWV Installer

Created: 08 Oct 2010 • Updated: 10 Nov 2010 • 36 comments
Jordan's picture
+6 6 Votes
Login to vote

With Symantec Workspace Virtualization 6.1 SP6 we introduced a new EXE based installer that replaces our standalone MSI installer, which is now wrapped inside the EXE, because we’re now installing a Visual C++ runtime that’s required for XPF package support. 

This new installer supports most of the old install options that the MSI did but the switches are a little different:

Command line arguments for SWV standalone installer:

/s ---- Silent mode running 

/e ---- Display error and reboot messages. This option will only work with /s and returns a standard MSI error code.

SWV.ADDLOCAL=SVS_Admin,SDK,Altiris_NS   ---- To install admin, sdk, NS.  You can pass them in any order or only one.

SWV.INSTALLDIR=<PATH>  ---- To specify the target dir for the installation

SWV.DEFAULT_FILE_REDIR=<PATH> ---- To change the meta data storage folder (Virtualization "redirect" directory). The default value is <system drive>:\fslrdr

SWV.PRODUCT_KEY=<PRODUCT KEY> ---- To specify the product key.

SEV.INSTALL=SWV  --- To install SWV alone (Using this option will not install VC runtime)

SEV.CFG=<CFG FILE PATH> --- Configuration file that contains the installer properties and values.

An example command line that would install everything would be: Symantec_Workspace_Virtualization.exe /s /e SWV.PRODUCT_KEY=xxxxx-xxxxx-xxxxx-xxxxx SWV.REBOOT=ReallySuppress SWV.ADDLOCAL=SVS_Admin,SDK,Altiris_NS

You’ll notice that we don’t have the option for not installing the default Global Excludes for Desktop and My Documents as these are no longer optional and are always installed.

Also by default a log file is saved to %systemdrive%\SWVAgent.log

One more thing of note is the SEV.CFG switch will you can use to pass in a config file that contains any of the above switches in it that start with SWV or SEV.  This is just a simple text file with each option in its own line.  Taking the previous install example from above you would create a text file containing the following:

SWV.PRODUCT_KEY=xxxxx-xxxxx-xxxxx-xxxxx

SWV.REBOOT=ReallySuppress

SWV.ADDLOCAL=SVS_Admin,SDK,Altiris_NS

To then call your config file you’ll need to do the following:  Symantec_Workspace_Virtualization.exe /s  SEV.CFG=test.txt

Comments 36 CommentsJump to latest comment

dpowell2's picture

Has 6.1 SP6 been re-released?

-3
Login to vote
jebba's picture

THANK YOU !!!!

the documentaion on these switches is poor at best - This helped!!!!

+2
Login to vote
SilentCastle's picture

Hi,

I can only find the SP4 version under trialware.  Does anyone have a link for SP6?

+5
Login to vote
daveram's picture

SilentCastle,

     SP6 was pulled back due to a bug with deleting all the installed printers. As of right now, SP4 is the latest release.

David Ramazetti

Senior Technical Solutions Consultant

XCEND Group

-5
Login to vote
ManelR's picture

Hi Jordan,

If we use the MSI package, will the C++ runtime be installed?

Thanks.

IT Systems Manager
LCFIB - Computing Lab
Barcelona School of Informatics
Universitat Politècnica de Catalunya - Barcelona Tech
0
Login to vote
Jordan's picture

No it will not.  The MSI does not contain the C++ runtime that is needed, which is one that's distributed with Visual Studio and not available via Microsoft's website.

We realize that this isn't the most ideal solution so if you have a preference with how you install SWV let sales know.

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

0
Login to vote
ManelR's picture

Hi Jordan,

I have the MSI for 6.1 SP6 MP1.

Can I install using this command?

msiexec PRODUCT_KEY=xxxxx INSTALL_ADMIN=1 REBOOT=ReallySuppress

or must I use:

msiexec PRODUCT_KEY=xxxxx ADDLOCAL=SVS_Admin REBOOT=ReallySuppress

Thanks.

IT Systems Manager
LCFIB - Computing Lab
Barcelona School of Informatics
Universitat Politècnica de Catalunya - Barcelona Tech
+1
Login to vote
Jordan's picture

If using the MSI, note that installing via the MSI is not recommended--especially on XP, you can use the old silent install stuff.  So the first one you listed.

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

-4
Login to vote
ManelR's picture

We're installing it in Windows 7 x86 with the first one command line.

Thanks.

IT Systems Manager
LCFIB - Computing Lab
Barcelona School of Informatics
Universitat Politècnica de Catalunya - Barcelona Tech
-4
Login to vote
Jordan's picture

The exe lays down files that are required for creating and consuming XPFs, the MSI does not install these files, but Win7 has most of the required files for XPF installed by default where earlier OSs don't.

So basically if you install via the MSI on XP XPF will not work.

If you install via the MSI on Win7 XPFs should work but this scenario is not supported, if you run into an XPF problem because you installed via the MSI support will tell you to reinstall with the exe.

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

-2
Login to vote
davidhilling's picture

This isnt working through the DS, we used the exe with the /s swv.cfg=svsadmin.txt

which contains

SWV.PRODUCT_KEY=*KEY*

SWV.REBOOT=ReallySuppress

SWV.ADDLOCAL=SVS_Admin,Altiris_NS

we also tried it straight command line it installs the agent but ignores the product key and addlocal commands.

edit = though we are on DS6.9 SP2 so that may be affecting it on win 7 we are upgrading to sp4 later this week. Ill try it on xp as well see if it works.

+4
Login to vote
Jordan's picture

Ya I didn't put it in the blog post but we ignore all product keys when installing via the EXE, not sure why that decision was made but it's what the higher ups wanted, so bascially you don't need a licnese key when installing via the EXE.

Not sure why your ADDLOCALs aren't working.

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

0
Login to vote
Jordan's picture

So your problem is that it should be SEV.CFG and not SWV.CFG.

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

+3
Login to vote
davidhilling's picture

That would explain it... worked perfectly now on the two I tried.

+4
Login to vote
ManelR's picture

Hi Jordan,

I was using the MSI because we were trying to upgrade 6.1 SP4 agent using a job in DS 6.9 SP4.

But, as you suggested, we have a lot of problems with 6.1 SP6 MP1 (Lotus Notes don't start, Office programs have erratic behaviour, file associations don't work, open attachments from mails don't work too, etc.).

The same environment with 6.1 SP4 works perfectly so ...

I'll try to setup the environment using the EXE instead of the MSI to see if that solves something.

Thanks.

Edit 09/Nov/2010: Jordan, in chapter 3 of Symantec Workspace Virtualization 6.1 SP6 User's Guide, all the instructions are given for the MSI installation process. Why then is not supported?

IT Systems Manager
LCFIB - Computing Lab
Barcelona School of Informatics
Universitat Politècnica de Catalunya - Barcelona Tech
0
Login to vote
Jordan's picture

That's just a documentation error, something obviously got overlooked.

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

+2
Login to vote
jhammons's picture

here: http://www.symantec.com/docs/DOC3208

The version attached to that article contains the switches for the exe installer.

+3
Login to vote
davidhilling's picture

When I install the agent on XP it appears to work fine, when I run it with the same commands on Win 7 X32 and x64 I get this in the log

('svs_admin') not found in feature table

Internal error 2711. svs_admin

I opened the MSI in wise the feature is there and by that name so it appears there may be a bug in the the installer or something. If I install the agent without installing the svs_admin it appears to work fine. Though if I do it manually it is also fine. 

0
Login to vote
Jordan's picture

The command line stuff for the new installer is case sensitive so please check to see if your WIN7 script is what I posted in this blog.

If the exact same script was working on XP but not Win7, ie you have a batch file you're running this from, please reply with the script so I can look at it.

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

-5
Login to vote
Easy_Livin's picture

With all the bugs it is best to not use this version until we can download it off the trialware? I was working with one of the sales engineers and was told this version was the one to go with. Seems like both sides of the house need to talk more often as this makes deployment of your product very iffy at best.

-1
Login to vote
Jordan's picture

No this is the one to go with.  I'm not sure why people are seeing all the installer issues that they are.

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

0
Login to vote
Jordan's picture

So I did some investigating and talking with the tester over install and apparently the command line, and config file, is case sensitive--which I wasn't aware of.  So if people are seeing any issues please make sure your script matches what I posted exactly.

If you're still having problems please post exactly what script you're using in your comments so I can look at it.

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

+1
Login to vote
davidhilling's picture

Heres the command im using

/S  SWV.PRODUCT_KEY=*KEY* SWV.REBOOT=ReallySuppress SWV.ADDLOCAL=SVS_Admin,Altiris_NS

should I also try capitalizing Admin in SVS_admin? Though i do notice in the log it shows the whole thing as lowercare.

Thing is if I run this command it does work

 /S SWV.PRODUCT_KEY=*Key* SWV.REBOOT=ReallySuppress SWV.ADDLOCAL= Altiris_NS 

So it most def has something to do with just the SVS_Admin part.

+3
Login to vote
PHcadidevile's picture

I'm having issues with the installer not finishing and the exe still running which then stops my other installs from running.  It installs all the files in c:\PF but the log file says ( below ) -  I'm using the exe with sp6 and I also used your command line on top with the same result. Anything can you provide feedback ?  thanks

exe /s   sample above

2010-11-09 13:03:20 Property(S): OriginalDatabase = C:\ProgramData\Symantec\SEV\GLFC92\Symantec_Workspace_Virtualization.msi
2010-11-09 13:03:20 Property(S): UILevel = 2
2010-11-09 13:03:20 Property(S): ACTION = INSTALL
2010-11-09 13:03:20 Property(S): ROOTDRIVE = C:\
2010-11-09 13:03:20 Property(S): CostingComplete = 1
2010-11-09 13:03:20 Property(S): OutOfDiskSpace = 0
2010-11-09 13:03:20 Property(S): OutOfNoRbDiskSpace = 0
2010-11-09 13:03:20 Property(S): PrimaryVolumeSpaceAvailable = 0
2010-11-09 13:03:20 Property(S): PrimaryVolumeSpaceRequired = 0
2010-11-09 13:03:20 Property(S): PrimaryVolumeSpaceRemaining = 0
2010-11-09 13:03:20 Property(S): SOURCEDIR = C:\ProgramData\Symantec\SEV\GLFC92\
2010-11-09 13:03:20 Property(S): SourcedirProduct = {88C8B390-F9DD-443D-A9E5-D2F1551A0BFB}
2010-11-09 13:03:20 Property(S): MsiRebootActionScheduled = 3
2010-11-09 13:03:20 Property(S): ProductToBeRegistered = 1
2010-11-09 13:03:20 === Logging stopped: 11/9/2010  13:03:20 ===
2010-11-09 13:03:20 Error CMSIExecutor::Execute C:\ProgramData\Symantec\SEV\GLFC92\Symantec_Workspace_Virtualization.msi failed with error code 3010
2010-11-09 13:03:20 CMSIExecutor::Execute Changing the Installer object status to 1
2010-11-09 13:03:20 CInstallerObject::Execute Executing postinstallation.
2010-11-09 13:03:20 CSetupManager::Execute return value 0
2010-11-09 13:03:20 CInstallerObject::Execute End of postinstallation.
2010-11-09 13:03:20 *********************************** ended ***********************************
2010-11-09 13:03:20 CSetupManager::Execute return value 0
2010-11-09 13:03:20 CSetupManager::VerifyAndTriggerReboot Going to verify and trigger the reboot

0
Login to vote
Jordan's picture

humm.  So our MSI is throwing error 3010 which is the generic MSI error for a reboot is required. If you manually reboot is the driver installed?  You should be able to test this by using SVScmd.

What OS are you trying this on?

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

0
Login to vote
PHcadidevile's picture

Yes the software is installed and working but the exe never ends so it just looks hung. No new installs can continue down the install script

Windows 7 32bit Ent

+1
Login to vote
ManelR's picture

Hi,

I'm installing without problems using the EXE with the following command line:

Symantec_Workspace_Virtualization.exe /s SWV.PRODUCT_KEY=xxxxx-xxxxx-xxxxx-xxxxx SWV.REBOOT=ReallySuppress

My environment is Win7 x86 too.

Hope this helps.

IT Systems Manager
LCFIB - Computing Lab
Barcelona School of Informatics
Universitat Politècnica de Catalunya - Barcelona Tech
+1
Login to vote
PHcadidevile's picture

thanks for your post but even with a cut and copy of your command line  same message in logs and the process never finishes. I am going to try it on a system without smp 7 agents installed on it and repost

+2
Login to vote
Jordan's picture

We haven't seen your issue on our machines.

If that doesn't work for it could you let us know what AV you're using?

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

-4
Login to vote
ManelR's picture

Hi,

We setup the SWV Agent before our antivirus (is McAfee VirusScan 8.7i) and it installs properly.

IT Systems Manager
LCFIB - Computing Lab
Barcelona School of Informatics
Universitat Politècnica de Catalunya - Barcelona Tech
0
Login to vote
PHcadidevile's picture

I tried it on  a win 7 32 bit without anything installed and it works just fine. I also install it before Mcafee and it hung.  It maybe another application that even after a reboot it will never let it "finish" or close.   I thought it was a hung msiexec from a diffrent install but even if I rem out the install and let my imaging process finish and try to install ir manually  with the switch  it never finishes.     I will post what application caused this    hopefully its not APPV :/

+2
Login to vote
PHcadidevile's picture

it works just with the /s switch if I put it as the first installed program in my install script. Sorry I don't have the time to cut 30 apps one by one to figure out the problem one but hope this helps others

+3
Login to vote
rene.piuk's picture

I got the Solution!!!

If you have problems with the Symantec_Workspace_Virtualization.exe use the MSI!!

So where can you found the MSI? Also you need two installations. One for the C++ runtime and one for the SWV.

Under „%ALLUSERSPROFILE%\SYMANTEC\SEV” you will find a Folder beginning with GL

There you find all extracted files.

For C++ runtime you need vc_red.cab and vc_red.msi

For SWV only the Symantec_Workspace_Virtualization.msi

In NS7 (hope NS7.1 also) you create a SW-Resource for the C++ runtime and then create a SW-Resource for SWV. In the SWV Resource you change the dependency to the C++ runtime.

Sample Command Line for SWV:

msiexec.exe /i "Symantec_Workspace_Virtualization.msi" PRODUCT_KEY= xxxxx-xxxxx- xxxxx - xxxxx ADDLOCAL=Altiris_NS REBOOT=ReallySuppress /qn ALLUSERS=2

msiexec.exe /i "Symantec_Workspace_Virtualization.msi" PRODUCT_KEY=xxxxx-xxxxx- xxxxx - xxxxx ADDLOCAL=SVS_Admin,Altiris_NS REBOOT=ReallySuppress /qn ALLUSERS=2

Properties Specific to SWV

Install the Virutalization Administration tool (GUI)

ADDLOCAL=SVS_Admin

Install the Virtualization SDK, Documentation, Libraries, Headers and sample code

ADDLOCAL=SDK

Altiris Notification Server Install

ADDLOCAL=Altiris_NS

Install all the features

ADDLOCAL=SVS_Admin,SDK,Altiris_NS

specifiy A different installation directory than the default:

INSTALLDIR="C:\Program Files\Alt Symantec Workspace Virtualization"

specifiy A different Virtualization "redirect" directory.

DEFAULT_FILE_REDIR="C:\fslrdr"

Maybe also interesting the newest version of SWV is 6.4.1236 can be downloaded at

https://fileshare.symantec.com

UID: sevrelease

PWD: S!m4NT3c

+2
Login to vote
Pascal KOTTE's picture

Yes, I see the Altiris integration option flag is now a feature in the latest packages. But I wonder if the old flag

  • ALTIRIS_NS=1

still working or not? As I see also another guy not working correctly with the flag

  • ADDLOCAL=Altiris_NS

Should try this.

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

-2
Login to vote
Pascal KOTTE's picture

Exactly what I propose in there

https://www-secure.symantec.com/connect/blogs/how-get-svs-or-swv-where-download-svs-21-and-swv-61

Why not still providing also the MSI, as done before ???

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

+1
Login to vote
Jordan's picture

If people want an MSI let sales know so PM can make that descision.

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

0
Login to vote