# US 2003/0208573 A1 · Remote execution of software using windows management instrumentation

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2003/0208573 A1
- Document ID: US20030208573A1
- Status: Published application
- Kind: A1
- Application number: 10/021,404
- Filed: 2001-10-30
- Published: 2003-11-06
- Earliest claimed: 2001-10-30
- Assignees: Hewlett-Packard Development Company, L.P.
- Inventors: Brian Harrison; Kyu-Woong Lee; Christina M. Rogers
- Web page: https://patentgrep.com/patent/US20030208573A1

## CPC

- H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)}
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04L 69/329: in the application layer [OSI layer 7]
- G06F 2209/549: Remote execution
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A method for remote execution of software. A device manager instanciates a WMI CreateProcess object on a managed device which will call an executable residing on the device manager. The process is started, calling an executable on the device manager. The executable on the device manager is called and launched on the managed device. The executable starts and finishes on the managed device.

## Claims

### Claim 1

A method for remote execution of software, comprising:
installing executable code on a management device;
communicatively coupling said management device to a remote system;
creating a class object;
executing a create method with a path to said executable code on said management device as an argument;
executing said executable code residing on said management device locally on said remote system.

### Claim 2 (depends on 1)

The method of claim 1 further comprising instanciating an object on said remote system which calls said executable code residing on said management device.

### Claim 3 (depends on 2)

The method of claim 2, wherein a device manager of said management device instanciates said object using Windows Management Instrumentation software.

### Claim 4 (depends on 2)

The method of claim 2 further comprising launching said executable code on said management device.

### Claim 5 (depends on 4)

The method of claim 4 further comprising starting and finishing said executable code by said remote system.

### Claim 6 (depends on 1)

The method of claim 1 further comprising:
installing an application and an uninstall executable code on said remote system;
running said uninstall executable code on said remote system as directed by a device manager of said management device.

### Claim 7 (depends on 6)

The method of claim 6, wherein said uninstall executable code is started on said remote system by instanciating and executing a Windows Management Instrumentation object.

### Claim 8 (depends on 7)

The method of claim 7, wherein said object comprises a CreateProcess object.

### Claim 9 (depends on 6)

The method of claim 6 further comprising:
communicatively coupling to a system/root/cimv2 space of said remote system;
creating a Win32_Process class object;
executing said Win32_Process class object with a path to said uninstall executable code as an argument.

### Claim 10 (depends on 1)

The method of claim 1 further comprising the step of implementing a Web Based Enterprise Management (WBEM) standard to facilitate said remote execution of software.

### Claim 11

A method of remote execution of software between a server and a client using Windows Management Instrumentation (WMI) software, comprising:
installing executable code on said server;
installing said WMI software on said client;
a device manager of said server performing:
a) accessing a system\root\cimv2 space of said client;
b) creating a Win32_Process class object;
c) executing a Win32_Process->Create method with a path to said executable code on said server as an argument;
executing said executable code residing on said server by said client, wherein said executable code is executed locally on said client.

### Claim 12

A client-server system, comprising:
a server having a device manager that instanciates an object which is used to call an executable residing on said server;
a client coupled to said server having said object, wherein once called, said executable is launched on said client once called and said executable starts and finishes remotely on said client.

### Claim 13 (depends on 12)

The client-server system of claim 12, wherein said device manager of said server instanciates a Windows Management Instrumentation (WMI) CreateProcess object on said client.

### Claim 14 (depends on 13)

The client-server system of claim 13, wherein said device manager accesses a system\root\cimv2 space of said client, creates a Win32_Process class object, and executes a Win32_Process->Create method with a path to said executable code on said server as an argument.

### Claim 15

A method for remote uninstallation of software, comprising:
installing an application and an uninstall executable code on a remote system over a network connection;
running said uninstall executable code on said remote system as directed by a device manager running on a management device.

### Claim 16 (depends on 15)

The method of claim 15 further comprising starting said uninstall executable on said remote system by instanciating and executing a Windows Management Instrumentation object.

### Claim 17 (depends on 16)

The method of claim 16, wherein said object comprises a CreateProcess object.

### Claim 18

A method for remote uninstallation of software between a server and a client using Windows Management Instrumentation (WMI) software, comprising:
loading executable code for uninstall of an application during initial installation of said application on said client
installing said WMI software on said client;
a device manager of said server performing:
a) accessing a system\root\cimv2 space of said client;
b) creating a Win32_Process class object;
c) executing a Win32_Process->Create method with a path to said executable code for uninstall on said server as an argument,
wherein said application is remotely uninstalled.

### Claim 19

A client-server system, comprising:
a server having a device manager which installs applications and uninstall executable code on client computers over a network connection;
a client computer coupled to said server which runs said uninstall executable code as directed by said device manager.

### Claim 20 (depends on 18)

The client-server system of claim 18, wherein said device manager starts said uninstall executable code on said client computer by instanciating and executing a Windows Management Instrumentation object.

### Claim 21 (depends on 20)

The client-server system of claim 20, wherein said device manager accesses a system\root\cimv2 space of said client computer, creates a Win32_Process class object, and executes a Win32_Process->Create method with a path to said executable code for uninstall on said server as an argument, wherein said application is remotely uninstalled.

### Claim 22 (depends on 18)

The client-server system of claim 18, wherein a Web Based Enterprise Management (WBEM) standard is used to facilitate remote uninstall of software.
