I am having some issues getting FEP 2010 to deploy via SCCM 2007R3. Environment is as follows Server 2008R2 and SQL2008R2 on a single server. I then installed SCCM 2007R3 and was able to add my desktop and a test server to the appropriate collections. Everything appears fne so far, I then installed FEP 2010 on teh same system and installed ok. SUP/WSUS are up and running fine I was able to sync from the Microsoft Servers and it is pulling updates just fine.
I tried two different articles when trying to deploy FEP Clients. In this article http://social.technet.microsoft.com/wiki/contents/articles/how-to-deploy-the-fep-2010-client-via-osd-and-test-deployment.aspx starting at step 20 in the tasks sequences I have no "Install Software" task sequence. So is did my install of SCCM 2007R3 not go as good as I thought?
The second article I tried http://blog-en.netvnext.com/2010/12/deploying-fep-2010-rc-to-client-systems.html#!/2010/12/deploying-fep-2010-rc-to-client-systems.html , I was able to get through all the steps but again nothing installed on my client system. I cannot even see any erros on the client or in SCCM.
I tried looking for a execmgr.log mentioned in other posts but I cannot seem to find it on either the client or SCCM logs folder. Does anyone have any ideas to offer?
2012年3月21日 17:12版主so have you sucessfully installed the client with the Advertisment /Package it creates? Befor you tackel the OSD portion. Is the client downloading the package atleast?
No I have not had any success installing the package? What log do I look in to see if the client is downloading the package?
go thorough this guide
To successfully deploy FEP, your SCCM should have healthy Software distribution and Software update point. i recommend you to first troubleshoot on Software distribution.
- create test collection
- Create a Test package
- Distribute Test package to a distribution point.
- Create a advertiesment which specify the package and test collection. use mandatory assign
- trigger the machine policy cycle on the test client.
- use TRACE to read client log files.
- Read Execmgr.log CcmExec.log and check CAS.log (Downloading the package) for any errors. you can see the progress of the software distribution by these logs.
Post any errors with these logs.
Sorry for the very late reply. we found out that we had installed several things out of order and decided to tear down and start from the begining. It is amazing how much beter things go when you follow the docs.
Thanks Again for your response.
- 已标记为答案 Moiz Rassiwala[MSFT]Microsoft Employee, Moderator 2012年6月11日 23:17