Time Delay for ClientPolicy.xml after installing the Altiris Agent
Last Updated October 24, 2009
Is there a way to force the Altiris Agent to get a client policy.xml file? There currently seems to be a delay before the default Altiris Agent Settings are passed to the newly installed agent.
The initial install time frame is hard coded for 15 minutes.
Normally, the client connects faster than 15 minutes, but the initial "policy" is set for 15 minutes. The Agent has to do the following before getting the first ClientPolicy.xml file:
-Sends a request via CreateResource.asp for a GUID -Supplies Name and Domain information to the NS -Gets a GUID from the NS -Places the GUID in the client Registry -Generates and sends a basic inventory to the NS -NS has to run the NS.Collection Delta Update Scheduled Task to place the client in it's collection(s). (Default is 5 minutes, but can be changed by the customer in larger environments) -The Client then requests a GetClientPolicies.asp every 5 minutes until it gets the Client Policies.xml. This usually doesn't take longer than 15 minutes to get the default ClientPolicy.xml file as defined in Altiris Agent Configuration for All Desktop computers...
So depending on when the NS.Collection Delta Update Scheduled Task runs and when the Altiris Agent can run the GetClientPolicies.asp that's what determines how fast the ClientPolicy.xml is generated.
Imported Document ID: HOWTO8844
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe