Re: revert to default domain policy

Hello MartyBorg,

Easiest way for this is using the tools from MS:
http://technet2.microsoft.com/windowsserver/en/library/48872034-1907-4149-b6aa-9788d38209d21033.mspx?mfr=true

It is included and via command line available

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

Thanks for the reply, I should have mentioned that I am running Server
2003. The link states that it is specifically for 2000. But I already
know how to revert. My question is;

What are the consequences of copying the Default policies, reverting,
and then switching the names so I continue running with the current
default policies, while I analyse the "default" default policies?

Is there an easier way to accomplish this?

"Meinolf Weber" wrote:

Hello MartyBorg,

Here is what you need:
http://www.microsoft.com/downloads/details.aspx?FamilyID=b5b685ae-b7d
d-4bb5-ab2a-976d6873129d&displaylang=en
Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
I have inherited a network that was run by 5 different Net Admins in
the last
year.
There are many changes in the default domain policy, and I suspect
that it
may be causing problems with my (60+) servers.
I want to revert to the default policy, for both the domain
controllers, and member servers, by moving the servers into their
own
OU, denying any policys to them, and applying only the default
domain
controller policy policys to the domain controllers, and default
domain policy to the member servers to establish a baseline.
My plan is to copy the current default policies to a new name, run
the revert process, and quickly rename new default policies to a new
name, and rename the saved copies back to the default names. I hope
to be able to evaluate the differences, and create GPO's that
address what I need to change, apply them to the user OU's, while
being able to apply the reverted copies to the server and domain
controller OU's.

Does this seem feasible?
Am I missing something?
Is there an easier / safer way?
I am trying not to impact the 500 users that may/or may not boot
during this process.


.

Relevant Pages

  • Re: Denying access to a server
    ... You could configure an ipsec filtering policy on those servers. ... policies use rules that use permit and block filter actions. ...
    (microsoft.public.win2000.security)
  • Re: revert to default domain policy
    ... I know how to revert the policies. ... There are many changes in the default domain policy, ... may be causing problems with my servers. ...
    (microsoft.public.windows.group_policy)
  • Re: revert to default domain policy
    ... There are many changes in the default domain policy, ... may be causing problems with my servers. ... I want to revert to the default policy, ... controller policy policys to the domain controllers, ...
    (microsoft.public.windows.group_policy)
  • Re: revert to default domain policy
    ... policies, while I analyse the "default" default policies? ... There are many changes in the default domain policy, ... may be causing problems with my servers. ... I want to revert to the default policy, ...
    (microsoft.public.windows.group_policy)
  • Re: Group Policy on Registry Level
    ... redo them after I know the servers are stable. ... First of all, you should try to find out, which policies are causing your trouble. ... Try to deactivate the policy with the GPMC. ... You have to run exchange setup with /domainprep after you recreate your default policies or your exchangeserver will stop working. ...
    (microsoft.public.windows.group_policy)