Skip to content

Commit 844281c

Browse files
authored
Update README.md
1 parent 129cae4 commit 844281c

1 file changed

Lines changed: 22 additions & 16 deletions

File tree

README.md

Lines changed: 22 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
# OpsMgr GenericServiceMonitoring ManagementPack
22

33
## Introduction:
4-
It is often necessary to monitor windows services across your entire SCOM environment. This MP gives you the ability to easily and quickly discover and monitor hundreds of services. The wildcard(*) notation allows great flexibility in discovering the services you are looking for.
4+
It is often necessary to monitor windows services across your entire SCOM environment. This Management Pack gives you the ability to easily and quickly discover and monitor hundreds of services. The wildcard(*) notation allows great flexibility in discovering the services you are looking for.
55

6-
This ManagementPack is currently under development and may contain errors. Please always test it in DEV environment befor importing the MP to production.
6+
This Management Pack is currently under development and may contain errors. Please always test it in DEV environment befor importing the Management Pack to production.
77

88
## Key Features
99

@@ -13,41 +13,41 @@ This ManagementPack is currently under development and may contain errors. Pleas
1313
## Supported Environments
1414

1515
- System Center Operations Manager 2012 R2
16-
- System Center Operations Manager 2016 (LTSC)
17-
- System Center Operations Manager 1807 (SAC)
16+
- System Center Operations Manager Long Term Servicing Channel (2016)
17+
- System Center Operations Manager Semi-Annual Channel (1807)
1818

1919
## How-To:
2020
### 1. Import the Management Pack into SCOM.
2121
### 2. Create the CSV file on one of your management server.
2222

23-
#### CSV File Schema:
23+
#### CSV file schema:
2424

2525
__ServiceName;Include;Exclude__
2626

27-
Include: Comma separated List of Servername(ShortName)
27+
Include: comma-separated list of servernames (ShortName; not FQDN)
2828

29-
Exclude: Comma separated List of Servername(ShortName)
29+
Exclude: comma-separated list of servernames (ShortName; not FQDN)
3030

31-
*: Every Host in the "Microsoft.SystemCenter.ManagedComputerServer" ClasS
31+
*: Every host in the "Microsoft.SystemCenter.ManagedComputerServer" class
3232

33-
#### CSV File Examples:
33+
#### CSV file examples:
3434

3535
__ServiceA;HostA,HostB;none__
3636

37-
ServiceA is monitored for HostA and HostB. There is no (none) exclusion.
37+
serviceA is monitored for hostA and hostB. There is no (none) exclusion.
3838

3939
__ServiceB;*;none__
4040

41-
ServiceB is monitored on every Host. There is no (none) exclusion.
41+
serviceB is monitored on every host. There is no (none) exclusion.
4242

4343
__Service*;*;HostB__
4444

45-
Service*(wildcard) is monitored on every Host and excluded for HostB.
45+
service*(wildcard) is monitored on every host and excluded for hostB.
4646

4747

48-
### 3. Start Sevice Ingest Task
48+
### 3. Start service ingestion task
4949

50-
1. The Task which starts the CSV ingestion process is found at the "Management Server View". Select the management server on which the CSV is located and execute the Task. (Example at Views -> State View Management Server)
50+
1. The task which starts the CSV ingestion process is found at the "Management Server View". Select the management server on which the CSV is located and execute the task. (example at Views -> State View Management Server)
5151
2. Click "Override" to enter the path to the CSV.
5252

5353
![alt text](https://github.com/spa5603/OpsMgr.GenericServiceMonitoring/blob/master/Graphics/RunTask.jpg)
@@ -57,8 +57,14 @@ This ManagementPack is currently under development and may contain errors. Pleas
5757
![alt text](https://github.com/spa5603/OpsMgr.GenericServiceMonitoring/blob/master/Graphics/OverrideParameter.jpg)
5858

5959

60-
### 4. Check discoverd Services
61-
The discovery is configured to run every 24h and detect newly processed servers. This setting can be changed at the xml code to meet your requirements. So it can take up to 24 hours until the service can be discovered.
60+
### 4. Check discoverd services
61+
The discovery is configured to run every 24h and detect newly processed services. This setting can be changed at the xml code to meet your requirements. So it can take up to 24 hours until the service can be discovered.
62+
63+
#### XML tag:
64+
<DataSource ID="DS" TypeID="Windows!Microsoft.Windows.TimedPowerShell.DiscoveryProvider">
65+
<IntervalSeconds>600</IntervalSeconds>
66+
<SyncTime></SyncTime>
67+
<ScriptName>OpsMgr.GenericServiceMonitoring.Scripts.GetServicesToMonitor.Script.ps1</ScriptName>
6268

6369
## Views:
6470

0 commit comments

Comments
 (0)