Client Management Suite

My requirement is to differentiate the production or non production machine from the list of managed computers/devices. 

For example, there are 10 database servers, 6 are in production and rest are used for testing purpose. A production computer may SPLA licensing whereas a development computer may be under MSDN. 

Which unique attribute or field of inventory can be used to differentiate the Prod or non-prod computers? 

How can I enable the licensing of computer software if require? 

Is there an existing field that can be used to denote this or would a new field need to be added to an existing inventory data class?  

Is there any way to find out that this server is used in Production Environment? 

Anybody can assist me on this.

Subnet?

Initially, I thought about the same but the customer is running production and Non-production endpoint in the same network. There is no separate subnet for Production environment.

Get creative with existing data classes, or make your own.  For example, name is already a data class -- so what if you had a naming convention for production vs. non-production?  Production is EMAIL1 but non-production is NP-EMAIL2.

If name or other similar ideas (like subnet) fail, create a custom data class and populate it with values.  I recommend creating a list that you define so that only proper values can be selected (instead of free text).  Use values that look good on a report so you aren't staring at 0's and 1's all the time.

You could even expand this into a Criticality Rating, and you could rate your servers High, Medium, Low, Test, Pre-Production, or Retired.

HI,

We have a similiar requirement here where we use active directory to group certain like machines together. For instance, we have all our "normal supported" machine in on OU, and our manufacturing systems in another.

Then it's easy to pull a report based on the ADSPath or distinguished name field from the INV_AEX_AC_Location Table (NS6).

Depending on your licensing setup, you could do a custom inventory to pull the windows product key or serial number from the registry.

The key thing would be to figure out something unique between the system types that you could target on. If it's not something being capture already, a custom inventory would do the trick.

Thanks Mclemson and LeeT for your suggestion.

The customer environment is not yet standarized!!!So Its not possinle to use IP/Subnet/Naming Convention or AD OU etc... So I am not able to use any existng data clase or inventory data to do so.

What I am thinking, If I create a new data class and add some attributes i.e. Host Name, IP address, Server Status to denote Production or Non-Production Environment.

So is there any way /method to add the attribute values of the custome data class from a spreadsheet ( *.CSV, *.TXT)?

Using connector solution, you could import a csv file and update the computer objects by name. 

So the csv would look like the following,

computerName,Status

serverA,Production

serverB,Non-Production

Then just create a source and a rule and should be all set.