Using CA AppLogic® › Appliance Developer Guide › Creating Appliances › Distribution Installations › Windows Installation Reference › Windows Server 2003 Two CD Installation Reference

Windows Server 2003 Two CD Installation Reference

This installation is based on a two CD install of Windows 2003 Server Standard Edition R2. For the example, you use two global volumes named win03-disk-1_iso and win03-disk-2_iso See the iso2class reference for other methods about specifying an ISO image for the installation.

You may also use the following example for other Windows editions:

• Enterprise
• DataCenter
• Web

Note: In the following text, the y in WIN03y indicates the Windows edition, such as S for Standard, E for Enterprise, DC for DataCenter, W for Web, on which the application was based.

To install and configure a WIN03y appliance using two CDs

1. Execute the following command in a 3T shell and select 32 or 64 bits and operating system:

   util iso2class app_name=win03_install install_size=10G console_type=graphic iso_volume1=win03-disk-1_iso iso_volume2=win03-disk-2_iso virt_options=acpi=1 cpu=1 mem=1G
   

   This command creates and starts the win03_install application, booting the singleton iso2class from the specified ISO image.

   Note: Initially, the volume size is set to 10GB. The system uses this size to verify there is enough disk space for the Windows installation. After the appliance is created, you can resize the volume depending upon the amount of free disk space remaining after the Windows installation. It is recommended to have at least 500MB of free disk space.

2. Access the graphic console of the singleton in one of the following two ways:
   • Select the application within the application list in the CA AppLogic® GUI and select Login (graphic).
   • Open the application in the infrastructure editor and select the singleton iso2class. Use the pull-down Appliance menu to select Login (graphic).

   Note: During Windows installation on a VMware grid, the mouse may not function as expected, due to the absence of VMware tools. The following keyboard shortcuts are useful:

   • To navigate between buttons use Tab key and / or arrow keys
   • To select use space bar or enter
   • To access the file menu of the selected window use Alt+f key
3. After the graphical console displays, the Windows 2003 Server installation should be visible.

   Proceed through the installation using the following notes:

   • Use a single NTFS partition.
   • Disable file and printer sharing for both network interfaces.
   • Use a work group.
4. When the installation from the first CD completes, Windows reboots and then displays the message that Windows Setup is not complete and requests the Windows Server CD2. At this point, in the 3t shell, continue with the iso2class utility.

   The utility stops the application and changes its descriptors:

   • The target volume of the OS install is made the boot volume.
   • The second CD iso_volume2 is made a secondary disk.

     If you are creating Windows appliance on ESX grid and VM tools gets mounted on Drive E:

     • Login through the graphical console
     • Press “Ctrl+Alt+Del” button on the center top of the graphical console window
     • Click inside the graphical console window
     • Using ‘tab’ and ‘arrow keys’ navigate to “start task manager”
     • Using ‘tab’, navigate to “new task” and hit ‘spacebar’
     • Type “E:\setup.exe /S /v /qn” to execute VMware tools installation silently

   The installation automatically reboots the appliance. After reboot, you must reopen the graphical console and login to the appliance.

5. Access the console and continue with the installation. The second CD auto mounts as drive D. Access this drive in Windows Explorer and execute the secondary installer, such as R2AUTO.EXE
6. After the installation completes:
   • If the VM tools were not installed during Step4 and you are creating Windows appliance on ESX grid, install VMware tools as follows:
     • Stop the application
     • In grid shell execute 3t vol copy _GLOBAL_RO:vmware_tools_windows APPNAME:vmware_tools_windows
     • Open infrastructure editor in browser
     • Right-click the singleton appliance ‘iso2class’ and select ‘user volumes’
     • Select volume ‘vmware_tools_windows’ for placeholder iso_volume1
     • Save and start the application
     • Login through the graphical console
     • Press “Ctrl+Alt+Del” button on center top of the graphical console window
     • Click anywhere inside the graphical console window
     • Using ‘tab’ and ‘arrow keys’ navigate to “start task manager”
     • Using ‘tab’ navigate to “new task” and press ‘spacebar’
     • Type “D:\setup.exe /S /v /qn” to execute VMware tools installation silently.

   The installation automatically reboots the appliance.

   After reboot, reopen the graphical console and login to the appliance.

   • Disable the page file:
     1. Open Control Panel, System, Advanced, Performance Settings, Advanced, Virtual Memory, No Paging File, Set to disable the page file.
     2. Restart the application.
     3. Open Windows Explorer, Tools, Folder Options, View and select Show hidden files and folders. Unselect Hide protected operating system files.
     4. Verify the page file: C:\pagefile.sys has been deleted. If not, delete it manually. You can view protected operating system files in Windows Explorer by changing the default settings:
     • Open Windows Explorer, Tools, Folder Options, View and reset Hide protected operating system files.
7. Increase the default Windows disk device timeout value in your appliance and set the value for the real time clock. Note that these settings require a reboot to take effect.
   1. Open the registry editor (Run > regedt32.exe) and navigate to the key HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/Disk.
   2. Add a new REG_DWORD value named TimeOutValue If this value already exists, skip this step.
   3. Set the TimeOutValue value to 60 decimal.
   4. Navigate to the key HKEY_LOCAL_MACHINE/System/CurrentControlSet/Control/TimeZoneInformation and set the value for RealTimeIsUniversal to 1. If this DWORD does not exist, create it and set it to 1.
   5. Close the registry editor.
8. Verify you have external network access through the external interface of the singleton. The singleton has two network interfaces: Local Area Connection which is an external interface and Local Area Connection 2 which is the internal interface.

   Open a command shell and ping www.google.com.

   If the ping fails, do one of the following:

   • Access Control Panel, Network Connections, Local Area Connection, Properties, Internet Protocol (TCP/IP), Properties. Click on Use the following IP address and enter usable values for your grid (IP Address, netmask, gateway, DNS server).
   • Execute the following commands in the command shell:

     netsh interface ip set address name="Local Area Connection" static [ip-address] [netmask] [gateway] 1 
     netsh interface ip set dns name="Local Area Connection" static [dns-ip] 
     

9. Install Service Pack 2 and high priority updates:
   1. Open IE and use Tools, Internet Options, Security to set the Internet security to medium.
   2. In IE, select Tools, Windows Update and install SP2. Reboot when the install completes.
   3. Remove the restore files associated with the installation of SP2:
      • Use Windows Explorer to delete the folder c:\WINDOWS\$NtServicePackUninstall$
      • Empty the Recycle Bin
      • Use Windows Explorer to compress the folder c:\WINDOWS\ServicePackFiles and all sub-directories:
      • Right-click the c:\WINDOWS\ServicePackFiles folder and select Properties, Advanced, Compress contents.
   4. In IE select Tools, Windows Update and install all the high priority updates. Optionally decline the unstable IE updates.
   5. Use Windows Explorer version 8 or higher to remove the restore files associated with the installation of the high priority updates:
      • Delete c:\WINDOWS\$*$ (approximately 30 folders)
      • Empty the Recycle Bin.
10. Install the Windows Server 2003 Resource Kit Tools:
    1. Point IE at http://www.microsoft.com/downloads/details.aspx?FamilyID=9D467A69-57FF-4AE7-96EE-B18C4790CFFD&displaylang=en or search online for Windows Server 2003 Resource Kit Tools.
    2. Install the tools in their default location C:\Program Files\Windows Resource Kits\Tools
11. (Optional) Install the Windows components which you want available on this appliance and which require access to the installation ISO images.

    Select Control Panel, Add or Remove Programs, Windows Components and install optional components such as IIS.

12. To prevent system shutdown dialogs from displaying the reason for system shutdown
    1. Open the Start menu and run gpedit.msc
    2. Go under Computer Configuration, Administrative Templates
    3. Click System
    4. On the right pane, double-click Display Shutdown Event Tracker
    5. Select Disabled and click Apply
13. Activate Windows, as required.
14. For 64-bit appliances, a Microsoft Windows bug prevents a 32-bit application to access the System32 folder on a computer running a 64-bit version of Windows Server 2003.

    For additional information about this issue, including fixing the issue, see http://support.microsoft.com/kb/942589 and apply this hotfix according to its instructions.

15. To transform this singleton into a fully managed appliance, install the Windows Server msi. This self-executing installer can be downloaded from the D or E drive.
    1. To locate the internal IP address of the controller, in a command line shell execute ipconfig /all and note the IP address of the DHCP server for Local Area Connection 2.
    2. Point IE at http://IP-address:8080/download/ and download the current Windows Server msi. For example, Server_Windows-1.0.0-1.msi:
       • Right-click the msi file and select Save Target As to download the file to the desktop.
    3. Double-click the msi file on the desktop to perform the installation.
    4. Delete the msi file and empty the Recycle Bin.
    5. If you manually configured the external interface, use Control Panel, Network Connections, Local Area Connection, Properties, Internet Protocol (TCP/IP), Properties to reset the interface to DHCP (Obtain an IP address automatically).
16. If this is a 64-bit appliance, use Windows Explorer to copy shutdown.exe from C:\WINDOWS\system32 to C:\WINDOWS\SYSWOW64.

    If Windows Explorer fails to copy, but instead moves the executable:

    1. Move shutdown.exe to C:\WINDOWS using Windows Explorer
    2. Open a bash shell and:
       • cp -p /cygdrive/c/WINDOWS/shutdown.exe /cygdrive/c/WINDOWS/system32/shutdown.exe. This command actually copies the file into C:\WINDOWS\SYSWOW64
       • Use Windows Explorer to move C:\WINDOWS\shutdown.exe to C:\WINDOWS\system32\shutdown.exe
17. If you are installing a 64-bit non-English localized version of Windows Server 2003, copy chcp.com from C:\WINDOWS\system32 to C:\WINDOWS\SYSWOW64 as described above.
18. Close the graphical console and close the infrastructure editor, if open.

    The installation is complete.

    • Press the [Enter] key in the 3T shell running iso2class to continue. When prompted, select The appliance is fully managed.

    After this, iso2class stops the application, changes the singleton boundary to that of a generic server appliance, and restarts the application.

19. If iso2class fails to start the application, select option #2 - "Exit from iso2class and investigate manually".
    • Start the application in debug mode: in 3Tshell execute the command app start app_name --debug.

    Once the application starts successfully, continue with the following steps.

20. Change the resulting singleton into a WIN03y catalog appliance class:
    1. Stop the application.
    2. Open the application in the infrastructure editor, right-click the singleton and select Modify Boundary:
       • Select the OS icon as windows.
       • Change the class name to WIN03y.

         Enter the description: Windows Server Appliance - based on Windows Server 2003 [Standard] Edition R2 32/64-bit. Replace Standard with your edition name.

       • Change the following resource settings:

         CPU (num)

         Min: 0.1

         Max: 4

         Default: 1

         Memory (bytes)

         Min: 256

         Max: 4G

         Default: 1G

         Bandwidth (bits/sec)

         Min: 1M

         Max: 1G

         Default: 100Mbps

         Please refer to the below resource table at the end of the document and change the resource settings based on the Windows edition.

       • Set the documentation URL to: http://doc.3tera.com/AppLogic35/en/Catalog_Ref/CatGenericWindows.html
       • Add terminals to the appliance until there is a total of 7 listed interfaces. With the default interface this will provides the maximum 8 interfaces. This step is required to avoid manual user intervention when adding terminals to future Windows appliances that are based off of this Windows server appliance.
    3. Right-click the singleton and select Attributes. Change the instance name to WIN03y.
    4. Start the application. SSH into the appliance and set the Administrator password (net user administrator new_password). Download the current version of TurboGate PV drivers through the internal interface, using the same method as the Server msi was downloaded previously. Install the TurboGate PV drivers. Do not reboot after the install.

       Note: You must change the administrator password because the Windows server MSI sets a new random password on initial boot.You must know the administrator password before installing the Turbogate PV drivers.

    5. Open a 3Tshell and perform the following command:

       app restart win03_install --debug
       

    6. A minute after the application begins to start, log in using the graphical console and complete the TurboGate PV drivers install:

       Click through the hardware setup wizard for the installation of the TurboGate PV drivers for all 8 terminals that are configured in the appliance.

       • If the app start has not timed out: shutdown the OS from in the graphical console; this will cause the app start --debug to fail, and then execute the following command:

         app stop win03_install 
         

       • If the app start has timed out: execute the following command in the 3Tshell followed by a shutdown within the graphical console:

         app stop win03_install
         

    7. Execute the following command in the 3Tshell and verify the appliance starts without error:

       app start win03_install
       

    8. Execute the following command in a bash shell on the appliance:

       rm -f /appliance/passwd.stamp
       

       We recommend you set a complex Administrator password that prevents any one from logging in to the appliance as the Administrator.

       • Set new complex password, such as net user administrator pq398hpaowht0293j^LWOIFH9htfw9jfe
       • Exit the ssh session.
       • Ssh into appliance and execute rm -f ~/.bash_history so the password is cleared from the bash history.
    9. If you have installed version 3.0.1 of the TurboGate PV drivers, disable the service named gkservice.

       This service is installed with the PV drivers and fails to start if there is more than one virtual network interface associated to the appliance. Disabling this service does not affect the performance of the PV drivers.

    10. Stop the application.
    11. Modify the boundary of the appliance again and remove the extra terminals that were added in the previous steps.
    12. Move the singleton into the /system_ms catalog where you have the required privileges.

        You must assign yourself full access rights to the catalog before you can move the singleton. For additional information, see catalog modify_acl in the Command Line Shell Reference Guide.

The WIN03y appliance is now ready for use.

Additional Information

Windows Server 2003 Resources

32-bit appliances

64-bit appliances

Review the Appliance Catalog Reference Guide for details on the behavior of the Windows APK which is installed by all of the Windows msis.