Role of Wuser32.exe on Clients
The Remote Control Agent, Wuser32.exe, is the key component for conducting all remote control operations and most other Remote Tools functions on clients. To determine whether the agent is started on clients running Windows NT 4.0 or later, you can use the Processes tab in Windows Task Manager. To determine whether the agent is started on clients running Windows 98, you can use the client's Control Panel. In Control Panel, double-click Remote Control, and then click Show Status. If the Remote Control Status dialog box opens, the agent is running. You can also use the client's Control Panel as an alternative way to determine whether the agent is started on clients running Windows NT 4.0 or later.
Wuser32.exe starts and runs in different ways, depending on the client's operating system.
On This Page
On Clients Running Windows NT 4.0 or Later
On Clients Running Windows 98
On Clients Running Windows NT 4.0 or Later
On clients running Windows NT 4.0 or later, Wuser32.exe runs as a standard service. This service appears as SMS Remote Control Agent in the Services list. By default, its startup type is set to Automatic. Because Wuser32.exe is a standard Windows service, you can use the net start or net stop commands to stop and restart Wuser32.exe. When you use these two commands, either the full service name (SMS Remote Control Agent) or the short name (Wuser32.exe) works.
Note
- You need administrative credentials to start or stop this service.
To stop and restart Wuser32.exe
To stop the service, type net stop wuser32 at the command prompt.
To restart the service, type net start wuser32 at the command prompt.
Note
- If, for testing purposes, it is necessary to run the Remote Control Agent as a non-service (which places the agent in the context of the logged-on user) on a client running Windows NT 4.0 or later, use the following command option: wuser32 /nosvc.
On Clients Running Windows 98
On clients running Windows 98, Wuser32.exe runs as a background application, instead of a service. Because of this, Wuser32.exe does not appear in the process list in Windows Task Manager. Wuser32.exe runs as a child process that is started by SMS Client Services (Clisvc95.exe) under the RunServices registry key. This is why you do not find Wuser32.exe listed under the regular Windows \Run and \RunServices registry keys. You can stop and start Wuser32.exe manually by running the Wuser32.exe file from the command line.
To stop and restart Wuser32
To stop the service, change the directory to %SystemRoot%\MS\SMS\Clicomp\RemCtrl at the command prompt, type wuser32 /x, and then press ENTER.
To restart the service, change the directory to %SystemRoot%\MS\SMS\Clicomp\RemCtrl at the command prompt, type wuser32, and then press ENTER.
For More Information
Did you find this information useful? Please send your suggestions and comments about the documentation to smsdocs@microsoft.com.