Hi there Jason Yes, my first response was to try and edit CCMEVAL.XML to prevent it looking at Task Scheduler but that's not the case. Neither this XML file nor the CCMEvalReport.XML file have any Task Scheduler section. What is chucking the error is CCMEVALTASK and not CCMEVAL - in this case a failed attempt to remediate a failed health check Jason From: [email protected] To: [email protected] Subject: RE: [mssms] CCMEVALTASK issue Date: Thu, 8 May 2014 12:37:29 +0000
Technically, you should be able to edit the xml file and remove the check. although, the whole point of running ccmeval using task scheduler is so that the client agent or its dependencies can be checked and fixed --that can't happen when it's being run by the client agent itself so it doesn't really make sense to do it as an advert. For example, if WMI is broken on the client, how will the deployment ever run to fix it? Who's idea was it to disable the task scheduler? Let me guess, it was done in the name of "security"? Misguided are most security folks (quote from Yoda). J From: [email protected] <[email protected]> on behalf of Jason Wallace <[email protected]> Sent: Thursday, May 8, 2014 4:40 AM To: [email protected] Subject: [mssms] CCMEVALTASK issue Hi there folks I have an issue with CCMEVAL and CCMEVALTASK which I would appreciate some input on please. I have a number of Windows XP (yes, I know) systems. On these Task Scheduler is disabled. Of course this means that CCMEVAL is not going to run so we run it through an advertisement. When we do that however all of the XP systems report an error back to the console. Checking the clients it seems that CCMEVAL itself runs through the checks in its XML file and reports no significant issues but it's CCMEVALTASK which then kicks off and throws an error, masking any errors in the console. Yes, the obvious thing is to enable Task Scheduler but that cannot be done on the XP estate so I am wondering if we can somehow prevent the check on the Task Scheduler component? Thanks
