Package Servers are not able to download Symantec Deployment Solution 7.1 packages

Issue

Package servers show a number of invalid packages when the packages are valid.

Cause

The manually defined Package Destination Location (\\%COMPUTERNAME%\Deployment\...), does not exist because the Task Server role has not been assigned to the Package Server.

NOTE: The manually defined Package Destination Location was set by Symantec.

Workarounds

• Assign the Task Server role to the Package Server. (Preferred)
• Remove the manually defined Package Destination Location. This may cause issues with Symantec Deployment Solution, but will allow the package to download to the Package Server.
• Create the share on the Package Server using a similar command line:

	:: Get the InstallDir
	FOR /F "tokens=2* delims= " %%A IN ('REG QUERY "HKEY_LOCAL_MACHINE\SOFTWARE\Altiris\Altiris Agent" /v InstallDir ^| findstr /i /c:"InstallDir"') DO SET InstallDir=%%B
	IF NOT EXIST "%InstallDir%\Agents" MD "%InstallDir%\Agents"
	IF NOT EXIST "%InstallDir%\Agents\Deployment" MD "%InstallDir%\Agents\Deployment"
	NET SHARE Deployment="%InstallDir%\Agents\Deployment" /GRANT:[DOMAIN]\[AltirisServiceAccount],FULL /GRANT:SYSTEM,FULL /GRANT:Administrators,FULL
	PAUSE

view raw set_deployment_security.cmd hosted with ❤ by GitHub

More Information

A review of the Symantec Management Platform, Site Servers page shows that one or more Package Servers have invalid packages.

A review of the Symantec Management Agent, Package Server tab shows that the packages are related to Symantec Deployment Solution.

A review of the package on the Symantec Management Platform server shows that the package is set to download to All Package Servers, but to a manually defined Package Destination Location.

The manually defined Package Destination Location is associated with Task Server.