AD Comp Objects dont get "moved" to the correct OU (and more)
Here's a noodle twist for you.
Our setup is a SCCM 2007 R2 SP2 setup [an elaborate multi server setup too ;)] and everything seems to work a treat.
For those that dont realise, MDT is such a welcome addition to SCCM. Makes alot of stuff so much the sweeter, but I digress slightly.
With our MDT infused SCCM TS, everything works a treat except for two niggles I have.
1: When deploying [from PXE] a captured SCCM Win7 OS build on a machine, everything works great - however, it doesnt place the computer object into the target OU that it has been told to in the Task Sequence.
This also seems to apply in other uses of the TS i.e. running a Refresh using it etc, however, everything else seems to work fine i.e. Driver Injection, Software Update installs, Additional Software installs, Model Specific checks, etc.
Seems to just be the comp obj that wont get moved to where I tell it.
EDIT: Just tried it from fresh using PXE, with no computer object in AD, and SCCM with MDT put the computer object in to the correct OU I'm happy to say.
However, I wager that if i move the AD object somewhere and then try again [leaving the computer object in AD] but just advertising it again, it wont move anywhere.
The latter two posts in the following thread seem to ring two to what I have:
however, I've tried the following script previously and I didnt get any joy with it:
Could be I'm just missing something....
2: The other niggle is that when rebuilding a machine in any sense, it creates a new SCCM computer object rather than reuse the existing one, causing there to be two objects.
The one used at the time of (re)deployment is set to Obsolete and the AD computer ojbect association is set to the new one, tho the new one of course then isnt linked to Collections where it is needed, which isnt a problem at the moment, but will mess things up later on down the line.
Just wondering if there is some option / command i can use to stop that happening, and additionally a command i can use (if it can continue to use the existing SCCM obj, rather than create a new one) that will allow me to remove / add the object to a collection as part of the deployment TS?
Hope that makes sense,
These two things are a bit annoying and i'm running out of time to get them working so any thoughts / ideas / help would be really appreciated here with this.
[have given up with posting on the MS forums as u either get a poster reword your question and posing that as the answer etc hehe ;)]