managing multiple "old" AD computer objects


so have implemented naming convention techs select location , department during imaging process  machine deployed; during process , computers automagically named "nyc-fin-1234567"... 1234567 being dell asset tag.... pretty nifty johan(!)

however... problem once machine gets re-imaged @ same location , deployed team marketing folks  (ie."mkt")... gets name nyc-mkt-1234567...

the problem seeing have multiple objects in ad same asset tag causing nightmares licensing management... nyc-fin-1234567 & nyc-mkt-1234567 respectively.

i working on powershell script trim names down respective tags , compare list duplicates - check  and compare duplicates properties "created date" , make determination , delete older object...

this checking duplicates proving little more difficult , haven't gotten evaluate section yet...  i still working on proficiency when comes more complex arrays.

am going right way or else have approach conundrum?

scripting games '14 :p



possibly change in procedure needs implemented. before re-imaging machine, should take machine off domain first, result in disabling computer object, re-image machine, , gets new name, , once added domain new computer object created new name.

now when retrieve objects based on asset tag, filter on objects enabled, , should have proper count.


if find post has answered question, please mark answer. if find post helpful in anyway, please click vote helpful.

don't retire technet



Windows Server  >  Windows PowerShell



Comments

Popular posts from this blog

some help on Event 540

WMI Repository 4GB limit - Win 2003 Ent Question

Event ID 1302 (error 1307) DFS replication service encountered an error while writing to the debug log file