Quote:
Once we install the Agent, it needs to grab a guid from the server and send a basic inventory.
We then force a policy update which grabs the policies (software) assigned to the machine. We can then force the software to install via the runadvertisment method by passing it the policy guid
|
Right - this is a timing and not just purely automatic. Even if you prestage all agent installations, the NEW NS agent needs to request a GUID from the NS, the NS has to wait for Automatic Collection Updating, and then that NS agent needs to chime in again to get its configuration policy.
https://kb.altiris.com/article.asp?article=20132&p=1
This is the basic script you need to establish a "hey do you have any policies to apply?"
You could create a collection of managed computers who are new to the NS and then have an alternate Altiris Agent policy with a more aggressive polling interval attached to the policy.
We can take it a step back and say, "Lets use tasks to delivery software installs instead of policies" Even though that may function faster, you would still have to wait for the above GUID generation and then having the agent assigned to a task server. Granted you could queue the task but the agent would need to still be registered with the NS.
In the end, it is difficult for anyone to use the NS has a staging solution as it is a "PULL" technology used to maintain objects in the environment. You need the "PUSH" technology within DS to not only provide the instant gratification of end results but a way to increase the staging speed.
You should be licenses for DS as it comes as a part of Client Management.