Deployment Solution

Hello!

We're in the process of migrating from Deployment Server 6.9 to Deployment Server 7.1. So far, I have site servers setup at four of our locations, but I noticed that for one of our site servers, the package service is showing 8 invalid packages, including:

- Audacity (which is what I'm using to test software deployment)
- BDC Linux Drivers (x64 and x86)
- BDC WinPE Drivers (x64 and x86)
- Drivers
- Sysprep Deploy.cab x86

I tried uninstalling and reinstalling the package service on this server, yet that did not solve the issue. What can I do to get these packages to download on this server?

Joey

Install the diagnosatics package or use the Remote Altiris Agent Diagnostics (RAAD) tool.

Hi Joey Hogan,

Maybe this KB http://www.symantec.com/docs/TECH122379 solves the problem with Drivers and BDC, but does not explain why the Audacity Package is invalid...

Network23

I ran the RAAD tool on both a good server and the one with the invalid packages, and found a few inconsistancies:

• Policies: the good server server has policies named "PXE Server Configuration" and "Preboot Configurations" while the invalid one does not. Additionally, the invalid server has "Deployment Site Server Components (x86) - Install", while the good one does not.
• SWD: The good server has nothing listed under SWD. The invalid server has "Deployment Site Server Components (x86)" enabled, and "Package Server Agent Package" disabled
• For some reason, the invalid server is missing the "Deployment" share.

The reason you are getting the invalid packages is because those packages reside in the deployment folder and because DS might not be installed at the site server then the issues happens. you could ignore the error message unless you have Deployment Components for site servers installed.

We are planning on using this server for software and image deployment. If the deployment site services/task handlers are not installing automatically, is there a way I can force them to install manually?

once the policy is enabled it should install DS components next update configuration. Deployment Site Server Components (x86 or x64) is the policy that needs to be enabled.

Nelo

Joey, Although I am not sure but see if following could be of some help:

https://www-secure.symantec.com/connect/forums/how-deployment-site-server

Thanks

That policy is enabled for both x86 and x64. I'm not sure if the server in question is not receiving the policy, or if it's just not applying it.

tool to see what's going on on the Package Server.

- BDC Linux Drivers (x64 and x86)
- BDC WinPE Drivers (x64 and x86)
- Drivers
- Sysprep Deploy.cab x86

All above packages are related to Deployment Solution and will be invalid till the time "DS Site Server Component" for the specific Site Server is not installed and configured properly. And after DS SS component is installed “refresh package” should change its status.

If above condition is satisfied and still packages are in invalid state than click on any such package and check the “package server” location accessibility for download location tab.

Thanks.

I did do that already, the results are posted above. I'm not 100% sure what they mean though, or what's causing it.

It looks like the site server/task handler component is not installing. Is there a way to either force or manually install those components?

and run the job.

Annoyingly they run with no error but don't do anything if you haven't got the correct .NET Framework version installed, 2.0 on Windows Server 2003 and 3.5 SP1 on Windows Server 2008 R2.

So you pegged the issue that the DS packages will not work without a Deployment share.  It's actually quite simple - the packages are pointing to a Deployment share that doesn't exist.

There are two things that will prevent the DS site services from installing.  1) a defect (later) 2) not having Task AND Package already installed.  The filter for the policy looks for Task and Package, and if not present, then it doesn't deploy the DS Site components.  Package isn't enough.  DS requires both or it wont work.

Until 7.2 and then that's fixed, but that's also not out yet for a couple of months.

Anyway, once you ensure you have task and package, if they still don't install, find the package and run the bat file manually.  If THAT fails, run the MSI's manually.  We have a KB on this somewhere, but I've no time to find it right now.  Anyway, the point is that we know that, at times, we've had issues with the installer not running to completion.  If you can't get it to run manually, call support.