What would be the best way to seperate servers by who is responsible

Customizations
1

(imported topic written by chrism91)

I was tasked to seperate out the 2 server groups by servers.

We have core services which does Domain Controllers and Exchange then we have DC System Support which handle IIS servers and APP servers.

I need a way to tell the differences between the 2 groups. AD is not an option. I was thinking about created a txt file on all the servers and doing a relavance to create automatic groups.

Has anyone done this before? If so what are the steps I need to do?

Thanks in Advanced

2

(imported comment written by BenKus)

Hi Chris,

You can do this a few ways:

  1. Make a property to identify computers with IIS and computers with DCs/Exchange Server. Then use the property to define management rights.

  2. Create a manual group and manually select the computers. Then use the group to define management rights.

  3. Use a manual method with file or reg key like you mentioned.

  4. Identify any other part of the system which you can use (perhaps naming convention?)

Ben

Ben

3

(imported comment written by chrism91)

Trying to stay away from manual groups. Anything manual in this company never gets updated.

The .txt file seems to be working pretty well. Would it be possible to to create a automatic group off that group that would look in the .txt file for a word like Devel or Test?

What would the relevance be to look in a file for a word to key off of? So an example would look like this:

file name: ICS.txt

content of file:

devel server for Operations

ok to reboot anytime

I would like to create a group that looks in the file for the word devel or production and if possible the “ok to reboot anytime”

Is what i’m asking for possible?

Thanks again Ben for your time and help.

Chris

4

(imported comment written by mcalvi91)

why not use the property for services and if it includes the AD/Xchg svcs, it goes to 1 group, otherwise it goes to another grp?

5

(imported comment written by chrism91)

Because our what we call core services. Core services include but not limited to just exchange. Other pieces go with exchange and core services like blackberry and citrix are part of core services.

6

(imported comment written by BenKus)

Hey Chris,

I would normally use registry keys for this type of thing… but if you want to use files, you could make 2 properties:

First property:

Name: “Internal Server Type” (or whatever)

Relevance:

(if (exists file (it)) then line 1 of file (it) else “unknown”) of “C:\ICS.txt”

Second property:

Name: “Restart Rules” (or whatever)

Relevance:

(if (exists file (it)) then line 2 of file (it) else “unknown”) of “C:\ICS.txt”

Hopefully that works for you,

Ben

7

(imported comment written by chrism91)

Thank you been. Thats what I was looking for. I’ll give it a try.