18 February 2015

SCCM 2012 R2 Client Uninstalls after Reboot

I encountered an issue with SCCM 2012 R2 when deploying the client to systems that were being upgraded from SCCM 2007. What would happen was that I pushed the client to the system through the console using the Install Client option. The client cleanly uninstalled the 2007 client and installed the 2012 client with no issues. Upon the first reboot of the system, the client would be completely uninstalled. The logs showed little information. The next thing I did was to manually install the client from a command line thinking there might be something going on when the server was trying to administer the installation. The same thing happened. The only option I could think of was to delete the computer from sccm and then manually reinstall the client. This worked and the client remained installed on the system.

Related Posts:

  • SCCM 2012 R2 Client Uninstalls after Reboot I encountered an issue with SCCM 2012 R2 when deploying the client to systems that were being upgraded from SCCM 2007. What would happen was that I pushed the client to the system through the console using the Install Client… Read More
  • Microsoft Office Updater One of the things that has annoyed me in the past is having to keep the Microsoft Office Updates folder up-to-date with the latest .MSP files. The reason I bother with keeping the Updates folder up-to-date is because it spe… Read More
  • SCCM: Package not updating on the distribution points You have made changes to your installation package and it does not update on the distribution points, even after validating and redistributing. I ran into this issue and could not figure out why it was doing this. I ended up… Read More
  • Running Programs as an Application Installation in SCCM 2012 Recently, I had to deploy an application, IntApp, with minimal intrusion and no reboots. Part of the process was to restart the application after a successful installation. The crux was that the application has to run und… Read More
  • Deploying enormous packages across a WAN As many of you might know, deploying huge packages through SCCM can be a challenge. The first question you might ask is, define enormous. IMO, anything over the default 5GB client cache size is enormous. Working in the archi… Read More

0 comments:

Post a Comment