Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We've recently upgraded from Forefront Endpoint Protection 2007 to 2010 and it now needs SCCM to deploy the clients, so we are using SCCM for the first time and struggling a little bit.

SCCM is fully installed and appears to be working. The clients are XP and have the System Center clients installed on them, but the FEP client are in "pending" - never installing.

If I look at one of the XP Clients and go to "Configuration Manager Properties" from the Control Panel then I can see that the ConfigMgr Site Codes is right and the proper management point path is there.

As this is our first attempt at a SCCM 2007 install we could be missing something really basic. How can I tell why items in "pending" are not installing?


share|improve this question
It turns out that the reporting is not accurately showing what is going on in the network. Some clients HAVE installed FEP, but I've only known that by logging on to those manually. The main problem with the others is that they are unable to properly uninstall Symantec Antivirus first even though FEP is supposed to do it. Manually uninstalling SAV allows FEP to later install, but the reporting part of the server shows only one "deployed" even though there have been a few installed for at least four days. I guess this is now a question regarding SCCM reporting. – Kieran Walsh Jun 9 '11 at 7:41
Many packages don't report status at all until the very end with either a success or failure. It could be that the install is waiting for something else to happen, could be a reboot, could be a pre-req install, could be a pre-req uninstall. Either way the package has started but hasn't actually finished. – GAThrawn Jun 10 '11 at 17:19
Thanks, these machines have been rebooted many times now though and according to Microsoft they think it may be a WMI problem on the clients. – Kieran Walsh Jun 16 '11 at 14:05

There's an overview of deploying the client here

A couple of things to check for any software distribution troubleshooting:

  • Look at the c:\windows\system32\ccm\logs\execmgr.log on the client. This is the log that tracks package installs
  • Are the clients actually in a collection to receive the package?
  • Is the advertisement mandatory? If you just set a start date with no mandatory installation date, the package will not run
share|improve this answer
Thanks for your help on this. I've got a support case open with Microsoft regarding this at the moment and I'll add a comment to the original post to update it. I did not know about the mandatory setting though, so that will be very useful. – Kieran Walsh Jun 9 '11 at 7:40
up vote 0 down vote accepted

In the end this particular problem turned out to be a corruption in the BITS service in IIS. Looking through the whole things as soon as you hit the BITS box an error popped up. The solution was to remove the BITS feature and then reinstall it. All worked fine after that - once we pushed out the deployment again. Cheers for the other answers.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.