Prevent Message Queuing 2.0 from moving to Active Directory when you join a Microsoft Windows 2000 domain

This article has been archived. It is offered "as is" and will no longer be updated.
Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
When a computer that is running Microsoft Windows 2000 joins a new domain, Microsoft Message Queuing, also known as MSMQ, 2.0 automatically tries to use a directory server in the new domain as its Message Queuing Active Directory server if the domain controller has Message Queuing 2.0 installed. This behavior may be problematic if the computer is a member of a Microsoft Windows NT 4.0 Message Queuing 2.0 enterprise and if you want the computer to remain a member of that enterprise.

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
260910 How to obtain the latest Windows 2000 service pack

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows 2000 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
    Date         Time   Version            Size    File name   --------------------------------------------------------------   05-Mar-2003  22:31         281,360  Mq1repl.dll   04-Feb-2003  15:51          14,096  Mq1sync.exe         19-Feb-2003  17:21          75,408  Mqac.sys   05-Mar-2003  22:31         217,360  Mqads.dll   30-Oct-2002  16:43          25,360  Mqbkup.exe   05-Mar-2003  22:31          76,560  Mqdscli.dll   05-Mar-2003  22:31          41,744  Mqdssrv.dll   21-Oct-2002  20:31          98,064  Mqmig.exe   05-Mar-2003  22:31         265,488  Mqmigrat.dll        05-Mar-2003  22:31         222,480  Mqoa.dll   05-Mar-2003  22:31           8,464  Mqperf.dll   05-Mar-2003  22:31         427,280  Mqqm.dll   05-Mar-2003  22:31         102,672  Mqrt.dll   05-Mar-2003  22:31          70,928  Mqsec.dll   05-Mar-2003  22:31         400,656  Mqsnap.dll          05-Mar-2003  22:31          23,824  Mqupgrd.dll   05-Mar-2003  22:31         110,352  Mqutil.dll   05-Mar-2003  22:31          64,784  Msmq.cpl				
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

This problem was first corrected in Microsoft Windows 2000 Service Pack 4.
For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the following article number to view the article in the Microsoft Knowledge Base:
265173 The Datacenter program and Windows 2000 Datacenter Server product
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.This hotfix must be installed and the following registry parameter must be set before the Windows 2000 server is moved to the Windows 2000 domain.

Follow these steps, and then quit Registry Editor:
  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following key in the registry:
  3. On the Edit menu, point to New, and then click DWORD Value.
  4. Type KeepCurrentDomain, and then press ENTER.
  5. On the Edit menu, click Modify.
  6. Type 1, and then click OK.
When you set Message Queuing 2.0 to 1, it still refers to its old server after you change the computer domain.

Article ID: 815643 - Last Review: 02/27/2014 21:17:42 - Revision: 3.4

  • Microsoft Message Queuing 2.0
  • kbnosurvey kbarchive kbhotfixserver kbqfe kbwin2ksp4fix kbbug kbfix kbwin2000presp4fix KB815643