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)

[rddvls1999]

Actually, I was just looking at the AppDiscovery.log, and saw the following:

 

Performing detection of app deployment type VLC(ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_b614fe1d-f1df-428b-909d-54657f77a633, revision 3) for system. AppDiscovery 8/21/2014 10:52:25 AM 2584 (0x0A18)

+++ Application not discovered. [AppDT Id: ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_b614fe1d-f1df-428b-909d-54657f77a633, Revision: 3] AppDiscovery 8/21/2014 10:52:25 AM 2584 (0x0A18)

+++ Did not detect app deployment type VLC(ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_b614fe1d-f1df-428b-909d-54657f77a633, revision 3) for system. AppDiscovery 8/21/2014 10:52:25 AM 2584 (0x0A18)

Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_b614fe1d-f1df-428b-909d-54657f77a633" AND Revision = 3)" AppDiscovery 8/21/2014 10:52:26 AM 2584 (0x0A18)

Performing detection of app deployment type VLC(ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_b614fe1d-f1df-428b-909d-54657f77a633, revision 3) for system. AppDiscovery 8/21/2014 10:52:26 AM 2584 (0x0A18)

+++ Application not discovered. [AppDT Id: ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_b614fe1d-f1df-428b-909d-54657f77a633, Revision: 3] AppDiscovery 8/21/2014 10:52:26 AM 2584 (0x0A18)

+++ Did not detect app deployment type VLC(ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_b614fe1d-f1df-428b-909d-54657f77a633, revision 3) for system. AppDiscovery 8/21/2014 10:52:26 AM 2584 (0x0A18)

ActionType - Install will use Content Id: Content_3d04b904-5578-4764-88b2-e05c8c5838e2 + Content Version: 1 for AppDT "VLC" [scopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_b614fe1d-f1df-428b-909d-54657f77a633], Revision - 3 AppDiscovery 8/21/2014 10:52:26 AM 2584 (0x0A18)

ActionType - Install will use Content Id: Content_3d04b904-5578-4764-88b2-e05c8c5838e2 + Content Version: 1 for AppDT "VLC" [scopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_b614fe1d-f1df-428b-909d-54657f77a633], Revision - 3 AppDiscovery 8/21/2014 10:52:26 AM 2584 (0x0A18)

Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_6f3ab019-198d-41a8-8f04-cf1fc9a7f5e8" AND Revision = 1)" AppDiscovery 8/21/2014 10:52:59 AM 2584 (0x0A18)

Performing detection of app deployment type PaperCut MF Client - Windows Installer (*.msi file)(ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_6f3ab019-198d-41a8-8f04-cf1fc9a7f5e8, revision 1) for system. AppDiscovery 8/21/2014 10:52:59 AM 2584 (0x0A18)

+++ MSI application not discovered [MSI Product Code: {1EF3289E-C805-11E2-8F40-0024E808B313}, MSI Product version: ] AppDiscovery 8/21/2014 10:52:59 AM 2584 (0x0A18)

+++ Did not detect app deployment type PaperCut MF Client - Windows Installer (*.msi file)(ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_6f3ab019-198d-41a8-8f04-cf1fc9a7f5e8, revision 1) for system. AppDiscovery 8/21/2014 10:52:59 AM 2584 (0x0A18)

Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_6f3ab019-198d-41a8-8f04-cf1fc9a7f5e8" AND Revision = 1)" AppDiscovery 8/21/2014 10:53:00 AM 2584 (0x0A18)

Performing detection of app deployment type PaperCut MF Client - Windows Installer (*.msi file)(ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_6f3ab019-198d-41a8-8f04-cf1fc9a7f5e8, revision 1) for system. AppDiscovery 8/21/2014 10:53:00 AM 2584 (0x0A18)

+++ MSI application not discovered [MSI Product Code: {1EF3289E-C805-11E2-8F40-0024E808B313}, MSI Product version: ] AppDiscovery 8/21/2014 10:53:00 AM 2584 (0x0A18)

+++ Did not detect app deployment type PaperCut MF Client - Windows Installer (*.msi file)(ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_6f3ab019-198d-41a8-8f04-cf1fc9a7f5e8, revision 1) for system. AppDiscovery 8/21/2014 10:53:00 AM 2584 (0x0A18)

ActionType - Install will use Content Id: Content_23c52018-ad4a-40de-8b22-e904fcfeb8d7 + Content Version: 1 for AppDT "PaperCut MF Client - Windows Installer (*.msi file)" [scopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_6f3ab019-198d-41a8-8f04-cf1fc9a7f5e8], Revision - 1 AppDiscovery 8/21/2014 10:53:00 AM 2584 (0x0A18)

ActionType - Install will use Content Id: Content_23c52018-ad4a-40de-8b22-e904fcfeb8d7 + Content Version: 1 for AppDT "PaperCut MF Client - Windows Installer (*.msi file)" [scopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_6f3ab019-198d-41a8-8f04-cf1fc9a7f5e8], Revision - 1 AppDiscovery 8/21/2014 10:53:00 AM 2584 (0x0A18)

You may want to also check your "PaperCut MF Client" package and make sure that the source files are present.

[Schikitar]

Hi rddvls1999,

 

Well it's been a few days but I have had a breakthrough, of sorts. Infact, the breakthrough may have me on the path of resolving three major issues which has plagued me for MONTHS!

 

I don't quite know what I've done (scary, I know) but here's the basic breakdown;

• It occurred to me that I had been too obsessed with capturing log files whilst the 'hang' was happening. I let a machine image overnight because we had noticed that occasionally the install would timeout and then the machine would complete the TS (sans applications).
• I grabbed the log files from there and inside the smsts-XXXXXXXX-XXXXXX.log file was a sudden jump from the previous entry at 2.18pm (around the time it was imaging) to about 6 hours later at 8.18pm

 Waiting for job status notification... InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
AppMgmtSDK handler is invalid. Trying to reconnect... InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
GetAppMgmtSDKInterface successful InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
Reconnecting to existing jobID '{682B9098-4ED7-4F9E-BBFE-61E30918C2F1}'.. InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
spAgent->GetJob(jobId, &spAgentJob), HRESULT=87d00215 (e:\qfe\nts\sms\dcm\sdk\cisdkclass.cpp,1756) DCMAgent 25/08/2014 8:18:15 PM 2724 (0x0AA4)
spAppMgmtSDK->SetEvaluationCallback( guidJobID, spNotifyCompPtr ), HRESULT=87d00215 (e:\qfe\nts\sms\client\osdeployment\installapplication\installapplication.cpp,456) InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
Failed to Reconnect to existing job, hr=0x87d00215 InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
Reconnect Job request failed, hr=0x87d00215 InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
ReconnectJob(spAppMgmtSDK, spCallback, guidJobID), HRESULT=87d00215 (e:\qfe\nts\sms\client\osdeployment\installapplication\installapplication.cpp,1233) InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
WaitforJobCompletion(spAppMgmtSDK, m_guidAppInstallJobID, ulAppInstallTimeout, nAppInstallRetryAttempts), HRESULT=87d00215 (e:\qfe\nts\sms\client\osdeployment\installapplication\installapplication.cpp,1122) InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
Step 2 out of 2 complete InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
Install application action failed: 'Microsoft Office Professional Plus 2013 with SP1'. Error Code 0x87d00215 InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
Sending error status message InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
   Setting URL = http://SCCM-SVR.lcgs.local, Ports = 80,443, CRL = false InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
   Setting Server Certificates. InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
   Setting Authenticator. InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
Set authenticator in transport InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
   Setting Media Certificate. InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
Sending StatusMessage InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
Setting message signatures. InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
Setting the authenticator. InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
CLibSMSMessageWinHttpTransport::Send: URL: SCCM-SVR.lcgs.local:80  CCM_POST /ccm_system/request InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
Request was successful. InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
Install application action cannot continue. ContinueOnErrorFlag is set to false. InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
hrInstallation, HRESULT=87d00215 (e:\qfe\nts\sms\client\osdeployment\installapplication\installapplication.cpp,914) InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
pInstall->InstallApplications(saAppNames, sContinueOnError), HRESULT=87d00215 (e:\qfe\nts\sms\client\osdeployment\installapplication\main.cpp,277) InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
Install Static Applications failed, hr=0x87d00215 InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
Process completed with exit code 2278556181 TSManager 25/08/2014 8:18:15 PM 2312 (0x0908)
!--------------------------------------------------------------------------------------------! TSManager 25/08/2014 8:18:15 PM 2312 (0x0908)
Failed to run the action: Install Office.
Item not found (Error: 87D00215; Source: CCM) TSManager 25/08/2014 8:18:15 PM 2312 (0x0908)
MP server http://SCCM-SVR.lcgs.local. Ports 80,443. CRL=false. TSManager 25/08/2014 8:18:15 PM 2312 (0x0908)
Setting authenticator TSManager 25/08/2014 8:18:16 PM 2312 (0x0908)
Set authenticator in transport TSManager 25/08/2014 8:18:16 PM 2312 (0x0908)
Sending StatusMessage TSManager 25/08/2014 8:18:16 PM 2312 (0x0908)
Setting message signatures. TSManager 25/08/2014 8:18:16 PM 2312 (0x0908)
Setting the authenticator. TSManager 25/08/2014 8:18:16 PM 2312 (0x0908)
CLibSMSMessageWinHttpTransport::Send: URL: SCCM-SVR.lcgs.local:80  CCM_POST /ccm_system/request TSManager 25/08/2014 8:18:16 PM 2312 (0x0908)
Request was successful. TSManager 25/08/2014 8:18:16 PM 2312 (0x0908)
Set a global environment variable _SMSTSLastActionRetCode=-2016411115 TSManager 25/08/2014 8:18:16 PM 2312 (0x0908)
Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 25/08/2014 8:18:16 PM 2312 (0x0908)
Clear local default environment TSManager 25/08/2014 8:18:16 PM 2312 (0x0908)
Let the parent group (Setup Operating System) decides whether to continue execution TSManager 25/08/2014 8:18:16 PM 2312 (0x0908)
The execution of the group (Setup Operating System) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows) TSManager 25/08/2014 8:18:16 PM 2312 (0x0908)
Failed to run the last action: Install Office. Execution of task sequence failed.
Item not found (Error: 87D00215; Source: CCM) TSManager 25/08/2014 8:18:16 PM 2312 (0x0908)

• Looking at the error codes I did a search on 0x87d00215 which turned up a few bits and pieces, but eventually a post, within a post within a post (Inception!) lead me to this article which I had to use Bing Translator to read - http://adminsccm.blogspot.com.br/2013/06/failed-to-get-dp-locations-as-expected.html
• This article goes on to describe a problem with the original CM Client installation, which is something I have had problems with for a long time. Using the steps in the article I manually created a new client package as outlined, then I ran some SQL queries to clean things up...

  • select * from ClientDeploymentSettings

    - to return the reference to the ccm client install and upgrade packages

  • update ClientDeploymentSettings set UpgradePackageID = '' where UpgradePackageID = 'LCG00003'
    - LCG00003 was an update package that was constantly showing up in distmgr.log with problems, I used this to remove it from the current client package 'LCG00002' (which also had problems)

  • update ClientDeploymentSettings set FullPackageID = 'LCG0011E' where FullPackageID = 'LCG00002'

    - to associate my new manually created package (LCG0011E) in place of the originally automatically generated package (LCG00002)

• At this point I edited the TS, added my new package to the "Setup Windows and Configuration Manager" step and set off imaging the same machine I've been using so far, then I went to lunch
• Upon returning from lunch (about 30mins) the OSD was nearly finished and shortly completed thereafter without incident. I logged in and Office was installed as was the most current version of the ccm client (5.00.7958.1303)
• I did a little dance
• Next I thought I would add all the other application installs back into the OSD TS (about 8 in total), so I went back and edited it
• This time I got an error complaining that the previous Config Manager setup package was no longer available - what the flip?
• I browse to the root of the Packages folder in the console and my manually created package has mysteriously disappeared
• In its place was a new automatically generated package (it had a new package ID as well)
• I decide to rerun the SQL query select * from ClientDeploymentSettings which returned the following;

FullPackageID	UpgradePackageID	UpgradeProgramName				UpgradeAdvertisementID 	UpgradeVersion 	EnablePeerCache
LCG0011F 	LCG00120 		Configuration Manager Client Upgrade Program 	LCG20058 		5.00.7958.1000 	1

• This is not what I had changed it to before lunch so ConfigManager has done it's own bit of magic here (obviously not happy with my manual package and tinkering)
• Okay, well I decided to then associate this newly automagically created package to the TS and set off another re-image of a machine
• Sadly, this has now resulted in the 'hang' happening in exactly the same spot as before

Whilst I'm no further ahead in terms of imaging machines I feel there is some insight to be gained here. I hope someone reading this might have a light-bulb moment, I'm not entirely sure what to do next...

[Schikitar]

Okay, here is the ccmsetup.log from a failed images machine. When I was imaging it I took note that the ccmclient started it's install at around 12.57pm, then at 1.01pm it finished and about 15 seconds later it began the Office install (which then fell over as expected.

 

Looking at this log it seems like the client is installing, then reports "An MP does not exist on this machine" followed by "No client is currently installed" and then it begins the installation again. Then right at the end it states "A Fallback Status Point has not been specified" and then it starts deleting all the ccmsetup files (which, oddly, are there and the client is installed).

 

Does this sound right/normal?? I think I need some help with rebuilding the client source files and configuring the install...

 

I have also attached the smsts-20140826-191650.log file which shows the 6 hour failover time between approximately 1pm and 7pm.

 

I hope someone can assist!

ccmsetup.log

smsts-20140826-191650.log

[killragtshirts]

Hi,

 

Did this ever get resolved/? I'm experiencing the exact same thing.

 

Thanks for all your info in the post.

[mmosley]

Hi,

 

I'm also having the same issue after upgrading to R2 SP1 CU1, has anyone had any luck in finding a resolution?

 

Thanks

[joengelhart]

I also am having this issue when applications are getting installed. Does anyone have a resolution yet?

 

Thanks!

[Epitome]

I too spent too much time trying to fix a nearly identical problem. I'm running SCCM 2012 R2 SP1 and ran into a 6 hour 'pause' during the "Install Optional Applications" step of my MDT-integrated SCCM OSD TS. It didn't matter which application was in second place on the list, it would pause at it for 6 hours, then finish the TS. I tried many different solutions for similar problems (setting high performance power settings, installing the applications while on a workgroup then joining the domain, etc). My manager agreed to let me call MS directly and their tech had a solution for me almost immediately:

Insert a "Restart Computer" command before "Install Optional Applications".

 

In my case it was between that and the previous step "Convert UDI App List". I would've thought a reboot would lose the data required to know which applications to install, but apparently not. So, once again the solution is: "Have you tried turning it off and on again?" Who woulda thunk it?

[Hamza SMAILI]

Hello , i have the same problem in my TS , but i resolved it by adding   before install application ( GPUPdate / force and  restart service CCMEXEC ) you can do a PS1 scrip : net stop ccmexec and net start ccmexec . 

Thank you 

Hamza SMAILI

[Mamejay]

On 5/5/2016 at 6:53 AM, Epitome said:

I too spent too much time trying to fix a nearly identical problem. I'm running SCCM 2012 R2 SP1 and ran into a 6 hour 'pause' during the "Install Optional Applications" step of my MDT-integrated SCCM OSD TS. It didn't matter which application was in second place on the list, it would pause at it for 6 hours, then finish the TS. I tried many different solutions for similar problems (setting high performance power settings, installing the applications while on a workgroup then joining the domain, etc). My manager agreed to let me call MS directly and their tech had a solution for me almost immediately:

Insert a "Restart Computer" command before "Install Optional Applications".

 

In my case it was between that and the previous step "Convert UDI App List". I would've thought a reboot would lose the data required to know which applications to install, but apparently not. So, once again the solution is: "Have you tried turning it off and on again?" Who woulda thunk it?

I joined just to say "THANK YOU!!"  

Super old thread but this has saved my sanity