Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Enabling security center on domain XP SP2 Workstations

39 views
Skip to first unread message

SoCal Systems Analyst

unread,
Sep 1, 2004, 3:15:06 AM9/1/04
to
Just finished upgrading to SP2 and was puzzled at the lack of functionality
of security center.

Previous post redirected me to

http://download.microsoft.com/download/8/7/9/879a7b46-5ddb-4a82-b64d-64e791b3c9ae/06_CIF_Maintenance.DOC

The document had a incorrect path for the policy setting to change to enable
SP2 Security Center.

To enable it do the following on your SP2 workstation:

START -> RUN -> gpedit.msc

In Group Policy go to Computer Configuration -> Administrative Templates ->
WINDOWS COMPONENTS (not System as documented) -> Security Center ->
Properties -> Enable.

Hope that helps someone.

Bill
--
SoCal Systems Analyst
Leading the fight to bring back Microsoft Olympic Decathalon

SoCal Systems Analyst

unread,
Sep 1, 2004, 4:33:06 AM9/1/04
to
And despite following all of the directions and reading several posts, the
Security Center service still won't start. This is clearly a bug with SP2.
All the dependencies are running without issue but Security Center Service
just won't run!

This sux!

Torgeir Bakken (MVP)

unread,
Sep 1, 2004, 5:09:13 AM9/1/04
to
SoCal Systems Analyst wrote:

> And despite following all of the directions and reading several posts, the
> Security Center service still won't start. This is clearly a bug with SP2.
> All the dependencies are running without issue but Security Center Service
> just won't run!
>
> This sux!

Hi

On the domain computers I have tried it on, I have no problem enabling
Security Center (using the gpedit.msc procedure locally on each
computer). I would say you have a specific problem on your computer.


--
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scriptcenter/default.mspx

SoCal Systems Analyst

unread,
Sep 1, 2004, 1:55:05 PM9/1/04
to
I think you're right. Time to make a phone call...

No One

unread,
Sep 4, 2004, 11:52:32 AM9/4/04
to

I had the same problem. I enabled the "Turn on Security Center"
policy, rebooted and still the Security Center Service would not
start.

Here is how I fixed it.
1. In the registry got to this key...
HKLM\Software\Policies\Microsoft\Windows NT
2. Create a new key named "Security Center" (without the quotes).
3. In this new key create a new DWORD value named
"SecurityCenterInDomain" (without the quotes).
4. Modify the value of this new DWORD value to 1.
5. Start the Security Center service and all should be OK.
6. Start the Security Center control panel applet and you should now
see that the Firewall/Updates/Anti-Virus will now be monitored.

Let me know how this works for you.


SoCal Systems Analyst

unread,
Sep 5, 2004, 2:25:01 AM9/5/04
to
That did the trick! Thanks for taking the time to answer my post and for
helping with this undocumented issue.

SCSA

Torgeir Bakken (MVP)

unread,
Sep 5, 2004, 3:25:10 PM9/5/04
to
SoCal Systems Analyst wrote:

> "No One" wrote:
>
>> I had the same problem. I enabled the "Turn on Security Center"
>> policy, rebooted and still the Security Center Service would
>> not start.
>>
>> Here is how I fixed it.
>> 1. In the registry got to this key...
>> HKLM\Software\Policies\Microsoft\Windows NT
>> 2. Create a new key named "Security Center" (without the quotes).
>> 3. In this new key create a new DWORD value named
>> "SecurityCenterInDomain" (without the quotes).
>> 4. Modify the value of this new DWORD value to 1.
>> 5. Start the Security Center service and all should be OK.
>> 6. Start the Security Center control panel applet and you should now
>> see that the Firewall/Updates/Anti-Virus will now be monitored.
>>
>> Let me know how this works for you.
>
>

> That did the trick! Thanks for taking the time to answer my post
> and for helping with this undocumented issue.

Hi

I don't know if undocumented is the correct word. This registry value
is created automatically for me when I use the gpedit.msc procedure
to enable the Security Center for a domain computer.

It is very odd that this didn't work for you.

dmkolb

unread,
Sep 15, 2004, 4:23:05 AM9/15/04
to

"SoCal Systems Analyst" wrote:

Bill I tried to run gpedit.msc on my laptop at work but I get an error
saying it don't exist. I am on a network at work, does this have to be done
by the administrator elsewhere? I will try to see if this laptop works on my
home network when I get home.

Torgeir Bakken (MVP)

unread,
Sep 15, 2004, 6:20:48 AM9/15/04
to
dmkolb wrote:

> "SoCal Systems Analyst" wrote:
>
>
>> Just finished upgrading to SP2 and was puzzled at the lack of
>> functionality of security center.
>>
>> Previous post redirected me to
>>
>>http://download.microsoft.com/download/8/7/9/879a7b46-5ddb-4a82-b64d-64e791b3c9ae/06_CIF_Maintenance.DOC
>>
>> The document had a incorrect path for the policy setting to change
>> to enable SP2 Security Center.
>>
>> To enable it do the following on your SP2 workstation:
>>
>> START -> RUN -> gpedit.msc
>>
>> In Group Policy go to Computer Configuration -> Administrative
>> Templates ->WINDOWS COMPONENTS (not System as documented) ->
>> Security Center -> Properties -> Enable.
>>
>>Hope that helps someone.
>
>

> Bill I tried to run gpedit.msc on my laptop at work but I get
> an error saying it don't exist. I am on a network at work, does
> this have to be done by the administrator elsewhere? I will try
> to see if this laptop works on my home network when I get home.

Hi

If this is Windows XP Home, it will not work (because it does not
have gpedit.msc).

If this is Windows XP Pro, it should have worked for you directly,
this does not need to be done by the administrator elsewhere.

If you have WinXP Pro:

That it does not start could mean that you have a problem with
your path definition. Run the FIXPATH.exe program available here
(inside FIXPATH.zip) to fix that (you need to have local
administrator rights though):

http://home.comcast.net/~stewartb/cmdprompt.html#6

Reboot after running the exe file, and try yo run gpedit.msc again.

dmkolb

unread,
Sep 16, 2004, 12:05:06 PM9/16/04
to

"Torgeir Bakken (MVP)" wrote:

torgeir
It is the home edition, so does this part of the upgrade not work for this
version? I tried the work around listed in another post, and that didn't work
either. So is this a useless part of the upgrade for us Home users?

Torgeir Bakken (MVP)

unread,
Sep 16, 2004, 1:04:36 PM9/16/04
to
dmkolb wrote:

> torgeir
> It is the home edition, so does this part of the upgrade not work
> for this version? I tried the work around listed in another post,
> and that didn't work either. So is this a useless part of the
> upgrade for us Home users?

Hi

I'm not sure what your problem is. Do you want to enable or disable
the Security Center on your WinXP Home computer?

dmkolb

unread,
Sep 17, 2004, 11:15:02 PM9/17/04
to

"Torgeir Bakken (MVP)" wrote:

Yes I want to enable it, (isn't this a good thing to have on?) But for some
reason it won't start. Also since I've updated my computer has slowed way
down when using Excel to open a file on the server. When I look in Task
Manager to see what is taking so long the program Spoolsv.exe is what's
working. Why is this a problem with Excel, when it wasn't before?
Thanks for your help.

Torgeir Bakken (MVP)

unread,
Sep 18, 2004, 1:21:29 PM9/18/04
to
dmkolb wrote:

> "Torgeir Bakken (MVP)" wrote:
>
>>I'm not sure what your problem is. Do you want to enable or disable
>>the Security Center on your WinXP Home computer?
>>
>

> Yes I want to enable it, (isn't this a good thing to have on?) But for some
> reason it won't start. Also since I've updated my computer has slowed way
> down when using Excel to open a file on the server. When I look in Task
> Manager to see what is taking so long the program Spoolsv.exe is what's
> working. Why is this a problem with Excel, when it wasn't before?
> Thanks for your help.

Hi

Yes, it is a good thing to have running (but not essential).
Anyway, on a WinXP Home computer, it should just default start up
and run after a SP2 installation, so I guess something have gone
wrong with your installation regarding the Security Center (SC).

1)
How do you try to start the Security Center?
What messages do you get then (if any)?


2)
Check the service that it is enabled:

Start/Run --> services.msc

Find "Security Center" in the list and double click on it.

If the Startup type is not set to Automatic, change it to Automatic.

Can you start/stop the service with the Start/Stop buttons?

Go into the Dependencies tab and check that everything looks good
there. SC is dependent on that the "Remote Procedure Call" (RPC)
and "Windows Management Instrumentation" (WMI) services are
running. Check the status of those services.

dmkolb

unread,
Sep 19, 2004, 12:49:02 AM9/19/04
to
> 1)
How do you try to start the Security Center?
What messages do you get then (if any)?

I attempt to start it from either Start/Programs/Accesories or from the
Control Panel and I get "The Security Service is unavailable because the
service isn't started or was stopped"

2)
Check the service that it is enabled:

Start/Run --> services.msc

Find "Security Center" in the list and double click on it.

If the Startup type is not set to Automatic, change it to Automatic.

Can you start/stop the service with the Start/Stop buttons?

Go into the Dependencies tab and check that everything looks good
there. SC is dependent on that the "Remote Procedure Call" (RPC)
and "Windows Management Instrumentation" (WMI) services are
running. Check the status of those services.

I tried this also and heres what I get:
Could not start Security Center on Local Computer.
Error 1068: The dependency Service or group failed to start.

RPC does start; WMI gives same as above.
when I try to open depencies I get Error Win32: The dependency service or
group failed to start!
Argh!

Torgeir Bakken (MVP)

unread,
Sep 19, 2004, 1:33:34 PM9/19/04
to
dmkolb wrote:

Hi

See if the tip from Karl B/Melvin Salazar works for you:

<quote>

From: "Karl B" <ka...@gfield.org.uk>
Subject: Possible solution to the windows update 0x800A0046 problem
Date: Sun, 30 May 2004 12:03:39 +0100
Newsgroups: microsoft.private.xpsp2.general

Firstly, I take no credit for this I was going though the network
newsgroup because my dialup network settings had vanished and a guy
named Melvin Salazar suggested the following which WORKED!

'You can also try doing the following, it worked for me:

Go to Services under the Administrative Tools folder.

Notice that the logon account is set to a NT/User account under the RPC
(remote procedure call) service. Change it to Local System account,
under the Logon tab, and restart the computer. Many of these services
depend on the RPC, but there was an error when it came to configuring
this paticular service.'

Now once I made these changes I was able to get my network icons back
as well as use Windows Update.

Thanks
Karl

</quote>

dmkolb

unread,
Sep 19, 2004, 11:43:02 PM9/19/04
to

"Torgeir Bakken (MVP)" wrote:


Nope didn't work either. Thanks for bearing with me thought. anybody else go
this problem?
>

Torgeir Bakken (MVP)

unread,
Sep 20, 2004, 5:08:27 AM9/20/04
to
dmkolb wrote:

> Nope didn't work either. Thanks for bearing with me thought.
> anybody else go this problem?

Hi

I'm out of ideas here now. I have not heard about this problem on
WinXP Home before either.

anon...@discussions.microsoft.com

unread,
Sep 21, 2004, 9:31:05 AM9/21/04
to

I am seeing this problem. Two notes of interest.

1. I do not think my install completed successfully
(I was installing from the CD). After the restart,
the system froze for a very long period. I finally
gave up and power cycled and it (seemingly) came
up ok. It was only after playing for a while that
I noticed Security Center was not working. I tried
the suggestions from this thread without success.

2. When I attempt to start SC from services.msc, it
fails with a message about not being able to access
a module (I do not have the system in front of me,
so I cannot quote the exact error message). I think
the error code was #126.

3. RPC looked ok. I changed the logon as suggested
but that did not solve the problem.

>.
>

jack

unread,
Sep 21, 2004, 11:56:49 AM9/21/04
to

I should have mentioned in this post that I am currently at
a loss as to how to fix this problem. SP2 has clearly not
installed correctly (e.g. Security Manager is not
functional) but OTOH most functinality seems ok and the
system implied that installation was successful.

Should I uninstall SP2? Are there any suggestions for
fixing the aforementioned problem with Security Manager/

j

>.
>

0 new messages