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:
- "All Windows 2000/XP/2003/Vista Workstations without Software Virtualization Agent installed"
- “Computers Requiring Software Virtualization Agent Upgrade”
- “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:
- Upgrade the solution to the last shipping solution
- Modify the solutioncenter.xml file
- Copy the new agent executable to the NSCAP directory
- 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:
- 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.
- On the NS machine navigate to \Program Files\Altiris\Notification Server\Include\xml6\
- 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”
- 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
- 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
- In the NS console navigate to Configure->Solutions->Software Virtualization
- On this page on the left hand navigation pane go to Software Virtualization-> Windows-> Software Virtualization Agent Rollout.
- Clone the collection named “Computers Requiring software Virtualization Agent Upgrade”. Right click the collection name and chose “Clone”
- 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”
- Scroll down until you find the line that states “AND t1.[Product Version] < ‘2.1.2095’ And change the value to ‘6.3.2055’
- Click the “Apply” button
- Enable the “Software Virtualization Agent Upgrade” Task.
- Change the “Applies to Collections” to include the cloned “Computers Requiring software Virtualization Agent Upgrade” collection
- Click the “Apply” button
- Follow the instructions in the “Getting SWV and NS to work together” section above.