Deployment Solution

Hi All,

I'm sure I'm doing something wrong but I just can't figure it out.

We have Deployment Console deploying SVS apps sucessfully on Server 1. We also have a 2nd server (server 2) at another site that I'd like our support staff there to deploy apps from. Unfortuantly, it's not working

1) When I configure a new job in Deployment Console to use the SVS apps from Server 2, it complains that it doesn't recognise a valid VSA file. But choose server 1 and it works all ok.
2) I've tried using the %SITE% variable and this shows the SVS app being copied across ok. But it still moans about it not being a valid VSA file. It just looks like it's transfering the .VSA file and doesn't know it's to be imported.
3) I'm sure I could get it working with the command line use of the SVSCMD.exe file. But it sort of defeats the object of having the deployment console to make setting up apps, easy.
4) Everytime I create a new deployment job, do I need to create it twice, once for each site or can I just create it once and the PC can decide where to pull it from.

I'm sure it's something that I have not configured correctly. Any help greatly appreicated.

Many thanks

Leonard

What exactly is the error that you are seeing. I've seen where the DS console doesn't think that SVS is installed, and that has to do with the AClient/DAgent not being the same version as the DS Server.

WHen I'm in deployment console, I go to do the following:-

1) Create new task - Manage SVS Layer
2) go to browse the SVS file from Server 2 (other site)
3) get error message saying "Warning: One of more files selected are not valid VSA files, please select valid VSA files."

Now if I browse server 1 where the original Deployment console is installed, it works ok.

If I map a drive letter to server 2 and then browse for the VSA file, it picks it up all ok. But it wont deploy as it's trying to get it from the drive letter rather then the UNC

I should point out that I have not install any Altiris software on Server 2. So do I need to install another deployment console onto this server but point it back to Server 1 database?

Thanks

No, you should not need to do this. When you use the %SITE% variable, are you doing a script to copy the VSA to the local computer? If that is the case, what happens if you manually try to import and activate the VSA file on the client?

To manually do this you would use the following commands:
"c:\program files\altiris\Software Virtualization Agent\svscmd" I -P "c:\your-vsa-file.vsa" -F
"c:\program files\altiris\Software Virtualization Agent\svscmd" "YOUR VIRTUAL LAYER NAME" A

The first command imports the VSA file.
The second command activates the file. If these are successful, the VSA file is fine, if they are not successful, the file is bad.

Just tried what you said and that works all. So I guess that tells us that the VSA file is ok. I even subsituted the server name for the %SITE% enviroment variable and this worked ok.

So have I been deploying SVS apps incorrectly (or incorrectly if you want to make use of more then 1 deployment location). Should I be using the command line option for deploying apps? If so, the downside is that you don't get a percentage showing in deployment console to see how it's going.

It's a solution but surely I should just be able to pick from the drop down list?

The way I handle SVS layers and DS. I have one DS at our HQ facility. I have 9 remote sites with just file servers. I have a deployment share on each of the file servers at those locations. I run a script that based on IP copies the VSA to the local machine from the local server and imports the VSA. The next part of the job activates the imported VSA and set it to be automatically active on startup. I'm not sure if it's the best way to handle it, but it works well in my environment.

Your idea sounds like it might work for me. I have just the 2 sites to look after. I'm also considering using DFS Namespaces to get around the problem. I used DFS roots before in Windows 2003 but haven't had a chance to see what it's like in 2003r2. From previous experience, it was slowed the network down as the client had to keep asking where to go to get it's data.

When you deploy apps you mention that you use a script. Is that script and the app deployed via deployment console? If so, any chance I could see the script to get some idea?

Many thanks

Leonard

Attached is a sample.

It's not pretty, but it works for me.