Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Known Issues for Administering Message Queuing

Updated: June 25, 2007

Applies To: Windows Server 2008

Review the following known issues before administering Message Queuing:

  • Public queues cannot be created when Message Queuing is installed in workgroup mode. For more information about creating public queues see Public and Private Queues.

  • Windows 2000 computers running Message Queuing 2.0 must have access to a either a Windows Server 2008 domain controller running the Windows 2000 Client Support feature to provide the Message Queuing directory service, or a Windows 2000 domain controller hosting a Message Queuing server in its site and its domain to access such objects in Active Directory Domain Services.

    The Windows 2000 Client Support feature has been removed from Message Queuing 5.0. To support message queuing on Windows 2000 down-level clients, at least one Windows Server 2003 or Windows Server 2008 domain controller with Windows 2000 Client Support feature must be configured in the domain.

  • Message Queuing 5.0 cannot be installed as a dependent client. A Windows Server 2008 computer with Message Queuing 4.0 installed can still act as a supporting server for computers with earlier versions of Message Queuing that are installed as a dependent client. Since support for versions of Windows earlier than Windows 2000 has been deprecated upon the release of Windows Server 2008, Message Queuing 4.0 only supports dependent clients that are installed on the Windows 2000 or Windows Server 2003 operating systems.

    The Windows 2000 Client Support feature has been removed from Message Queuing 5.0. To support message queuing on Windows 2000 down-level clients, at least one Windows Server 2003 or Windows Server 2008 domain controller with Windows 2000 Client Support feature must be configured in the domain.

  • As of the release of Message Queuing 4.0, the only supported server authentication method between clients and servers is Kerberos V5. Message Queuing 1.0 and 2.0 (when running against an MSMQ 1.0 controller server on NT 4.0) supported the use of Server certificates. Since the support lifecycle for all operating systems that run MSMQ 1.0 has ended, the use of Server certificates as a Server authentication method is no longer supported.

  • The default behavior of this version of Message Queuing may have been changed from previous versions of Message Queuing in order to enhance security under certain conditions. For more information about these changes see Security Enhancements that Affect the Default Behavior of Message Queuing.

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.