Deploying in workgroup mode
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
Deploying in workgroup mode
For Message Queuing, any mode of operation that does not allow access to Active Directory is known as workgroup mode. Note that this is regardless of whether a computer belongs to a domain, and that computers that belong to a domain can operate in workgroup mode. Computers in workgroup mode require direct connectivity with a destination computer for messaging.
Computers that belong to a domain
If you are installing Message Queuing on a computer that is a member of a Windows Server 2003 or Windows 2000 domain, you can specify whether the computer will operate in domain mode, by installing the Active Directory Integration subcomponent, or in workgroup mode, by not installing the subcomponent. In the context of Message Queuing, workgroup mode can be defined as any mode of operation that does not allow access to a directory service, even if the applicable computer belongs to a domain.
The default installation setting is that the Active Directory Integration component is installed, and when your computer is part of a domain, Setup will attempt to contact a Windows Server 2003 or Windows 2000 Server domain controller in the local site or a nearby site. If successful, the computer will operate in domain mode, meaning that access to Active Directory will be enabled. If one of these domain controllers cannot be located, you will be prompted for the name of an MSMQ 1.0 PEC or PSC (in a Windows NT 4.0 enterprise) in the local site. If you do not supply such a name, and select Next in the setup process, Message Queuing will be installed in workgroup mode. In such a situation, where the Active Directory Integration subcomponent is installed but the computer is unable to access a domain controller, the next time you restart such a computer, or stop and restart the Message Queuing service, Message Queuing will automatically attempt to contact a domain controller in the local domain. If a domain controller is available and contact is successful, the computer will then operate in domain mode.
Computers that do not belong to a domain
For computers that are not part of a domain and have no access to Active Directory, during default setup they are installed as independent clients in workgroup mode. The Active Directory Integration subcomponent is still installed, and if the workgroup computer later joins a domain, this subcomponent is activated. Conversely, a Message Queuing computer can be part of a domain and then join a workgroup. Such a computer can later rejoin the same domain.
The following restrictions exist when using Message Queuing in workgroup mode:
Computers in workgroup mode require direct connectivity with a destination computer, and only support direct message transmission. Messages sent by such computers cannot be routed.
There is no access to Active Directory. As such, you can create and manage private queues only on a local computer. You can view the list of private queues on another computer, and the messages in them, using the Computer Management snap-in. For information on managing queues on remote computers, see Manage queues on other computers. You cannot view or manage public queues or any other information in Active Directory. You can, however, send messages to or retrieve messages from private queues if there is direct connectivity.
Internal certificates cannot be used for sending authenticated messages; an external certificate must be used. For more information on user certificates, see Managing user certificates.
Messages cannot be encrypted. For more information on encryption, see Encryption for Message Queuing.
There is no support for dependent clients. For more information on restrictions on the deployment of dependent clients, see Dependent clients.
Cross-platform messaging is not supported. For more information, see Cross-Platform Messaging.
Joining a Windows NT 4.0 domain
When a computer running Message Queuing in workgroup mode joins a Windows NT 4.0 domain, the installation subcomponent for Active Directory Integration is removed. After the computer has been joined to the domain and rebooted, open the Control Panel, double-click Add or Remove Programs, click Add/Remove Windows Components, and in the Windows Components Wizard, select Application Server, click Details, select Message Queuing, click Details, and select Active Directory integration.