After deploying the FEP 2010 Server, you not be able to see the FEP Policies !!! So yes it can happen.
The cause:
The version of microsoft.configurationmanagement.managementprovider.dll file under <Installation path>\Microsoft Configuration Manager\AdminUI\bin has not been updated from 4.00.6487.2000 to 4.00.6487.2156 after installing the hotfix KB2271736 !!!
The solution :
1. Close the Configuration Manager console.
2. Rename microsoft.configurationmanagement.managementprovider.dll to microsoft.configurationmanagement.managementproviderOLD.dll
3. Reapply the hotfix KB2271736 , a new DLL file will be created
Now you can see the good version of the DLL file and FEP 2010 policies are visible in the Configuration Manager console.
Note also, this problem might appears not only on the FEP server, but also on a remote ConfigMgr console.
Now, Forefront Endpoint Protection (FEP) 2010 RTM version is available on TechNet and MSDN.
Download is expected be available from the volume License site (VLCS) on December 29th.
Forefront Endpoint Protection 2010 is the next version of Forefront Client Security and it builds on System Center Configuration Manager 2007 SP2 R2 or R3.
Windows Storage Server 2008 R2 and SQL Server 2008 with Service Pack 2 are supported on System Center Configuration Manager 2007. Go to this link to see link the announcement.
Today, a new KB2476479 has been published by Microsoft to solve a problem for SU deployment management and ConfigMgr 2007 clients running Windows 7 or Windows 2008. In effect these clients may reboot even though the SU deployment management settings are configured to suppress reboots on all clients. By default the reboot will be scheduled for 3:00am but can occur at other times as well. So, to resolve this issue, we should disable the Automatic Updates policy on the ConfigMgr 2007 client computers.
For additional information go to this link