<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://itprosecure.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Forefront Client Security Administration</title><link>http://itprosecure.com/blogs/fcs_administration/default.aspx</link><description /><dc:language>en</dc:language><generator>CommunityServer 2008 SP2 (Build: 31104.93)</generator><item><title>Forefront Client Security: Modifying Database and Environment Variables to Support the DTS Package for Proper Data Storage on a Forefront Client Security SP1 Server</title><link>http://itprosecure.com/blogs/fcs_administration/archive/2009/06/02/forefront-client-security-modifying-the-dts-package-database-variables-for-increased-data-storage-on-a-forefront-client-security-sp1-server.aspx</link><pubDate>Tue, 02 Jun 2009 09:14:00 GMT</pubDate><guid isPermaLink="false">1a239f15-06da-4ba6-a63f-d3ae39b9339d:312</guid><dc:creator>lynn lunik</dc:creator><slash:comments>0</slash:comments><description>Summary: In this Blog entry I review several configuration parameters for the Database and Operating System Environment on a Forefront Client Security SP1 Single Server Topology on Windows 2008 that allow proper data storage for both Short Term Data and Long Term Data transferred by the Nightly Data Transformation Services Scheduled Task....(&lt;a href="http://itprosecure.com/blogs/fcs_administration/archive/2009/06/02/forefront-client-security-modifying-the-dts-package-database-variables-for-increased-data-storage-on-a-forefront-client-security-sp1-server.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://itprosecure.com/aggbug.aspx?PostID=312" width="1" height="1"&gt;</description><category domain="http://itprosecure.com/blogs/fcs_administration/archive/tags/Forefront+Client+Security/default.aspx">Forefront Client Security</category><category domain="http://itprosecure.com/blogs/fcs_administration/archive/tags/Windows+2008/default.aspx">Windows 2008</category><category domain="http://itprosecure.com/blogs/fcs_administration/archive/tags/Security/default.aspx">Security</category></item><item><title>Forefront Client Security: Troubleshooting the MOM 2005 Data Transformation Services (DTS) Package Task on a Forefront Client Security SP1 Server</title><link>http://itprosecure.com/blogs/fcs_administration/archive/2009/05/18/forefront-client-security-troubleshooting-the-mom-2005-data-transformation-services-dts-package-task-on-a-forefront-client-security-sp1-server.aspx</link><pubDate>Mon, 18 May 2009 21:55:00 GMT</pubDate><guid isPermaLink="false">1a239f15-06da-4ba6-a63f-d3ae39b9339d:309</guid><dc:creator>lynn lunik</dc:creator><slash:comments>2</slash:comments><description>In this Blog entry I review troubleshooting methods for the DTS Package Task used by MOM 2005 which is part of Forefront Client Security SP1 running as a Single Server Topology on Windows 2008.  I demonstrate how to use the DTS Package Task, invoked with Switch Parameters from a Command Prompt to ensure the DTS Package Task executes properly.  Additionally, I review the output of a &amp;#39;successful&amp;#39; DTS Package Task for reference, and to ensure the overall health of a Forefront Client Security SP1 configuration running as a Single Server on Windows 2008....(&lt;a href="http://itprosecure.com/blogs/fcs_administration/archive/2009/05/18/forefront-client-security-troubleshooting-the-mom-2005-data-transformation-services-dts-package-task-on-a-forefront-client-security-sp1-server.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://itprosecure.com/aggbug.aspx?PostID=309" width="1" height="1"&gt;</description><category domain="http://itprosecure.com/blogs/fcs_administration/archive/tags/Forefront+Client+Security/default.aspx">Forefront Client Security</category><category domain="http://itprosecure.com/blogs/fcs_administration/archive/tags/Windows+2008/default.aspx">Windows 2008</category><category domain="http://itprosecure.com/blogs/fcs_administration/archive/tags/Security/default.aspx">Security</category></item><item><title>Forefront Client Security: Using a Group Policy Object (GPO) to Harden Service and Registry Key Entries for the Forefront Client Security SP1 Agent on a Windows Vista Enterprise SP1 Workstation</title><link>http://itprosecure.com/blogs/fcs_administration/archive/2009/04/26/forefront-client-security-using-a-group-policy-object-to-harden-service-and-registry-key-entries-for-the-forefront-client-security-sp1-agent-on-a-windows-vista-enterprise-sp1-workstation.aspx</link><pubDate>Sun, 26 Apr 2009 20:40:00 GMT</pubDate><guid isPermaLink="false">1a239f15-06da-4ba6-a63f-d3ae39b9339d:308</guid><dc:creator>lynn lunik</dc:creator><slash:comments>0</slash:comments><description>In this Blog Entry I use a Group Policy Object to modify Security Settings for both Services and Registry Keys critical to Forefront Client Security.  This GPO removes Local Administrator ability to modify the Forefront Client Security Services and Registry Entries while providing the Administrative Capabilities to a separate Domain Global Security Group (DGSG) designated as Forefront Client Security SP1 Agent Administrators. ...(&lt;a href="http://itprosecure.com/blogs/fcs_administration/archive/2009/04/26/forefront-client-security-using-a-group-policy-object-to-harden-service-and-registry-key-entries-for-the-forefront-client-security-sp1-agent-on-a-windows-vista-enterprise-sp1-workstation.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://itprosecure.com/aggbug.aspx?PostID=308" width="1" height="1"&gt;</description><category domain="http://itprosecure.com/blogs/fcs_administration/archive/tags/Forefront+Client+Security/default.aspx">Forefront Client Security</category><category domain="http://itprosecure.com/blogs/fcs_administration/archive/tags/Security/default.aspx">Security</category><category domain="http://itprosecure.com/blogs/fcs_administration/archive/tags/Windows+Vista/default.aspx">Windows Vista</category></item><item><title>Forefront Client Security: Using the Log Files from the Forefront Client Security Agent SP1for Analysis</title><link>http://itprosecure.com/blogs/fcs_administration/archive/2009/04/13/forefront-client-security-using-the-log-files-from-the-forefront-client-security-agent-sp1for-analysis.aspx</link><pubDate>Mon, 13 Apr 2009 07:24:00 GMT</pubDate><guid isPermaLink="false">1a239f15-06da-4ba6-a63f-d3ae39b9339d:307</guid><dc:creator>lynn lunik</dc:creator><slash:comments>0</slash:comments><description>In this Blog entry I review the numerous Log Files useful when Administering the Forefront Client Security SP1 Agent.  Specifically I focus on using the &amp;#39;mpcmdrun.exe -getfiles&amp;#39; Command Utility to generate a number of useful Log Files for further analysis.  The &amp;#39;mpcmdrun.exe&amp;#39; utility is a &amp;#39;Hidden File&amp;#39; and can only be invoked in the User Context of a Local Administrator in the Forefront Client Security SP1 Agent....(&lt;a href="http://itprosecure.com/blogs/fcs_administration/archive/2009/04/13/forefront-client-security-using-the-log-files-from-the-forefront-client-security-agent-sp1for-analysis.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://itprosecure.com/aggbug.aspx?PostID=307" width="1" height="1"&gt;</description><category domain="http://itprosecure.com/blogs/fcs_administration/archive/tags/Forefront+Client+Security/default.aspx">Forefront Client Security</category><category domain="http://itprosecure.com/blogs/fcs_administration/archive/tags/Windows+2008/default.aspx">Windows 2008</category></item><item><title>Forefront Client Security: Deploying the FCS Client Agent in a Corporate Environment to a Target currently running an unmanaged FCS Client Agent</title><link>http://itprosecure.com/blogs/fcs_administration/archive/2009/04/09/forefront-client-security-deploying-the-fcs-client-agent-to-a-target-currently-running-standalone-fcs-client-agent.aspx</link><pubDate>Thu, 09 Apr 2009 19:05:00 GMT</pubDate><guid isPermaLink="false">1a239f15-06da-4ba6-a63f-d3ae39b9339d:306</guid><dc:creator>lynn lunik</dc:creator><slash:comments>0</slash:comments><description>In this Blog entry I have taken a single Target Client Workstation running a Standalone Installation of the Forefront Client Security SP1 Agent, created a new Forefront Client Security Client Policy to manage this Target Client Workstation, pushed out the Client Policy using Group Policy Objects (GPOs), then pushed out the MOM 2005 Agent for Alerting and Reporting to the Target Client Workstation.  In the end, the Target Client Workstation moved from a Standalone Installation of the Forefront Client Security SP1 Agent to a Fully Managed Forefront Client Security SP1 Agent.  Thereby allowing ongoing Support and Management from a single Console....(&lt;a href="http://itprosecure.com/blogs/fcs_administration/archive/2009/04/09/forefront-client-security-deploying-the-fcs-client-agent-to-a-target-currently-running-standalone-fcs-client-agent.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://itprosecure.com/aggbug.aspx?PostID=306" width="1" height="1"&gt;</description><category domain="http://itprosecure.com/blogs/fcs_administration/archive/tags/Forefront+Client+Security/default.aspx">Forefront Client Security</category><category domain="http://itprosecure.com/blogs/fcs_administration/archive/tags/Windows+2008/default.aspx">Windows 2008</category></item></channel></rss>