Home » Forums » Symantec Products and Technologies » Application Virtualization & Streaming

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

SVS Agent not installed error on machines upgraded to SVS 2.1 SP2
Submitted by LShackleton on 20 August, 2008 - 05:36.

Since I've manually sent upgraded agents out to several machines now using a DS deployment job with the switches: REINSTALL=ALL REINSTALLMODE=vomus PRODUCT_KEY=xxxxx-xxxxx-xxxxx-xxxxx, I can no longer deploy my SVS layers to them through DS - the error being that the SVS agent is not installed - status code 999.

We have the same problem

Submitted by Lund on 4 September, 2008 - 02:35.

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 ?

Symantec is aware of the problem and a fix is being worked on

Submitted by Lund on 4 September, 2008 - 05:53.

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.

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

Work Around?

Submitted by bhawver on 7 November, 2008 - 10:45.

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

Jordan's picture
Submitted by Jordan on 7 November, 2008 - 15:45.

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.

Re: GOTO

Submitted by bhawver on 7 November, 2008 - 15:59.

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.