OK, We have Regional Support Staff at each of our divisions / Sites. We have security roles, which scope these regionals to their Sites. Each site is also an OU in AD, so we have scoped each regional to only be able to see / image/ push software etc to PCs in their OUs / Sites. Makes sense.
When our regionals receive new PCs, they get imaged and added to AD via a script that runs while in WinPE, after the image has been dropped. Once a day the AD import runs and the PC is then known to Altiris as being in the correct OU (in Altiris) and thus within the scoping of each regional that has access to that OU.
The problem lies between the time the agent checks in and becomes a known PC to altiris and the AD import. Scoping says they can only send jobs to PCs in their OUs, but that PC doesn't reside in their OU until the AD import into Altiris. So, the Regional can't do anything to that PC until the next day, once it is imaged.
So, where do new PCs exist in Altiris, so that I can assign our Regional Security Roles rights to that place? Or how do I tell Altiris to put new machines in a certain OU until the AD import tells Altiris where the PC actually resides?
If you need more info, just let me know.