Sysvol目录共享問題

lou

我把Sysvol目录的共享去除了,現在組策略不可訪問,但我現在不知道這個目錄的共享權限設置,help me!

frankpro

How to Rebuild SYSVOL and Its Content in a Domain             \r\n------------------------------------------------------------------------------\r\nThe information in this article applies to:\r\n\r\n - Microsoft Windows 2000 Server, versions SP1, SP2 \r\n - Microsoft Windows 2000 Advanced Server, versions SP1, SP2 \r\n-------------------------------------------------------------------------------\r\n\r\nIMPORTANT: This article contains information about modifying the registry. Before you \r\nmodify the registry, make sure to back it up and make sure that you understand how to restore \r\nthe registry if a problem occurs. For information about how to back up, restore, and edit the \r\nregistry, click the following article number to view the article in the Microsoft Knowledge Base:\r\n\r\n   Q256986 Description of the Microsoft Windows Registry\r\n\r\nSUMMARY\r\n=======\r\n\r\nThe article describes how to use the 0xD2 and 0xD4 burflags to rebuild the File\r\nReplication service (FRS) database and System Volume (SYSVOL) content. This\r\narticle addresses a scenario in which either every SYSVOL or every FRS JET\r\ndatabase in the domain is corrupted, and your only option is to rebuild the FRS\r\ndatabase and SYSVOL content.\r\n\r\nIf the problems with FRS are due to topological or environmental problems (for\r\nexample, too many downstream partners, excessive changes on the replicated\r\nfolders, and so on), if you rebuild SYSVOL, the resolution is only temporary.\r\nYou must understand and address the root cause of this problem. If you do not,\r\nproblems that led you to rebuild SYSVOL in the first place may recur.\r\n\r\nNOTE: It is recommended that you use the procedure that is described in this\r\narticle as a last resort to restore a domain\'s SYSVOL and its contents. You\r\nshould only use this procedure if you cannot repair FRS, or if time is a\r\ncritical factor.\r\n\r\nMORE INFORMATION\r\n================\r\n\r\nWARNING: If you use Registry Editor incorrectly, you may cause serious problems\r\nthat may require you to reinstall your operating system. Microsoft cannot\r\nguarantee that you can solve problems that result from using Registry Editor\r\nincorrectly. Use Registry Editor at your own risk.\r\n\r\nFRS is a multiple-threaded, multiple-master replication engine. Windows\r\n2000-based domain controllers and servers use FRS to replicate system policies\r\nand logon scripts for client computers that are running Windows 2000 and\r\nearlier. FRS can also replicate content between Windows 2000-based servers that\r\nhost the same fault-tolerant Distributed File System (DFS) roots or child node\r\nreplicas.\r\n\r\nTo rebuild SYSVOL, you must have Windows 2000 Service Pack 2 (SP2) or the FRS\r\nPost-Service Pack 1 (SP1) update installed on all domain controllers.\r\n\r\nFor additional information about the changes to FRS in Windows 2000 SP2, click\r\nthe article number below to view the article in the Microsoft Knowledge Base:\r\n\r\n   Q272567 File Replication Service Improvements in Windows 2000 Service Pack 2\r\n\r\nIt is highly recommended that you install the latest service pack (or FRS update)\r\non all domain controllers.\r\n\r\nFor additional information about the changes to FRS in Service Pack 3 (SP3),\r\nclick the article number below to view the article in the Microsoft Knowledge\r\nBase:\r\n\r\n   Q307319 Changes to the File Replication Service\r\n\r\nHow to Build the FRS Database and SYSVOL Content\r\n------------------------------------------------\r\n\r\nThe following names are used in the procedure described in this section:\r\n\r\n - Domain name: RESKIT.COM\r\n\r\n - Core hub server: Hub1\r\n\r\n - Second hub server: Hub2\r\n\r\n - SYSVOL: C:\\Winnt\\Sysvol\\Sysvol\\Reskit.com\r\n\r\n1. Stop FRS on all domain controllers.\r\n\r\n2. Configure FRS to be non-authoritative for all replica sets on every domain\r\n   controller except Hub1. To do so:\r\n\r\n   a. Start Registry Editor (Regedt32.exe).\r\n\r\n   b. Locate and click the BurFlags value under the following registry key:\r\n\r\n   HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\NtFrs\\Parameters\\Backup/Restore\\Process\r\n   at Startup\r\n\r\n   c. On the Edit menu, click DWORD, type \"D2\" (without the quotation marks),\r\n      and then click OK.\r\n\r\n   d. Quit Registry Editor.\r\n\r\n   After you complete these steps, FRS on this particular computer is instructed\r\n   to reinitialize its database and to overwrite the contents of SYSVOL with\r\n   data from an upstream partner.\r\n\r\n3. Build a good set of policies and scripts, and then place them in a temporary\r\n   folder on a disk drive on Hub1 (the chosen hub domain controller). Make sure\r\n   that the file structure and the files are current and good.\r\n\r\n   To complete this step, check Active Directory to determine which policies\r\n   folders are still good and which contain orphaned data. Policy information is\r\n   located in the Group Policies container. You can use the Active Directory\r\n   Users and Computers snap-in to view this container:\r\n\r\n   a. Start the Active Directory Users and computers snap-in.\r\n\r\n   b. On the View menu, ensure that Advanced is selected.\r\n\r\n   c. Double-click RESKIT.COM, double-click System, and then double-click\r\n      Policies.\r\n\r\n      The right pane lists all of the Group Policy objects (GPOs) in Active\r\n      Directory. If SYSVOL contains a folder name that has a globally unique\r\n      identifier (GUID) that is not listed in this container, that folder\r\n      contains orphaned data and you can deleted it. If Active Directory\r\n      contains a policy for which a folder name that has the same GUID does not\r\n      exist, you can delete that policy setting.\r\n\r\n4. Delete the contents of SYSVOL on Hub1. When you do so, the SYSVOLs on all\r\n   other domain controllers are emptied before the good content is replicated.\r\n\r\n5. Configure Hub1 to be authoritative for the replica set. To do so:\r\n\r\n   a. Start Registry Editor (Regedt32.exe).\r\n\r\n   b. Locate and click the BurFlags value under the following registry key:\r\n\r\n   HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\NtFrs\\Parameters\\Backup/Restore\\Process\r\n   at Startup\r\n\r\n   c. On the Edit menu, click DWORD, type \"D4\" (without the quotation marks),\r\n      and then click OK.\r\n\r\n   d. Quit Registry Editor.\r\n\r\n6. Verify that Hub2 has a direct NTDS connection object from Hub1, and vice\r\n   versa. If either Hub1 or Hub2 does not have the appropriate connection\r\n   objects, create the objects manually.\r\n\r\n7. Start FRS on Hub1.\r\n\r\n8. Start FRS on Hub2.\r\n\r\n9. Verify that Hub2 receives an empty SYSVOL from Hub1.\r\n\r\n10. On Hub1, copy the file structure for the good SYSVOL content from the\r\n   temporary folder to the Sysvol\\Sysvol\\Reskit.com folder.\r\n\r\n   The good content replicates from Hub1 to Hub2. When the replication process\r\n   is completed, Hub2 logs an event ID 13516 message in its FRS event log.\r\n   There are now two domain controllers with good content in SYSVOL.\r\n\r\n11. Start FRS on one domain controller at a time. Make sure that the domain\r\n   controller has an NTDS connection object that is pulling from another domain\r\n   controller whose SYSVOL has already been rebuilt.\r\n\r\nAfter you complete these steps, all domain controllers have correct content in\r\ntheir SYSVOLs and good data in their FRS JET databases. Use HEALTH_CHK to\r\nperiodically monitor the domain controllers to ensure that SYSVOL continues to\r\nreplicate.