polarbear101
Dec 28, 2011, updated at 14:09:03 (UTC)
view5247
view7
0
Goto Top

Windows 2k8 R2 Server nach Restore kein Sysvol und Netlogon

GermansolvedQuestionWindows ServerMicrosoft

Nach einem Full Restore ist kein Sysvol und Netlogon mehr vorhanden.

Hi *all

Nach Full Restore ist kein Sysvol und Netlogon mehr vorhanden.
Finde folgendes Verzeichnis auf dem zurueckgeladenen Server:
c:\Windows\SYSVOL\sysvol\xxx.yyy.com\NtFrs_PreExisting___See_EventLog
Hier sind die Logon Scripts und Policies.

Habe folgendes versucht, leider ohne Erfolg:
repadmin /syncall
CALLBACK MESSAGE: The following replication is in progress:
    From: 4752ff38-26b7-4eda-a73e-5f07d7ba3f2e._msdcs.xxx.yyy.com
    To  : f7bef194-e159-4171-b9e4-4067ac5f0f29._msdcs.xxx.yyy.com
CALLBACK MESSAGE: The following replication completed successfully:
    From: 4752ff38-26b7-4eda-a73e-5f07d7ba3f2e._msdcs.xxx.yyy.com
    To  : f7bef194-e159-4171-b9e4-4067ac5f0f29._msdcs.xxx.yyy.com
CALLBACK MESSAGE: SyncAll Finished.
SyncAll terminated with no errors.

repadmin /showrepl
C:\Users\mb>repadmin /showrepl
Repadmin: running command /showrepl against full DC localhost
Default-First-Site-Name\2K8SRV01
DSA Options: IS_GC
Site Options: (none)
DSA object GUID: f7bef194-e159-4171-b9e4-4067ac5f0f29
DSA invocationID: 13b27689-009a-4d9c-a274-2a130acec1ef

==== INBOUND NEIGHBORS ======================================

DC=xxx,DC=yyy,DC=ch
    Default-First-Site-Name\2K8SRV02 via RPC
        DSA object GUID: 4752ff38-26b7-4eda-a73e-5f07d7ba3f2e
        Last attempt @ 2011-12-28 14:37:19 was successful.

CN=Configuration,DC=xxx,DC=yyy,DC=ch
    Default-First-Site-Name\2K8SRV02 via RPC
        DSA object GUID: 4752ff38-26b7-4eda-a73e-5f07d7ba3f2e
        Last attempt @ 2011-12-28 14:39:46 was successful.

CN=Schema,CN=Configuration,DC=xxx,DC=yyy,DC=ch
    Default-First-Site-Name\2K8SRV02 via RPC
        DSA object GUID: 4752ff38-26b7-4eda-a73e-5f07d7ba3f2e
        Last attempt @ 2011-12-28 13:55:13 was successful.

DC=DomainDnsZones,DC=xxx,DC=yyy,DC=ch
    Default-First-Site-Name\2K8SRV02 via RPC
        DSA object GUID: 4752ff38-26b7-4eda-a73e-5f07d7ba3f2e
        Last attempt @ 2011-12-28 13:55:13 was successful.

DC=ForestDnsZones,DC=xxx,DC=yyy,DC=ch
    Default-First-Site-Name\2K8SRV02 via RPC
        DSA object GUID: 4752ff38-26b7-4eda-a73e-5f07d7ba3f2e
        Last attempt @ 2011-12-28 13:55:13 was successful.
Der Server laeuft so weit.
Wie kann Sysvol und Netlogon wieder aktiviert werden ?
Bin auf aeltere Beitraege gestossen, moechte jedoch nichts zerschiessen um den Server nicht nochmals laden zu muessen.

Besten Dank fuer Eure Hilfe.

Gruss
Markus
comment-contentCommentShareShare
Share on Facebook Share on Twitter Share on Reddit Share on Linkedin

Content-Key: 178149

Url: https://administrator.de/contentid/178149

Printed on: April 25, 2024 at 11:04 o'clock

7 Comments
Latest comment
Goto Top
Member: Dani
Dani Dec 28, 2011 at 14:10:28 (UTC)
Goto Top
Hallo Markus,
kurze Gegenfrage:
Wie hast du das Fullbackup erzeugt (mit welcher Software) und wie hast du es wieder hergestellt?
Handelt es sich bei dem Server um einen DC?
Hast du noch andere DC in deinem Netzwerk?


Grüße,
Dani
Member: Hubert.N
Hubert.N Dec 28, 2011 at 14:17:19 (UTC)
Goto Top
kleien Ergänzung dazu: Ein dcdiag wäre auch noch eine Sache, die interessant wäre...
Member: polarbear101
polarbear101 Dec 28, 2011 at 14:26:32 (UTC)
Goto Top
Hallo Dani

Danke fuer Deine Zeit

Zu Deinen Fragen:
- Fullbackup wurde gemacht mit wbadmin, restore mit dem USB-Windows Boot mit "recovery" (sorry weiss nicht wie das Teil heisst)
- ist ein DC
- es ist noch ein anderer DC im Netz aktiv, der hat Sysvol und Netlogon
Member: polarbear101
polarbear101 Dec 28, 2011 at 14:29:11 (UTC)
Goto Top
Hier noch dcdiag:


Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\mb>dcdiag

Directory Server Diagnosis

Performing initial setup:
Trying to find home server...
Home Server = 2k8srv01
        • Identified AD Forest.
        Done gathering initial info.

        Doing initial required tests

        Testing server: Default-First-Site-Name\2K8SRV01
        Starting test: Connectivity
        ......................... 2K8SRV01 passed test Connectivity

        Doing primary tests

        Testing server: Default-First-Site-Name\2K8SRV01
        Starting test: Advertising
        Warning: DsGetDcName returned information for
        \\2K8SRV02.xxx.yyy.com, when we were trying to reach 2K8SRV01.
        SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.
        ......................... 2K8SRV01 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.
        ......................... 2K8SRV01 passed test FrsEvent
        Starting test: DFSREvent
        ......................... 2K8SRV01 passed test DFSREvent
        Starting test: SysVolCheck
        ......................... 2K8SRV01 passed test SysVolCheck
        Starting test: KccEvent
        ......................... 2K8SRV01 passed test KccEvent
        Starting test: KnowsOfRoleHolders
        ......................... 2K8SRV01 passed test KnowsOfRoleHolders
        Starting test: MachineAccount
        ......................... 2K8SRV01 passed test MachineAccount
        Starting test: NCSecDesc
        ......................... 2K8SRV01 passed test NCSecDesc
        Starting test: NetLogons
        Unable to connect to the NETLOGON share! (\\2K8SRV01\netlogon)
        [2K8SRV01] An net use or LsaPolicy operation failed with error 67,
        The network name cannot be found..
        ......................... 2K8SRV01 failed test NetLogons
        Starting test: ObjectsReplicated
        ......................... 2K8SRV01 passed test ObjectsReplicated
        Starting test: Replications
        ......................... 2K8SRV01 passed test Replications
        Starting test: RidManager
        ......................... 2K8SRV01 passed test RidManager
        Starting test: Services
        ......................... 2K8SRV01 passed test Services
        Starting test: SystemLog
        An error event occurred. EventID: 0x00000457
        Time Generated: 12/28/2011 15:27:11
        Event String:
        Driver FinePrint 6 required for printer FinePrint is unknown. Contac
        t the administrator to install the driver before you log in again.
        An error event occurred. EventID: 0x00000457
        Time Generated: 12/28/2011 15:27:12
        Event String:
        Driver SHARP MX-4501N PCL6 required for printer !!192.168.50.10!SHAR
        P MX-4501N PCL6 is unknown. Contact the administrator to install the driver befo
        re you log in again.
        An error event occurred. EventID: 0x00000457
        Time Generated: 12/28/2011 15:27:16
        Event String:
        Driver CutePDF Writer required for printer CutePDF Writer is unknown
        . Contact the administrator to install the driver before you log in again.
        An error event occurred. EventID: 0x00000457
        Time Generated: 12/28/2011 15:27:18
        Event String:
        Driver Foxit Phantom Printer Driver required for printer Foxit Phant
        om Printer is unknown. Contact the administrator to install the driver before yo
        u log in again.
        An error event occurred. EventID: 0x00000457
        Time Generated: 12/28/2011 15:27:18
        Event String:
        Driver Journalnotizdruck-Treiber required for printer Journalnotizdr
        uck is unknown. Contact the administrator to install the driver before you log i
        n again.
        ......................... 2K8SRV01 failed test SystemLog
        Starting test: VerifyReferences
        ......................... 2K8SRV01 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 : xxx
        Starting test: CheckSDRefDom
        ......................... xxx passed test CheckSDRefDom
        Starting test: CrossRefValidation
        ......................... xxx passed test CrossRefValidation

        Running enterprise tests on : xxx.yyy.com
        Starting test: LocatorCheck
        ......................... xxx.yyy.com passed test LocatorCheck
        Starting test: Intersite
        ......................... xxx.yyy.com passed test Intersite
Member: Hubert.N
Hubert.N Dec 29, 2011 at 16:54:54 (UTC)
Goto Top
Prüfe mal die DNS-Einstellungen / Namensauflösung.
Member: polarbear101
polarbear101 Dec 30, 2011 at 08:11:03 (UTC)
Goto Top
Besten Dank
DNS Einstellungen sind OK
Aufloesung korrekt.
Member: polarbear101
polarbear101 Dec 30, 2011 at 08:17:03 (UTC)
Goto Top
Problem ist geloest.

Schande, dass ein DC nicht ohne Probleme restored werden kann.


Service "File Replication Service" STOP

Registry Key auf "D4" aendern:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\NtFrs\Parameters\Backup/Restore\Process at Startup]
"BurFlags"=dword:00000000

Service "File Replication Service" START

Eigenartigerweise musste das auf beiden DC's gemacht werden.

Danach war alles wieder OK:
The File Replication Service is no longer preventing the computer 2K8SRV02 from becoming a domain controller.
The system volume has been successfully initialized and the Netlogon service has been notified that
the system volume is now ready to be shared as SYSVOL.

Type "net share" to check for the SYSVOL share.


The File Replication Service successfully added the connections shown below to the replica set:
"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"

Outbound to "2K8SRV01.xxx.yyy.com"
Inbound from "2K8SRV01.xxx.yyy.com"


Gruss
Markus
GermansolvedQuestionWindows ServerMicrosoft
Hotly discussed
gleixnerdCheck of ZFW Firewallgleixnerd - 5 CommentsjstrickerWireguard VPN on UDM Pro behind Fritzbox - Handshake did not completejstricker - 3 Comments