Re: Broken Domain
anonymous_at_discussions.microsoft.com
Date: 07/14/04
- Next message: anonymous_at_discussions.microsoft.com: "Re: Broken Domain"
- Previous message: anonymous_at_discussions.microsoft.com: "Re: Broken Domain"
- In reply to: Tim Springston [MSFT]: "Re: Broken Domain"
- Next in thread: Herb Martin: "Re: Broken Domain"
- Reply: Herb Martin: "Re: Broken Domain"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 14 Jul 2004 10:38:11 -0700
We did manage to get the SYSVOL restored but you are right
in that the Default Group Policies are messed up. They
exist but we can not edit them. I found a copy of
recreatedefpol.exe and it restored them. Thanks for that.
I need to reboot this weekend and I hope I'll be able to
add a second DC after that.
Thanks again.
>-----Original Message-----
>Hi Rob-
>
>If the contents of the SYSVOL are gone, the best option
is to restore from a
>system state backup from when they were present, or
simply a restore of that
>directory. Or a GPMC backup of your policies.
>
>If no backup is available, there is are tools to recreate
the default
>policies. This will not recreate any GPOs created by you
or your team; it
>will only recreate those which would be present by
default.
>
>In Windows 2000 there is a tool called
RECREATEDEFPOL.EXE to do this. It
>is available from Microsoft PSS
(http://www.microsoft.com/support). You
>should not be charged for the call if all you want is
that file.
>
>For Windows Server 2003 domains we include a tool called
DCGPOFIX.EXE
>(installed by default).
>
>
>C:\Documents and Settings\Administrator>dcgpofix /?
>
>Microsoft(R) Windows(R) Operating System Default Group
Policy Restore
>Utility v5.1
>
>Copyright (C) Microsoft Corporation. 1981-2003
>
>Description: Recreates the Default Group Policy Objects
(GPOs) for a domain
>
>Syntax: DcGPOFix [/ignoreschema] [/Target: Domain | DC |
BOTH]
>
>/target: {Domain | DC | BOTH}
>Optional. Specifies the GPO to be restored -- the
Default Domain Policy
>GPO, th
>e Default Domain Controllers Policy GPO, or both.
>
>/ignoreschema:
>Optional. Use this switch to have this tool ignore the
schema version of the
>Act
>ive Directory. Otherwise this tool will only work on the
same schema
>version as
> the Windows version in which the tool was shipped.
>
>Please repost if you have any additional questions or
concerns.
>
>--
>Tim Springston
>Microsoft Corporation
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>"Rob Milman" <rmilman@graycon.com> wrote in message
>news:2c47a01c46924$aa0c52d0$a401280a@phx.gbl...
>> We had a rogue administrator, who is no longer employed
>> with us, do something really stupid. He deleted the
Sysvol
>> folders on all of our DC's. It tooks us a while, but we
>> were able to restore most functionality to our domain.
>> However, some things are still broken. We are unable to
>> add additional domain controllers or setup trusts
between
>> a new domain. Is there any troubleshooting or other
>> suggestions that can be made for us to fix this busted
>> domain? Or should we admit defeat and just rebuild from
>> scratch?
>>
>> Thanks in advance for your help.
>>
>> Rob Milman
>
>
>.
>
- Next message: anonymous_at_discussions.microsoft.com: "Re: Broken Domain"
- Previous message: anonymous_at_discussions.microsoft.com: "Re: Broken Domain"
- In reply to: Tim Springston [MSFT]: "Re: Broken Domain"
- Next in thread: Herb Martin: "Re: Broken Domain"
- Reply: Herb Martin: "Re: Broken Domain"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
