SVS Agent not installed error on machines upgraded to SVS 2.1 SP2

We upgraded our clients through the Notification Server.
Now we have the same problem when deploying SVS applications through DS.

Did you find a solution ?

kb.altiris.com
Article ID: 41927

The error "SVS Agent is not installed" is received when trying to run SVS layer management through the Deployment Solution console

--------------------------------------------------------------------------------
Applies To

• Deployment Solution 6.9

--------------------------------------------------------------------------------
Problem/Symptoms

When trying to run SVS layer management through the Deployment Solution console, the error "SVS Agent is not installed" is received, even though the agent is installed.

--------------------------------------------------------------------------------
Environment

Deployment Solution, all versions
Software Virtualization Solution 2.1 SP2

--------------------------------------------------------------------------------
Cause

This version and future versions of SVS have changed the name of the installed product from "Altiris Software Virtualization" to "Symantec Software Virtualization". Because the AClient and DAgent are looking for a specific string to determine if the product is installed, it does not detect that the SVS agent is present.

--------------------------------------------------------------------------------
Resolution

Symantec is aware of this situation and a fix is being worked on for future release.

--------------------------------------------------------------------------------

Is there a work around? It's great that Altiris confirmed the problem, however, they didn't give any sort of resolution or work around. I cannot be waiting around for them to release the next service pack (as the previous one was just released!) and this is causing me some serious heart burn!

Goto HKLM->Software->Microsoft->Windows->Current Config->Uninstall and find the key for SVS.

One of the values is called "Display Name", change that from "Symantec Virtualization Agent" to "Altiris Vitualization Agent".

now DS will find SVS on that machine.

Word of Warning, all we've done is check to see that DS can find SVS but we haven't tried anything outside of import and activate. We don't know if you'll be able to uninstall or apply patches, but changing Display Name back to Symantec should resolve any issues if they do exist.

I'd try this out on a VM or a machine you don't mind reimagning before making the change network wide.

Thanks so much for the work around. I certainly hope they will have a real fix soon, as it's going to be a bear trying to keep track of all of the clients that have this work around.

We are currently using scripts to manage our layers. By using svscmd.exe with the appropriate switches we are able to deploy, manage, and delete layers as needed. It is not pretty, but it does work. Just as an FYI for those who may not know, a list of switches for svscmd can be found by entering svscmd in a command window.

I am having same problem with sva error. I am new to DS and I wondering "jhedges" if I can see a sample of the script you use in your environmet if it possible...thanks in advance

This reg hack doesn't seem to work for Symantec Workspace Virtualization Agent 6.1.4063 with Altiris Deployment Console 6.9 (build 365) SP1.

Also the reg hack in this thread has a typo: "Altiris Vitualization Agent" should be "Altiris Virtualization Agent". (Missing 'r')

I've looked high and low for a KB article but nothing.

Thus I've opened a support case: 281699548

Here's a later update...

In SWV 6.1 (Build 4063) with Deploy Solution 6.9 (build 375) SP2 you will need to rename the "Display Name" value for the SWV client in the registry

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{2984AD92-9972-4C05-A332-25E09DB93D78}]

FROM: "DisplayName"="Symantec Workspace Virtualization Agent" 
TO: "DisplayName"="Software Virtualization Agent"

Then restart the AClient service.

Were your layers created with the same version that is present on the workstations?
Does a manual install of a layer work?