Similar to the -u option you'll probably want to make sure your tools
support LDAP v3. LDAP v2 only supports a subset of the characters LDAP v3
supports. If you retrieve results using LDAP v2 containing characters not
supported by LDAP v2 I believe the object will be returned but those
characters may be returned as a LDAP v2 supported character. If LDAP v2 is
important to you I'd suggest testing those tools with the special characters
you plan on using to make sure they work to your satisfaction. The tools
"in the box" default to LDAP v3.
Jason
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Active directory is Unicode compliant and so are tools, but you could run
into some tools that have problems with "special" characters. Various tools
have -u switch to make them unicode aware. I always use "special" characters
in OU names and usernames (my language has some), and have not run into any
issue with AD itself. In the future Unicode support will be stronger and
stronger, so there should be no problems with that.
--
Regards
Matjaz Ladava, MCSE, MCSA, MCT, MVP
Microsoft MVP - Active Directory
(e-mail address removed), (e-mail address removed)
http://ladava.com
Hello all,
I wanted to know if I name a group, OU or any item in AD and put a special
character like éèàêç , will it cause any problems in the futur? If so, is
there a RFC or document that would explain this?
thanks
michael
