Clear the database before importing

[Graham Turner]

am experiencing issues of refresh of service startup that is controlled by a
security template imported from the file system using GPO editor.

ie we have imported a security template into a GPO linked to the Domain
Controllers container, updated the file (modifying the parameter controlling
the startup type to automatic from disabled).

when this file is reimported we still get the service configured as disabled

suggests that the previously imported value is not being refreshed on the
subsequent import of the template file settings;

this goes against observed behaviour say wrt to the update of the registry
values that are set by the security template file - these are being updated
correctly

looks like the "clear the database before importing" is a way to go but just
wanted to understand what exactly this check box does

it would seem to indicate that it clears all the security values that are in
the GPO before proceeding - ???

quite happy to proceed along these lines but why is it that registry values
settings are updated and not service startup values ??

GT

 

[Nick Finco [MSFT]]

You should see the settings from the imported template take precedence over
the settings that are currently in the GPO. Verify that the template you
are importing still has the service settings defined. What SP of Win2k are
you running?

When you do an import without the "clear the database before importing"
option checked, you will merge the settings from the template being imported
into the GPO. The new settings will take precedence but any old settings
will remain in the GPO. When you select the option, the settings in the GPO
will be cleared and ONLY the settings contained in the imported template
will exist in the GPO.

N

 

[Graham Turner]

Nick, thanks for the post reply.

the DC's are running w2k / sp3

am coming round to it being something a bit more involved and not related to
the application of the settings in the template .

the issue that this is all about is the intermittent failure of the spooler
service.

have thought this was due to somehow the startup value being incorrectly
defined by the security template as disabled which somehow was causing the
spooler to fail .

the reported behaviour is that the computer management applet reports the
service startup as disabled when in fact the CCS registry value is 2
(correct).

unless you have any known info on this, will now focus on why this spooler
is failing on another newsgroup - perhaps driver issues as the print servers
are upgraded from Windows NT4 to w2k ??

GT