Client install fails during OSD

Question

Hi,
OS Deployment usually works without any issues for us. Sometimes (like 1 out of 15 deployments) the SCCM client will not install correctly and the system will boot up without any applications. That's okay, we just restart it and it works on the second attempt.
Lately however, I discovered an issue with a certain model (Lenovo R500): The SCCM client configuration now fails every time (tried four times in a row!). It wasn't that bad before...
Here are some answers to questions some of you might probably consider asking. :)
- We are using diskpart /clean at the start of every task sequence
- The system is domain joined before the SCCM client install step
- Jason Sandys ConfigMgrStartup Script (client health GPO) is active
- Client push install is active
- The BIOS is up to date
- These are our setup parameters during OSD: SMSMP=*FQDN* CCMEVALHOUR=12 PATCH="\\*FQDN*\hotfixes\configmgr2012ac-r2-kb3026739-x64.msp"
- I tried installing newer network card drivers during the OSD in case the old drivers suddenly can't handle it any more but that also didn't improve the situation
I thought maybe the GPO or the client push are interfering with the setup while running the OSD, but that also happens if the GPO is disabled. Also, the client push install never interfered with the OSD before and I don't think that it suddenly would.
I zipped and uploaded the ccmsetup.log and client.msi.log to OneDrive, I would really appreciate it if someone could take a look at the logfiles and identify any potential issue that I'm not seeing.
Logfiles: http://1drv.ms/18FTcAH
Thank you!

Answer 1

I just found a solution thanks to another fellow forum member that suggested I make sure that "Client Push" was not enabled.  I too was experiencing intermittent failures in OSD at the "Setup Windows and ConfigMgr" step that did
not make any sense.
After a review of the ccmsetup logs on the OSD machine and ccm.log on the server I was able to see that "Client Push" was beating the TS to installing the client by 4 seconds causing the TS to fail.
Torsten indicated that Client Push and OSD can be problematic.  
OSD Client Patch fails intermittently 
After reviewing your ccmsetup.log I see the same evidence at time stamp 11:40:50 that I saw in my logs indicating that ccmsetup was already running when the TS went to install the client.
An instance of ccmsetup is running as a service. The current instance will be terminated. ccmsetup 2/26/2015 11:40:50 AM 1920 (0x0780)
Installation will be cancelled due to shutdown. Windows Installer will return error code 1602. ccmsetup 2/26/2015 11:40:50 AM 1920 (0x0780)
MSI: Aktion 11:40:50: Rollback. Aktion wird rückgängig gemacht: ccmsetup 2/26/2015 11:40:50 AM 1920 (0x0780)
An instance of ccmsetup is running as a service. The current instance will be terminated. ccmsetup 2/26/2015 11:40:50 AM 1920 (0x0780)
Installation will be cancelled due to shutdown. Windows Installer will return error code 1602. ccmsetup 2/26/2015 11:40:50 AM 1920 (0x0780)
File C:\WINDOWS\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi installation was cancelled (1602) ccmsetup 2/26/2015 11:41:00 AM 1920 (0x0780)
Hi pfitchie,
I unmarked my reply as answer, it happened again and after reading your thread and this reply it all makes sense. I now disabled the Clientpush and will see what happens. Is there a possibility this is only happening if you apply CU4 during the OSD? It never
happened before.