Didn't have much time to solve it so we demoted the server and ran = dcpromo again. After that sysvol was recreated. DNS issues we solved earlier on, half the root hints were invalid.... Now that both were solve the eventvwr got more relaxed. The netlogon (scripts) and the policies directory underneath the sysvol weren't recreated or replicated from the other servers. After doing this manually...like more things because we didn't want to wait for the = servers themselves to wake up and notice the difference....whole office staring = at us for this to be fixed.....everybody could log on to this office again. I saw most of the technet info, the thing I was wondering about was that = I wanted to recreated the sysvol dir and share it manually....haven't done = it but I'm curious if it would have worked. We chose the save way out. Greetings and thanks for the help Rob Beekmans A-Tree -----Oorspronkelijk bericht----- Van: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] Namens Robert Barrett Verzonden: donderdag 1 mei 2003 19:19 Aan: 'thin@xxxxxxxxxxxxx' Onderwerp: [THIN] Re: OT: Sysvol share recreating We had the same issue on a couple of our DC's after installing DNS. Our solution (found this in TechNet somewhere) was: The directories end up being down one level further than they should be. They have to be moved back to where they belong and then the following = key edited in the registry. HKLM\System\CurrentControlSet\Services\Netlogon\Parameters Sysvol ready change from 0 to 1 Restart the server. -----Original Message----- From: Erik Blom [mailto:erik.blom@xxxxxxxxxx]=20 Sent: Thursday, May 01, 2003 6:08 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: OT: Sysvol share recreating Rob: I found this on technet: (search on "Active Directory Disaster = Recovery") ******** Non-Authoritative Restore Active Directory Non-authoritative restore is the default method for the restoration of Active Directory, and it will be used for the majority of restore operations. Using this method, settings and entries that existed in the domain, schema, configuration, and optionally the global catalog naming contexts maintain the version number they had at the time of backup.=20 After a non-authoritative restore, the DC is updated using normal replication techniques. That is if the version number of an attribute is less than the version number of the same attribute stored in its = replication partners database (indicating the object has changed since it was last backed up). The object on the restored server will be updated with the changes that were made to that object since the time of the last backup. This ensures an up-to-date version of the database.=20 SYSVOL By restoring the SYSVOL non-authoritatively, the local copy that is held = on the restored DC will be compared with that of its replication partners (using MD5 Checksums). Once the DC reboots, it will contact its = replication partner(s), compare SYSVOL information, and replicate the necessary = changes, bringing it up to date with the other DCs within the domain.=20 This method should be used when there is at least one other functioning = DC in the domain. This is the default SYSVOL restoration method and will = occur automatically if a non-authoritative restore of the Active Directory is carried out.=20 If there is no other functioning DC in the domain, a PRIMARY restore of = the SYSVOL should be done. A primary restore builds a new ntfrs (Windows NT = File Replication Service) database by loading the data present under SYSVOL = on the local DC. This method is the same as non-authoritative except that = the SYSVOL should be marked PRIMARY.=20 ******** ------------------------ thin@xxxxxxxxxxxxx wrote: ------------------------ =09 >Hi, >=20 >Short off topic question.... >=20 >Debugging a customer issue with DC replications.....I noticed that on >one DC the SYSVOL and NETLOGON shares where missing. Checking closer,=20 >the sysvol folder isn't shared, the folder underneath are gone. >=20 >Is there any way beside DCpromo twice to recover it between two cups of >coffee?' The've got two other DC's with valid info >=20 >thanks for any help >=20 >grx >Rob > >******************************************************** >This Week's Sponsor - Emergent Online >EOL's Universal Printer new Features include: >Network Printing, Pagestreaming, 2400 DPI. >No Client Software Required! >http://www.go-eol.com/ >********************************************************** > >For Archives, to Unsubscribe, Subscribe or >set Digest or Vacation mode use the below link:=20 >http://thethin.net/citrixlist.cfm > ******************************************************** This Week's Sponsor - Emergent Online EOL's Universal Printer new Features include: Network Printing, Pagestreaming, 2400 DPI. No Client Software Required! http://www.go-eol.com/ ********************************************************** For Archives, to Unsubscribe, Subscribe or=20 set Digest or Vacation mode use the below link: http://thethin.net/citrixlist.cfm ******************************************************** This Week's Sponsor - Emergent Online EOL's Universal Printer new Features include: Network Printing, Pagestreaming, 2400 DPI. No Client Software Required! http://www.go-eol.com/ ********************************************************** For Archives, to Unsubscribe, Subscribe or=20 set Digest or Vacation mode use the below link: http://thethin.net/citrixlist.cfm ******************************************************** This Week's Sponsor - Emergent Online EOL's Universal Printer new Features include: Network Printing, Pagestreaming, 2400 DPI. No Client Software Required! http://www.go-eol.com/ ********************************************************** For Archives, to Unsubscribe, Subscribe or set Digest or Vacation mode use the below link: http://thethin.net/citrixlist.cfm