Today we posted guidance on using an existing WSUS server from an Configuration Manager deployment for FCS definition distribution. The complete guidance, Deploying FCS definition updates with a shared System Center Configuration Manager WSUS infrastructure (http://technet.microsoft.com/en-us/library/dd185652.aspx
), can be read on TechNet.
Refer to Supported configurations for using WSUS to distribute Forefront Client Security Definition updates within System Center Configuration Manager 2007 (http://support.microsoft.com/default.aspx/kb/958491) for supported FCS and Configuration Manager shared configurations.
Hello FCS experts – and you know who you are. You are the ones who have figured out the tips and tricks for using FCS, and have found the most interesting and relevant TechNet information about FCS. The TechNet team wants to make it easier for experts like you to share their favorite TechNet articles and links, so they’ve release their v1 of social bookmarking.
And you can use it to share your best or favorite links on TechNet or MSDN with others.
Available in two flavors – TechNet (social.technet.microsoft.com) and MSDN (social.msdn.microsoft.com). Chris Slemp has a bunch of info on how to use this great new tool on his blog (http://blogs.msdn.com/cslemp/archive/2008/09/09/launched-social-bookmarking-v1-on-msdn-and-technet-video.aspx).
A tip: use the tags! It makes the relevant content easier to for others to find based on category…
Today we are pleased to announce the availability of Forefront Client Security Service Pack 1 (SP1).
FCS SP1 adds support for:
Agent protection on Windows Server 2008 – both Server and Core.
Server role support on Windows Server 2008 (server only) for FCS server components.
FCS Enterprise Manager on Windows Server 2008 (server only).
To obtain FCS SP1, first install FCS. After successfully installing FCS, you will be offered SP1 via Microsoft Update. For more information, read the FCS SP1 Release Notes (http://go.microsoft.com/fwlink/?LinkID=126287) or see Microsoft Knowledge Base article 951951 (http://support.microsoft.com/default.aspx/kb/951951)
Did you know that Microsoft has an open source hosting website? Codeplex (www.codeplex.com) is a Microsoft website that hosts customer-driven projects, and allows customer collaboration on these projects.
The cool thing about Codeplex is that it allows YOU, our customers, to share your FCS solutions. There’s a section for Forefront Client Security tools – you can reach it by entering Forefront in the search text box in the upper right of the Codeplex homepage, or go straight there by navigating to http://www.codeplex.com/fcscompete. The full list of available customer-driven tools is on the Releases tab, in the Releases list box on the right hand side.
Yaniv Feldman has posted a solution for updating FCS definitions using MOM 2005 tasks (http://www.codeplex.com/fcscompete/Release/ProjectReleases.aspx?ReleaseId=14225). You can read more about the tool and how to use it on Yaniv’s blog: http://blogs.microsoft.co.il/blogs/yanivf/archive/2008/06/09/forefront-client-security-remote-definitions-update-using-mom-tasks.aspx.
Johan Blom has also contributed a tool to the FCS Codeplex collection. Johan’s contribution sets scan exclusions for Exchange 2007 servers, making it easier to use FCS to protect your Exchange server. Johan’s project can be accessed on Codeplex here: http://www.codeplex.com/fcscompete/Release/ProjectReleases.aspx?ReleaseId=14026. You can read more about the tool and how to use it on Johan’s blog at http://www.msforefront.com/, and looking for the title “Scanning exclusions when running FCS on Exchange 2007 made easy”.
Have you posted an FCS tool to the FCS Codeplex collection? If so, send us an email using the feedback link in this blog to let us know!
The Forefront and System Center teams recognize the importance of enabling customers to take advantage of both Forefront Client Security (FCS) and System Center Configuration Manager in their environments today. This is a request that we have received from the Microsoft field and customers around the world.
FCS and Configuration Manager both rely on Windows Server Update Services (WSUS) as a key part of the overall Microsoft architecture. FCS is optimized for automatic signature distribution via WSUS. Configuration Manager also uses the WSUS server role for key software distribution scenarios. This allows each product to do their own jobs effectively, and helps customers limit the infrastructure it may require for both solutions. Questions have arisen around support for the coexistence of FCS and Configuration Manager in an enterprise, while still leveraging the same WSUS server role. There have been additional questions and feature requests regarding the automated deployment of FCS signature files through the Configuration Manager console, using the Configuration Manager client relationship.
We are in the process of writing a Knowledge Base article which will clarify the scenarios that are supported when using Forefront Client Security and System Center Configuration Manager. At the same time, we are updating the documents which were posted on Codeplex to provide guidance on what customers should do when configuring their environments under the supported scenarios included in the KB article. We are targeting the release of the KB article and prescriptive guidance by the end of August.
We really appreciate your patience while we put together the necessary documentation.
Forefront and System Center Teams