Link to home
Start Free TrialLog in
Avatar of tamco
tamcoFlag for United States of America

asked on

LDIFDE config file???

How do I ensure that strict replication consistency is enabled for newly promoted domain controllers?

I have attempted to use the documentation available from Microsoft here: http://technet.microsoft.com/en-us/library/cc949134(WS.10).aspx#BKMK_Ensure_Strict.

I created a file as mentioned in the documentation, however I continue to receive an error every time I try to run the command: ldifde -i -f <Path>\<FileName>

The error is in the code snippet below. I have tried variations of removing whitespace and just succeed in getting different error messages.

Any help would be much appreciated.

FYI - In addition to the link above, I also used the following link to attempt to solve the issue myself prior to posting:
http://technet.microsoft.com/en-us/library/cc755456(WS.10).aspx

Connecting to "<PDC>"
Logging in as current user using SSPI
Importing directory from file "x:\strict_repl.txt"
Loading entries.
There is a syntax error in the input file
Failed on line 3.  The last token starts with 'd'.
0 entries modified successfully.
An error has occurred in the program
No log files were written.  In order to generate a log file, please
specify the log file path via the -j option.

Open in new window

ASKER CERTIFIED SOLUTION
Avatar of tamco
tamco
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I was about to say, at the end of the first article you posted, someone else has the same problem and suggests the exact ADSIedit work around you just mentioned!

Was going to ask if you'd tried that yet... :) lol

Nevermind!

Pete
Would be interesting to see the content of the log file though?

"specify the log file path via the -j option."
Avatar of tamco

ASKER

Pete,
I was the one to post that solution actually. :-)
I have tried the -j option a few times, every time I receive the error "Unable to open log file."  It doesn't seem to matter what path I use for the log file or if the file already exists or not.
Awinish,
The links listed show me how to turn it on on a case by case basis.  I already completed that, I want to enable this for the domain so any new DC's automatically have it enabled.