Sending this again without my signing cert, Mike Dougherty graciously let me know that my emails to the list have been blank for him in gmail since my cert got renewed 6/14, so my mails may not have been seen by everyone. So, apologies if you've already seen this.
Todd == Anybody seeing the "Regular Maintenance" task located at Task Scheduler\Task Scheduler Library\Microsoft\Windows\TaskScheduler causing any problems with the SCCM client on Windows Server 2012? I'd noticed that my clients were messed up shortly after deployment but always seemed to fix themselves overnight. A little investigation showed that the ccmeval tasks were not running near midnight because they had no schedule after the client was installed, but said last run after 3am. The "regular maintenance" task runs around 3 am, and in fact both CCM tasks and this task have the same exact 'last run' time. In trying to get WS2012 to OSD, I can pretty reliably get the following to happen every time I deploy a 2012 server. This particular vm is on ESX 5.0. (I know it's not officially supported on 5.0, but the same symptoms occur on 5.1) Suspiciously, this does not happen if I deploy the same TS to a hyper-v VM. 0:00 start task sequence 0:12 TS completes (the most recent vmware tools are installed during the TS, and there are a couple of restarts after that so they are fully installed at first full boot) 0:13 client restart (client looks to restart because all of the log files update with the same time stamp) 0:14 "Regular maintenance task" runs 0:15 client restart- all tabs available in CM control panel applet, all actions available, SCEP installed, but not updated (icon is red) 0:16 client restart 0:21 "Regular maintenance" task run 0:23 client restart - tabs missing, only 2 actions available(machine and user policy actions only), SCEP still installed, but still not updated. no other log activity for 24 minutes and from previous tests there will not be until "Regular Maintenance" runs around 3a the next morning. 0:47 Manually run "MSchedExe.exe start" from command prompt (ccmsetup and ccmeval start immediately, observed in task manager) 0:47 "Manual Maintenance" task in the same location as "Regular Maintenance" listed as "running" 0:49 Ccmexec.exe doubles in RAM usage (after ccmeval and ccmsetup start and briefly show up in task manager, SCEP, conhost.exe, msiexec, all conspire to peg the processor on the vm at 100% for a little bit) 0:49 logs all update (presumably client restart/reinstall/repair) 0:50 client restart (all logs update again) - all tabs and actions available in CP applet, software center notifies of new software, SCEP still "red" 0:52 I manually run SU Deployment eval cycle (SCEP updates (icon turns green).) 0:53 I can manually install a deployed application from the software center successfully. After this the client seems healthy, and stays healthy. My question is why does the Regular Maintenance task trigger the ccmeval and ccmsetup? Is what happens around midnight on 2008 R2 with the CCMEval task, included or added to the "Regular Maintenance" tasks in WS2012? The CM tasks in 2012 do not have "next run time" nor any "triggers". Are we to assume that these tasks now get started by "Regular Maintenance"? Why does "Regular Maintenance" run twice after deployment when it's not scheduled to run until 3AM the following morning? Anybody have any more information? Should I call PSS? Todd
