Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
Problem with setting MachineObjectOU to value which contains spaces

Unanswered Problem with setting MachineObjectOU to value which contains spaces

  • Monday, April 12, 2010 8:02 PM
     
     
    Sign In to Vote
    0

    I'm using MDT 2010.  When trying to specify an OU via the MachineObjectOU variable either from a Set Task Sequence Variable step or from the Rules/customsettings.ini, I am having trouble with it working if the path includes an OU which contains a space in the name.

    For example:

    OU=Workstations,OU=Computer Accounts,DC=domain,DC=net

    OU=Try This,DC=domain,DC=net

     

    I can specify the same exact string from the GUI of the Deployment Wizard and it will work as expected and place the new computer account in the correct OU.

    I have tried quoting it in these two ways:

    MachineObjectOU="OU=Workstations,OU=Computer Accounts,DC=domain,DC=net"

    MachineObjectOU=OU=Workstations,OU="Computer Accounts",DC=domain,DC=net

     

    I've searched all over and have found some similar mentions of problems, but those ended up being solved by permissions to the OUs.  In my case, I've tested with a Domain Admin account which most certainly has permissions.  I can specify other OUs that do not contain spaces through the same exact methods and they work without a problem.

     

    Has anyone else run into this, or does anyone know of a workaround other than renaming the OUs?

     

All Replies

  • Monday, April 12, 2010 8:19 PM
     
     
    Sign In to Vote
    0

    Are you deploying Windows XP/2003 or something later?  The following should work:

    MachineObjectOU=OU=Workstations,OU=Computer Accounts,DC=domain,DC=net

    -Michael Niehaus
     Senior Software Development Engineer
     mniehaus@microsoft.com

     

     
  • Tuesday, April 13, 2010 3:04 PM
     
     
    Sign In to Vote
    0
    We are using MDT for XP and 7 deployments.  It behaves the same with either.
     
  • Friday, February 10, 2012 3:35 PM
     
     
    Sign In to Vote
    0

    *big bump*

    i am also encountering this issue...

     
  • Friday, February 10, 2012 4:07 PM
     
     
    Sign In to Vote
    0

    If using Windows 7, do you have a copy of the unattend.xml from c:\windows\panther that shows what was inserted by MDT into the OU field?  (It's a little harder to get that with XP unless you specified /debug:true, in which case the sysprep_after.inf file would have it.)

    Do you have a copy of the netsetup.log file from c:\windows\debug that shows the attempt to join the machine to the specified OU?

    Thanks, -Michael Niehaus Senior Program Manager, Microsoft Deployment Toolkit mniehaus@microsoft.com http://blogs.technet.com/mniehaus

     
  • Wednesday, November 21, 2012 11:51 PM
     
     
    Sign In to Vote
    0

    I had the same problem as Braden mentioned. I used ADSIEdit tool, browsed all the way up to the OU where I want to place the machine, then open the properties of OU, copy the DN path and pasted in the custom.ini file. Boom! it worked fine..

    You shouldn't use quote when you give DN path for the ou in MDT.

    • Edited by alampcs Wednesday, November 21, 2012 11:53 PM
    •