Re: add a new 2003 server to domain as DC

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hi Ulf,

So happy to see that you are still around, really stucked and I got my
DCs in my dreams last night, but however no lights to solve my SYSVOL
replication problems, :))

have tried hard to fix the problem on sunday, once removed new DC,
cleaned metadata, adsiedit and dns record on old DC and recovered
FrsComputerReference and ServerReference values following Q312862, then
tried to integrate new DC again, but still failed to get SYSVOL
replication work. with FRSDIAG.exe tool, seems it also tries to
sychronize with some non-exist DCs, but checked with ntdsutil/metadata
cleanup, Domain MSC plugins, adsiedit records, dns records, all those
GUIDs/DCs appeared nowhere, is there a way I could still do a better
clean around?

guess something bad are once when our old DC crashed, we have booted an
offlined older DC, let seize all roles and also renamed the backup
DC/configured IP to the crashed one, without any cleanup work, now even
tried to rename this DC again but those dirty records never shows up
again either in metadata or in adsi records, but seems some dirty GUIDs
are still somewhere, just cannot get access to them.... is this
possible?

followed your outline, today removed again the new DC but configured it
only functioning as a member file server and secondary DNS server,
diagnosed again on both server:

---------------------------
netdiag /v /debug output:
---------------------------
new Server:
[WARNING] You don't have a single interface with the <00> 'WorkStation
Service', <03> 'Messenger Service', <20> 'WINS' names defined.
old pdc: passed all

---------------------------
dcdiag /v /a /c on old pdc, basically passed all tests but actually
problem in VerifyEnterpriseReferences:
---------------------------
Starting test: VerifyEnterpriseReferences
LDAP Error 0x5e (94) - No result present in message.
......................... BYRONBDC failed test
VerifyEnterpriseReferences

but now I am quite stucked here, found no more hints around, is this
the key problem prevented new DC integration/replicate SYSVOL with new
DC, or I should rather re-install/install a new 2k3 server to test
whether it's because my new Server also get dirty?

and, is there a chance, can man backup current DC, put offline, and
install a new DC as first DC for domain, then still restore/import all
pc/user accounts and group policies to new dc? so I'd have a chance to
surrender, kill both dc and make a clean installation for a new DC, it
might be an easier curve for me now.... are doing some restructuring
with our network, but a consulting work or MS case will cost too much
for our group.

Thank you very much for the help, and viel Gruss,

Paulo

.

Relevant Pages

  • Re: add a new 2003 server to domain as DC
    ... DCs in my dreams last night, but however no lights to solve my SYSVOL replication problems,:)) ... offlined older DC, let seize all roles and also renamed the backup DC/configured IP to the crashed one, without any cleanup work, now even tried to rename this DC again but those dirty records never shows up again either in metadata or in adsi records, but seems some dirty GUIDs are still somewhere, just cannot get access to them.... ... only functioning as a member file server and secondary DNS server, ... dcdiag /v /a /c on old pdc, basically passed all tests but actually problem in VerifyEnterpriseReferences: ...
    (microsoft.public.windows.server.active_directory)
  • Re: SYSVOL GPOs re:copying
    ... If you create a test user account on each DC, does it successfully replicate to each of the other DCs? ... Stop FRS on each of the new DCs. ... open a command prompt and change directory into the GPMC scripts folder. ... The effort and/or risk in fixing this server seems to exceed the ...
    (microsoft.public.win2000.active_directory)
  • Re: PDC Is not replicating !!
    ... server on the replication DC. ... I have ACE server installed. ... > DCs replicating by disabling replication when USN rollback is ... > If you used imaging to copy your production environment into a lab ...
    (microsoft.public.win2000.active_directory)
  • Re: Sites & Services - DSAccess w/E2K3 SP2
    ... I don't believe the firewalls are the issue as they are set to any-any among ... the all the DCs and exchange server. ... All the DCs replicate information in a mesh ... Immediately after upgrading to Exchange 2003 SP2, ...
    (microsoft.public.exchange.admin)
  • Re: LSASS.exe process near 100% usage
    ... Try pulling the network cable from the back of the server when the spike ... Do the DCs ever reboot on their own? ... The DC that was not gracefully demoted, was it a FSMO Role holder? ... 824196 Description of the License Logging Service in Windows Server ...
    (microsoft.public.win2000.active_directory)