Back to Basic – DomainOUlist.xml or not…
Posted by Mikael Nystrom on April 21, 2012
So, from time to time people ask me how to use the domainOUlist.xml file and to be honest I’m not sure you should. It is documented in the help file for MDT that you can either use the file or put the same information in customsettings.ini. So, you need to pick and choose here?
If you like the idea of putting this in customsettings.ini, this is how it should look like
In customsettings.ini add the following:
[Settings]
Priority=Default
[Default]
OSInstall=Y
DomainOUs1=OU=Computers, OU=Tellers, OU=NYC, DC=WOODGROVEBANK, DC=Com
DomainOUs2=OU=Computers, OU=Managers, OU=NYC, DC=WOODGROVEBANK, DC=Com
Or if you prefer files, create a file called DomainOUList.xml and store that in the scripts folder that looks like this:
<?xml version=”1.0″ encoding=”utf-8″?>
<DomainOUs>
<DomainOU>
OU=Computers,OU=Tellers,OU=NYC,DC=WOODGROVEBANK,DC=Com
</DomainOU>
<DomainOU>
OU=Computers,OU=Managers,OU=NYC,DC=WOODGROVEBANK,DC=Com
</DomainOU>
</DomainOUs>
Now, if you run the LiteTouch wizard, you will be presented with these two options to place the new machine. As long as you have set SkipDomainMembership=NO, otherwise you will not get prompted in the Wizard.
/mike
GPO Deployment - how do you do things? said
[...] like this if you could point me in the right direction. There are a couple of ways to do it: Back to Basic Works really well as you don't have to mess about remembering OUs. Reply With [...]
Back to Basics – DomainOUlist.xml or not… « Chris Nackers Blog said
[...] Read his post here. Today, 8:42 am MDT 2008, MDT 2010, MDT 2012, Microsoft Deployment Toolkit No Comments Short URL [...]
Back to Basics – DomainOUlist.xml or not… said
[...] Read his post here. [...]