Share via

Installing Message Queuing servers

  • Article

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

Installing Message Queuing servers

This topic covers the installation of Message Queuing server software on computers running on platforms from the Windows Server 2003 family 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 Server 2003 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, and such computers are referred to as having independent client functionality or dependent client functionality.

Before installing a Message Queuing server on a Windows Server 2003 family computer in a particular site, verify that there is at least one 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 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 2003 or Windows 2000 domain controller in the local site or in a nearby site. If a suitable domain controller cannot be found, Setup assumes that you are installing a Message Queuing client in a Windows NT 4.0 environment and prompts you for the name of a controller server (PEC or PSC) before Setup can continue.

If a Windows Server 2003 or Windows 2000 domain controller is not available, you can also start the installation again and install Message Queuing without the Active Directory Integration subcomponent. 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. In the context of Message Queuing, any mode of operation that does not allow access to a directory service 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 Active Directory Integration subcomponent will be installed, but the computer will not be able to access Active Directory 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 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 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.

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

  • You must install a Windows Server 2003 family platform from the server family.

  • To install a Message Queuing server on a Windows Server 2003 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 nondomain 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, 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 on the administrative permissions required for installation, see Installation permissions.

Installing additional Message Queuing servers

In a domain environment, when Message Queuing servers are installed on additional Windows Server 2003 family computers in the same site, Setup automatically attempts to locate a Windows Server 2003 domain controller, or Windows 2000 domain controller, in the local or a nearby site. If one cannot be located, Setup assumes that you are installing a Message Queuing client in a Windows NT 4.0 environment and prompts you for the name of a controller server (PEC or PSC) before Setup can continue.

For information on installing Message Queuing servers on additional Windows 2000 computers in the same site, see the version of this topic in the online Help file for Message Queuing in a Windows 2000 computer.

If you are installing a Message Queuing server with routing services in a mixed-mode domain environment, you must specify the name of a Windows Server 2003 domain controller running the Message Queuing directory service (Downlevel Client Support) or a Windows 2000 domain controller hosting a Message Queuing server in the same site (not the name of an MSMQ 1.0 PSC) if prompted during setup.

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