Customer noticed that Package servers are unable to download Deployment Solution package DriversDB. This package is used by DeployAnywhere to store drivers.
In at least one instance of the issue, package servers showed the size of the package as 0.00 KB. In another instance of the issue, codebases for the package were not being published.
If "Update Distribution Points" is selected for the package, an error may be seen: "Unable to update the distribution points for the package. Reason: {0}"
Deployment Solution 8.x
In at least one instance of this issue, it was discovered that the package reference location on the SMP in the following location was missing: \Program Files\Altiris\Notification Server\NSCap\bin\Deployment\DriversDB
DriversDB folder in \Program Files\Altiris\Notification Server\NSCap\bin\Deployment\DriversDB should be a symbolic linked folder over to the actual source location of stored drivers: \Program Files\Altiris\Deployment\DriversDB
In the event that the symbolic link folder is missing but the source location still holds the drivers, the DriversDB symbolic link folder can be recreated by using 'mklink' in an administrator command prompt on the SMP. This may also require logging in to the Notification Server/SMP with the application identity credentials. The following commands below are given as example only and should be verified before running:
REM Change directory to the install directory and location of the required symbolic link folder:
cd \Program Files\Altiris\Notification Server\NSCap\bin\Deployment
REM Make a symbolic link folder called DriversDB that points to \Program Files\Altiris\Deployment\DriversDB
mklink /j /d DriversDB C:\Program Files\Altiris\Deployment\DriversDB
Once the link is created, verify that "Update Distribution Points" for the package works as expected and that the Package Servers download a valid package.
If the source DriversDB package is lost and the above steps are not possible, please contact Broadcom Technical Support for further assistance.