"Neil" <N***@discussions.microsoft.com> wrote in message
news:442B2181-9449-4038-B9FC-A28FDA8F6B6F@microsoft.com...
>I am currently researching the process to update a Windows 2000 Server
>schema
> environment to Windows Server 2003 schema.  Because I have an Exchange
> 2000
> server on the network, I was looking at KB article #314649.  It has some
> explicit instructions for running the ldifde.exe program from the command
> line.  However, the instructions are a little hard to understand.  In
> particular, this part:
>
> ---------
>
> "From the console of the schema operations master, load the
> Inetorgpersonfix.ldf file by using Ldifde.exe to correct the
> LdapDisplayName
> attribute of the houseIdentifier, the Secretary, and the labeledURI
> attributes. To do this, type the following command, where X is a
> case-sensitive constant and dn path for forest root domain is the domain
> name
> path for the root domain of the forest wrapped in quotation marks:
>
> ldifde -i -f inetorgpersonfix.ldf -v -c DC=X "dn path for forest root
> domain"
>
> ---------
>
> I do not understand what the value X in DC=X is supposed to be (it only
> says
> it is a case-sensitive constant), and I can't tell if the "dn path for
> forest
> root domain" is supposed to be the value of X or is supposed to be added
> on
> the end of the command string in addition to some other value for X.  The
> only logical thing I can interpret from this is a FQDN, such as
> server1.mydomain.org encompassing both the values of "DC=X" (server1)  and
> "dn path for forest root domain" (mydomain.org).  Can anyone help clarify
> this or tell me where I can find the value for these on my network?  (I'm
> 99%
> sure, but just want to be 100% sure.)  Thanks!
>

"Jorge de Almeida Pinto [MVP - DS]" wrote:

> >>>>ldifde -i -f inetorgpersonfix.ldf -v -c DC=X "dn path for forest root
> >>>>domain"
>
> If you open up the LDF file you will see DC=X.
> The option -c means replace DC=X with "dn path for forest root domain"
>
> run ldifde /? to see it for yourself
>
> --
>
> Cheers,
> (HOPEFULLY THIS INFORMATION HELPS YOU!)
>
> # Jorge de Almeida Pinto # MVP Windows Server - Directory Services
>
> BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
> BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
> ------------------------------------------------------------------------------------------
> * This posting is provided "AS IS" with no warranties and confers no rights!
> * Always test before implementing!
> ------------------------------------------------------------------------------------------
> #################################################
> #################################################
> ------------------------------------------------------------------------------------------
> "Neil" <N***@discussions.microsoft.com> wrote in message
> news:442B2181-9449-4038-B9FC-A28FDA8F6B6F@microsoft.com...
> >I am currently researching the process to update a Windows 2000 Server
> >schema
> > environment to Windows Server 2003 schema.  Because I have an Exchange
> > 2000
> > server on the network, I was looking at KB article #314649.  It has some
> > explicit instructions for running the ldifde.exe program from the command
> > line.  However, the instructions are a little hard to understand.  In
> > particular, this part:
> >
> > ---------
> >
> > "From the console of the schema operations master, load the
> > Inetorgpersonfix.ldf file by using Ldifde.exe to correct the
> > LdapDisplayName
> > attribute of the houseIdentifier, the Secretary, and the labeledURI
> > attributes. To do this, type the following command, where X is a
> > case-sensitive constant and dn path for forest root domain is the domain
> > name
> > path for the root domain of the forest wrapped in quotation marks:
> >
> > ldifde -i -f inetorgpersonfix.ldf -v -c DC=X "dn path for forest root
> > domain"
> >
> > ---------
> >
> > I do not understand what the value X in DC=X is supposed to be (it only
> > says
> > it is a case-sensitive constant), and I can't tell if the "dn path for
> > forest
> > root domain" is supposed to be the value of X or is supposed to be added
> > on
> > the end of the command string in addition to some other value for X.  The
> > only logical thing I can interpret from this is a FQDN, such as
> > server1.mydomain.org encompassing both the values of "DC=X" (server1)  and
> > "dn path for forest root domain" (mydomain.org).  Can anyone help clarify
> > this or tell me where I can find the value for these on my network?  (I'm
> > 99%
> > sure, but just want to be 100% sure.)  Thanks!
> >
>
>
>

"Paul Williams [MVP]" wrote:

> The option -c will replace the string DC=X with another string.  Therefore,
> you should input your domain's DN, e.g. LDIFDE -i -f inport.ldf -c DC=X
> DC=domain-name,DC=com
>
> Note.  The above is from memory, and might be missing something, but you
> catch my drift.
>
> --
> Paul Williams
> Microsoft MVP - Windows Server - Directory Services
> http://www.msresource.net  |  http://forums.msresource.net
> 
>
>
>

"Jules" wrote:

> I am having a problem with this process also. I use the following syntax.
> ldifde -i -f inetorgpersonfix.ldf -v -c DC=X DC=domainname,DC=com
> I then receiv the following message.
>
> Connecting to "server.domain.com"
> Logging in as current user using SSPI
> Importing directory from file "inetorgpersonfix"
> Error occured during initialization
> File operation failure
> 0 entries modified successfully.
> An error has occurred in the program
>
> Any help will be greatly appreciated.
>
> "Paul Williams [MVP]" wrote:
>
> > The option -c will replace the string DC=X with another string.  Therefore,
> > you should input your domain's DN, e.g. LDIFDE -i -f inport.ldf -c DC=X
> > DC=domain-name,DC=com
> >
> > Note.  The above is from memory, and might be missing something, but you
> > catch my drift.
> >
> > --
> > Paul Williams
> > Microsoft MVP - Windows Server - Directory Services
> > http://www.msresource.net  |  http://forums.msresource.net
> > 
> >
> >
> >

"Jules" wrote:

> Correction... There was a typo that caused this message. the correct message
> is.
>
>
> Connecting to "server.domain.com"
> Logging in as current user using SSPI
> Importing directory from file "inetorgpersonfix.ldf"
> Loading entries
> 1: CN=secretary,CN=Schema,CN=Configuration,DC=mmpcinc,DC=com
> Entry DN: CN=secretary,CN=Schema,CN=Configuration,DC=domainname,DC=com
> change: modify
> Attribute 0) lDAPDisplayName:secretary
>
> Add error on line 3: No Such Object
> The server side error is "Directory object not found."
> 0 entries modified successfully.
> An error has occurred in the program
>
>
>
> "Jules" wrote:
>
> > I am having a problem with this process also. I use the following syntax.
> > ldifde -i -f inetorgpersonfix.ldf -v -c DC=X DC=domainname,DC=com
> > I then receiv the following message.
> >
> > Connecting to "server.domain.com"
> > Logging in as current user using SSPI
> > Importing directory from file "inetorgpersonfix"
> > Error occured during initialization
> > File operation failure
> > 0 entries modified successfully.
> > An error has occurred in the program
> >
> > Any help will be greatly appreciated.
> >
> > "Paul Williams [MVP]" wrote:
> >
> > > The option -c will replace the string DC=X with another string.  Therefore,
> > > you should input your domain's DN, e.g. LDIFDE -i -f inport.ldf -c DC=X
> > > DC=domain-name,DC=com
> > >
> > > Note.  The above is from memory, and might be missing something, but you
> > > catch my drift.
> > >
> > > --
> > > Paul Williams
> > > Microsoft MVP - Windows Server - Directory Services
> > > http://www.msresource.net  |  http://forums.msresource.net
> > > 
> > >
> > >
> > >

"Neil" wrote:

> I have not yet tried to run the fix, but the reference I'm using for this is
> KB article #314649.  The KB article goes into detail about different
> scenarios in which to use the inetorgpersonfix.ldf fix and also how to use
> the ADSI Edit tool to check in AD and see if the LDAP attribute names were
> mangled and need to be fixed.  It may be the case that your attributes are
> not mangled and don't need the fix (guessing here).  The article seemed to
> indicate that, under my scenario, the attribute names should be mangled but
> they are not.  So I'm a bit confused myself. 
>
> "Jules" wrote:
>
> > Correction... There was a typo that caused this message. the correct message
> > is.
> >
> >
> > Connecting to "server.domain.com"
> > Logging in as current user using SSPI
> > Importing directory from file "inetorgpersonfix.ldf"
> > Loading entries
> > 1: CN=secretary,CN=Schema,CN=Configuration,DC=mmpcinc,DC=com
> > Entry DN: CN=secretary,CN=Schema,CN=Configuration,DC=domainname,DC=com
> > change: modify
> > Attribute 0) lDAPDisplayName:secretary
> >
> > Add error on line 3: No Such Object
> > The server side error is "Directory object not found."
> > 0 entries modified successfully.
> > An error has occurred in the program
> >
> >
> >
> > "Jules" wrote:
> >
> > > I am having a problem with this process also. I use the following syntax.
> > > ldifde -i -f inetorgpersonfix.ldf -v -c DC=X DC=domainname,DC=com
> > > I then receiv the following message.
> > >
> > > Connecting to "server.domain.com"
> > > Logging in as current user using SSPI
> > > Importing directory from file "inetorgpersonfix"
> > > Error occured during initialization
> > > File operation failure
> > > 0 entries modified successfully.
> > > An error has occurred in the program
> > >
> > > Any help will be greatly appreciated.
> > >
> > > "Paul Williams [MVP]" wrote:
> > >
> > > > The option -c will replace the string DC=X with another string.  Therefore,
> > > > you should input your domain's DN, e.g. LDIFDE -i -f inport.ldf -c DC=X
> > > > DC=domain-name,DC=com
> > > >
> > > > Note.  The above is from memory, and might be missing something, but you
> > > > catch my drift.
> > > >
> > > > --
> > > > Paul Williams
> > > > Microsoft MVP - Windows Server - Directory Services
> > > > http://www.msresource.net  |  http://forums.msresource.net
> > > > 
> > > >
> > > >
> > > >