Installing Message Queuing Servers

Updated: June 25, 2007

Applies To: Windows Server 2008, Windows Vista

This topic covers the installation of Message Queuing server software on computers running on platforms from the Windows 7 and Windows Server 2008 R2 families that do not have previous versions of Message Queuing installed.

For the purposes of this documentation, the term Message Queuing server refers to a Windows 7 or Windows Server 2008 R2 family computer that has Message Queuing installed. The term Message Queuing client can refer to either an independent client or a dependent client. Both of these terms are used to describe Message Queuing servers that have particular Message Queuing components installed. For more information about dependent clients see Dependent Clients. For more information about independent clients see Independent Clients.

noteNote
Message Queuing 5.0 cannot be installed as a dependent client. A Windows Server 2008 R2 computer with Message Queuing 5.0 installed can still act as a supporting server for computers with earlier versions of Message Queuing that are installed as a dependent client. Message Queuing 5.0 only supports dependent clients that are installed on the Windows 2003 (or later) operating system.

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 later) operating system.

Before installing a Message Queuing server on a Windows 7 or Windows Server 2008 R2 family computer in a particular site, verify that there is at least one Windows Server 2008 R2, Windows Server 2008, Windows Server 2003 or Windows 2000 domain controller trusted for delegation in the local site or in a nearby site. To reduce replication traffic, configure a Windows Server 2008 R2, Windows Server 2008, Windows Server 2003 or Windows 2000 domain controller in each site as a global catalog server. During setup, an attempt is made to automatically detect the nearest Windows Server 2008 R2, Windows Server 2008, Windows Server 2003 or Windows 2000 domain controller in the local site or in a nearby site.

If a Windows Server 2008 R2, Windows Server 2008, Windows Server 2003 or Windows 2000 domain controller is not available, you can also start the installation again and install Message Queuing without the directory service integration feature. If this option is chosen, only private queues can be created and managed, direct connectivity is needed to send messages, and the computer will never try to access Active Directory Domain Services. In the context of Message Queuing, any mode of operation that does not allow access to Active Directory Domain Services is called workgroup mode, even if the applicable computer belongs to a domain.

Alternatively, Message Queuing can be installed on a computer that belongs to a workgroup and has not joined a domain. In this case, Setup will install Message Queuing in workgroup mode. In this mode of operation, only private queues can be created and managed, and direct connectivity is needed to send messages. However, in this case, the directory service integration feature will be installed, but the computer will not be able to access Active Directory Domain Services and will continue to operate in workgroup mode until it joins a domain. After the computer joins a domain, the next time you restart it, or stop and restart the Message Queuing service, Message Queuing will automatically attempt to access Active Directory Domain Services through a domain controller in the local domain and create an msmq object.

Similarly, if a Message Queuing server is taken offline or if all the domain controllers from its domain in the local and nearby sites are offline, the computer will not have access to Active Directory Domain Services and will operate in offline mode. As in workgroup mode, only private queues can be created and managed and direct connectivity is needed to send messages. Each time the computer is restarted, Message Queuing will attempt to locate its domain controller. If successful, Message Queuing will return to the domain mode of operation, which enables access to Active Directory Domain Services.

Before you can install a Message Queuing server, the following requirements must first be met:

  • To install a Message Queuing server on a Windows Server 2008 R2 family domain controller, you must be logged on with domain administrative permissions or belong to the Domain Admins group.

  • To install a Message Queuing server with routing services on a non-domain controller, you must be logged on with enterprise administrative permissions or belong to the Enterprise Admins group.

  • To install Message Queuing, you may also need the Delete MSMQ Configuration Objects permission, because if Setup finds an msmq (MSMQ Configuration) object in Active Directory Domain Services, it must delete the object before creating a new one.

  • To uninstall Message Queuing, you must be granted the Delete MSMQ Configuration Object permission.

For more information about the administrative permissions required for installation, see Installation Permissions.

In a domain environment, when Message Queuing servers are installed on additional Windows 7 or Windows Server 2008 R2 family computers in the same site, Setup automatically attempts to locate a Windows Server 2008 R2, Windows Server 2008, Windows Server 2003 domain controller, or Windows 2000 domain controller, in the local or a nearby site.

If you are installing a Message Queuing server on Windows Server 2000 with the Routing Service feature in a mixed-mode domain environment, you must specify the name of a Windows Server 2008 domain controller running Message Queuing with Windows 2000 Client Support or a Windows Server 2003 / Windows 2000 domain controller hosting a Message Queuing server in the same site if prompted during setup.

noteNote
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.

You can also choose to install a Message Queuing server without routing on a non-domain controller in a workgroup environment (or any other environment that does not provide a directory service such as Active Directory Domain Services). In this case, direct connectivity is required to send messages.

See Also

Community Additions

ADD
Show: