execmgr.log is a key log file, as you know. Other logs you can investigate would be ones related to content: CAS.log ContentTransferManager.log DataTransferService.log Jeff From: [email protected] To: [email protected] Subject: RE: [mssms] Programs take a while to kick off Date: Thu, 13 Nov 2014 20:18:45 +0000
I looked, and yes the package is set to copy to the package share. It is a very small package, maybe 1Mb or less and all the clients are on a well connected LAN. I only have 55 clients on the SCCM 2012 server so there is no resource contention. I can see that there is some kind of pause between when the client starts the program for execution and when it actually kicks off, but I can’t figure out what logs are relevant to figuring out what is happening for those 20 minutes. It worked better on subsequent nights – so that points to it being a caching issue, but the advert is set to run from the DP so I don’t get it. It is an autoit script that checks to see if the computer needs to reboot due to pending file renames or if the CCM SU status is pending reboot and then notifies the user via a countdown that the computer is going to reboot unless someone hits cancel. If the timer reaches zero, then it reboots. If it is canceled, it just exits without rebooting. There is a collection of machines that are in reboot pending mode that is based off a DCM baseline for pending reboot, so if the DCM doesn’t clear the machine from the pending reboot status, the machines stays in the collection and reboots the next day. The collection is set to run the reboot computer process every day at 3:00AM. This lets us reboot computer in off hours, and lets the users here postpone the reboot if they are using the computer. I know it sounds like overkill, but I work for a large hospital and need to make sure the computer is not in use before rebooting it. From: [email protected] [mailto:[email protected]] On Behalf Of Jeff Poling Sent: Thursday, November 13, 2014 9:09 AM To: [email protected] Subject: RE: [mssms] Programs take a while to kick off Just checking. . .do you have the "Copy content in this package to a package share on distribution points" option enabled on the package? Jeff From: [email protected] To: [email protected] Subject: Re: [mssms] Programs take a while to kick off Date: Thu, 13 Nov 2014 04:47:58 +0000 But the advertisement is set to run from DP So there should not be any caching involved or delay on downloading the package. On Nov 12, 2014, at 6:33 PM, "Jeff Poling" <[email protected]> wrote: Based on the log snip, it looks like the delay is due to waiting on the content of the package..... Jeff Sent from my Windows Phone From: Miller, Todd Sent: 11/12/2014 5:38 PM To: [email protected] Subject: [mssms] Programs take a while to kick off I have a program that is set to run at 3:07AM potentially every day. This is a package/program and it is set to run from the DP. My problem is that the execmgr kicks off at the right time, but there is an inexplicable delay between when execmgr kicks off and when the executable is started – in this logged case there is a 20 minute delay. I was wondering if anyone might know what additional logs I could look in to see what is causing or happening during this delay. Here is an excerpt from the execmgr log Successfully raised SoftDistWaitingContentEvent event for program Reboot for patches execmgr 11/12/2014 3:07:00 AM 4880 (0x1310) Execution Request for advert XXX20052 package XXX000F9 program Reboot for patches state change from NotExist to WaitingContent execmgr 11/12/2014 3:07:00 AM 4880 (0x1310) Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="XXX000F9",ProgramID="Reboot for patches", actionType 1l, value , user NULL, session 4294967295l, level 0l, verbosity 30l execmgr 11/12/2014 3:07:00 AM 4880 (0x1310) ***WHAT IS GOING ON IN THIS GAP ?? *** Processing [{0B69F939-8B42-4B98-BDB2-187A7DC966C5}, 0]: OnContentAvailable execmgr 11/12/2014 3:26:27 AM 1232 (0x04D0) [{0B69F939-8B42-4B98-BDB2-187A7DC966C5}]: Content Version 15 is available for advert XXX20052, pkg: XXX000F9, program Reboot for patches. execmgr 11/12/2014 3:26:27 AM 1232 (0x04D0) An existing MTC token was not supplied, using ExecutionRequest's Id as MTC token and this execution request is the owner of resultant MTC task. execmgr 11/12/2014 3:26:27 AM 1232 (0x04D0) Request a MTC task for execution request of package XXX000F9, program Reboot for patches with request id: {9FCC9C91-DC56-4BC5-9D39-10F98A32E574} execmgr 11/12/2014 3:26:27 AM 1232 (0x04D0) Execution Request for advert XXX20052 package XXX000F9 program Reboot for patches state change from WaitingContent to Ready execmgr 11/12/2014 3:26:27 AM 1232 (0x04D0) Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you.
