Video Screencast Help

Getting SWV and NS to Work Together

Created: 22 Nov 2010 | 13 comments
Jordan's picture
+1 1 Vote
Login to vote

The Symantec Software Virtualization Solution is a tool that allows Symantec Workspace Virtualization (SWV) to integrate with Symantec’s Notification Server (NS), however the newest release of SWV does not support the SVS Solution as we have moved over to Symantec’s Software Management Solution (SMS) for use with NS7.  However, this does not mean you cannot continue to use NS6 to properly inventory your virtual applications with newer versions of SWV—this article will cover the steps necessary to get newer versions of SWV and NS6 to work together. 

For NS7 users, be aware that we’re now using SMS and the SVS Solution won’t install at all with NS7.

The last major update of the SVS Solution was SVS 2.1 SP3, build 2.1.3076, and all subsequent releases of the SVS solution have only been updated to include the new build number and the updated SWV agent—the solution itself has not changed in several years.  Because of this you may be familiar with the first part of this article because the solution still thinks we’re on SVS 2.1 for many things.

Getting SWV and NS to work together by changing the Agent Names

The first change that needs to be done is change the name that NS looks for when inventorying software, we’ve changed the name of the agent from “Software Virtualization Agent” to “Symantec Workspace Virtualization Agent”, and this is just a simple registry change to make that can be made by many different methods such as DS.

Under HKEY_LOCAL_MACHINE\Software\Altiris\Altiris Agent\Plugin Objects\Agents\Software Virtualization Agent you need to change the “Agent Name” value from “Symantec Workspace Virtualization Agent” to “Software Virtualization Agent”.

Once the RegKey has been modified, send a basic inventory to the NS and the agent name will update automatically.

A second option for getting NS to modify the SQL reports and change the name from “Software Virtualization Agent” to “Symantec Workspace Virtualization Agent” which needs to be done in the following three places:

  1. "All Windows 2000/XP/2003/Vista Workstations without Software Virtualization Agent installed"
  2. “Computers Requiring Software Virtualization Agent Upgrade”
  3. “Computers With Software Virtualization Agent Installed”

If the SVS report pack was installed then each of the reports must be cloned and then edited to also reflect this name change.

Enabling NS to upgrade SWV to newer versions

Because the solution itself is no longer being updated NS, by default, thinks the last version of SVS\SWV available for upgrading is SVS 2.1 this is because the SolutionCenter.XML file that contains this information is not longer getting properly updated to reflect new updates.  Because of this the upgrade option for SVS\SWV will be grayed out.

If upgrading to SWV version 6.2.1562 

Obtain the solution zip file and run the install on the NS machine to be upgraded.  After the solution install completes follow the instructions in the “Getting SWV and NS to work together” section above.

If upgrading to a SWV version post 6.2.1562

For newer versions of SWV the process is much more involved, the following four steps need to be done and will be covered in detail in this section:

  1. Upgrade the solution to the last shipping solution
  2. Modify the solutioncenter.xml file
  3. Copy the new agent executable to the NSCAP directory
  4. Modify the NS SVS agent upgrade report template

Upgrade the solution to the last shipping solution

Since 6.2.1562 is the latest version of the solution you’ll start off by installing this version regardless of the SWV version you want to use.  This can be an upgrade from a previous version or a clean install but if you’re already on a version from the 6.x line you can skip this step.

Modify the solutioncenter.xml file

Next the product version number needs to be manually updated in the solutioncenter.xml file so that NS will know that a new version is available. For example, if upgrading from build 2.1.2095 to 6.3.2055 do the following:

  1. On the NS console navigate to Configure -> Solution Center. On the Currently Installed tab note the value of the “Update Version” for the currently installed Altiris Software Virtualization Solution. 
  2. On the NS machine navigate to \Program Files\Altiris\Notification Server\Include\xml6\
  3. Edit the SolutionCenter.xml file. Search for productName=“Altiris Software Virtualization Solution” and change the version listed in productVersion=”2.1.2095” to “6.3.2055”
  4. Save the file.  Refresh the console screen and verify that the new “Update Version” shows 6.3.2055.

Copy the new agent executable to the NSCAP directory

  1. Navigate to \Program Files\Altiris\Notification Server\NSCap\Bin\Win32\X86\SVSolnAgent and replace the Software_Virtualization_Agent.msi file with the new agent version you want to distribute.

Note that the new agent installer is named “Symantec_Workspace_Virtualization_Agent.msi” so for NS to recognize it we’ll need to rename the installer to “Software_Virtualization_Agent.msi”.

Modify the NS SVS agent upgrade report template

  1. In the NS console navigate to Configure->Solutions->Software Virtualization
  2. On this page on the left hand navigation pane go to Software Virtualization-> Windows-> Software Virtualization Agent Rollout.
  3. Clone the collection named “Computers Requiring software Virtualization Agent Upgrade”. Right click the collection name and chose “Clone”
  4. Left click the newly created collection name, and then click the edit pencil in the right hand window. In the Query box select “Enter SQL directly”
  5. Scroll down until you find the line that states “AND t1.[Product Version] < ‘2.1.2095’ And change the value to ‘6.3.2055’
  6. Click the “Apply” button
  7. Enable the “Software Virtualization Agent Upgrade” Task.
  8. Change the “Applies to Collections” to include the cloned “Computers Requiring software Virtualization Agent Upgrade” collection
  9. Click the “Apply” button
  10. Follow the instructions in the “Getting SWV and NS to work together” section above.

Comments 13 CommentsJump to latest comment

SK's picture

Hello Jordan,

I wouldn't bother modifying the SolutionCenter.xml file, because the next time the NS goes out to SolutionSam either directly to the web or to a customers local store which has been updated, the xml file will be overwritten.

Simply running either the SP4 solution EXE or MSI manually will install the product.

I have nearly finished creating an add-on pack for the SP4 solution, which will contain all of the required modifications as well as an additional report.

SK

Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.

+1
Login to vote
Jordan's picture

I realize that the changes won't stay but they'll work for sending out an update quickly, though I agree that using the CMD to install is a better idea--but we wanted to give customers the information they needed to get NS to behave in a way they may want and let them decide how to go forward.

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

0
Login to vote
SK's picture

Hello Jordan,

I wouldn't even bother changing the registry, because the next time SWV is upgraded, it will be changed back I believe.

SK.

Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.

0
Login to vote
MrSoapsud's picture

The key HKEY_LOCAL_MACHINE\Software\Altiris\Altiris Agent\Plugin Objects\Agents\Software Virtualization Agent doesn't exist on my XP box which has had 6.3.2059 of SWV installed.

0
Login to vote
Jordan's picture

For that key to exist you need to have the old solution installed, SWV itself does not install this solution.

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

0
Login to vote
SK's picture

If SWV is installed with the NS parameter, that key will be created, however, if it still doesn't (I have seen this myself), then a simple registry merge will add it.

SK.

Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.

0
Login to vote
ManelR's picture

Hello,

Is it possible to integrate SWV with NS7? (i.e. using CMS7 to manage and distribute layers).

I think that CMS7 onlyl knows about SVS and not SWV.

I've found some menus in CMS relating to VSA files but nothing about XPF files (the format that we're now using with SWV 6.1 SP6 MP1).

Any doc about this integration?

Thanks.

PS: The integration of SWV with DS 6.9 SP4 will be of our interest too ;-)

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

NS7 is a different beast all togethor and something that I cannot comment on right now because I don't know the answer as to how to get SWV to work with CMS.  I'll see if I can find that out.

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

0
Login to vote
Jordan's picture

I've been told that this will work with CMS as well, the person I talked to was pretty sure that CMS used the same registry keys but if it doesn't you could do a search in the registry for "Software Virtual Solution" and hope that turns up the correct key.

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

0
Login to vote
Pascal KOTTE's picture

that is :)

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

0
Login to vote
MrSoapsud's picture

Does all this workaround stuff fix the issue that the NS6 server is not seeing virtual application inventory information? All your document talks about is Agent detection/ distribution as far as I can see?

0
Login to vote
Jordan's picture

my understanding is virtual applications only get inventoried when the layers are active.

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

0
Login to vote
MrSoapsud's picture

Sorry - must have been my mistake when installing the agent. Integration with NS6 as far as layers is concerned is working, although the VSPName is appearing in the DB with \Extract_32436712 on the end?

0
Login to vote