So - "yes" of a sort, depending on what you're after.
You can use the ALERTING module to track things ... but that's a bit of a catch-22 (since the component needs to be functioning).
There's also Agent Health stuff (which isnt real-time) to ensure that agent components are up & running (and re-installing them if needed / desired). You can find information on that here -- Agent Health - Install / Uninstall, Update and Repair the Agent components for instance.
... what's the concern here (to provide context) ?
Are we talking about "I don't want local-admin users to stop services", or more of a "I need to monitor key services on key devices" ... or something else ?
the context here is to supervise the landesk services is they're up/down , because of many reason some admins disable the landesk service and i don't want local admin to stop service in case of someone stopped them i would like to see the machines that have services down to start them
That make sense !
So - there's some catch-22 situations here.
So my first point is that "if you give people local admin, there's not much you can do" (and you CAN "not give" them local admin via things like the AppSense range which can elevate certain programs for certain users, without giving them "carte blanche" local admin rights).
This is usually a political battle to be fought.
Now - the Agent Health stuff can help you with "people disabling" stuff within reason (depending on how smart / determined your local-admin users are) ... the "real" solution here (from a technological point of view) would be to pull their rights (i.e. - stuff that AppSense & such usually help with / focus on). USUALLY it's more of a political / social problem.
If you want a real-time thing ... that too ends up in a catch-22 situation. Yes, we have an alerting module, but if people disable services & such, it may not work profoundly well ... so there's usually falling back to other systems that track services (usually more for server management) ... but that doesn't necessarily solve the problem any better.
So I would argue / make the point that the "real" problem isn't a technological one ... but there *IS* a purely technological solution if it's not a situation that can be handled / solved via political / social approaches. It'd just involve the use of something like the AppSense suite to remove the Local Admin privileges when they aren't needed ...
Does that help / make sense?
This is a "well rehearsed" problem you're describing (one I run into pretty often) and the above is usually the response that I end up puting forward to a CIO or whoever I can help convince ... if the soft / social approach doesn't work (and there's a bunch of "I don't wanna" type situations), then there *ARE* technological solutions ... but that tends to get people cross too (unsurprisingly, not a lot of people like having "their local admin privileges" pulled, even if it's usually a very good idea) ...
Does that work for you / your boss(-es) ?
just to clarify things, users don't have local admin access, I was talking about IT admins... my need was to supervise landesk services "in real time" requests......etc".
Ah - good clarification there then. Hmm - what do you mean by "requests" ...?
As in "I was asked to perform thing X" type of thing? Or what are we talking here?
phoffmann as I said some of our admin , disables landesk services on machines for their diagnosis in case of problems and they let services stop after the diagnosis
I would like to have if there is a possibility to supervise landesk services on client machines; that's all
Oh something like that? Yeah - that's simple (albeit not real-time -- it'll be based off of inventory data).
You just create a query that'll check whether the service(s) you care about are stopped & get a list of devices where any of that applies.
Something like this for instance ... (as a starting point) - click on the picture to get the full-size picture.
... again - this is based off of data from inventory scans. So if (for instance) the Local Scheduler service is stopped (if that's your ONLY source of sending inventory), then you won't be getting updated information (so running inventory as part of logon or so is useful).
But yeah - that's an easy enough starting point that you can build from (with data to show you which service(s) is/are affected).
So - you don't HAVE to supervise.
You can schedule a query like that to run a report ... and have that e-mailed to you / people on a daily / weekly basis or whatnot, for instance.
<It's a nice lazy option to just "build the report you want" in a console query & then use said query as "the report" ... super simple way to build up reports. >
It was meant as a basis to start from -- you can go all sorts of places from there .
1 of 1 people found this helpful
you can also restrict a admin in access to services via a GPO and service -rights .
How to Grant Users Rights to Manage Services (Start, Stop, Etc.) - TechNet Articles - United States (English) - TechNet … (just a quick search example i found)
We used that for years to stop local admin users to have there fingers on the Landesk-Services