We use WDS images combined with GPOs to automate the installation of our desktops.
This all works great, except that when a WDS deployment to a new/existing PC is completed, there's a fifty/fifty chance of the GPOs applying on first boot.
That unfortunately means that following a refresh of our development environment, someone has to check the machines and initiate a reboot / GPUpdate for around 15-20 PCs.
Machines are either pre-staged or have existing computer accounts in AD because they are re-imaged rather than new.
Just wondering if anyone has experienced similar problems with GPOs not applying following a WDS installation? At the moment we're considering hacking a script into the image so that workstations are automatically rebooted following a WDS installation, but that feels more like a work around rather than dealing with the problem's root cause.