Re: Security Center - Control Panel opens on first login...

Hi Steven,

I suppose I misused the word "compromised". I was referring to the
functionality of the components that are monitored by the Security
Center. If I disable the service (wscsvc) then users will no longer
receive notifications re: WU/AU, AV, etc. It would preferable to leave
the Security Center active so users will at least receive a
notification should the *functionality* of one of the monitored
services (AV, WU/AU or WF) be compromised (not necessarily by an
attack... software does occasionally "break"), and a failure on one of
those components does increase exposure. I hope that clears it up...

As for my initial question, i'm still searching. I just don't want
every user seeing the near full screen Security Center control panel
on first login.

On Feb 1, 9:33 pm, "Steven L Umbach" <n...@xxxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:
I don't know the direct answer for your question but Security Center will
not necessarily warn a user if their computer has been compromised. It will
just warn them if the Windows Firewall is not active, they have no AV, etc.
Also if the computer is compromised the attack could easily disable Security
Center anyhow so not seeing it could give a false sense of security.

Steve

"kick" <dafo...@xxxxxxxxx> wrote in message

news:1170264798.496206.133470@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

I'm looking for a means of disabling execution of the Security Center
control panel on the first login for each user post update to SP2. I'm
well versed in controlling the notifications via registry and
disabling the wscsvc service entirely, but that's not what i'm after.
I want the Security Center to remain active so that users will receive
notifications should their PC be compromised for any reason... I just
don't want them seeing the control panel on their first login.

Any thoughts? I've scanned the microsoft.public.windowsxp.* forums and
didn't come up with much...

Thanks.


.

Relevant Pages

  • Re: SSL 2.0
    ... this is the classic tradeoff between compatibility and security. ... by default from Windows 2000 Server to Windows 2003 Server. ... may look at the instructions for disabling SSL3 and SSL3.5 and say ...
    (microsoft.public.inetserver.iis.security)
  • Re: Security Center - Control Panel opens on first login...
    ... functionality of the components that are monitored by the Security ... receive notifications re: WU/AU, AV, etc. ... control panel on the first login for each user post update to SP2. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: lets vote for better security
    ... Liberals and security professionals who occassionally wear a black hat. ... Then MSFT started disabling things by default and a lot of the community ... Since when is an app responsible for the ... :>: default installation and be disable-able by Group Policy. ...
    (microsoft.public.security)
  • Re: Need help with securing a local workstation
    ... I suggest you also change the ntfs permissions ... setting as disabling the command prompt for instance can cause batch files ... components/Windows Explorer to hide and disable drives, ... Depending on your security ...
    (microsoft.public.win2000.group_policy)
  • Re: Core services... ?
    ... Microsoft MVP (Windows Server System: Security) ... affecting end users in our environment. ... decide if it would strengthen our environment by disabling any unnecessary ...
    (microsoft.public.windowsxp.security_admin)