Kaseya Technical Success - Server Role Identifier

Identify Server role(s) for Automation.


This script empowers advanced automation via policy management. This is a catalyst in identifying and managing servers based on their roles to truly distinguish the management of Active Directory, SQL, Web, and so forth.

Agent Procedure Details below:

Audit and ID All Server Roles by running a batch file IDSRVROLES.CMD that looks at running services and other key indicators on a system to create a results file called SERVERROLES.TXT in the Agent Temp folder.

Once completed, these roles can be added to any system custom field for advanced automation and policy management.


1/17/2019: Sharepoint identification improved per community suggestion.

Oscar Romero
Kaseya Technical Success

  • Name: Oscar Romero
  • Company: Kaseya
  • Website: http://www.kaseya.com
  • Contact Developer
  • Summary
  • Kaseya Technical Success - Server Role Identifier
  • Version: 2.0
  • Initially Released August 10th, 2018
  • Discussion
    Gravatar for Colton Morrison
    Colton Morrison over 2 years ago

    You should change the .cmd SharePoint Server entry to the following:

    REM SharePoint Server

    find /i "SharePoint Timer Service" %t%\netstart.log.txt

    if not errorlevel 1 set SPS=1

    What is searched for currently as part of the .cmd file is for something like SharePoint Foundation, which is basic and assumes the SQL instance is on the same server. This does not work for those who have SharePoint environment with a SQL DBs running on another server (i.e. SharePoint farm of 2 or more servers).

    Please update. Thanks!

    Gravatar for Oscar Romero
    Oscar Romero about 2 years ago

    Appreciate the suggestion Colton.

    I have made the edit on the cmd file and updated the file.