Manglende Netlogon og Sysvol
Hej EksperterI forbindelse med migrering af en Windows 2003 Server PDC til en Windows 2008 Server, oplever jeg en fejl i synkroniseringen af de to DC'er, hvilket medføre at Netlogon og Sysvol ikke er oprettet/shared.
I Eventloggen under File Replication Service finde jeg følgende fejl: EventID nr. 13508 Ntfrs:
------------------------------------------
The File Replication Service is having trouble enabling replication from SERVER02 to SERVER05 for c:\windows\sysvol\domain using the DNS name server02.domæne.dk. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name server02.domæne.dk from this computer.
[2] FRS is not running on server02.domæne.dk.
[3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
----------------------------------------------------------------
I Eventloggen under File Replication Service finde jeg følgende fejl: EventID nr. 13566 Ntfrs:
----------------------------------------------------------------
File Replication Service is scanning the data in the system volume. Computer SERVER05 cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL.
To check for the SYSVOL share, at the command prompt, type:
net share
When File Replication Service completes the scanning process, the SYSVOL share will appear.
The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume.
----------------------------------------------------------------
De 5 roller er PDC roller er tilsyneladende overført korrekt.
----------------------------------------------------------------
Jeg har logget en DCdiag for at se på hvad problemerne består i:
----------------------------------------------------------------
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
Home Server = Server05
* Identified AD Forest.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\SERVER05
Starting test: Connectivity
......................... SERVER05 passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\SERVER05
Starting test: Advertising
Warning: DsGetDcName returned information for \\server02.domæne.dk,
when we were trying to reach SERVER05.
SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.
......................... SERVER05 failed test Advertising
Starting test: FrsEvent
There are warning or error events within the last 24 hours after the
SYSVOL has been shared. Failing SYSVOL replication problems may cause
Group Policy problems.
......................... SERVER05 passed test FrsEvent
Starting test: DFSREvent
......................... SERVER05 passed test DFSREvent
Starting test: SysVolCheck
......................... SERVER05 passed test SysVolCheck
Starting test: KccEvent
......................... SERVER05 passed test KccEvent
Starting test: KnowsOfRoleHolders
......................... SERVER05 passed test KnowsOfRoleHolders
Starting test: MachineAccount
......................... SERVER05 passed test MachineAccount
Starting test: NCSecDesc
......................... SERVER05 passed test NCSecDesc
Starting test: NetLogons
Unable to connect to the NETLOGON share! (\\SERVER05\netlogon)
[SERVER05] An net use or LsaPolicy operation failed with error 67,
Win32 Error 67.
......................... SERVER05 failed test NetLogons
Starting test: ObjectsReplicated
......................... SERVER05 passed test ObjectsReplicated
Starting test: Replications
......................... SERVER05 passed test Replications
Starting test: RidManager
......................... SERVER05 passed test RidManager
Starting test: Services
......................... SERVER05 passed test Services
Starting test: SystemLog
......................... SERVER05 passed test SystemLog
Starting test: VerifyReferences
......................... SERVER05 passed test VerifyReferences
Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Running partition tests on : Schema
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Running partition tests on : Configuration
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Running partition tests on : fjedre
Starting test: CheckSDRefDom
......................... fjedre passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... fjedre passed test CrossRefValidation
Running enterprise tests on : domæne.dk
Starting test: LocatorCheck
Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error
1355
A Good Time Server could not be located.
......................... domæne.dk failed test LocatorCheck
Starting test: Intersite
......................... domæne.dk passed test Intersite
Håber at nogen har et hint eller tip.
