How does the DS Library package get assigned to Package Servers for replication?


Article ID: 179683


Updated On:


Deployment Solution





How does the DS Libary Package get assigned to Package Servers for replication? How can this be initiated on demand, rather than waiting up to two days for this to occur?


The DS Libary Package is assigned to Package Servers that also have DS installed. This is determined by using information from Basic Inventory. It looks for the Altiris eXpress Server in NT services. This is stored in AeX AC NT Services. There are two scheduled tasks that must execute as well. The first is DS Library Collection Update —it executes daily at 2:00 default. The second is Update DS Package Servers for DS Library—this item is part of the NS.Daily shared scheduled, which also executes at 2:00 a.m.

The following steps can be used to trigger replication of this package on demand:

The following command line will kick off the Update DS Package Servers for DS Library task.

“%ProgramFiles%\Altiris\Notification Server\bin\ScheduleProcessor.exe” {DFD99441-EF14-4739-812C-0E29E88614BD}

Adjust %ProgramFiles% to reflect the path for your Altiris Install

The linked task that needs to occur prior to this one is DS Library Collection Update—it executes on its own schedule every day at 2:00 default. You can launch it by either running it from Scheduled Tasks function in Windows (NS.DS Library Collection Update.{…} or using the following command line:

“%ProgramFiles%\Altiris\Notification Server\bin\ScheduleProcessor.exe” {5141f21b-56a4-4531-817d-692331fe95f3

Both this task and NS.Daily occur at 2:00 a.m. by defaul. It’s entirely possible that Daily occurs before this, which would cause the two day turnaround time for the DS library to filter down.

Additionally, the DS Package Servers collection is dependent on basic inventory occurring. It checks AeXInv_AeX_AC_NT_Services for the Altiris eXpress Server.

The proper flow for replication of this package on demand would be to add the computer to the NS, send basic inventory, verify in the Resource Manager that data from Basic Inventory has been populated, and specifically check the AeX AC NT Services class. Execute the DS Library Collection Update task (or use the above command line) and then execute Update DS Package Services for DS Library task using the above listed command line.

For diagnostic purposes, run the following query:

SELECT [SWDPackage].[Name], [Inv_AeX_AC_Identification].[Name], [SWDPackageServer].[Status]
FROM SWDPackageServer, SWDPackage, Inv_AeX_AC_Identification
WHERE [Inv_AeX_AC_Identification].[_ResourceGuid] = [SWDPackageServer].[PkgSvrId]
AND [SWDPackage].[PackageId] = [SWDPackageServer].[PackageId]
AND [SWDPackage].[_Latest] = '1'
AND [SWDPackage].[PackageId]='{444140ab-d897-4434-98bf-fa85b6b51dfe}' /* DS Library Package */
ORDER BY [Inv_AeX_AC_Identification].[Name], [SWDPackage].[Name

Make sure your new DS package server shows up in the list; just to speed things along, it might not be a bad idea to purge your client policy cache with the following SQL command


Then have your DS do an update config (or let it occur naturally)—it should start pulling the DS Library package.