Thanks. But why does not LDIFDE.EXE follow the RFC 2253 spec ?
If I go from an accpted format and include one single escape and a comma I get the following error:
---
Loading entries.
Add error on line 5: Invalid DN Syntax
The server side error is: 0x2081 Multiple values were specified for an attribute that can have only one value.
The extended server error is:
00002081: NameErr: DSID-03050B83, problem 2003 (BAD_ATT_SYNTAX), data 0, best match of:
---
And according to the spec I should be able to use both \= and "=" both they don't work with LDIFDE.EXE
The attribute field is of a type Unicode String.
Johan
----- Dmitri Gavrilov [MSFT] wrote: -----
Use base64 encoding for such values, for the whole value. That would let
ldifde decode them properly. On top of that, you must properly escape RDN
values in DNs. This is defined in the standard, don't remember the number
off the top of my head. Search for and RFC with "distinguishedName".
One hint is to create the entry in AD with a gui tool, and then export it
using ldifde -- you will see how to properly format it.
--
Dmitri Gavrilov
SDE, Active Directory Core
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
"Johan" <anonymous@discussions.microsoft.com> wrote in message
news:48E47D5F-8069-4637-B77B-5019AD413E4C@microsoft.com...
command tool ldifde.
also goes into the DN.
format error. I do have tried to use the hexvalue of e.g. "<" , but that
didn't work.
