sysvol & netlogon not sharing

  • Thread starter Thread starter HocusPocus
  • Start date Start date
H

HocusPocus

Situation:

Trying to promote a DC (W2K sp4), the GUI portion completes
successfully. Reboot the box so that the policies and scripts can
replicate in. These items start to replicate and then suddenly stops.

More details:
-the staging directory grows until it has ~2,530 items (total size is
99MB), at this point no other files enter the staging directory.
-the policies directory replicates in ~167 (of 320) GPO's, at this
point no additional policies enter this directory.
-there are no events indicating that the staging directory is out of
space, but to rule this out I have increased the "Staging Space Limit
in KB) = 3567e0 (or 3.5Gb)....this seems to have no effect (yes, I
stopped the ntfrs services - made the change to the above registry key
- then restarted the service).
-I still see the domain controller listed in the sysvol seeding
registry key - so I know where the new DC is sourcing from - all
connectivity is there (ping by netbios, IP, FQDN, and GUID)
-the SYSVOL directory structure is intact and complete (with the
exception that sysvol and netlogon aren't shared)
-I can see that the new DC is logging event 1704 - so it is applying
policy successfully.
-UltraSound is not reporting any long VVJoins, however, it is
reporting "Very old backlogged files" from the source DC to the new
DC.
-automatically generated connection objects exist - and checking the
replication topology generates connection objects successfully.
-repadmin /showreps shows no failures
-went through KB 257338....everything seems in order
-MPS Reports
-dcdiag...clean
-netdiag...clean
-repadmin (again)...clean
-netdomqueryfsmo....good
-last four events in the FRS event log are:
-13554 - FRS successfully added outbound connections
-13553 - the new DC has been added to the domain system volume
replica set
-13565 - the new DC cannot become a domain controller until sysvol
is shared
-13501 - the file replication service is starting

I am in the process of demoting this DC, and then will let the
deletion of this DC replicate forestwide. Then I will try the
promotion again, however, I feel that I will run into the same issue
again.
I have saved the ntfrs_000x.log files, which I will be looking at
shortly.

If anyone else has any additional ideas - I am game.
 
I would suggest pulling the DC out of the AD, and then going through the
directory to make sure that all of it is gone... Just like you would when
you forcibly demote a controller.

Then do your normal health checks and replmon... Finally once you're sure
everything is cool, bring the new server up as a member. Do your dns checks
with pings and NSLOOKUP and then promote...

I would expect things to be ok then.
 
Nope - removed the DC (demoted it) verified that it was gone via
ntdsutil and ADSIedit.
Waited 8 hours, renamed the box and ran dcpromo.
Still have the same situation - the GUI finishes successfully and I
reboot. When the server comes up I watch the staging directory grow
(I also watch the GPO's replicate into the 'Policies' directory). The
staging directory grows until it has ~2,530 files (about 99 MB); 167
policies get moved into the 'Policies' directory - and then everything
stops.
 
Back
Top