Windows Mapped Drive monitor is used to monitor the network drives. Mapped Drives is used to access data over the network. Using these mapped drives, it is easy to access the data. It is very much essential to ensure the connectivity of Mapped Drives and the only way this can be achieved is through monitoring the Mapped Drives.
Note
- To create the Windows Mapped Drive monitor on Windows XP, you need to install the hotfix patch from the link http://support.microsoft.com/kb/923262
- For Windows XP x64/Vista, it is mandatory for local monitoring that the Service Log On account should have administrator privileges.
Visit http://www.microsoft.com for more information on how to get the license for the hotfix.
Monitored attributes for Windows Mapped Drive monitors
The following table lists the monitored attributes of a Windows Mapped Drive monitor.
| Attribute | Description |
|---|---|
| Availability (%) | Monitors availability of the mapped drive. If the mapped drive is connected, the value is 100%; otherwise it is 0%. |
| Used (%) | Percentage of disk space currently in use by the monitored mapped drive. |
| Free Space (MB) | Indicates amount of free space available on the Mapped drive. |
| MappedDisk Instances (#) | Number of mapped drives for the logged in sessions that correspond to the same Mapped To location. For example, if a user with Mapped drive X logs in to the system using two different RDC consoles, the value of the attribute is 2. The value indicates that two sessions have access to the same mapped drive. |
Configuration information for Windows Mapped Drive monitors
The following table describes the information required during configuration of the Windows Mapped Drive monitor.
| Configuration information | Description |
|---|---|
| Input fields on the Configuration tab | |
| Instance Name | Name for the monitor instance. By default, instance name consists of Mapped Drive Name, Mapped To, and Target IP/Host Name. |
| Tag | Specify a tag value to search or group the objects. You can enter multiple name-value pairs, text, or include both (name-value pair and text). This gives you the option to group objects in different forms. Click the + icon to select a default tag class. The Enter Tag Details screen opens. Select Tag Class from the drop-down list and enter a tag value. Click Add to append tag class and value. Click Finish. Note The tag specified by you is not considered as a default class. You cannot enter special characters &"/<>' in the tag field.
|
| Source Agent | Agent attached to the selected device. If Agent is not available on selected device, local agent is taken. User can select the source agent from the drop-down list. (Agent, which collects the monitor data). |
| Target IP/Host Name | IP/Host name of the selected Device. Target system where service to be monitored is running. |
| Username | For local monitoring and it does not require User name. For remote monitoring, you have to provide the user name and this is required for WMI to get data on remote box. |
| Password | For local monitoring and it does not require password. For remote monitoring, you have to provide the Password for the corresponding User name and this is required for WMI to get data on remote box. |
| Mapped Drive Name | Load attribute choice will list all the connected mapped drive at the given time. |
| Mapped To | Lists the provider name (Mapped To) of the selected Mapped Drive. For example, in RDC if two users are connected to the same computer at the same time, and both users have the same Mapped drives connected to different (Mapped To) locations, then it will list the different location in the load attribute choice. |
| Control tab | |
| Collect Data | Select/clear check box to enable/disable data collection for the monitored component. By default, data collection is enabled (check box selected). |
| Statistics Poll Interval | Specify the time interval between two consecutive Statistical data polls. Default is 5 minutes. |
| Statistics Poll Timeout | Specify the time-out period for each poll of statistical data. If no data is available at the end of this interval, system records zero availability and proceeds with the next scheduled poll. Default is 30 seconds. |
| Configuration Poll Interval | Specify the time interval between two consecutive configuration data polls. Default is 24 hours (One day). |
| Configuration Poll Timeout | Specify the time-out period for each poll of configuration data. If no data is available at the end of this interval, system records zero availability and proceeds with the next scheduled poll. Default is 10 minutes. |
| Group tab | |
| Group Membership | This enables you to add a device and its monitors to one or more groups. Optionally, you may associate the device with a group. A group is used to logically organize the devices and monitors by department, geographic area, or service. Assigning a device to a group also enables the system administrator to restrict or allow access to certain devices. To associate the device with a group, select the group name here. |
Additional configuration and setup issues
The following table presents details about Additional configuration and setup issues for the Windows Mapped Drive monitor.
| Issue | Details |
|---|---|
| NO_DATA conditions | If mapped drives are not connected after the monitor creation, except Availability attribute all the other stats attributes shows NO_DATA in the next statistics poll. |
| Monitor configuration | No additional configuration requirements for this monitor. Maintain the default configuration of BMC ProactiveNet. |
| External setup | No external setup requirements for this monitor. |
| External dependencies | No external dependencies for this monitor. |
| BMC ProactiveNet agent dependencies | BMC ProactiveNet agent installation on the monitored host is not mandatory. Monitor instances can be created from BMC ProactiveNet agents running on Windows. |
Remote monitoring requirements
Remote (Agentless) monitoring requires the following:
- The machine hosting BMC ProactiveNet agent must be running version 7.1 SP2 or later software.
- The machine hosting BMC ProactiveNet agent and the machine to be monitored must have the same operating system. Monitoring across platforms causes inconsistencies and errors.
- The machine hosting BMC ProactiveNet agent and the machine to be monitored must be in the same domain and workgroup, and have Administrative privileges on the OS.
- The account details (user name and password) on both machines must be same. Ensure that you run the agent on this account.
To set up agentless monitoring
- On the Windows machine to monitor, configure a valid user account with Administrative privileges.
- Select a BMC ProactiveNet agent (Windows) machine (running version 7.1 SP2 or later), and configure the ProactiveNet Agent service to run under the valid user account (the account set up in step 1).
- Go to Start > Settings > Control Panel > Administrative Tools.
- Double-click Services.
- Double-click ProactiveNet Agent Service to view Service Properties.
- Select This Account, and enter the NT user account and password in the respective fields (the account set up in step 1). Restart the ProactiveNet Agent service.
- Launch BMC ProactiveNet Administration Console, and create a device on the Agent for the non-agent machine to monitor.
- Right-click Devices and click Add Device.
- Select the device type for the remote machine and specify its name.
- Click Finish.
Close and open the Devices node, to view the non-agent machine in the Devices list.
- Return to the Administration Console, and explore the Devices node.
- Right-click the non-agent machine, and navigate to click Windows Mapped Drive Monitor.
- On the Windows Mapped Drive Monitor Create screen,
- Select BMC ProactiveNet agent machine (set up in step 2) as the Source Agent.
- All other input fields are the same as for the basic monitor.
- Click Finish to create the Windows Mapped Drive Monitor for the non-agent machine.
Overview
Content Tools
Apps
Reporter Replacement
com.bmc.atlassian.bmc-util-plugin-2.section.label
Tasks