Clients stuck in Deployment Pending or Locally Removed in SCCM yet FEP is installed
-
Friday, July 29, 2011 5:51 PMI am having an issue where lately I will go look at a machine by remote desktop that is in the Deployment Pending category in SCCM and it has FEP installed and functioning. My logging in to the machine will somehow trigger the machine to then report that it has had FEP locally removed. I followed the advice in this technet article (http://social.technet.microsoft.com/Forums/en-US/FCSNext/thread/ca9656df-a6e8-4d37-a9b6-c260af56d8be) and created an advertisement to the Locally Removed category and now those machines are being returned to the Deployment Pending category. Can someone please let me know how to get these machines into the Deployment Succeeded category where they belong? FEP has never been uninstalled from the machine. Thank you for your help.
John
All Replies
-
Saturday, July 30, 2011 9:21 AM
Hi,
Do the SCCM client on these computer actually work as they should or are they suffering from corrupt WMI? is the computers showing up like Deployment pending actually doing other SCCM client tasks like, inventory, sw installation e.t.c?
It sounds to me that the clients are not reporting back as they should.
Regards,
Jörgen
-- My System Center blog ccmexec.com -- -
Monday, August 01, 2011 6:25 PM
I am not sure how to check that. I am looking through my list of computers that I was working on at the end of last week. So far I found one that is still in Deployment Pending yet FEP is installed. I looked through the execmgr.log file and found this exit code several times as different users have logged in and the advertisement has been triggered.
<![LOG[Execution is complete for program Install. The exit code is 327426, the execution status is Success]LOG]!><time="05:49:35.978+420" date="07-21-2011" component="execmgr" context="" type="1" thread="884" file="execreqmgr.cpp:3908">
I tried to look up the exit code, but I cannot find anything on it through a couple different google searches. This machine has 2 advertisements that are active.
Name Program Package Collection
1) FEP - Deployment Install FEP - Deployment WSUS Enabled
2) Definition Updates Update Definitions FEP - Operations All Systems
I hope this helps to narrow down where the issue might be coming from.
John
-
Monday, August 01, 2011 7:12 PM
Hi,
Check the EppSetup.log master setup log file for the FEP client, it is located in %allusersprofile%\Microsoft\Microsoft Security Client\Support
More FEP installation log files can be found here.. http://technet.microsoft.com/en-us/library/gg477022.aspx
I hope this will give you a better clue to what is wrong.
Regards,
Jörgen
-- My System Center blog ccmexec.com -- -
Wednesday, August 03, 2011 4:40 PM
I looked at this file on the original machine I was using for testing and saw this error in it in the eppsetup.log file:
ERROR 2011/04/27 10:06:43:041 TID:5036 PID:5032
Operation failed: Start WPP logging - Can't complete the Setup Wizard. An error has prevented Setup Wizard from continuing. Please restart your computer and try again. Error code:0x800700A1. The specified path is invalid. [800700A1]I went ahead and uninstalled FEP and the SCCM client and pushed both out from the server. This made the machine go into Deployment Succeeded. I found another machine with this same error today that has FEP installed and updating normally. I have not uninstalled from that machine yet. I am hoping there is another way to fix this.
-
Wednesday, August 10, 2011 5:23 PM
I tried to install the client again on the second machine I found that had FEP installed successfully but was still reporting as Deployment Pending. I selected "Always install (repair or upgrade existing client)", but it made no change. The advertisement that is supposed to run was still not running. The advertisement is set to run at 'logon' and 'always rerun program'. I ended up making the system run the advertisement again by completely uninstalling the SCCM client and pushing it again from the server. After the new installation of the client, the advertisement would run again and complete with the message saying that FEP was already installed. This would then cause the system to move from Deployment Pending to Deployment Succeeded.
Does anyone know why the 'Always install (repair or upgrade existing client)' option is not working? I believe that when the client was first pushed to the machine that it did not fully install correctly for some reason whether that was someone logging out in the middle of the install or the machine restarted or any number of other interruptions. I appreciate all the help so far and any future help.
John
-
Tuesday, May 22, 2012 5:45 PMDid you ever find a workable solution to this problem. I have one very similar. I have clients that move from pending to removed when FEP installs. I hope that I don't have to go into all of them and uninstall the SCCM client to make it work again.
Mike in IT
-
Wednesday, September 05, 2012 5:59 PM
We got most of the machines working correctly with some manual intervention and we left the rest to get fixed as they were either replaced on our lifecycle plan or re-imaged due to a virus or yearly re-imaging cycle (labs). I'm sorry I do not have a solution for you.
John
-
Monday, October 22, 2012 4:35 PMHi Jonh your FEP its the trial version http://social.technet.microsoft.com/Forums/en-US/FCSNext/thread/8b385884-aa2f-4546-8623-50c9e7da7d32/
Givan X
.png)
