I wanted to share with you what Microsoft told me. With SP1 they have changed a view due to performance reasons. That view is vLocalResourceIDXRef. I am guessing this is the view where the pxe machines look for advertisements.
they changed it to
SELECT MachineID, GUID, ArchitectureKey FROM MachineIdGroupXRef
WHERE (ArchitectureKey = 5 AND MachineID BETWEEN 16777216 AND 33554431) OR (ArchitectureKey != 5)
UNION ALL
SELECT MachineID, GUID, ArchitectureKey FROM vCASSystemIDXRef
I don't know what the second number used to be, but certainly higher. So .....
An imported machine has an ID 16'777'XXX. -> pxe boots just fine
An AD Group Discovered machine has the ID 2'097'15X'XXX
If you import a machine that has been discovered with the ad system group discovery (same name) it will merge into the ad group discovered object and therefore has a 2 Billion ID. Which will be filtered out by the vLocalResourceIDXRef view. -> does not pxe boot
In other words, you cannot dynamically add software via AD Group while staging a machine. :angry:
Unless you guys have hint.
The goal is to provision a machine with additional individual sw via AD Groups, and let it install during the TS.