Application Install Hang during OSD

[Schikitar]

Hi all,

 

I have an error that has plagued me since, I think, upgrading to SCCM 2012 R2. I have a handful of OSD's which I have setup and generally, they all exhibit the same issue at seemingly random times. I could have multiple machines on my bench all using the same OSD and a couple of them will hang during the installation of applications. So, it installs the Windows image, sets up the CCM client, reboots and finishes the client install and then starts installing applications. When it hits about the third or fourth application it just sits there and does nothing for as long as the machine stays on (no error).

 

It seems to be something that happens after a fixed amount of time (not sure how long), probably ~10 minutes after the last reboot. It makes no difference how I order the apps to install. I've sorted the log list by date and time to try and find an error somewhere but I can't see anything. The really frustrating thing is, if I have a machine that is failing it will usually keep failing repetitively but then suddenly it might start working and completed the TS all the way through.

 

Can anyone give me any advice as to what logs I should keep a closer eye on (client/server) or if anyone has heard of anything similar. It's really frustrating when you have hundreds of machines to do!

 

Sorry if I'm a bit light on info, I'm not sure what to provide as I'm still learning!

 

Cheers!

[Schikitar]

Attached are all the log files from the client...

_LOGS.zip

[rddvls1999]

Schikitar,

 

The only time I've seen the OSD hang like that is when the app that's being installed is waiting for a user response. Is it the same app that's hanging the process, or different ones? Have you tried enabling F8 support and viewing the smsts.log file in real time (speaking of that, it's missing in the logs you posted). Another thing to do would be to try installing the app in question as system on a fully functional system to see what the behavior is (does it install successfully or does it hang).

[giftedwon]

is your DP local or accross a WAN. It can be a bandwidth issue.

[Schikitar]

Hi Guys, apologies for the late reply, I had kinda given up hope that no one would respond due to this being a bit of an odd issue!

 

rddvls1999, normally I would agree, however, I have tried changing the order of the application installs and it seems to be a problem that trikes after a certain amount of time has passed since the last reboot (after the ccm client install), it's not stuck on a particular application. Also, as I mentioned, it might hang on the 1st, 2nd, 3rd attempts (or more) but then on the next attempt goes through without issue with all applications installed. When it happens it definitely seems to be 'waiting' for something, or after that fixed time another process is, or isn't, happening in the background interrupting the whole OSD process (ccm client policy processing maybe??). I will try and capture the smsts.log, didn't think to view it in realtime, will also try that...

 

giftedwon, no, not across a WAN, clients are connected via 1gb Ethernet.

 

This is still an ongoing and intermittent issue, usually happening at the most inconvenient times (like when reimaging a senior staff members machine, gah)!

[rddvls1999]

Schikitar,

 

The smsts.log file should be present on a machine, even if it failed the osd. Have you tried enabling f8 support? If you have, you could try launching task manager during the osd to see if you can see any errant processes that may be causing the issue.

 

Please post all the logs from the ccm\logs directory from the next failed deployment. Also, have you looked at the reports from a machine that failed? Does that give any clues as to the cause?

 

Paul

[rddvls1999]

Also check the root of the c: drive for a folder called smstslog (I believe). There may be some logs left in that directory that are not being copied to the ccm\logs directory in the event of a failed deployment.

[Peter33]

You should check the ciagent.log, cidownloader.lod and cistore.log on your client while it is in this state. Enable F8 command line support as mentioned and deploy cmtrace.exe as normal package as one of your first steps after the "setup config manager" step in your task sequnce, to have a proper log file viewer.

The client is most likely busy with sorting out the policies for your applications. The 3 log files will tell you if that's the case.

You also might want to cleanup the revision history of your applications, to reduce the number of policies that have to be processed. Policy processing is a massive overhead regarding the application model.

[Schikitar]

Hi guys,

 

Had a machine do this today that we were imaging using PXE (also have another machine that is skipping some app installs, that's using TS media). First time through it imaged but just seemed to skip a bunch of applications (Office and a few others), so we kicked it off again and second time round it hung sometime after it started installing the second application in the list (see attached image of the TS). I did find the smsts.log file this time, it was as suggested in C:\_SMSTaskSequence\Logs - I have attached all the log files I could find.

 

Appreciate your assistance, I've got other problems with my SCCM install as well, I figure I should mention it, but I have packages stuck in my distmgr queue which is also driving me crazy (have separately attached that, ignore if not relevant). About to give up on SCCM, it's a full time job for me at the moment and I can't afford the amount of time it sucks out of me, I have too many other things to deal with and my boss is getting quite shirty!

 

Cheers!

logs.zip

distmgr.log

[rddvls1999]

in looking at the logs (ccmexec.log & the smsts.log in the ccm folder), I think that the second app (PaperCut MF Client) is invoking a reboot outside of SCCM's control. Have a look in the NT event logs to see if you see a reboot being called around 10:53am (client time). Perhaps you can place a "restart computer" step in between the application installs until you can figure out which one(s) require a reboot and control it.

 

From SMSTS.log:

 

Setting TSEnv variable 'SMSTSInstallApplicationJobID__ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/Application_235b8c8d-16fe-4880-9bca-e6023045199e'='{9B5A9551-DF84-4C4D-A00D-A9C15963E194}' InstallApplication 8/21/2014 10:53:00 AM 2248 (0x08C8)

Waiting for installation job to complete.. InstallApplication 8/21/2014 10:53:00 AM 2248 (0x08C8)

From CCMEXEC.log:

Notifying endpoint 'DCMAgent' of __InstanceCreationEvent settings change on object CCM_ApplicationCIAssignment.AssignmentID="DEP-LCG2004E-ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/Application_235b8c8d-16fe-4880-9bca-e6023045199e" for user 'S-1-5-18'. CCMEXEC 8/21/2014 10:52:58 AM 1972 (0x07B4)

Notifying endpoint 'CIStore' of __InstanceCreationEvent settings change on object CCM_CIVersionInfo.ModelName="ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/Application_235b8c8d-16fe-4880-9bca-e6023045199e",Version="3" for user 'S-1-5-18'. CCMEXEC 8/21/2014 10:52:58 AM 1972 (0x07B4)

Notifying endpoint 'CIStore' of __InstanceCreationEvent settings change on object CCM_CIVersionInfo.ModelName="ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_6f3ab019-198d-41a8-8f04-cf1fc9a7f5e8",Version="1" for user 'S-1-5-18'. CCMEXEC 8/21/2014 10:52:58 AM 1972 (0x07B4)

Notifying endpoint 'CIStore' of __InstanceCreationEvent settings change on object CCM_CIVersionInfo.ModelName="ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/RequiredApplication_235b8c8d-16fe-4880-9bca-e6023045199e",Version="3" for user 'S-1-5-18'. CCMEXEC 8/21/2014 10:52:58 AM 1972 (0x07B4)

Notifying endpoint 'PolicyAgent_PolicyEvaluator' of __AggregateEvent settings change on object for user 'S-1-5-18'. CCMEXEC 8/21/2014 10:52:59 AM 1032 (0x0408)

WM_QUIT received in the main message loop. CcmExec 8/21/2014 10:53:19 AM 1536 (0x0600)

Shutting down CCMEXEC... CcmExec 8/21/2014 10:53:19 AM 1536 (0x0600)

BEGIN ExecuteSystemTasks('PreShutdown') CcmExec 8/21/2014 10:53:19 AM 1532 (0x05FC)

Using system task exclusion list 'SchedulerStartup;SchedulerShutdown;SchedulerLogon;SchedulerLogoff;ClientRegistrationStartup'. CcmExec 8/21/2014 10:53:19 AM 1532 (0x05FC)

Invoking system task 'StatusAgentShutdown'. CcmExec 8/21/2014 10:53:20 AM 2672 (0x0A70)

Invoking system task 'PolicyEvaluator_PreShutdown' via ICcmSystemTask2 interface. CcmExec 8/21/2014 10:53:20 AM 2672 (0x0A70)

Invoking system task 'MtcShutdown'. CcmExec 8/21/2014 10:53:20 AM 2672 (0x0A70)

END ExecuteSystemTasks('PreShutdown') CcmExec 8/21/2014 10:53:20 AM 1532 (0x05FC)

BEGIN ExecuteSystemTasks('Shutdown') CcmExec 8/21/2014 10:53:20 AM 2672 (0x0A70)