SMS: Forced Disconnect Not Available on NetWare Distribution ServersID: Q202063
|
If a client has a file open when a distribution process tries to copy files to the target distribution servers, the distribution may fail or go into an endless retry cycle.
WARNING: Using Registry Editor incorrectly can cause serious problems that
may require you to reinstall your operating system. Microsoft cannot
guarantee that problems resulting from the incorrect use of Registry Editor
can be solved. Use Registry Editor at your own risk.
For information about how to edit the registry, view the "Changing Keys And
Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete
Information in the Registry" and "Edit Registry Data" Help topics in
Regedt32.exe. Note that you should back up the registry before you edit it.
If you are running Windows NT, you should also update your Emergency
Repair Disk (ERD).
With Systems Management Server 1.2, a registry option was introduced to force a disconnection of the client so the distribution phase could complete. The registry entry is located at:
The Use Forced Disconnect parameter should have a value of 1.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Components\SMS_Despooler
Microsoft has confirmed this to be a problem in Systems Management Server version 2.0.
This setting is still available in Systems Management Server 2.0. However, this setting only applies to Windows NT distribution servers, and not to Novell NetWare distribution servers.
For additional information about how to force disconnect Windows NT distribution servers, please see the following article in the Microsoft Knowledge Base:
Q128458 SMS Despooler Does Not Support Forced Installation and Upgrade
Additional query words: prodsms sms20 novel novell
Keywords : kbSMS200 kbSMS200bug kbDespooler kbNovell kbbug2.00
Version : winnt:1.2,2.0
Platform : winnt
Issue type : kbbug
Last Reviewed: February 20, 1999