AD container errors as invalid and will not pull objects into ConfigMgr

All replies

• 

  

  1

  Sign in to vote

  True:

  [..]
  This problem occurs when your user domain name contains a forward slash (/) character. This can occur, for example, if you are a member of an organizational unit (OU) whose name contains a forward slash character.
  [..]

  Source: http://support.microsoft.com/kb/2704983

  and

  [..]
  If the name of an organizational unit contains a forward slash character (/), the system requires an escape character in the form of a backslash (\) to distinguish between forward slashes that separate elements of the canonical name and the forward slash that is part of the organizational unit name.
  [..]
  Source: http://technet.microsoft.com/en-us/library/cc977992.aspx

  --

  Tobias Redelberger
  StarNET Services (HomeOffice)
  Frankfurter Allee 193
  D-10365 Berlin
  Tel: +49 (30) 86 87 02 678
  Mobil: +49 (163) 84 74 421
  Email: T.Redelberger@starnet-services.net
  Web: http://www.starnet-services.net

  
  

  • Proposed as answer by Tobias Redelberger Tuesday, May 28, 2013 10:59 AM
  • Edited by Tobias Redelberger Tuesday, May 28, 2013 11:14 AM
  • Marked as answer by Robert Marshall - MVPMVP Saturday, June 1, 2013 6:11 PM

  Tuesday, May 28, 2013 10:58 AM
• 

  

  0

  Sign in to vote

  I've opened up some Connect feedback on this.  Feel free to vote it up and hit the "I can too" button:

  https://connect.microsoft.com/ConfigurationManagervnext/feedback/details/814686/ad-discovery-fails-to-discover-from-ous-with-a-forward-slash-in-the-name

  If you haven't given feedback to the ConfigMgr product team before, see this like about registering for Microsoft Connect:

  http://myitforum.com/myitforumwp/2013/12/02/giving-feedback-on-microsoft-connect-for-configmgr-2012-help-yourself-help-the-community/

  I hope that helps,

  Nash

  ---

  Nash Pherson, Senior Systems Consultant
  Now Micro - My Blog Posts
  If you've found a bug or want the product worked differently, share your feedback.
  <-- If this post was helpful, please click "Vote as Helpful".

  Saturday, January 25, 2014 4:17 PM
• 

  

  0

  Sign in to vote

  I spent several hours trying to resolve this issue. I finally came across this thread.

  I did have an OU with a / in it. I have changed it and the error has gone away. Thanks!

  Monday, February 13, 2017 8:44 PM