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. 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 Config Mgr Site Codes is right and the proper management point path is there.
- Houston bisexual chat room
- Free chating with milfs frer
- how to start an internet dating service
- hayden panettiere milo ventimiglia still dating
- Free sex camp winsor ont
- best female dating profiles
- goth dating com
Either way the package has started but hasn't actually finished. 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.
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? It turns out that the reporting is not accurately showing what is going on in the network.
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.
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.
Some clients HAVE installed FEP, but I've only known that by logging on to those manually.