Hi Sherry
Thanks for your answer. I wholly agree with EVERY-SINGLE-WORD and also the
sentiment behind it.
The reason that I care is that it is yet another reason for the customer to
beat up on CM. Sadly the majority of the client estate is Windows XP and
Client Status - Client Check is skewed as a result.
What is preventing Task Scheduler is the security team. Yes, I know the irony
of a security team allowing an un-patchable OS to run but that's life
Jason
Date: Thu, 8 May 2014 05:53:55 -0700
From: [email protected]
Subject: Re: [mssms] CCMEVALTASK issue
To: [email protected]
I don't have a solution for you... but more of a "who cares" answer. :)
reasons not to care about the failed status on the advert:1) It's xp anyway.
(so... no one is supposed to care anymore)2) uh, the advert ran. Let's pretend
that means the client is at least healthy enough to do that.3) Failures or
remediations as a result of the ccmeval are reported up differently--and never
by advert status anyway--so... look at THOSE reports about what may or may not
be working right regarding the elements that ccmeval is doing.4) It's XP. If
someone is MAKING you care about it, tell them if they want you to care about
the advert status as a result of a ccmeval
run (which is slightly ridiculous just typing it), you require that task
scheduler be automatic and running. Period, end of discussion.5) what's
stopping and disabling it? a gpo? well... there's this lovely thing in
classic packages (or a task sequence for example) to run something else first.
something like a vbscript to change it to automatic... and start it. then
ccmeval runs and it'll be ok. so... who cares if the task scheduler is then
stopped and disabled 90 minutes later. You win! (for 89 minutes).6) (again,
because I think it's the relevant point): It's xp. Get rid of it. Sherry
Kissinger
From: Jason Sandys <[email protected]>
To: "[email protected]" <[email protected]>
Sent: Thursday, May 8, 2014 7:37 AM
Subject: RE: [mssms] CCMEVALTASK issue
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
