<<< Date Index >>>     <<< Thread Index >>>

Re: Security Center and Windows XP clients in domain



The information in your snip is incorrect. Is that content located on a current site? (URL pls).

WF does indeed install by default on domain members, with the default settings allowing file and printer sharing within the scope of the local subnet and remote assistance from anywhere. Of course, you can change this with a custom inf at install, or manage settings enterprise-wide with Group Policy. The Windows Security Center isn't disabled per se-- the service is still set to automatic, though it does not start by default. The monitoring of AV/FW/AU is indeed disabled (in fact, the entire HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Security Center reg key is removed). But you can still configure those items from the WSC.


HTH

T



----- Original Message ----- From: <albatross@xxxxxx>
To: <bugtraq@xxxxxxxxxxxxxxxxx>
Sent: Monday, August 30, 2004 11:27 PM
Subject: Security Center and Windows XP clients in domain






From the Symantec site:



Q: Which Symantec products will the product update apply to?

A: The product update applies to customers who use Symantec Client Security, Symantec AntiVirus Corporate Edition, and Symantec AntiVirus Enterprise Edition if their client systems are not members of a Windows domain. This is because Windows XP Service Pack 2 does not enable the Windows Security Center or the Windows Firewall if it detects that the computer is a member of a Windows domain. It also applies to administrators who choose to enable the Windows Security Client in a domain. Product updates for other Symantec products may be released in the future but none are scheduled at this time.



As stated in the answer if a windows XP client is joining a Domain SP2 won't enable neither the Security Center and Firewall. Does somebody have any mor information about this?



albatross