OSD PXE boot: no policy available

Question

Hi,
We have some issues with certain machines, PXE boots says "no policy available" whereas they are in the correct collection.
We found out that the object seems to be corrupt due to the fact we import it manually (via MAC-address) and autodiscovery of groups in which computer objects reside. The latter is needed to populate collections, f.e. we deploy Office 2013 to the a collection
"Office 2013" which queries the AD-group Office 2013.
If we disable the AD Directory Groups Discovery and delete, recreate the object, PXE boot works fine again. However, we 'd need to find out the root cause since we cannot to this every time this issue occurs (and it happens more often lately).
Please advise.
J
Jan Hoedt

Answer 1

Thanks, I know about the PXE-log but that doesn't give us extra info. We 'd need to know how to avoid corruption of the computer object. Leaving as is doesn't solve the problem, pc just won't boot, disabling ad group discovery recreating the object is only
a workaround for now but not acceptable as solution.
Probably the corruption occurs because at the time of creating the object, the ad discovery is done. AD discovery runs every 5 minutes. We need this discovery interval at 5 mintues because after OS deploy immediately applications/packages are deployed based
upon collections (which query AD group memberships).
Jan Hoedt