The Symantec Management Platform (SMP) can be used to deploy the Symantec Workspace Virtualization (SWV) agent using a Managed Software Delivery policy.
For reference and best practices related to Software Management, see HOWTO59040. Note that this document also applies to SMP version 7.5. See page 13, Manual Creation, as a guide for adding the SWV agent package as outlined below.
1. Store the installation files either on the Notification Server (NS) or any place accessible by the console. Note that there are two for the SWV agent – one for 32 bit machines, and one for 64 bit machines. Current naming has the 32 version called Symantec_Workspace_Virtualization.exe, and the 64 bit version called Symantec_Workspace_Virtualization_x64.exe, but this is subject to change.
2. Go to page 13 of HOWTO59040 and follow the steps to add a package (pages 13-18)
3. Edit the command line (page 18) as needed to meet your situation. Commonly, we will use the silent switch, force a reboot, and install the Virtual Admin Tool. This would be the command line for those options:
4. Enter the Success Codes as 3010,1641 and click OK.
5. Under the rules tab (page 20), creation of a detection rule can be helpful for ongoing manageability. One way to do this is to use a file version rule. To use this, click the New link followed by the Plus sign (Add) link and select Standard Rule > File Version. Enter the full path to the Virtualization executable (by default this is located at C:\Program Files\Symantec\Workspace Virtualization\SVSCmd.exe).
6. For Version type, you can use either File Version or Product Version. Navigate to the above folder (or your installation folder) on a machine that has the agent installed, right click SVSCmd.exe, and in the details tab note the Product (or File) version number.
7. Then in the new detection rule, select the equals sign (=) in the Version must be and then enter the version number (such as 7.5.770).
8. Put a descriptive name in the Name field, such as SWV x64 version 7.5.770 detection rule.and click OK.
9. Also recommended is an applicability rule. Click the drop down and select 64 bit platform for instance when building a package for the x64 installer.
10. Verify that you have a descriptive name for the SW resource and click OK.
11. NOTE: The SWV agent requires a reboot after installation. Normally we would include a forced reboot in the command line, but Managed Software Deliveries will show the installation as failed even though it installed successfully because the success codes are not returned before the reboot. You can include a reboot task to a Managed Software Delivery to complete the installation and show the installation as successful. See page 47 in HOWTO59040 for instructions. The task to add is of type Power Control and is named Restart Computer
You can now use a Managed Software Delivery policy to deliver the SWV agent to the desired set of machines as discussed in HOWTO59040. We recommend testing against a test machine to ensure the configuration is correct and will work before deploying to your production environment. Commonly encountered issues include using curly quotes instead of straight quotes in your commend lines (often found during cut and pasting), and detection rule logic errors.
Imported Document ID: HOWTO107267
Subscribing will provide email updates when this Article is updated. Login is required.