Re: Problem creating computer accounts in OU containing a fwd slash ("

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance




"Ryan Hanisco" <RyanHanisco@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:F1BD92F2-7694-4A28-A2FB-1529D628BD1A@xxxxxxxxxxxxxxxx

Here is the document containing the naming rules:
http://support.microsoft.com/kb/909264

Thanks for the pointer. I did come across that article (until I did, I had been suspecting that forward slashes simply weren't legal/correct for OU names, which made me wonder why ADUC had allowed it).

The other possibility is that the problem is not related to that at all and
it is really elsewhere. Though I would certanly start there -- Occam's razor.

I tried renaming the OU so that it doesn't have a slash and the problem went away, then added it back and the problem returned - so that seems to pretty well isolate it.

I assume this has something to do with the fact that NTDS paths use forward, not back, slashes for object hierarchy. The forward slash in the OU name is escaped by a backslash if you look at its canonical name in ADUC, i.e. mydomain.com/ParentOU/Lab\/Testing . However, it would appear that something behind the scenes in AD that defines the join ACLs after creating the account isn't set up to do this kind of escaping, and so the computer path it tries to use for that operation fails.

Interestingly, it doesn't matter if the defined join *user* is in an OU with a slash - only the location of the computer triggers the problem.

I didn't want to burn a support case just to report this, since it doesn't really affect us in any important way, but I figured if I mentioned it here the MS devs might pick it up.
--m

.



Relevant Pages

  • Re: How to replace path slash character delimiters, when saving fi
    ... the slash delimiters are still there. ... the folder name, the slashes are automatically removed, and a little yellow ... > a filename, so I also dont need all the fuss that goes with it."- meaning ... >> Just use Favorites | Add to Favorites. ...
    (microsoft.public.windowsxp.general)
  • Re: why there is // ?
    ... only if no alias is already set ... The double slashes are a common off-by-1 mistake. ... slash, it is usually error-prone, as in the first command. ... they make quite a difference when setting environment variables ...
    (comp.unix.shell)
  • Re: why there is // ?
    ... The double slashes are a common off-by-1 mistake. ... slash, it is usually error-prone, as in the first command. ... POSIX 1003.2 "4.11 Pathname Resolution" states: ... Trailing slashes were and still are useful to force the ...
    (comp.unix.shell)
  • Re: [PATCH] reiserfs: fix handling of device names with /s in them
    ... The generic block device code ... Your patch handles at most one slash. ... But the description mentions 'slashes' ... Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org ...
    (Linux-Kernel)