Video Screencast Help
Endpoint Virtualization Community Blog

Problems with WMI when you upgrade from SWV 2.X to SWV 6.1

Created: 31 Mar 2009 • Updated: 29 Jul 2010 • 19 comments
Jordan's picture
+4 4 Votes
Login to vote

Some of you may notice when you upgrade from any version of SVS to SWV 6.1 that WMI doesn't work.  This is a known issue that we found late in the test cycle but it's very easy to workaround.  What's happening is basically the WMI provider isn't getting registered and the old one is gone (we've moved the install path of SWV).  So there are 3 options to fix this issue:

1) Uninstall SVS and do a clean install of SWV 6.1
2) After the upgrade run a repair on SWV 6.1 via Add or Remove Programs.
3) Run the following Batch commands:
regsvr32 "C:\Program Files\Symantec\Workspace Virtualization\SvsWmi.dll" /s
mofcomp "C:\Program Files\Symantec\Workspace Virtualization\SvsWmi.mof"

And just as a reminder, this is only for upgrades not clean installs.  And if neither of these workaround do solve WMI issues with 6.1 upgrades please post in the comments section.

Comments 19 CommentsJump to latest comment

Tech-O's picture

Did Symantec Release version 6.1

0
Login to vote
FrankB's picture

This helped a bit, but all the features are missing of those that are now in the 6.1 beta version.

Cheers, FrankB

______________________________________________
Frank Bastiaens
Senior Technical Consultant
Vanderlet B.V.

+2
Login to vote
Tech-O's picture

people who own 2.1 will not have the new features of 6.1.. I find this to be rip, i need to get our account manager involved if this if true . Our company brought CMS II just for SVS and now they are saying that hey you don't own the new SWV suite so you don't get the new features of the (SWV)client. Then what do we get for buying CMS II (Nothing!!!!). a waste of money and our management is going to love this one 

+2
Login to vote
Jordan's picture

@emerkle: I see NOTHING! I know NOTHING!

@Frank: Unfortunantly none of the new features were added to WMI, I'm pushing for some in the next release like applying patches, if people have suggestions on what they'd like to do with SWV's WMI reply to this thread.  Also letting your account manager know and/or support know you want the new features in WMI will increase the likely hood of them getting in sooner.

@emerkle:  Please do check with your rep.  I know nothing of sales and who gets the upgrade for free and who doesn't so there's nothing I can tell you.

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

+2
Login to vote
Scot Curry's picture

Hi emerkle:

I have some good news for you.  If you are a CMS 6.x Level II customer you do get the new SWV 6.1 product as part of your AUP, so you will be getting all of the cool new isolation, patching, and multi-user features of SWV 6.1.

Hope you find this helpful.  Talk to you soon,
Scot

0
Login to vote
Tech-O's picture

I'm suprised since this is not what was communicated at MF in Vegas.
They said no isolation features or the multi-user(citrix) would be included. Only patching

0
Login to vote
Scot Curry's picture

Hi emerkle,

There was some confusion as to the exactly what was going to happen.  The reaction of the customers really caused the Product Management team to give a complete description of how we were going to proceed.  They have decided that the users who made the investment in CMS II had shown a commitment to Software Virtualization and they should get the new features.  Sorry about the confusion, and I hope you like the new features.

Scot

+3
Login to vote
JPFortune's picture

I was part of the beta for 6.1 and the release is very disppointing compared to the features in the beta.  Were there too many bugs or did other beta people really complain?

+2
Login to vote
Scot Curry's picture

I hope you are referring to the features that were released with CMS 7.  If that is the case, the CMS 6 Level I customers just get a virtualization agent as part of their upgrade.  Any customer that had CMS 6 Level II or TMS gets the complete Symantec Workspace Virtualization tool, which would have been all of the features (isolation, patching, dependant layers, multi-user, etc.) that you saw in the Symantec Workspace Streaming 6.1 beta.

Hope that helps

+3
Login to vote
Jordan's picture

@JPFortune: Not sure what you mean.  What version do you have?  You can get this via SVSadmin under the help menu.

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

+2
Login to vote
emilioVRT's picture

Hi Jordan, could you write down the script to run by command line to obtain the upgrade? I'm trying using that
start /wait msiexec.exe /qn /I Software_Virtualization_Agent.msi INSTALLDIR="C:\Program Files\Symantec\Workspace Virtualization" REINSTALL=All REINSTALLMODE=vomus INSTALL_ADMIN=1 product_key=XXXXXXX reboot=suppress /log c:\temp\upgSVS-SWV.log
but the agent remain always the old version. Note that I have to specify the new install directory because the 2.1 version is installed in c:\program file\altiris\Software Virtualization Agent while the new version by default is installed in c:\program files\Symatec\Workspace Virtualization

thanks

+1
Login to vote
Jordan's picture

what version of SWV 6.1 are you using?  The early beta didn't have the new install location which could be why you're having that issue.

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

-1
Login to vote
bulrich's picture

I'm having an issue still even after performing all three of the specified fixes for WMI in the begining of the article(copied below).   We have a script running that worked wonderfully with 2.1.  Attempting to test migrate to 6.1 to make sure everything works and we're stuck.

The line that is failing is as follows:

SET colItems = objWMIService.ExecQuery("Select * from VirtualSoftwarePackage" )

According to the documentation it's supposed to be a Class, yet when we looked for the Class it is not listed and we get an error 0x80041013 (which is provider not found).  We also listed all the providers and it's not listed as well.

Any suggestions?

------------------------------
1) Uninstall SVS and do a clean install of SWV 6.1
2) After the upgrade run a repair on SWV 6.1 via Add or Remove Programs.
3) Run the following Batch commands:
regsvr32 "C:\Program Files\Symantec\Workspace Virtualization\SvsWmi.dll" /s
mofcomp "C:\Program Files\Symantec\Workspace Virtualization\SvsWmi.mof"

And just as a reminder, this is only for upgrades not clean installs. And if neither of these workaround do solve WMI issues with 6.1 upgrades please post in the comments section.
-------------------------------------

+1
Login to vote
Jordan's picture

Need to know the version of 6.1 you've got (the numbers after 6.1).

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

+1
Login to vote
bulrich's picture

Using version 6.1.4047

+2
Login to vote
Jordan's picture

I can't replicate you issue.  I upgraded from 2.1.6071 to 6.1.4047 and then registered the WMI dll and MOF.

To validate that WMI was working I ran the following code:
strComputer = "."
SET objWMIService = GetObject( _
"winmgmts:{impersonationLevel=impersonate}!\\" & _
strComputer & "\root\default" )
SET colItems = objWMIService.ExecQuery( _
"Select * from VirtualSoftwarePackage Where Active = True" )
FOR EACH objItem IN colItems
WScript.Echo "Id: " & objItem.Id
NEXT

I'm wondering if, for some reason, the DLL or MOF aren't getting registered.  If you run Regsvr32 without the /s switch you'll get an alert window saying what the result are.  Mofcomp will output to the cmd window what's going on, you're going to want to see the following:
MOF file has been successfully parsed
Storing data in the repository...
Done!

If both of these are succeeding I have to wonder if your code is correct, you may be in the wrong namespace so VirtualSoftwarePackage cannot be found.

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

+1
Login to vote
bulrich's picture

I was able to get it working this morning.  Had to uninstall/reinstall, reg and mof 3 times before it was able to recognize the script.  With that said the strange part is the script it working but the "VirtualSoftwarePackage" is not being recognized as a valid class.   (used Paessler WMI Tester 2.0.1 to test WMI as well)

-1
Login to vote
Jordan's picture

What do you mean by "Had to uninstall/reinstall, reg and mof 3 times before it was able to recognize the script"?  Did the scripts error out?  Did they not run the first few times?  I'm curious.

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

+1
Login to vote
bulrich's picture

The scripts kept erroring out when it got to the portion where it called for the Select * from VirtualSoftwarePackage".   Uninstalled 6.1 competely, made sure it's folders and reg keys (the obvious ones) were deleted, restarted.   Rebooted again.  Installed 2.1.3071.  Tried the script, worked fine.   Upgraded to 6.1.4047, registered the dll and as well as the mof.   Tried script, bombed out with the error code of 0x80041013.   Uninstall.   

Repeated that two additional times.  On the third time, for some reason I can't seem to understand, everything came into alignment and everything started working.  Script got past the VirtualSoftwarePackage block, kept going, hit the server for our vsa cache, recognized the system needed layers,   got the packages and started importing and activating.   I can't explain it but it just seems to be working now like nothing ever went wrong.

Very odd.

-1
Login to vote