Using CA AppLogic® › Appliance Developer Guide › Creating Appliances › Distribution Installations › Windows Installation Reference › Windows Server 2008 Filer Installation Reference

Windows Server 2008 Filer Installation Reference

Versions of CA AppLogic® later than 2.9.1 include support for Windows Server 2008 appliances and applications. Filesystem level operations over ntfs08 volumes are provided by the Sys_Filer_Window08 template application and the /system_ms:Filer_Windows08 appliance. These may be imported from your CA AppLogic® software version directory as follows. You must be a grid maintainer to perform these operations.

Perform these steps:

1. Import the Sys_Filer_Windows08 application:
   1. Go to the CA AppLogic®-version Download Directory on the BFC server.

      For example, /opt/bfc/applogic-versions/<release number>.

   2. Copy the file Sys_Filer_Windows08-<version>.tar to the grid controller using following command

      scp Sys_Filer_Windows08-<version>.tar <controller IP>:/vol/_impex/
      

   3. SSH to the grid controller and untar the file using command

      tar -xf Sys_Filer_Windows08-<version>.tar
      

   4. Import the application as follows

      3t app import Sys_Filer_Windows08 Sys_Filer_Windows08 
      

2. Import the system_ms catalog:
   1. Go to the CA AppLogic®-version Download Directory on BFC server.
   2. Copy the file system_ms-<version>.tar to the grid controller using following command

      scp system_ms-<version>.tar <controller IP>:/vol/_impex/
      

   3. SSH to the grid controller and untar the file using command

      tar -xf system_ms-<version>.tar
      

   4. Import the catalog /system_ms as follows

      3t cat import /system_ms system_ms 
      

Notes:

• The system_ms catalog contains the IIS03yx4/IIS03yx8 assemblies which contain references to the /system_ms:IIS03y appliances. The infrastructure editor displays an error message every time an application is opened as long as any one of the /system_ms:IIS03y appliances is missing.

  To resolve this issue, either create all of the /system_ms:IIS03y appliances or remove the unused IIS03yx4/IIS03yx8 appliances from the system_ms catalog.

• The /system_ms:Filer_Windows08 appliance has an empty boot volume which is replaced with a working boot volume during the installation procedure detailed below. Follow the instructions in this topic to create a functioning Windows Server 2008 filer appliance (/system_ms:Filer_Windows08).

The Filer_Windows08 appliance is based on Windows Server 2008 Standard Edition Core Install 32-bit (either SP1 or SP2). The Core Install is used to reduce the size of the filer appliance boot volume. The first step in creating this appliance is to create a base server class using the same OS as follows:

1. Copy a Windows 2008 Server 32-bit ISO image to the impex volume of the grid controller. Either SP1 or SP2 ISOs may be used. This example uses the ISO image en_windows_server_2008_datacenter_enterprise_standard_sp2_x86_dvd_342333.iso downloaded from the Microsoft MSDN site.
2. Open a 3t shell and use the iso2class utility to begin an installation of Windows Server 2008 Standard Edition Core Install 32-bit:
   • Execute the following command:

     util iso2class app_name=win08sc-install iso_volume1=en_windows_server_2008_datacenter_enterprise_standard_sp2_x86_dvd_342333.iso os=windows install_size=4.5G console_type=graphic virt_options=acpi=1 cpu=1 mem=1G. 
     

   Note: The install_size may vary depending on the operating system installation size.

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

3. Access the graphic console of the singleton in one of the following two ways:
   • Select the win08sc-install application within the application list in the CA AppLogic® GUI and click on the icon for Login (graphic).
   • Open the application win08sc-install in the infrastructure editor and select the singleton iso2class. Use the pull-down Appliance menu to select Login (graphic).
4. After the graphical console appears, the Windows 2008 Server installation interface should be visible. Proceed to install the OS. The singleton reboots during installation, rendering the graphical console inoperative. When this event occurs, simply close and reopen the graphical console.
5. When the installation completes, the singleton reboots itself and Windows prompts you to set a new password. Type in your new password and press Enter. Windows sets a new password for Administrator and displays a message indicating that the Administrator password set successfully. Press OK and Windows logs into the administrator desktop automatically. Next, perform the following operations:
   • If 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 hit ‘spacebar’
     • Type “D:\setup.exe /S /v /qn” to execute VMware tools installation silently.

   The installation will reboot the appliance automatically. This requires a few minutes.

   After reboot, open the graphical console again and login to the appliance.

6. When the desktop becomes visible, perform the following operations in the command shell:
   • Set the page file size to 16M:
     • wmic computersystem where name="%COMPUTERNAME%" set AutomaticManagedPagefile=False
     • wmic pagefileset where name="C:\\pagefile.sys" set InitialSize=16,MaximumSize=16
   • Reboot: shutdown –r –t 0
7. After a minute reopen the graphical console and login to the Windows desktop.
8. Disable power management hibernation support: powercfg -h off. Execute dir. There should be approximately 1GB of free space on the disk.
9. Set the default Windows disk device timeout value to 60 seconds:
   • Execute regedit to open the registry editor.
   • Navigate to the key HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/Disk.
   • Right-click on disk in the left pane and select New=>DWORD. Type TimeOutValue followed by <enter>. Right-click on TimeOutValue and select modify. Set the type to decimal and enter 60 for the value. Click OK.
10. If you intend to install the TurboGate PV drivers, then disable TCP checksum offload:
    • In the registry editor, navigate to HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/Tcpip/Parameters.
    • Right-click Parameters in the left pane and select New=>DWORD. Type DisableTaskOffload followed by <enter>. Right-click on DisableTaskOffload and select modify. Enter 1 for the value. Click OK.
    • Close the registry editor.
11. Activate windows as follows:
    • Configure external network access:
      • netsh interface ipv4 set address name="Local Area Connection" source=static address=X.X.X.X mask=X.X.X.X gateway=X.X.X.X (use valid network settings)
      • netsh interface ipv4 add dnsserver name="Local Area Connection" X.X.X.X index=Y (where X.X.X.X is the IP address of the DNS Server and Y is its place in the list, for example 1)
      • Verify external network access (for example, ping www.google.com)
    • Update the Windows 2008 Server product key and activate Windows:
      • Update the product key: slmgr.vbs –ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX (use the appropriate product key); wait 30 seconds for the command to complete asynchronously
      • Activate Windows: slmgr.vbs –ato; wait 1 minute for the command to complete asynchronously
      • Verify the activation: slmgr.vbs –xpr; you should see a pop-up indicating Windows is activated; if not, repeat the above steps
12. Shutdown the OS and continue the iso2class install as follows:
    • shutdown -s -t 0
    • Wait 5 seconds and then, within the 3t shell running the iso2class utility, press the <enter> key and then the Y key followed by the <enter> key to continue such that the second volume becomes available to the singleton.
13. After a minute, reopen the graphical console and login to the Windows desktop.
14. To transform the singleton into a fully managed CA AppLogic® appliance, install the Server Windows msi. The installer can now be located on the E drive of the singleton. In the command shell type E: and <enter> to navigate to the E drive.Execute Server_Windows-2.0.4-1.msi to install the Windows Server MSI. The installer for the Windows Server MSI is available on the E drive.

    Note: Copy the VMware setup files from drive D to drive C.

15. If you intend to install the TurboGate PV drivers, copy E:\TurboGate_GTools-3.0.1.exe to C:\.
16. Complete the basic installation:
    • shutdown -s -t 0
    • Wait 5 seconds and then, within the 3t shell running the iso2class utility, press the <enter> key and then the Y key followed by the <enter> key to continue.
    • When prompted in the 3t shell, select The appliance is fully managed. The iso2class stops the application, changes the singleton boundary to that of a generic server appliance, and restarts the application (the appliance will enter maintenance mode during the restart).
17. If desired, install the TurboGate PV drivers:
    • From a 3t shell, SSH into the singleton ssh win08sc-install:main.iso2class.
    • Set the Administrator password: net user administrator password (select a password).
    • Login through the graphical console and execute C:\TurboGate_Tools-Setup-V3.0.1.exe. Select Install Anyway as required. Do not reboot after the install. Select ‘I want to reboot later’ and click the finish button.
    • Execute the following command within a 3t shell:

      app restart win08sc-install --debug
      

    • If you are performing the installation on a Xen grid, a minute after the application begins to start, log in using the graphical console and wait for another minute or so until the driver installation completes. This is indicated by the result of ipconfig /all delineating each ethernet adapter as Halsign GK Ethernet Adapter #X).

      At this point:

      • If the application start has not timed out, it may complete normally. Otherwise shutdown the OS from within the graphical console.This causes the app start --debug to fail. Next, execute app stop win08sc-install in the 3T shell
      • If the application start has timed out, execute app stop win08sc-install in the 3T shell followed by shutdown within the graphical console.
    • Execute the following command within the 3Tshell and verify the appliance starts without error:

      app start win08sc-install
      

18. SSH into the singleton and set the Administrator password (net user administrator password). Login through the graphical console and, in the command shell, change the computername: wmic computersystem where name="%COMPUTERNAME%" rename name="WIN08SC"
19. Within the SSH session Bash shell:
    • rm -f /appliance/passwd.stamp
    • As required rm -f /cygdrive/c/TurboGate_Tools-Setup-V3.0.1.exe
    • Set a complex Administrator password that prevents any one from logging to the appliance as the Administrator without first setting a new password in an SSH session (for example, net user administrator pq398hpaowht0293j^LWOIFH9htfw9jfe).
    • Exit the SSH session.
    • Execute rm -f ~/.bash_history so the password is cleared from the Bash history.
    • Exit the SSH session.
20. Change the singleton into a WIN08SC catalog appliance class:
    • Stop the application
    • Open the application in the infrastructure editor.
    • Right-click the singleton and select Attributes. Change the instance name to WIN08SC.
    • Right-click the singleton and select Modify Boundary:
      • Change the class name to WIN08SC.
      • Enter the description, for example: Windows Server Appliance - based on Windows Server 2008 Standard Edition Core Install SP2 32-bit.
      • Change the following resource settings:

        CPU (num)

        Min: 0.25

        Max: 4

        Default: 0.5

        Memory (bytes)

        Min: 512

        Max: 4G

        Default: 768M

        Bandwidth (bits/sec)

        Min: 1M

        Max: 2G

        Default: 100M

21. 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. See catalog modify_acl in the Command Line Shell Reference Guide for more information.

    The WIN08SC base class is now created.

22. Proceed to create a functioning Windows Server 2008 filer appliance (/system_ms:Filer_Windows08).

Create a Functioning Windows Server 2008 Filer Appliance.

You can create a functioning Windows Server 2008 filer appliance (/system_ms:Filer_Windows08).

Perform these steps:

1. Branch the WIN08SC instance within the win08sc-install application.
2. Right-click the appliance in infrastructure editor and select Modify boundary. Go to volumes tab and add a new placeholder volume.
3. Configure the singleton instance to use apk_volume for the placeholder volume with a mount point of D:\ . This volume is available because of the os=windows options used with iso2class.

   If apk_volume is not present then copy the apk_windows volume from 3t shell using command vol copy _GLOBAL_RO:apk_windows appname:apk_volume

4. Save and start the application.
5. SSH into the singleton and set the Administrator password (net user administrator password).
6. Login to the graphical console of the singleton and in the command shell D:\Filer_Windows-3.0.8-1.msi to install the Windows Filer MSI.
7. Within the SSH session Bash shell:
   • Set a complex Administrator password to prevent any one from logging in to the appliance as the Administrator without first setting a new password in an SSH session (for example, net user administrator pq398hpaowht0293j^LWOIFH9htfw9jfe).
   • Log into the SSH shell again.
   • Execute rm -f ~/.bash_history so the password is cleared from the Bash history.
   • Exit the SSH session.
8. Stop the application.
9. This step requires maintainer access to the grid.
   • In a 3t shell class, unlock /system_ms:Filer_Windows08
10. Create a new application win08filer-install with an instance of /system_ms:Filer_Windows08 and branch the instance. Modify the boundary of the resulting singleton and set the Documentation URL to http://doc.3tera.net/AppLogic35/en/CatFilerWindows08.html. Save the application.
11. Execute the following commands within a 3t shell:

    vol destroy win08filer-install:Filer_Windows08.boot --force 
    vol copy win08sc-install:WIN08SC.boot win08filer-install:Filer_Windows08.boot 
    class destroy /system_ms:Filer_Windows08 --force 
    

12. Within the infrastructure editor for win08filer-install drag the singleton into the /system_ms catalog.
13. This step requires maintainer access to the grid.
    • In a 3t shell class lock /system_ms:Filer_Windows08

The /system_ms:Filer_Windows08 appliance class completes and becomes ready for use.