Demoting 2003 server; Active directory wizard states no other AD DCs can be contacted
i have inherited windows infrastructure in pdc / gc server 2003 standard, , had existing server 2008 configured dc & gc. this in single forest, single domain.
existing servers:
win2k-app, 172.16.86.7: 2003 pdc / gc / dns
erbapp, 172.16.86.25: 2008 dc / gc / dns
new server:
erb-svr-01, 172.16.86.12: 2008r2 dc / gc / dns
dns
win2k-app: preferred dns 127.0.0.1, alternate dns 172.16.86.12
erbapp: preferred dns 127.0.0.1, alternate dns 172.16.86.12
erb-svr-02: preferred dns 127.0.0.1, alternate dns 172.16.86.25
i have added 2008r2 server mix purposes of making pdc, , demote 2003 member (for now) until can domain functional level @ least 2008.
procedures adding new dc
win2k-app: ran adprep32 /forestprep, /domainprep /gpprep, , /rodcprep 2008r2 cd. all successful.
erb-svr-02: installed adds , installation completed without issues.
win2k-app: transferred fsmo roles new 2008r2 server without issues. verified "netdom query fsmo":
schema master erb-svr-02.erb.local
domain naming master erb-svr-02.erb.local
pdc erb-svr-02.erb.local
rid pool manager erb-svr-02.erb.local
infrastructure master erb-svr-02.erb.local
command completed successfully.
win2k-app: ran dcpromo demote server.
- got message dc global catalog , should make sure gcs accessible users before proceeding. my 2008 , 2008r2 gc, proceeded.
- on remove active directory dialog, left box unchecked , proceeded
- got warning though unchecked box, there no other ad dcs domain contacted.
- cancelled wizard
i'm getting mixed signals various tools run:
net share on erbapp / erb-svr-01 (2008/2008r2) servers shows there no netlogon or sysvol folders being shared
net share on win2k-app (2003) server shows netlogon , sysvol folders being shared properly
repadmin /showreps on win2k-app shows successful both 2008 servers
dcdiag /q on win2k-app shows:
no record of frs, sysvol started. the ad may prevented starting"
dcdiag /q on erb-svr-01 shows:
when trying reach erb-svr-02.
server not responding or not considered suitable.
......................... erb-svr-02 failed test advertising
unable connect netlogon share! (\\erb-svr-02\netlogon)
[erb-svr-02] net use or lsapolicy operation failed error 67,
the network name cannot found..
......................... erb-svr-02 failed test netlogons
dcdiag /q on erbapp shows:
server not responding or not considered suitable.
......................... erbapp failed test advertising
unable connect netlogon share! (\\erbapp\netlogon)
[erbapp] net use or lsapolicy operation failed error 67, network name cannot found..
......................... erbapp failed test netlogons
using frsdiag tool on win2k-app , trying propagation file tracer on 2 other dcs, get:
not access share (on both erbapp , erb-svr-01)
using frsdiag tool on win2k-app force replication on target server(s):
- erb-svr-02 "finished successfully"
- erbapp "finished successfully"
- win2k-app "failed all" - details below:
detecting machine's domain role ... domain controller
gathering ntfrsutl sets output , gathering upstream partners ....done!
triggering pull replication detected upstream partners ...
could not detect upstream partners, server seems orphaned! should double check this!
event log on win2k-app jrnl-wrap
event type: error
event source: ntfrs
event category: none
event id: 13568
date: 10/22/2014
time: 12:22:19 am
user: n/a
computer: win2k-app
description:
file replication service has detected replica set "domain system volume (sysvol share)" in jrnl_wrap_error.
replica set name : "domain system volume (sysvol share)"
replica root path : "c:\winnt\sysvol\domain"
replica root volume : "\\.\c:"
a replica set hits jrnl_wrap_error when record trying read ntfs usn journal not found. this can occur because of 1 of following reasons.
as sits, if turn off win2k-app server, users can log-in windows domain, it's slow , mapped drives cannot accessed without asking credentials, tells me replication of domain information , policies not working. i know dcs need have sysvol / netlogon folders shared , working there information out there wanted give me guidance.
given circumstances, should next? i've read 50+ articles on various things don't want screw migration up.
i wound calling microsoft.
my replication issue fixed performing d4 on 2003 server, , d2 on new 2008 server.
Windows Server > Migration
Comments
Post a Comment