Microsoft KB Archive/176549

= INFO: Using E-mail to Send Unattended Install Scripts =

Article ID: 176549

Article Last Modified on 8/20/2007

-

APPLIES TO


 * Microsoft Message Queue Server 1.0

-



This article was previously published under Q176549



SUMMARY
The information in this article applies only to the version of Microsoft Message Queue Server (MSMQ) packaged with Microsoft NT Server 4.0 Enterprise Edition. There is a separate article dealing with unattended install scripts and the version of MSMQ bundled with the Microsoft NT Option Pack.

This article describes how to create a series of batch files to automate the unattended installation of MSMQ Independent and Dependent clients and MSMQ servers. A batch file can be inserted into an email message with instructions for the user to double click the batch file icon. This automatically starts an unattended installation of MSMQ Client or Server software from an install share on an MSMQ Server. The Msmqinst.ini file automatically sets all MSMQ settings. However, Windows 95 requires the Distributed Component Object Model for Windows 95 (DCOM95) prior to installation.



MORE INFORMATION
When determining your client rollout process it is important to consider the topology of the MSMQ Enterprise Network. For example, let's say you are an administrator of a firm's computer systems. You have a Primary Enterprise Controller (PEC) located at the headquarters in Seattle. The Primary Site Controllers (PSC) are required at three regional branches in Chicago, New York, and Atlanta. There are 1,000 Independent MSMQ Clients at each of the four locations. In this case, you need to create a separate batch file for each type of install. PSC, Independent Client and each of the four locations.

Seven different batch files are required for this scenario. The first three are for each PSC at Chicago, New York, and Atlanta. The last four are for the independent client installs in Seattle, Chicago, New York, and Atlanta. The PEC in this case serves as an install share for each of the three PSCs. When these PSCs are installed, each should be set up with its own install share. After the PSCs in Chicago, New York and Atlanta are setup and tested, they can serve as install shares for their individual locations Independent Client installations. You need to create four Msmqinst.ini files, one for each site.

The following lines in a batch file make a net connection to an MSMQ install share and start the unattended MSMQ Setup routine. The batch file can then be sent in an e-mail message to the individuals that need to install MSMQ Independent Client. The following example runs the Setup routine for an Independent Client in quiet mode. @echo off Rem Rem \\server\msmqinst\client.ind\setup /q A separate batch file is required for each type of MSMQ installation. The Setup in quiet mode references the Msmqinst.ini file in either the install folder or the Windows folder. If there is a Msmqinst.ini file in both the MSMQ install folder and the Windows folder, MSMQ Setup uses the Msmqinst.ini file in the Windows folder. The Msmqinst.ini parameters need to be set prior running a Setup.

