Friday, October 12, 2012 6:28 PM
I recently installed SCCM Client on all of my workstations. They already had FEP 2010 installed manually by going to the SMSPKGC$ share and running FEPInstall. The clients are from an image and we are using WSUS. I removed the registry keys for SUSClientID and SUSClientValidation and now they are visible in WSUS. But all the clients in FEP are stuck in "Deployment Pending" even though the SCCM client is installed, approved, and is configured correctly.
Monday, October 15, 2012 9:22 AMModerator
Thank you for the post.
1. Have you run sysprep when/after you imaged your clients?
2. FEP is based on SCCM client agent. Please verify if your SCCM client show correctly in SCCM console first.
3. Try to delete some registry keys mentioned in article below.
If there are more inquiries on this issue, please feel free to let us know.
TechNet Community Support
Monday, October 15, 2012 4:06 PM
No they were not Sysprepped after imaging. I tried to delete the keys, but I get "Access is Denied". I am signed on as Administrator, FEP service is stopped.
Wednesday, October 17, 2012 6:17 AMModerator
Friday, October 19, 2012 3:45 PMI have had these computers listed in Deployment Succeeded before. This has only been happening since I went to Rollup 1. I just un-installed and re-installed FEP on one client and it shows as succeeded. This computer was imaged and not Sysprepped.
Friday, October 19, 2012 8:31 PMI modified the default dekstop policy and I applied it to the "FEP Clients" and all it sub-folders. I turn on 2 computers who are listed in "Deployment Pending". After a few minutes, they pull down the new policy, but they are still listed in "Deployment Pending". I can right click on any client in this group, choose "FEP computer details report" and I will get up to date information. So if my server can communicate with the clients, why are they still in "Deployment Pending"? It has nothing to do with Sysprep. I proved that by manually re-installing FEP on a client today. If the SID on that computer was invalid, it would not have shown up in "Deployment Succeeded".