Installing Independent Clients

Applies To: Windows Server 2008, Windows Vista

An independent client can be defined as an installation of Message Queuing 5.0 on a supported operating system for which the Routing Service feature is not installed. Since the Routing Service feature is not available as a Windows feature on Windows 7, Message Queuing is always installed as an independent client.

This topic covers the installation of Message Queuing servers with independent client functionality on Windows 7 or Windows Server 2008 R2 family computers. Computers configured as independent clients can operate in workgroup mode or Active Directory domain mode. These computers run the Message Queuing service, host queues, send and receive messages, operate while disconnected from the network, access Active Directory Domain Services directly, and when running on Windows Server 2008 R2 family computers, can act as a supporting server for dependent clients. However, for an independent client in workgroup mode, direct connectivity is required to send messages, and the computer cannot act as a supporting server for dependent clients. For more information, see Independent Clients.

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, and such computers are referred to as having independent client functionality or dependent client functionality.

Before installing a Message Queuing server with independent client functionality, note the following:

• To install Message Queuing in domain mode, you must have network connectivity. During installation, if the directory service integration feature is enabled, Setup will automatically attempt to contact a Windows Server 2008, Windows Server 2003 or Windows 2000 domain controller. If this attempt is successful, Message Queuing is installed in domain mode. If this attempt is not successful, Message Queuing will automatically be installed in workgroup mode. 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. The workgroup mode of operation requires direct connectivity to send messages.

• If your computer is in a domain, but without Active Directory Domain Services access, the directory service integration feature (known as the MSMQ Active Directory Domain Services Integration feature on Windows 7) will attempt to access a domain controller and work in domain mode each time the computer, or the Message Queuing service, is restarted. If your computer is not part of a domain and is in workgroup mode, installing this feature provides you with the option of joining the computer to a domain at a later time.

• You must be logged on with local administrative permissions (as a member of the local Administrators group). For more information about the permissions required for installation, see Installation Permissions.

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

• A Message Queuing server configured with independent client functionality does not have the Windows 2000 Client Support feature enabled so independent clients cannot provide Active Directory Domain Services access for Message Queuing 2.0 clients running on Windows 2000 computers.

For more information about using Server Manager or unattended setup to install independent clients, see Installation Overview.