SMS: Autostarting Remote Control Option Is Inconsistent

Last reviewed: April 15, 1997
Article ID: Q158647
The information in this article applies to:
  • Microsoft Systems Management Server, version 1.2

SUMMARY

When you set the Site Properties\Clients to automatically start the Remote Troubleshooting component, you may observe different behaviors, depending on the operating system the client is running. The following list shows the observed behavior for different operating systems:

  • MS-DOS clients: USERTSR and USERIPX are installed and placed in the Autoexec.bat file, to be started automatically when the computer starts.
  • Windows 3.1 and 3.11 clients: USERTSR and USERIPX are installed and started automatically from the Autoexec.bat file. WUSER is installed, but must be started manually, regardless of the 'automatically start this component' setting.
  • Windows for Workgroups clients: USERTSR is not loaded. If the client is a NetWare client, USERIPX is started automatically. WUSER is not started automatically, regardless of the 'automatically start this component' setting.
  • Windows 95 clients: USERTSR and USERIPX are not loaded. WUSER is installed, but must be started manually.
  • Windows NT clients: The Remote Control Agent service is installed and started automatically, regardless of the 'automatically start this component' setting.


Additional query words: prodsms helpdesk diagnostics wuser32 agent
Keywords : kbusage smsremtshoot
Version : 1.2
Platform : WINDOWS
Issue type : kbprb


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 15, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.