Re: distinguishedName contains a backslash char
From: Joe Richards [MVP] (humorexpress_at_hotmail.com)
Date: 02/13/05
- Next message: Joe Richards [MVP]: "Re: dsquery user exchange features"
- Previous message: Joe Richards [MVP]: "Re: There are multiple accounts with name HOST/mars.strc.local of type"
- In reply to: wenj: "Re: distinguishedName contains a backslash char"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 12 Feb 2005 19:57:51 -0500
It is acceptable but can cause issues. Some applications can have issues with it
including ADUC on Windows 2000 ADUC with certain specific domain configurations.
Generally I recommend that you use your samaccountname value in your cn.
joe
-- Joe Richards Microsoft MVP Windows Server Directory Services www.joeware.net wenj wrote: > Yes, that is what I meant :) > I see now how it is derived, and it seems that it is working as advertised, > since the CN has the user name as John, Doe - and it sticks the backslash in > there as to skip the comma. I just needed assurance that this was acceptable > and that it would not create migration (intra-forest and Exch) issues. Thank > you very much! > > "Al Mulnick" wrote: > > >>When you say built from, what do you mean exactly? >>The distinguished name is the distinguished name, meaning it is derived from >>the path that uniquely identifies it. Basically CN + Path == DN. >> >>Is that what you meant? >> >> >> >> >>"wenj" <wjuhl@optonline.net.nospam> wrote in message >>news:939D0ECB-3BEC-4DD6-95B1-48A06B873682@microsoft.com... >> >>>Hello Al! >>>I appreciate the insight! Can you tell me what field/attribute the >>>distinguishedName is built from, such as the Display Name? >>>Thanks again! >>> >>>"Al Mulnick" wrote: >>> >>> >>>>That's an escape character. It translates into "whatever the next char, >>>>treat it as a literal". >>>>Commas are not valid characters, so they get escaped by the backslash to >>>>indicate that it's ok to leave it there and just ignore it in terms of >>>>the >>>>syntax. Notice how the rest of the segments are separated by commas? >>>> >>>>Al >>>> >>>> >>>>"wenj" <wjuhl@optonline.net.nospam> wrote in message >>>>news:DB082BAF-9363-4927-9744-431E57693DCD@microsoft.com... >>>> >>>>>My user accounts sport a backslash char in their distinguishedName >>>>>attributes, as seen below. Although I see reference to the backslash >>>>>char >>>>>in >>>>>RFC's, I cannot gather if it is potentially an issue. A MS tech once >>>>>said >>>>>that it was because the domain was upgraded from NT4, but I also see >>>>>the >>>>>same >>>>>behavior in my pristine Root domain. My main concern is that I have >>>>>two >>>>>children off the Root - one that will be migrating to the other using >>>>>the >>>>>QMM >>>>>product. There is Exch 5.5 in the environment, with an ADC in >>>>>readiness >>>>>for >>>>>Exch2003. Where did this char come from, and will it potentially cause >>>>>issues from a migration point of view? >>>>>CN=Doe\, John,OU=Service Management,DC=ad,DC=wenj,DC=net >>>>>Thanks! >>>> >>>> >>>> >> >>
- Next message: Joe Richards [MVP]: "Re: dsquery user exchange features"
- Previous message: Joe Richards [MVP]: "Re: There are multiple accounts with name HOST/mars.strc.local of type"
- In reply to: wenj: "Re: distinguishedName contains a backslash char"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
