| Unattended install of the Web Interface |
|
|
| Written by Playwell, Sunday, 15 October 2006 | ||||||||||||||||||||||||||||||
|
This article will explain in detail how to install IIS and the Web interface unattended The web interface is often an essential part of the Citrix infrastructure. We rely heavily on web interface servers to support Program Neighborhood agent or provide programs both externally and internally. When it’s a bigger environment we like to have the same configuration for web interface servers with a common task. Automating the installation can be a good start. Citrix documented a silent installation of the Citrix Web Interface in article CTX106114. We show you a script that shows a silent install of IIS with the necessary components and the unattended installation of Web Interface including creating a Web Interface and PN agent site on a Windows 2003 server. First we install IIS. We make use of a very handy builtin Windows tool called sysocmgr and an ini file with the components we like to install. The ini file looks like this: [InternetServer] [Components] aspnet = on iis_inetmer = on iis_asp = on iis_www = on This will install IIS including ASP.net, active server pages and the IIS management MMC snapin. Save this file as %windir%\temp\iis.inf. Second we make sure the Windows 2003 CD is available so the source files can be found by Windows. Now we can install IIS by issuing the flowing command: sysocmgr.exe /i:%systemroot%\inf\sysoc.inf /u: %windir%\temp\iis.inf This method can be used to install any Windows component. For more information on how to install other components see the deploy.chm located in the deploy.cab on your Windows 2003 Cd-Rom. Second we install the Access Suite Console including requirements. This is not absolutely necessary but we like to have some control over the web interface after it’s installed. To install Java Runtime Enviroment: "<Citrix Cd-Rom>\Support\JRE1.4.2\j2re-1_4_2_06-windows-i586-p.exe" /S /v/qn To install J sharp we first unpack the jsharp installation file: "<Citrix Cd-Rom>\Support\Jsharp11\Vjredist” /T: c:\windows\temp /C Then install J sharp: " c:\windows\temp \inst.exe" /l /q The install Access suite Console to the default installation path: msiexec /i "<CD-Rom>\Administration\Access Suite Console\CitrixMMC.msi"/l* c:\logs\psc.log /qb- Now we are ready to install the Web Interface. To install the web interface we have 2 choices. The first choice is to unpack the webinterface.exe file with a compression tool like winzip, or winrar and install the MSI with the right parameters. After that we can use the sitemgr tool to add/delete sites from IIS. The second choice is to run webinterface.exe with the right parameters. The annoying part of this installation is that the command line parameters are set in the Windows environment. So we use these lines in batch: set WI_COMMAND_LINE=-q -noasc -g c:\\logs\\wi.log -c "WIDest=1:/Citrix/MetaFrame,Config=Local,FarmName=Example,XMLService=server1.example.local:80;Server2.example.local:80,PNADest=1:/Citrix/PNAgent" "<CD-Rom>\web interface\webinterface.exe" You may ask yourself what do these lines mean exactly. First we set the environment by using set.exe. We tell the installation to be quiet (-q), then we tell it not to look for the Citrix access console (-noasc). Then we tell it to create a log file of the installation to c:\logs\wi.log. The next portion seems a little complicated but it’s not. First we say to create a web interface site in the default site of IIS (widest=). Sites have an identifier in IIS to set them apart and the default site has an identifier of 1. For other identifiers fire this little script to get the names of the site and their identifiers: Set IISOBJ = getObject("IIS://LocalHost/W3SVC") For each Object in IISOBJ if (Object.Class = "IIsWebServer") then WScript.Echo " Site " & Object.ServerComment & " Identifier " & Object.Name end if next After the identifier we state the path of the virtual directory in IIS. In our case the default path (1:/Citrix/MetaFrame). We tell the site to keep the configuration local and we not make use of a configuration server(Config=Local ) and then we tell it to be part of the farm ‘Example’ (Farmname=Example). We point the web interface to xml services on the citrix servers server1.example.local and server2.example.local on port 80 (XMLService=server1.example.local:80;Server2.example.local:80). The last parameter here is to create PN Agent Virtual Directory in the default path(PNADest=1:/Citrix/PNAgent) After setting the parameters the web interface can be installed by running webinterface.exe. If we place the contents of c:\windows\temp to a share on the server \\server\share the script looks like this: sysocmgr.exe /i:%systemroot%\inf\sysoc.inf /u:server\share\iis.inf "<Citrix Cd-Rom>\Support\JRE1.4.2\j2re-1_4_2_06-windows-i586-p.exe" /S /v/qn "\\server\share\inst.exe" /l /q msiexec /i "<CD-Rom>\Administration\Access Suite Console\CitrixMMC.msi"/l* c:\logs\psc.log /qb- set WI_COMMAND_LINE=-q -noasc -g c:\\logs\\wi.log -c "WIDest=1:/Citrix/MetaFrame,Config=Local,FarmName=Example,XMLService=server1.example.local:80;Server2.example.local:80,PNADest=1:/Citrix/PNAgent" "<CD-Rom>\web interface\webinterface.exe" IISreset This will enable you to install web interface on a server in 10 minutes. IIS will be reset so IIS is temporarily unavailable.
Powered by JoomlaCommentCopyright (C) 2006 Frantisek Hliva. All rights reserved.Homepage: http://cavo.co.nr/ |
||||||||||||||||||||||||||||||
| < Prev | Next > |
|---|
|