Alternative method for Importing/Activating SWV layers through Software Management


Article ID: 178640


Updated On:


Workspace Virtualization (formerly SVS) Software Management Solution




As an alternative to delivering XPF files throughout the environment to be imported/activated on all client machines, it is possible to allow the SWV Agent to import the layer directly from the Software Library or other network share without the need to download the file. 

To configure a software delivery policy in this manner, create a software release for the layer as normal in the Symantec Management Console, skipping the steps for creating a package and command line. For more information on creating software releases, refer to page 44 of the Software Management Best Practices guide at

Next, create a new command line for the software resource.  Name the command line as desired and deselect the “Command line requires a package” option; this will allow us to run the delivery without needing to download a file.  Set the Installation type to <other> and Command type to Custom.
The command line syntax should look like the following:

SVSCMD.exe *Layer GUID* IMPORT –PATH “\\network path\Layer.xpf” “Layer Name” A

For example:
SVSCMD.exe 5aaab89a-0fdb-4887-9799-067fdea890f6 IMPORT –PATH “\\server1\software library\ Virtualized Apps\Firefox.xpf” “Firefox” A

- Layer GUID is obtained via the SWV Admin and typically differs from the GUID assigned by Software Management.  To view the layer guid, open the SWV Admin, right click the layer, and select Info
-Layer Name indicates the layer as displayed in the SWV Admin.  The .xpf extension must be left off for the command line to function properly.

Next, create the software delivery task or policy, Select the newly created command line in the Command line drop down menu and select <none> for the Package drop down menu.  Depending on the share settings for the XPF location, it may be necessary to open the Advanced Options and adjusting the Run tab > Run as > Specific user with credentials that will have rights to the share. 

If the command line fails, verify it works locally using the credentials set in the policy/task to ensure that the share is accessible.  If the layer fails to import or activate for reasons other than permissions, refer to for further command line troubleshooting steps.

If the command line is configured properly, the SWV Agent will import and activate the layer from the network share.  Once the layer is imported, it will remain so unless it is removed from the SWV Agent.