SMS Program Group Controller and AutoDisconnect

 Last reviewed: April 22, 1997
Article ID: Q121385

The information in this article applies to:
  • Microsoft Systems Management Server versions 1.0 and 1.1

SUMMARY

Windows NT and LAN Manager servers default to 15 minutes of idle time per connection before marking the connection as available for AutoDisconnect. This behavior is intended to keep system resources available, and assumes that clients will transparently reconnect when the client application accesses the server. Sometimes this AutoDisconnect behavior can cause strange application problems such as segment load failures or "drive not ready" errors.

When the Systems Management Server Program Group Controller (PGC) invokes APPSTART to execute a shared application off a server, it opens the executable file in read-only mode and keeps it open until the user exits the application and PGC detects that the connection needs cleaned up.

MORE INFORMATION

This became a critical issue for shared applications under Systems Management Server and this technique eliminates the need to disable AutoDisconnect for the server, and lets PGC manage the connection. The Windows NT Server component correctly maintains the connection for clients running an application through PGC and APPSTART over all supported protocols.

If problems occur:

  • Disable AutoDisconnect and run the application as usual from PGC.

    -or-

  • Run the application from the server, bypassing PGC controls (through File Manager).

If these steps fail to pinpoint the issue, the application may not be network-aware and you should contact the vendor of the application.

Additional query words: directhosting sms prodsms
Keywords : kbnetwork ntconfig ntdomain nthowto smspgc
Version : 1.0 1.1
Platform : WINDOWS

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 22, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.