Microsoft KB Archive/237577

From BetaArchive Wiki
Knowledge Base


How To Create Unattended Installation Scripts for Localized Versions of MSMQ from the Windows NT Option Pack

Article ID: 237577

Article Last Modified on 7/1/2004



APPLIES TO

  • Microsoft Message Queue Server 1.0



This article was previously published under Q237577

SUMMARY

This article describes the creation of the unattended installation scripts required for localized versions of the Windows NT Option Pack.

For background information on Windows NT Option Pack unattended installation scripts, please see:

202139 How To Create an Unattended MSMQ Installation From the Windows NT 4.0 Option Pack


This article assumes that you are familiar with the process outlined in article Q202139.

MORE INFORMATION

The MSMQ portion of the Windows NT 4.0 Option Pack installation procedure has been localized. This does not effect any of the other Option Pack components, but the Msmqinst.ini and Unattend.txt files do require modification for the MSMQ portion to work. The table below gives the English label and then the translated command for French, German, and Spanish. If you require another additional language, please contact Microsoft Product Support Services:

Language: French
Components: Composants
ClientType: ClientType
ServerType: ServerType
ON: ACTIF
Common Parameters: Paramtres communs
Path: Chemin d'accs

Language: German
Components: Komponenten
ClientType: ClientType
ServerType: ServerType
ON: ON
Common Parameters: Allgemeine Parameter
Path: Pfad

Language: Spanish
Components: Componentes
ClientType: TipoCliente
ON: Activado
Common Parameters: Parametros comunes
Path: Ruta de acceso

The following is an example of French unattended installation script. This example is for a Windows NT Workstation, installing a minimal Windows NT Option Pack and an optional MSMQ independent client.

;;mysetup.txt

   [Version]
   Signature="$Windows NT$"

;NOTE: Windows NT Option Pack Setup sets the [Global] section later,
;automatically. You can also specify the installation mode that unattended
;MSMQ Setup runs in, based on the configuration of your target computer.
;For example, if your target computer will:
;
;A) Receive a new MSMQ installation (fresh mode), but no "FreshMode="
;line is specified, then Typical is the default value.
;
;B) Receive a MSMQ re-installation or uninstallation (maintenance mode), 
;but no "MaintanenceMode=" line is specified, then ReinstallComplete is the
;default value.
;
;C) Receive an upgrade of MSMQ (upgrade mode), but no "UpgradeMode="
;line is specified, then UpgradeOnly is the default value.

   [Global]
   FreshMode=Custom
;MaintanenceMode=AddRemove|ReinstallFile|ReinstallComplete|RemoveAll
;UpgradeMode=AddExtraComps|UpgradeOnly

;NOTE: the [Components] section below is valid only when
;FreshMode = Custom, MaintanenceMode = AddRemove, and
;UpgradeMode = AddExtraComps
;for the [Global] section above.

;Note: The following [Components] selections for PWS are used For WinNT 
;Workstation and Win9x. For WinNT Server, 
;iis and it's supporting ;parameters should be used.
   [Composants]

   Msmq_Client_Core=ACTIF
   Msmq_Admin=OFF
   Msmq_Doc=OFF
   Msmq_SDK=OFF

   [Components]

   ; pws
   iis_common = ON
   iis_www = OFF
   iis_pwmgr = OFF
   iis_doc_common = OFF
   iis_doc_pwmcore = OFF
   iis_doc_asp = OFF

   ;mts
   Mts_Core=ON
   Mts_Mmc=ON

;The following MSMQ Core Components lines should be changed to match the 
;type of Windows Operating system.
;
;Msmq_Server_Core should be used for WinNT Server installs.
;Msmq_Client_Core should be used for Win95, Win98, and WinNT Workstation. 
;You must change the [Msmq_Server] section header below to match.
;You must change the ServerType= and ClientType= to match also. For ;example,:
;if you are installing an MSMQ Client to an NTServer computer, you can 
;specify Msmq_Server_Core=ON and [Msmq_Server] with ServerType=IND in the ;msmq path section below.

   Msmq_Client_Core=ON
   Msmq_Admin=OFF
   Msmq_Doc=OFF
   Msmq_SDK=OFF

   ;iis path parameters:
   [iis]
   Path=c:\myunatten\myiis
   PathFTPRoot=c:\myunatten\myinetpub\ftproot
   PathWWWRoot=c:\myunatten\myinetpub\wwwroot
   PathPROGRoot=c:\myunatten\myprogroot

   ;mts path and security params:
   [mts_core]
   Path=c:\myunatten\mymtx
   USERID=domain\username
   PASSWORD=enterpassword

;If you install an MSMQ client on a computer running Windows NT
;Workstation 4.0, or Windows 95/98, you must replace the [Msmq_Server]
;section with [Msmq_Client], and the ServerType entry with ClientType.
;ClientType values ;include IND (independent client) and DEP (dependent

;client). You must also set Msmq_Server_Core=ON or Msmq_Client_Core=On
;to match.

;msmq path parameters:
   [Msmq_Client]
   Chemin d'acces="c:\Program Files\msmq"
  ;Path="c:\Program Files\msmq"
   ClientType=IND 
                

Note that in this script, these are the lines that differ from the example used in Q202139:

[Composants]

Msmq_Client_Core=ACTIF

Chemin d'acces="c:\Program Files\msmq"
                


Sample Msmqinst.ini

The following is a sample Msmqinst.ini file with a primary enterprise controller (PEC) server name of "Pacific" and with a site name of "Islands", and a connected network named "IPCN". You must edit this text file to appropriately reflect your desired configuration. If you will only be installing MSMQ clients, then only the top three lines are necessary.

When MSMQ Setup is running, it first looks in the local Windows folder for an Msmqinst.ini file. If it does not find one, it looks in the default share location. If you have multiple configurations, you can put different versions of the Msmqinst.ini file in separate folders on the share and copy the appropriate Msmqinst.ini file locally prior to the call to Setup.

;;msmqinst.ini

   [Parametres communs]
   ControllerServer=Pacific
   Supporting Server=Pacific
   ;the lines below this point are used only for MSMQ Servers:
   DataDevice=c:\msmq,80
   LogDevice=c:\msmq,20
   IPAddresses=IPCN IP
   StopServices=Allow

   ; Setup uses the following section to install a PSC on a server computer
   ; named Lanai to the PEC named Pacific. This PSC's Site will be named
   ; Kanaha. The Site Link Costs will be 10. Note: There is NO cost based
   ; routing in the Option Pack version of MSMQ, and the SiteLinks
   ; parameter can be removed:

   [Lanai]
   ControllerServer=Pacific
   ServerType=PSC
   SiteName=Kanaha
   SiteLinks=10

   ; Setup uses the following section to install a BSC on a server computer
   ; named Molokai to the PEC named Pacific in the Islands Site:

   [Molokai]
   ControllerServer=Pacific
   ServerType=BSC

   ; Setup uses the following section to install
   ; an MSMQ routing server named Kahulawe to the Islands Site:

   [Kahulawe]
   ControllerServer=Pacific
   ServerType=RS

Note that in the script above, the following line differs from the example in Q202139:

[Parametres communs]
                

Keywords: kbhowto KB237577