Browse Prior Art Database

Coordinated hybrid protocol for remote machine management

IP.com Disclosure Number: IPCOM000238133D
Publication Date: 2014-Aug-04
Document File: 2 page(s) / 37K

Publishing Venue

The IP.com Prior Art Database

Abstract

On a UAC enabled remote windows machine, carrying out operations on system Registry and services is not possible. Many of the NetBios over TCP/IP based remote machine management software operations depends on target machine system registry & services to carry out system management. Latest Windows systems come with User Access Control (UAC) to restrict access to the system resources. Even administrators and administrative privileged users are not allowed to access the system resources without requesting elevation. This blocks Netbios based remote machine management clients from carrying out the activity. Even if the client is genuine, legitimate , access will not be possible without elevation. This causes severe broken linkage when installing software on the target machines, or checking health of the target machine or performing other remote management tasks

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 100% of the total text.

Page 01 of 2

Coordinated hybrid protocol for remote machine management

In the following, there is discussion on making use of two coordinated protocols to perform the installations, executions and management of remote windows machines.

Both the http protocol & SOAP messages sent to the web services management module (WSMAN) are considered.

WSMAN service running on the remote machine, acknowledges the SOAP message request coming from the client to establish the connections.

Client encapsulates the required action on the target machine within the SOAP message and sends it to the target machine WSMAN service.

WSMAN service on the target machine creates a resource in the system registry based on the message received from the client.

Client sends NetBios message to read the data from the system resource created by WSMAN services and executes the tasks in that resource.

1


Page 02 of 2

1 . Client module establishes the connection to the windows target machine, and uses WSMAN messages to access the system registry.

Through WSMAN messages client writes an entry in the target machine system registry regarding the activity.

2 . Client module establishes the connection to the windows target machine, and uses WSMAN messages to access the system services.

Through WSMAN messages client starts/stops an service on the target machine.

2