Simple relevance for Windows Server

Content Authoring
1

(imported topic written by jgstew)

Is there a simple piece of relevance that can be used to distinguish between Windows Client and Windows Server, starting with WinXP / 2003 at the earliest?

I’m looking for something to add to the following to either exclude servers, or include only servers depending on the need:

/* Windows Only */ windows of operating system

/* 64bit Only */ x64 of operating system

/* WinXP or later */ version of operating system >= “5.1”

2

(imported comment written by NivS)

Set this relevance clause to False:

operating system as string starts with "Win2
3

(imported comment written by jgstew)

Thats pretty good, though not y3k compliant. :slight_smile:

I was hoping for something that would be more direct other than just the name, but this is definitely the sort of thing I was looking for.

4

(imported comment written by NivS)

You can also use WMI, the Win32_OperatingSystem class has a property called producttype:

Value

Meaning

1

Work Station

2

Domain Controller

3

Server

http://msdn.microsoft.com/en-us/library/aa394239(v=vs.85).aspx

So something like this will give you only Workstations

(select ("ProductType from Win32_OperatingSystem") of WMI) as string contains "1"
5

(imported comment written by jgstew)

Thanks, this is more of what I was hoping to find.

I’ve added this here:
http://bigfix.me/relevance/details/2998563

6

(imported comment written by MattPeterson)

This should get the results your looking for, and becuase it searches the registry and doesn’t access wmi it will evaluate much quicker…

value “ProductType” of key “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ProductOptions” of registry = “ServerNT”

7

(imported comment written by jgstew)

Thanks. This is what I was hoping for, something consistent in the registry.

It turns out one of my colleagues had already made use of this in an Analysis, which I submitted here:
http://bigfix.me/analysis/details/2994625

8

(imported comment written by MattPeterson)

That analysis is part of the BES Inventory and License site, published by IBM. Which is also where I found that key.

9

(imported comment written by jgstew)

That makes sense. Now that you say that, I think what happened was we copied the IBM version and made some changes, then globally hid the IBM version. I was definitely confused when the Mac OS X & UNIX Version were in the BES Inventory and License site, but the Windows version was only found in a custom site of ours.