Using C # to control the services of a remote computer

· Using C # to control the services of a remote computer

· http://developer.51cto.com 2006-01-25 16:47 TrackBack tb.blog.csdn.net/trackback I want to comment (2)

Some classes are provided in. NET to display and control services on Windows systems and to enable access to the remote computer Service service. This article explains how to use the System.Management component to manipulate services on remote and local computers.

provides classes in. NET to display and control services on Windows systems, and to enable access to remote computer service services, such as the ServiceController class under the System.ServiceProcess namespace, System.Management the classes of some of the WMI operations below. Although the use of ServiceController can be very convenient to achieve the control of the service, but also intuitive, concise and easy to understand. But I think his functionality is probably a little bit more than just using WMI to manipulate a service, and it can be cumbersome to operate on multiple services and not be able to list the specific data for all the services in the system. Here's how to use the System.Management component to manipulate services on remote and local computers.

WMI provides a scalable, extensible management architecture as part of the Windows 2000 operating system. The Public Information Model (CIM) is an extensible, object-oriented architecture designed by the Distributed Management Task Standards Association (DMTF) for managing systems, networks, applications, databases, and devices. The Windows management specification, also known as CIM for Windows, provides a uniform way to access management information. If you need to get detailed WMI information, ask your reader to review MSDN. The System.Management component provides access to a wide range of management information and management event collections related to system, device, and application setting checkpoints based on the Windows Management Instrumentation (WMI) architecture.

But the above is not our most concern, the following is the topic we need to talk about. There is no doubt that we will refer to the SYSTEM.MANAGEMENT.DLL assembly and use the classes under the System.Management namespace, such as Managementclass,managementobject. The following is a class called Win32servicemanager that wraps some of the relevant operations of the service, the code reads as follows:

Using System; Using System.Management; Namespace ZZ. Wmi { public class Win32servicemanager {private string strpath; Private ManagementClass ManagementClass; Public Win32servicemanager (): This (".", Null,null) { } Public Win32servicemanager (string host,string username,string password) { This.strpath = "////" +host+ "//root//cimv2:win32_service"; This.managementclass = new ManagementClass (strpath); if (username!=null&&username.length>0) { ConnectionOptions connectionoptions = new ConnectionOptions (); Connectionoptions.username = Username; Connectionoptions.password = Password; Managementscope Managementscope = New Managementscope ("////" +host+ "//root//cimv2", connectionoptions); This.managementClass.Scope = Managementscope; } } Verify that you can connect to the remote computer public static bool Remoteconnectvalidate ( String host,string username,string password) { ConnectionOptions connectionoptions = new ConnectionOptions (); Connectionoptions.username = Username; Connectionoptions.password = Password; Managementscope managementscope = new Managementscope ("////" +host+ "//root//cimv2", connectionoptions); Try { Managementscope.connect (); } Catch { } return managementscope.isconnected; } Gets the value of the specified service property public Object Getservicevalue (String servicename,string PropertyName) { ManagementObject mo = This.managementClass.CreateInstance (); Mo. Path = new Managementpath ( This.strpath+ ". name=/"" "+servicename+"/""); return Mo[propertyname];