Device Monitoring Studio Server - TODO
Download Device Monitoring Studio Server Hide this button

Management MMC Snap-In

During installation, Device Monitoring Studio Server installs a configuration MMC Snap-In. A link to snap-in is added to Start Menu and the snap-in is also available in the list of all snap-ins.

Administration MMC Snap-In

This snap-in is used for two purposes: administration and management.

Snap-in provides you with three types of objects:

Currently, there can be only one computer object (administration of remote servers is not supported yet).
A connection represents a single client connection to the server.
A session represents a single monitoring session from a client.


For the purposes of administration, Device Monitoring Studio Server Management MMC Snap-In provides you with the Properties command on the Computer node. After invoked, it opens the following window:

General Page Security Page

General Page

General page contains two settings: here you may control whether the server accepts connections and whether it is available for auto-discovery.

Security Page

Device Monitoring Studio Server supports Windows Security. This page allows you to configure users and groups and grant them required rights. The following permissions are defined:

Connect to serverA user is allowed to establish a connection to the server. This permission must be granted for any other permission to be effective.
Auto-discoverIf a user is granted this permission to the server, he will see it in the auto-discovery list in Connect to New Server window in Device Monitoring Studio client. Connect to server permission must also be granted.
Create monitoring sessionA user must have this permission to start monitoring session. Connect to server permission must also be granted to him. If the user has this permission, it may monitor any supported device.
Restart DeviceThis permission is required to restart any supported device connected to the server. Connect to server permission is also required. Note: this permission is currently ignored and no remote restart is implemented.

Note that if you change the security settings of the server, they will become effective only when all current connections are closed. You may force this by manually dropping connections.



For each connection, the following information is displayed:

Name of the user who established a connection.
Name or address of the computer user's client is running on.
Current connection status. Disconnected connections are automatically removed from the list.
Session ID
ID of the client's session on his computer.
Process ID
ID of the client's process on his computer.
Shows if the client is 32-bit or 64-bit.

The following commands are provided to the administrator:

Drop Connection
Disconnect the connection and all its sessions.
Send Messageā€¦
Send a text message to the client over the connection.
Drop All Sessions
Drops all connection sessions but does not disconnect a connection.


For each session, the following information is displayed:

A list of devices monitored by this session.
Session status, including server and client pause.
Bytes Transferred
A number of bytes collected and transferred by this session.
Creation Time
Session creation time.
Data Source
The type of the device(s) this session monitors.
Active duration of the session.

Information is automatically refreshed every 5 seconds.

The following commands are provided to the administrator:

Drops this session.
Pauses the session. Note that a session may be paused on the server and on the client separately. A client is not notified if the session is paused on the server. The status column shows whether the session is paused on server, client, or both.
Resumes a session paused on the server.