P
Phil
Hi !
My problem is the following one :
- I've got a Win2k native mode domain
- 4 DC : 1 is my Root Server, 2 is my Exchange 2k SP3, 3 is my HTTP/FTP
server, and 4 SPSv1.0+VPN
All my DCs are Windows 2000 Server SP3 except one, my root server which is
SP4.
The domain is working properly, no serious problem. A feww errors in the
event managers but nothing apparently "crippling my domain.
I was planning to migrate my domain to Windows 2003.
I first checked up all the points mentioned in article Q331161 and
everyhting looked ok.
I first tried the "adprep /forestprep" command and here's what i got
(translation from French) :
Connection to PHILWIN2KSERVER opened
Liaison SSPI successful Naming Context
DC=Philolga,DC=fr detected
Naming Context
CN=Schema,CN=Configuration,DC=Philolga,DC=fr detected
Naming Context CN=Configuration,DC=Philolga,DC=fr detected
Current schema version is 13
Updating schema version to 30
ERROR : unable to transfer schema FSMO role: 52 (Unavailable).
I tried twice, then rebooted the DC but same thing.
I checked my domain with Netdiag and all is correct.
I then checked my DCs with DCdiag and got this :
C:\Program Files\Support Tools>DCDIAG.EXE /e /test:frssysvol
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Premier-Site-par-defaut\PHILWEB2K
Starting test: Connectivity
......................... PHILWEB2K passed test Connectivity
Testing server: Premier-Site-par-defaut\ALEXIA
Starting test: Connectivity
......................... ALEXIA passed test Connectivity
Testing server: Premier-Site-par-defaut\PHILBACKUP
Starting test: Connectivity
......................... PHILBACKUP passed test Connectivity
Testing server: Premier-Site-par-defaut\PHILWIN2KSERVER
Starting test: Connectivity
......................... PHILWIN2KSERVER passed test Connectivity
Doing primary tests
Testing server: Premier-Site-par-defaut\PHILWEB2K
Starting test: frssysvol
......................... PHILWEB2K passed test frssysvol
Testing server: Premier-Site-par-defaut\ALEXIA
Starting test: frssysvol
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
......................... ALEXIA passed test frssysvol
Testing server: Premier-Site-par-defaut\PHILBACKUP
Starting test: frssysvol
......................... PHILBACKUP passed test frssysvol
Testing server: Premier-Site-par-defaut\PHILWIN2KSERVER
Starting test: frssysvol
......................... PHILWIN2KSERVER passed test frssysvol
Running enterprise tests on : Philolga.fr
I obviously used the Admin account which is member of all the groups
required to start an adprep command.
I had an event 13559 on my Root DC. As I couldn't get rid of it in spite of
the manipulation mentioned in this event, I "simply" did a DC Promo,
transfered the roles from my root to my Exchange Server, then, after an
hour, did another DC promo on my root server, transfered back the roles to
my DC Root, checked that it was the GC and tried another adprep, but same
thing...
I browsed the Technet and the Web but to no avail !!
Anaybody has an idea or a suggestion to try to narrow the problem a litlle
bit !!??
thx in advance for your help.
Phil.
My problem is the following one :
- I've got a Win2k native mode domain
- 4 DC : 1 is my Root Server, 2 is my Exchange 2k SP3, 3 is my HTTP/FTP
server, and 4 SPSv1.0+VPN
All my DCs are Windows 2000 Server SP3 except one, my root server which is
SP4.
The domain is working properly, no serious problem. A feww errors in the
event managers but nothing apparently "crippling my domain.
I was planning to migrate my domain to Windows 2003.
I first checked up all the points mentioned in article Q331161 and
everyhting looked ok.
I first tried the "adprep /forestprep" command and here's what i got
(translation from French) :
Connection to PHILWIN2KSERVER opened
Liaison SSPI successful Naming Context
DC=Philolga,DC=fr detected
Naming Context
CN=Schema,CN=Configuration,DC=Philolga,DC=fr detected
Naming Context CN=Configuration,DC=Philolga,DC=fr detected
Current schema version is 13
Updating schema version to 30
ERROR : unable to transfer schema FSMO role: 52 (Unavailable).
I tried twice, then rebooted the DC but same thing.
I checked my domain with Netdiag and all is correct.
I then checked my DCs with DCdiag and got this :
C:\Program Files\Support Tools>DCDIAG.EXE /e /test:frssysvol
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Premier-Site-par-defaut\PHILWEB2K
Starting test: Connectivity
......................... PHILWEB2K passed test Connectivity
Testing server: Premier-Site-par-defaut\ALEXIA
Starting test: Connectivity
......................... ALEXIA passed test Connectivity
Testing server: Premier-Site-par-defaut\PHILBACKUP
Starting test: Connectivity
......................... PHILBACKUP passed test Connectivity
Testing server: Premier-Site-par-defaut\PHILWIN2KSERVER
Starting test: Connectivity
......................... PHILWIN2KSERVER passed test Connectivity
Doing primary tests
Testing server: Premier-Site-par-defaut\PHILWEB2K
Starting test: frssysvol
......................... PHILWEB2K passed test frssysvol
Testing server: Premier-Site-par-defaut\ALEXIA
Starting test: frssysvol
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
......................... ALEXIA passed test frssysvol
Testing server: Premier-Site-par-defaut\PHILBACKUP
Starting test: frssysvol
......................... PHILBACKUP passed test frssysvol
Testing server: Premier-Site-par-defaut\PHILWIN2KSERVER
Starting test: frssysvol
......................... PHILWIN2KSERVER passed test frssysvol
Running enterprise tests on : Philolga.fr
I obviously used the Admin account which is member of all the groups
required to start an adprep command.
I had an event 13559 on my Root DC. As I couldn't get rid of it in spite of
the manipulation mentioned in this event, I "simply" did a DC Promo,
transfered the roles from my root to my Exchange Server, then, after an
hour, did another DC promo on my root server, transfered back the roles to
my DC Root, checked that it was the GC and tried another adprep, but same
thing...
I browsed the Technet and the Web but to no avail !!
Anaybody has an idea or a suggestion to try to narrow the problem a litlle
bit !!??
thx in advance for your help.
Phil.