Without knowing what settings were in the template, perhaps the easiest way
to clean the machine up would be to join it to the domain, use Group Policy
to deploy basicsv.inf to the server, then, while it is still in the domain
and affected by GP, go in and manually reset the local policy settings.

Laura
----- Original Message -----
From: "None None" <somedays123hotmail.com>
To: <focus-mssecurityfocus.com>
Sent: Thursday, September 20, 2001 4:08 PM
Subject: W2K Security Templates

> Folks,
>
> Has anyone run across this with W2K Security Templates, it does not appear
> to be addressed on MS's site or any readily available documentation:
>
> A Windows 2000 Security template was created on a W2K Advanced server that
> was part of a domain. That template was then applied to a W2K stand alone
> server (not part of a domain). Services on the template were set so that
> some services were DISABLED (telephony for example) and some were set to
> MANUAL, with EVERYONE as the group with security rights assigned (service
> dependencies are not the issue). Now that the template has been applied,
the
> services are not accessible. This means you are not able to start/stop or
> change the default state of the service. Trying to do so simply hangs
> SERVICES.EXE. We tried to apply a new template without specifying anything
> in the services area, no luck. Even a "SECEDIT /configure /DB filename
/CFG
> filename /overwrite" does not work. As the configuration reaches the
> services section it simply hangs and the new template does not get
applied.
>
> Anyone have a clue why we can remove the template and get back to
> configuring the services?
>
> Thanks,
>
> SD
>
> _________________________________________________________________
> Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
>

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]