FEP 2010 client is installed on Windows Server 2008 R2 Core, but no status reports are available from this system. The FEP Computer details report displays:
FEP 2010 is supported on Windows Server 2008 R2 Core edition. However, out of the box you may have noticed that it does not report its status back to ConfigMgr. We all know that status reports are done using the DCM (Desired Configuration Management) component of ConfigMgr.
DCM requires .NET Framework 2.0 and this is not installed out of the box on Windows Server 2008 R2 Core.
You can install .NET 2.0 on your Core server, but only a subset of the .NET components will be available. This is done to minimize the footprint of Windows Server 2008 Core.See the below blog post regarding .NET 2.0 on Windows Server 2008 R2 Core: http://blogs.technet.com/b/server_core/archive/2008/11/25/net-2-0-and-server-core-in-windows-server-2008-r2.aspx That's all great info, but what do you have to do to get DCM working? The above blog already gives you the pointers how to install .NET 2.0. :) For DCM to work however you have to install the 32bit version of .NET 2.0, you can do this by running the below command: Note: You need to reboot the server after installation!
Dism /online /enable-feature /featurename:NetFx2-ServerCore-WOW64 If you're not sure what .NET components are installed, you can run the below command to get an overview: oclist|find /i "netfx"