Are Approved Pending Clients cached on WDS?

my wds pxe response settings set respond known , unknown clients and i've checked box: for unknown clients, notify administrator , respond after approval. this works first time every new unknown client , after approve it, creates computer object in active directory if delete computer object in ad (wait fifteen minutes replication) , try pxe boot same client again, gets right through to wds without having approve again. there must local cache, database or registry key that holds approved client information and doesn't go out , check active directory make sure object still exist. not good!!! ideas?

you correct in if perform operations listed above, subsequent boot attempts of client post-delete not work. because windows deployment services can't differentiate between between "normal" active directory replication  delay , instance account did exist in ad, deleted.

your scenario follows:

1. boot machine first time. entry gets added database on \mgmt share. reason database entry made can list of devices in pending state. database temporary store aids in management scenario.
2. approve device. entry marked in database having been approved. @ same time machine account in ad created represent physical device. note ad true data store server. computer not allowed boot until computer object created above appears on dc/gc being used wds pxe provider (binl). ensures ad replication has occurred.
3. after computer object found have replicated in ad, device allowed boot. installation continues.
4. later, use adu&c delete computer account (question – why need operation outside of beta testing?).
5. immediately try boot device again before background process has run clean-up accounts temporary database in \mgmt. such, wds server won’t let device boot because thinks there replication latency problem in ad – e.g. device shows having been approved in database device doesn’t yet appear on dc/gc used binl. unbeknownst wds, however, fact device *never* appear in ad again – because delteted.
   • solution: must two-step process: delete account ad *and* delete temporary database. latter, either wait normal clean-up of temporary database occur before trying boot device again (happens every 24hrs – should working correctly in rc1+) or use wdsutil /delete-autoadddevices manually purge record.

thanks -

--scott

Windows Server  >  Setup Deployment