PropertySource - Windows Services

I agree - it definitely adds a lot of flexibility for creating groups having all of the services listed as a property of the device.  The only problem I see is that the list can be extensive.  There might even be a character limit for the field, so for some servers, it might not actually populate the entire list.  Mosh's idea to only include running services is a great idea.  I had thought of that when I wrote the script originally, but decided against it in case services happened to be stopped for whatever reason (such as patching), right as the collector was performing an active discovery sweep.  My fear is that it might override the property and populate an incomplete list.

Great idea, instead of doing individual ones to see, just grab all of them and then do an applies to function 

This is really useful Brandon, thanks.  I was only interested in the Running state services and I wanted the list sorted on the service's caption in the MSC console, so I modified the code slightly:

import com.santaba.agent.groovyapi.win32.WMI;

def hostname = hostProps.get("system.hostname");

def wmiQuery = " SELECT Name, Caption, State, Status FROM Win32_Service WHERE State='RUNNING' ";

def session = WMI.open(hostname);

def result = session.queryAll("CIMv2", wmiQuery, 15);

def runningServicesList = result.CAPTION.sort();

def winServicesRunning = runningServicesList.toString().replaceAll(",", "  |  ");

println "WinServicesRunning=" + winServicesRunning;

This will be something I will be implementing across the board, but it won't be listing all services.  Instead, the output will only display relevant services to automatically detect the type of server.  For example - using an if statement to decide that the server must be a Domain Controller because it is running Active Directory Domain Services, Active Directory Web Services, and DFS Replication.  The output would then be something like "Server.Role=Domain Controller" or "Server.Role=[Application] Web Server".

We're working on building dynamic groupings based on AppliesTo functions that are mentioning this same thing. Server.Role sounds interesting for grouping as well, however this would require a different property source for every type of role, using the generic "services" as a appliesTo function, it allows to just create those on demand instead of specific role based ones. This might work to do just for specific services you know will exist, then use the services property source to do the generic types of roles. 

Thanks!

@Brandon @Mosh is this something you guys are constantly using/relying on ?

@Tom Lasswell @Brandon thank you for your input.

On 16/06/2017 at 2:21 PM, Brandon said:

The only problem I see is that the list can be extensive.  There might even be a character limit for the field, so for some servers, it might not actually populate the entire list.

@Brandon this is correct and the list can be truncated. The property source character limit is 2,000 currently.

I created something very very similar on my portal a while back, and here's the proof the list can get truncated:

Note, on this particular device there is a "WalletService" service, and of course Windows Firewall.

Here's what the end of the property source (that lists services alphabetically) looks like:

Note the property source value ends "WalletS" - a truncation of "WalletService" - and Windows Firewall is absent.

@Antony Hawkins pretty awesome.