For 32 bit machines
HKEY_LOCAL_MACHINE\SOFTWARE\Mission Critical Software\OnePoint\Configurations\ForefrontClientSecurity\Operations\
Agent\Consolidators
For 64 bit machines
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Mission Critical Software\OnePoint\Configurations\ForefrontClientSecurity\Operations
\Agent\Consolidators
Keys are ‘Consolidator 1 Host’ and ‘Consolidator 1 AD Name’
After installing Microsoft Forefront Client Security on a server, you receive the below error when attempting to deploy a policy
to an OU.
Error:
The policy cannot be deployed
Further details:
Exception has been thrown by the target of an invocation.
Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
This is caused due to the version of Forefront Client Security not being supported on Windows 2008 server. You will not receive the error
on a Windows 2003 server.
BUT there is a fix. Install Forefront service pack 1. I had to install it earlier and it took less then a minute to install. No reboot was required.
For more info see http://support.microsoft.com/kb/951951
To install Forefront Client Security manually with the options for the client machine to contact the MOM Server (managed), run the below command:
Browse to the folder within command prompt to where clientsetup.exe resides.
Type the following – clientsetup.exe /CG ForefrontClientSecurity /MS MOMServerName and press enter
In most cases /CG is ForefrontClientSecurity but may be different depending on what you originally set it to.
Without MOM
To install without MOM so the client is unmanaged, type clientsetup.exe /nomom
To manually download the latest Microsoft Forefront definition, visit the below URL:
http://www.microsoft.com/security/portal/Definitions/ADL.aspx
Subscribe to new tech posts.
We will never send you spam email or forward your details to third parties.
This will close in 0 seconds