Re: Easy way for forced policy
From: Jim Snowdon (j_snowdon@hotmail.com)
Date: 06/06/02
- Next message: Consultant®: "Re: C$ D$ ..."
- Previous message: Ronen: "untrusted domain in certificate"
- In reply to: Ray: "Easy way for forced policy"
- Next in thread: N.P.: "Re: Easy way for forced policy"
- Reply: N.P.: "Re: Easy way for forced policy"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Jim Snowdon" <j_snowdon@hotmail.com> Date: Thu, 6 Jun 2002 15:55:07 +0100
Hi Ray,
I've just started to look at doing this, as we are running a NT domain
backend but win2kpro frontend, we changed the local GPO on the workstations
from default to another setting, then deployed the workstations. we now want
to make some amendmends to the local GPO's on the workstations, i do not
belive that you can do it the way that Ed has suggested, i'm currently
looking at the secedit.exe command, hoping that you can export new settings
and then import into a new machine, somehow scripting it or use SMS to
deploy update.
Regards Jim
"Ray" <rrooy@mexico.com> wrote in message
news:uNa9UZJDCHA.1732@tkmsftngp02...
> Hi there,
>
> I have 100 standalone Win2K Professional (SP2) computers on which I want
to
> put a policy file. Now I only am familiar with the NTPOL from NT 4.0. Who
> can tell me with which application I can make a default policy file and
> where I must copy this file on those 100 standalone Win2K machines ???
>
> Thank you,
>
> Raymond
>
>
- Next message: Consultant®: "Re: C$ D$ ..."
- Previous message: Ronen: "untrusted domain in certificate"
- In reply to: Ray: "Easy way for forced policy"
- Next in thread: N.P.: "Re: Easy way for forced policy"
- Reply: N.P.: "Re: Easy way for forced policy"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]