Add Microsoft IIS

Step 1: Prepare Microsoft IIS for monitoring.

Prerequisites
Local Monitoring: Credentials are not required. The agent user is used for monitoring. Remote Monitoring via WMI: Credentials are required. The credentials to be provided include the username and password used to log into the remote Windows host. Before you can monitor Microsoft IIS entities, you must ensure the following prerequisites have been met: Remote Monitoring of IIS: If the Cloud agent and IIS are installed on different machines, then Microsoft Visual C++ needs to be installed on the Windows machine running the Cloud agent. The DLL msvcr100.dll , which is part of the Microsoft Visual C++ installation, is required. Local Monitoring of IIS: If the Cloud agent and IIS are installed on the same machine, Microsoft Visual C++ is not required. IIS has been installed on a Windows Server. For more information about running the installation wizards from Server Manager, see Installing IIS 8.5 on Windows Server 2012 R2. IIS Management Compatibility Components have been installed. To install the components: Click Start, click Control Panel, click Programs and Features, and then click Turn Windows features on or off. Follow the installation wizards and on the Select Server Roles page, select Web Server (IIS). For more information about running the installation wizards from Server Manager, see Installing IIS 8.5 on Windows Server 2012 R2. In Server Manager, expand Roles in the navigation pane and right-click Web Server (IIS), and then select Add Role Services. In the Select Role Services pane, scroll down to Web Server>Management Tools. Check the following boxes: IIS 6 Management Compatibility IIS 6 Metabase Compatibility IIS 6 Management Console IIS 6 WMI Compatibility Enable FTP Server. DCOM settings and WMI namespace security settings have been enabled for a remote WMI connection. WMI uses DCOM to handle remote calls. DCOM settings for WMI can be configured using the DCOM Config utility (DCOMCnfg.exe) found in Administrative Tools in Control Panel. This utility exposes the settings that enable certain users to connect to the computer remotely through DCOM. The following procedure describes how to grant DCOM remote startup and activation permissions for certain users and groups. Click Start, click Run, type DCOMCNFG, and then click OK In the Component Services dialog box, expand Component Services, expand Computers, and then right-click My Computer and click Properties In the My Computer Properties dialog box, click the COM Security tab Under Launch and Activation Permissions, click Edit Limits In the Launch Permission dialog box, follow these steps if your name or your group does not appear in the Groups or user names list In the Launch Permission dialog box, click Add In the Select Users, Computers, or Groups dialog box, add your name and the group in the Enter the object names to select box, and then click OK In the Launch Permission dialog box, select your user and group in the Group or user names box. In the Allow column under Permissions for User, select Remote Launch and select Remote Activation, and then click OK The following procedure describes how to grant DCOM remote access permissions for certain users and groups. Click Start, click Run, type DCOMCNFG, and then click OK In the Component Services dialog box, expand Component Services, expand Computers, and then right-click My Computer and click Properties In the My Computer Properties dialog box, click the COM Security tab Under Access Permissions, click Edit Limits In the Access Permission dialog box, select ANONYMOUS LOGON name in the Group or user names box. In the Allow column under Permissions for User, select Remote Access, and then click OK . Allowing Users Access to a Specific WMI Namespace It is possible to allow or disallow users access to a specific WMI namespace by setting the "Remote Enable" permission in the WMI Control for a namespace. The following procedure sets remote enable permissions for a non-administrator user: In the Control Panel, double-click Administrative Tools In the Administrative Tools window, double-click Computer Management In the Computer Management window, expand the Services and Applications tree and double-click the WMI Contro Right-click the WMI Control icon and select Properties In the Security tab, select the namespace and click Security Locate the appropriate account and check Remote Enable in the Permissions list Firewall Settings Click Start, click Run, type GPEDIT.MSC, and then click OK In the Group Policy dialog box, expand Administrative Templates, expand Network, expandNetwork Connections, and then expand Windows Firewall Select Standard Profile and double click on Windows Firewall : Allow Inbound Remote Administration Exceptions In the dialogue box that pops up, select Enabled and click on Apply If required, repeat the above 2 steps for Domain Profile as well

Prerequisites

Local Monitoring: Credentials are not required. The agent user is used for monitoring.

Remote Monitoring via WMI: Credentials are required. The credentials to be provided include the username and password used to log into the remote Windows host.

Before you can monitor Microsoft IIS entities, you must ensure the following prerequisites have been met:

Remote Monitoring of IIS: If the Cloud agent and IIS are installed on different machines, then Microsoft Visual C++ needs to be installed on the Windows machine running the Cloud agent. The DLL msvcr100.dll , which is part of the Microsoft Visual C++ installation, is required.

Local Monitoring of IIS: If the Cloud agent and IIS are installed on the same machine, Microsoft Visual C++ is not required.
IIS has been installed on a Windows Server. For more information about running the installation wizards from Server Manager, see Installing IIS 8.5 on Windows Server 2012 R2.
IIS Management Compatibility Components have been installed. To install the components:
1. Click Start, click Control Panel, click Programs and Features, and then click Turn Windows features on or off.
2. Follow the installation wizards and on the Select Server Roles page, select Web Server (IIS). For more information about running the installation wizards from Server Manager, see Installing IIS 8.5 on Windows Server 2012 R2.
3. In Server Manager, expand Roles in the navigation pane and right-click Web Server (IIS), and then select Add Role Services.
4. In the Select Role Services pane, scroll down to Web Server>Management Tools. Check the following boxes:
  - IIS 6 Management Compatibility
  - IIS 6 Metabase Compatibility
  - IIS 6 Management Console
  - IIS 6 WMI Compatibility
5. Enable FTP Server.
DCOM settings and WMI namespace security settings have been enabled for a remote WMI connection.

WMI uses DCOM to handle remote calls. DCOM settings for WMI can be configured using the DCOM Config utility (DCOMCnfg.exe) found in Administrative Tools in Control Panel. This utility exposes the settings that enable certain users to connect to the computer remotely through DCOM.

The following procedure describes how to grant DCOM remote startup and activation permissions for certain users and groups.
1. Click Start, click Run, type DCOMCNFG, and then click OK
2. In the Component Services dialog box, expand Component Services, expand Computers, and then right-click My Computer and click Properties
3. In the My Computer Properties dialog box, click the COM Security tab
4. Under Launch and Activation Permissions, click Edit Limits
5. In the Launch Permission dialog box, follow these steps if your name or your group does not appear in the Groups or user names list
  1. In the Launch Permission dialog box, click Add
  2. In the Select Users, Computers, or Groups dialog box, add your name and the group in the Enter the object names to select box, and then click OK
6. In the Launch Permission dialog box, select your user and group in the Group or user names box. In the Allow column under Permissions for User, select Remote Launch and select Remote Activation, and then click OK
The following procedure describes how to grant DCOM remote access permissions for certain users and groups.
1. Click Start, click Run, type DCOMCNFG, and then click OK
2. In the Component Services dialog box, expand Component Services, expand Computers, and then right-click My Computer and click Properties
3. In the My Computer Properties dialog box, click the COM Security tab
4. Under Access Permissions, click Edit Limits
5. In the Access Permission dialog box, select ANONYMOUS LOGON name in the Group or user names box. In the Allow column under Permissions for User, select Remote Access, and then click OK
  .
Allowing Users Access to a Specific WMI Namespace

It is possible to allow or disallow users access to a specific WMI namespace by setting the "Remote Enable" permission in the WMI Control for a namespace.
The following procedure sets remote enable permissions for a non-administrator user:
1. In the Control Panel, double-click Administrative Tools
2. In the Administrative Tools window, double-click Computer Management
3. In the Computer Management window, expand the Services and Applications tree and double-click the WMI Contro
4. Right-click the WMI Control icon and select Properties
5. In the Security tab, select the namespace and click Security
6. Locate the appropriate account and check Remote Enable in the Permissions list
Firewall Settings
1. Click Start, click Run, type GPEDIT.MSC, and then click OK
2. In the Group Policy dialog box, expand Administrative Templates, expand Network, expandNetwork Connections, and then expand Windows Firewall
3. Select Standard Profile and double click on Windows Firewall : Allow Inbound Remote Administration Exceptions
4. In the dialogue box that pops up, select Enabled and click on Apply
5. If required, repeat the above 2 steps for Domain Profile as well

Step 2: Decide how you want to add the Microsoft IIS.

You can add Microsoft IIS entities using one of two ways:

Add them from UI
Use the agent's omcli add_entity command with the appropriate JSON files

Adding Entities from the UI

From the Management Cloud main menu, select Administration, Discovery, and then Add Entity. The Add Entity page displays.
Select the Microsoft IIS Entity Type.

Enter the following UI properties.

Microsoft Internet Information Services UI Fields

Microsoft Internet Information Services UI Fields
Entity Name: Name of this entity displayed in the Oracle Management Cloud console. Host Name: Hostname of Microsoft IIS Server Installation Directory: Absolute installation path of the Microsoft IIS Server. You need to specify the path using double backslashes ( \\). Example: `C:\\Windows\\system32\\inetsrv` Logging Directory: Absolute path to log file directory. Cloud Agent: Cloud agent monitoring the host where Microsoft Internet Information Services is installed. Monitoring Credentials Host Username: Windows user on the Microsoft IIS Server host Host Password: Password for the Windows user

Entity Name: Name of this entity displayed in the Oracle Management Cloud console.
Host Name: Hostname of Microsoft IIS Server
Installation Directory: Absolute installation path of the Microsoft IIS Server. You need to specify the path using double backslashes ( \\).
Example: C:\\Windows\\system32\\inetsrv
Logging Directory: Absolute path to log file directory.
Cloud Agent: Cloud agent monitoring the host where Microsoft Internet Information Services is installed.

Monitoring Credentials

Host Username: Windows user on the Microsoft IIS Server host
Host Password: Password for the Windows user

See Add Entities from the Console for detailed instructions on using the Add Entity UI.

Using omcli and the Appropriate JSON Files

Download and extract the required JSON file(s) from the master JSON zip file. See the table below for the specific JSON files you'll need.

Edit the file(s) and specify the requisite properties shown below.

Microsoft Internet Information Services JSON Files and Properties

Microsoft Internet Information Services JSON Files and Properties
Definition Files omc_microsoft_iis_server_local_sample.json host_name: Hostname of Microsoft IIS Server install_dir: Absolute installation path of the Microsoft IIS Server. You need to specify the path using double backslashes ( \\). Example: `C:\\Windows\\system32\\inetsrv` omc_microsoft_iis_server_remote_sample.json omc_is_remote: Property to indicate if the Microsoft IIS Server is local(no) or remote(yes) Credential File: omc_microsoft_iis_server_remote_creds_sample.json Credential properties (Applicable for remote monitoring via WMI) wbem_username: Windows user on the Microsoft IIS Server host wbem_password: Password for the Windows user

Definition Files

omc_microsoft_iis_server_local_sample.json

host_name: Hostname of Microsoft IIS Server
install_dir: Absolute installation path of the Microsoft IIS Server. You need to specify the path using double backslashes ( \\).
Example: C:\\Windows\\system32\\inetsrv

omc_microsoft_iis_server_remote_sample.json

omc_is_remote: Property to indicate if the Microsoft IIS Server is local(no) or remote(yes)

Credential File: omc_microsoft_iis_server_remote_creds_sample.json

Credential properties (Applicable for remote monitoring via WMI)

wbem_username: Windows user on the Microsoft IIS Server host
wbem_password: Password for the Windows user

Add the entity using omcli.

omcli add_entity agent DEFINITION_FILE [-credential_file CREDENTIAL_FILE [-encryption_method_gpg]]

Verify the status of the newly added entity.
```
omcli status_entity agent DEFINITION_FILE
```

See step 4. Adding Entities to Your Service of Add Entities Using JSON Files for more information.

Step 3: (Optional but recommended) Set up alerts.

To enable lights-out monitoring, you can set up alert rules to generate alerts and send notifications if your entities have performance issues.

See Set Up Alert Rules and Set Up Alert Thresholds and Notifications.

Troubleshooting

If you run into any issues regarding discovery or monitoring of Microsoft IIS, see the following: