CA AppLogic® Release 3.5 New Windows APK Readme

1.0 Welcome

2.0 Appliance Kit Installation for Windows
    2.0.0.1 Files
    2.0.0.2 Compatibility
    2.0.0.3 Preparing the Image
    2.0.0.4 Installing the APK
    2.0.0.5 Important Windows-specific Information
    2.0.0.6 Customizing Appliance Behavior - Quick Reference

3.0 Windows Server 2003 Single CD Installation Reference

4.0 Windows Server 2003 Two CD Installation Reference
4.1 Complete the Appliance (Windows Server 2003)

5.0 Windows Server 2008 Base Server Class Installation Reference
5.1 Complete the Appliance (Windows Server 2008)

6.0 Resources

7.0 Automated Steps

8.0 Contact CA Technologies

1.0 Welcome

Welcome to the CA AppLogic^® readme. This readme contains topics from the Appliance Developer Guide that have been updated for a new Windows APK included with CA AppLogic.

The new Windows APK provides an easier installation and user-friendly interface for configuring Windows-based appliances. Support for the localized versions of the Windows OS is planned for a future release.

2.0 Appliance Kit Installation for Windows

The following instructions pertain to Windows Server 2003 (32-bit and 64-bit) and Windows Server 2008 (32-bit and 64-bit) installations.

2.0.0.1 Files

• Windows_APK.*.msi - the appliance kit

2.0.0.2 Compatibility

The Windows_APK.*.msi versions are compatible with the following OS distros:

• Windows 2003 Server, all varieties (32-bit and 64-bit)
• Windows 2008 Server, all varieties (32-bit and 64-bit)

To install the APK, you need the following:

• An existing appliance based on Windows.
• A vanilla installation of the OS, in a Xen HVM environment.
• (Optional) Paravirtual (PV) device drivers (third-party, not released with the APK - requires separate license). The APK has been tested with the Halsign TurboGate drivers v3.0.1.

2.0.0.3 Preparing the Image

The following steps may vary, depending on how the OS was originally installed. The APK setup script does not perform these steps, which are up to the discretion of the operator to perform. Some of these steps require GUI access and an automated script may not be able to execute them. Other steps are invasive and may be destructive. Therefore, running these steps in an automated script may be inadvisable.

Skip any steps that are not appropriate.

1. Disable all desktop experience visual elements (animated menus, shadows, full-window drag, and so on) for best operation over VNC or remote desktop.
2. Disable the screen saver and screen lockout.
3. Set a strong password for the Administrator account.
4. Un-install or disable any OS services that will not be used (for example, the Browser service and the Server service).
5. Install all Windows Update hotfixes (each hotfix will require a separate reboot).

   Note: Failure to install the updates on Windows 2008 can cause the APK to fail.

6. Enable Remote Administration (using Terminal Services)

   Note: Enabling remote administration is different from configuring the OS as a Terminal Server. Configuring the OS as a Terminal Server requires paid licenses for each client. Enable remote administration only if this is the intended use of the installation.

7. Configure the network with a publicly accessible IP address. You can now perform the remaining steps using the remote desktop.
8. If Cygwin is already installed on the system, verify that the following GNU utilities are installed (these utilities should be in the base packages, but double-check and add them if they are missing): bash, wget, gzip, and tar.
9. Install the Xen-aware (paravirtual or PV) device drivers, if desired. If using PV drivers, we recommend that you reboot Windows after installing the drivers and before installing the APK. Verify that the PV drivers operate normally.

Note: The minimum Windows 2003 installation requires over 1GB of disk space. Windows 2008 needs nearly 8GB for the full installation (less for the server core). Leave adequate room for installing the Windows Update hotfixes (keep in mind that Windows will retain All previous versions of the binary files replaced by the hotfixes). Verify that at least 300 MB of free space is available for installing the APK, Cygwin, and for extra space for log files, temporary files, and so on.

2.0.0.4 Installing the APK

Install the APK on a live system. You cannot install the APK for Windows into a mounted OS disk image that is not actually running. For best results, use an OS image that has external network access configured and log into it using a remote desktop client from your favorite OS (for example, rdesktop). Using an OS image that has external network access configured provides better interactive operation than using VNC to see the HVM emulated video screen.

Perform one of the following installation options:

• Typical / Complete Install

  Provides an installation wizard that installs the Windows APK, including the APK Automation Prep Script.

• Custom Install

  Provides an installation wizard that enables you to decide whether to run the APK Prep Script. The script requires that you manually reboot the operating system to ensure that the required system configuration takes effect.

• Silent Install with APK Prep Script Disabled

  Enables you to perform an installation without user prompts or the APK prep script. Use the following command:

  msiexec /q /i Windows_APK*.msi PREP_APK=no
  

  Note: If you disable the APK prep script, manually perform the automated steps.

• Silent Install with APK Prep Script Enabled

  Enables you to perform an installation without user prompts and running the APK prep script. Use the following command:

  msiexec /q /i Windows_APK*.msi
  

2.0.0.5 Important Windows-specific Information

File Names

Unless otherwise stated, names in this document are in the Cygwin file namespace, which emulates a POSIX system.

Note: These names cannot be used with any non-Cygwin utilities. This includes the APK binaries themselves (vme and udlparse), and all of the native Windows command line tools. Most Cygwin utilities will accept either a Cygwin name (POSIX-style) or a Windows name (for example, C:\path\), with the exception of those utilities that consider strings with a colon (:) in them to indicate the computername:filename (for example, scp, rsync, and notably tar). The utilities that consider strings with a colon (:) in them to indicate the computername:filename can be forced to accept a Windows name with the --force-local option.

To convert a file name between the Windows and Cygwin namespaces, use cygpath, for example.

windowspath=`cygpath -w /var/run/applogic/appliance.desc` 

Disk Mounts

When specifying a mount point for disks, use the following names, as desired:

• X - A single letter (A,B,D-Z) will make the disk accessible as X:\.
• X:\ - Same as X
• C:\dir1\[dir2\...] - Makes the disk accessible in the given sub-directory of the boot file system. If the directory does not exist, it will be created.

Note: We do not recommend that you allow the APK to create the directory, because the default directory permissions may not be what you anticipated.

Leaving a disk without a mount point specified in the class descriptor will cause the APK to ignore the disk and leave its mount assignment in Windows as-is. In this case, any mount point assignment for that disk done manually from Windows itself is persistent and takes priority over assignment of the same mount point to another disk through the class descriptor (the latter assignment will have no effect and will leave the disk un-mounted). For example, suppose you have specified the following in the infrastructure editor:

• disk 0 -> (boot)
• disk 1 -> (no mount assigned)
• disk 2 -> Z:\ 

You log into the appliance, remove Z from disk2 and assign it to disk1. Then Z will stay assigned to disk1 across reboots and the "disk2 -> Z" assignment in the class descriptor will not take effect. Disk2 will not be mounted anywhere, until Z is removed from disk1 or something other than Z is set for disk2.

C:\ is reserved and cannot be assigned as the mount point for any disk. Any assignment for the boot disk will be ignored and it will be reported as mounted on C:\ in the appliance instance descriptor.

Do not use mount paths with sub-directories on any drive except C:. Doing this may cause your mount not to be useable, as it depends on the order in which the disks are mounted.

Keep in mind that Windows will not refuse to mount an un-formatted disk (or one formatted with a file system that is not understood by Windows). No error or warning is issued at all when the mount is assigned by the APK, but attempts to access the mount point and any subpaths will fail.

User Names

The APK installation script will assign root as the Cygwin alias for the Administrator. Therefore, root will be the user name seen by any Cygwin binary and will show up as the current user name in a Cygwin shell and in directory listings. This setting allows accessing the appliance using the remote shell command (3t ssh component-name).

Note that the mapping between Cygwin user names and Windows user names is not automatic. This mapping is described in the /etc/passwd and /etc/group files, which are not automatically updated when adding or removing Windows users. Cygwin includes utilities to maintain the /etc/passwd and /etc/group files. When using these utilities, take care to preserve the special mapping for root created by APK; otherwise ssh login from the grid will stop working.

2.0.0.6 Customizing Appliance Behavior - Quick Reference

Appliance Init Configuration

If the file /etc/sysconfig/applogic_init is present, the APK init script reads it as a shell include script (with the "." command). The following parameters can be defined in /etc/sysconfig/applogic_init:

Note: The /etc/sysconfig/applogic_init file is executed before any configuration data is retrieved or applied; therefore, the script cannot rely on the presence of any of the appliance's configuration files. Do not use this file for executing initialization code, only for the configuration variables defined above.

This is an example of a /etc/sysconfig/applogic_init:

APK_CONFIG_FILES=/etc/httpd/conf.d/myconfig.conf

APK_AUTH_KEY_PATH=/root/.ssh/alternate_keys 

Appliance Post-start Check

If the file /etc/sysconfig/applogic_appliance is present, the APK late init script reads it as a shell include script (with the "." command), after all other services on the appliance have been started. The return status from the script indicates whether the appliance is to be considered started successfully or failed. If the script prints a message to stderr and returns an error, the last line from this message will be used as the error message sent to the controller.

This is an example of post-start check file, for a web server appliance which verifies that the server is up and responds to HTTP GET to the home page:

if ! wget -q -O /dev/null http://localhost/ ; then

echo "start failed - Web server is not responding" >&2

return 1

fi

return 0 

Avoid using /etc/sysconfig/applogic_appliance , as startup script to launch appliance services. Doing this will prevent your setup form being used or tested outside of an appliance that has the APK installed.

Note: For Windows, unlike the other platforms supported by the APK, the applogic_appliance post-start check is initiated after the Windows Service Control Manager (SCM) has loaded all services - not when they have completed initializing. Things are further complicated by the fact that in Windows Server 2003 and 2008, some services are started by other services using an API call, rather than as an explicit dependency (and therefore cannot be accounted for simply by waiting on the automatic services load completion event). Therefore any 'startup check' code added to the /etc/sysconfig/applogic_appliance file must account for this and wait for any of the services that it needs to monitor, in case they have not yet initialized.

3.0 Windows Server 2003 Single CD Installation Reference

This example installation is based on a single CD install of Windows Server 2003 Standard Edition SP2. For the example, we use a global volume named win03_iso (see the iso2class reference for other ways to specify an ISO image for the installation). The same example below may be used for the other Windows editions (Enterprise, DataCenter, and Web Edition).

Note: In the following text in this topic, the y placeholder in WIN03y is for the Windows edition that the appliance is based upon (S for Standard, E for Enterprise, DC for DataCenter).

To install and configure a WIN03y appliance using a single CD

1. Open a 3T shell, execute the following command, and select the appropriate bits (32 or 64) and OS:

   util iso2class app_name=win03_install install_size=10G console_type=graphic iso_volume1=win03_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: The volume is specified to be initially 10GB in size. This size is used to verify that enough disk space exists for the Windows installation. After the appliance is created, you can resize the volume depending upon the amount of free disk space left after the Windows install (we recommend that you leave at least 500MB of free disk space).

2. Access the graphic console of the singleton in one of the following two methods:

   • Select the application within the application list in the CA AppLogic GUI and click the icon for Login.
   • Open the application in the CA AppLogic editor and select the singleton iso2class. Use the pull-down Appliance menu to select Login.

     During Windows installation on a VMware grid, due to the absence of VMware tools, the mouse may not function as expected. 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 appears, the Windows 2003 Server installation should be visible. Run through the installation with the following notes:

   • Use a single NTFS partition
   • Select Custom Setting - Disable file and printer sharing for both network interfaces
   • Use a workgroup
4. Configure the external network interface to provide access to the Internet. No reboot is required.
5. Set the Internet security to medium.
6. Use Windows Update and install Service Pack 2 and all high priority updates. Multiple reboots will be required.
7. Install the Windows Server 2003 Resource Kit Tools.
8. (Optional) Install the Windows components that you want available on the appliance.
9. Activate Windows as required.
10. 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. To read more about this issue and fix this issue, see http://support.microsoft.com/kb/942589 and apply this hotfix according to its instructions.
11. For 64-bit appliances, download and install the Microsoft Visual C++ 2005 SP1 Redistributable Package (x64).
12. To transform this singleton into a fully managed CA AppLogic appliance, execute the Windows Server exe installer. This self-executing installer can be downloaded from either the grid controller through the internal interface, or from the D or E drive. This interface has already been properly configured through DHCP.

    1. To find the internal IP address of the controller, execute the following command in a command line shell and record the IP address of the DHCP server for Local Area Connection 2.

       ipconfig /all 
       

    2. In Internet Explorer, go to http://IP-address:8080/download/new.
    3. Right-click the exe file and select Save Target As to download the file to the desktop.

       The current Windows Server exe (for example, Server_Windows-3.5.1.exe) is downloaded.

    4. Double-click the Server Windows EXE file on the desktop to perform the base class appliance installation.

       The Windows APK is installed as a pre-requisite.

    5. Delete the exe file and empty the Recycle Bin.
13. If there are junction points on the volume, Windows appliance volume resizing fails. Delete junction points to prevent Windows volume resize failures. The following examples show junction points that you can find on a Windows boot volume.

    • WINDOWS\assembly\GAC_32\System.EnterpriseServices\2.0.0.0__b03f5f7f11d50a3a\
    • WINDOWS\assembly\GAC_MSIL\IEExecRemote\2.0.0.0__b03f5f7f11d50a3a\

    Note: The names on your volumes can be different.

    You can search for junction points using the Command Prompt. The output of the following command reports the path for any junction points that it finds.

    dir/S /A:L
    

14. Close the graphical console and close the application editor (if it is open).

    The installation is complete.

15. Press Enter in the 3T shell running iso2class to continue, and, when prompted, 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.

16. If iso2class fails to start the application, perform the following steps:

    1. Select option #2 Exit from iso2class and investigate manually.
    2. Start the application in debug mode by executing the following command in the 3Tshell:

       app start app_name –debug
       

17. After the application starts successfully, complete the appliance.
18. Manually reboot the OS (to ensure required system configuration takes effect) to complete the transformation of this singleton into a fully managed CA AppLogic appliance.

Note: Review the Appliance Catalog Reference Guide for information about the behavior of the Windows APK that is required by all of the Windows MSIs.

4.0 Windows Server 2003 Two CD Installation Reference

This example installation is based on a two CD install of Windows Server 2003 Standard Edition R2. For this example, we use two global volumes named win03-disk-1_iso and win03-disk-2_iso (See the iso2class reference for other ways to specify an ISO image for the installation). The same example below may be used for the other Windows editions (Enterprise, DataCenter and Web).

Note: In the following text in this topic, the y placeholder in WIN03y is for the Windows edition that the appliance is based upon (S for Standard, E for Enterprise, DC for DataCenter, W for Web).

To install and configure a WIN03y appliance using two CDs

1. Open a 3T shell, execute the following command, and select the appropriate bits (32 or 64) and OS:

   util iso2class app_name=win03_install install_size=10G console_type=graphic iso_volume1=win03-disk1_iso iso_volume2=win03-disk2_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: The volume is specified to be initially 10GB in size. This size is used to verify that enough disk space exists 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 install (we recommend that you leave 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 click Login.
   • Open the application in the CA AppLogic editor and select the singleton iso2class. Select Login from the Appliance drop-down menu.
   • During Windows installation on a VMware grid, due to absence of VMware tools, the mouse may not function as expected. The following keyboard shortcuts are useful:

     • To navigate between buttons, use the Tab key or arrow keys.
     • To select an option, use the space bar.
     • To access the file menu of the selected window, use the Alt+F key.
3. After the graphical console appears, the Windows 2003 Server installation should be visible. Run through the installation with the following notes:

   • Use a single NTFS partition.
   • Disable file and printer sharing for both network interfaces.
   • Use a workgroup.
4. When the installation from the first CD is complete, Windows will reboot. Windows will then inform you that Windows Setup is not complete and ask for Windows Server CD2. At this point, in the 3t shell, continue with the iso2class utility. iso2class 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 the “Ctrl+Alt+Del” button on the center top of the graphical console window.
     • Click anywhere inside the graphical console window.
     • Navigate to “start task manager" using the tab and arrow keys.
     • Navigate to “new task” and press the ‘spacebar'.
     • Type E:\setup.exe /S /v /qn to execute VMware tools installation silently.
     • The installation will reboot the appliance automatically. After reboot, reopen the graphical console and login to the appliance.
5. Access the console and continue with the installation. The second CD will automount as drive D. Access this drive in Windows Explorer and execute the secondary installer (for example R2AUTO.EXE)
6. Configure the external network interface to provide access to the Internet. No reboot is required.
7. Set the Internet security to medium.
8. Use Windows Update and install Service Pack 2 and all high priority updates. Multiple reboots will be required.
9. Install the Windows Server 2003 Resource Kit Tools.
10. (Optional) Install the Windows components that you want available on the appliance.
11. Activate Windows as required.
12. 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. To read more about this issue and fix this issue, see http://support.microsoft.com/kb/942589 and apply this hotfix according to its instructions.
13. For 64-bit appliances, download and install the Microsoft Visual C++ 2005 SP1 Redistributable Package (x64).
14. To transform this singleton into a fully managed CA AppLogic appliance, execute the Windows Server exe installer. This self-executing installer can be downloaded from either the grid controller through the internal interface, or from the D or E drive. This interface has already been properly configured through DHCP.

    1. To find the internal IP address of the controller, execute the following command in a command line shell and record the IP address of the DHCP server for Local Area Connection 2.

       ipconfig /all 
       

    2. In Internet Explorer, go to http://IP-address:8080/download/new.
    3. Right-click the exe file and select Save Target As to download the file to the desktop.

       The current Windows Server exe (for example, Server_Windows-3.5.1.exe) is downloaded.

    4. Double-click the Server Windows EXE file on the desktop to perform the base class appliance installation.

       The Windows APK is installed as a pre-requisite.

    5. Delete the exe file and empty the Recycle Bin.
15. If there are junction points on the volume, Windows appliance volume resizing fails. Delete junction points to prevent Windows volume resize failures. The following examples show junction points that you can find on a Windows boot volume.

    • WINDOWS\assembly\GAC_32\System.EnterpriseServices\2.0.0.0__b03f5f7f11d50a3a\
    • WINDOWS\assembly\GAC_MSIL\IEExecRemote\2.0.0.0__b03f5f7f11d50a3a\

    Note: The names on your volumes can be different.

    You can search for junction points using the Command Prompt. The output of the following command reports the path for any junction points that it finds.

    dir/S /A:L
    

16. Close the graphical console and close the application editor (if it is open).

    The installation is complete.

17. Press Enter in the 3T shell running iso2class to continue, and, when prompted, 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.

18. If iso2class fails to start the application, perform the following steps:

    1. Select option #2 Exit from iso2class and investigate manually.
    2. Start the application in debug mode by executing the following command in the 3Tshell:

       app start app_name –debug
       

19. After the application starts successfully, complete the appliance.
20. Manually reboot the OS (to ensure required system configuration takes effect) to complete the transformation of this singleton into a fully managed CA AppLogic appliance.

The WIN03y appliance is now ready for use.

Note: Review the Appliance Catalog Reference Guide for information about the behavior of the Windows APK that is required by all of the Windows MSIs.

4.1 Complete the Appliance (Windows Server 2003)

Completing the appliance includes changing it from singleton to a WIN03y catalog appliance class, and, if you configure TurboGate PV drivers, making further modifications.

Follow these steps:

1. Stop the application, open the application in the CA AppLogic editor, right-click the singleton, and select Modify Boundary:

   1. Select the OS icon as windows.
   2. Change the class name to WIN03y.
   3. Enter the following description:

      Windows Server Appliance – based on Windows Server 2003 Standard Edition R2 32/64-bit

      Note: Use the correct edition name.

   4. 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

      Note: See the resource table and change the settings based on the Windows edition.

   5. Set the documentation URL to:

      http://doc.3tera.com/AppLogic35/index.htm?toc.htm?CatGenericWindows.html
      

2. 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, select Attributes, and change the instance name to WIN03y.
4. Start the application, securely log in to the appliance using SSH, and set the Administrator password (net user administrator new_password). Download the TurboGate PV drivers through the internal interface (similar to how you previously downloaded the Server msi). Install the TurboGate PV drivers. Do not reboot after the installation.

   Note: Change the administrator password because the windows server EXE sets a new random password on initial boot and you must know the administrator password before installing the TurboGate PV drivers.

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

   app restart win03_install --debug
   

6. Wait one minute after the application starts, then log in using the graphical console and complete the TurboGate PV drivers install: Click through the hardware setup wizard to install the TurboGate PV drivers for all 8 terminals that are configured in the appliance.

   Note: Perform one of the following sets of steps, depending on whether the app start has timed out:

   • If the application start has not timed out, it may complete normally; otherwise, shutdown the OS from within the graphical console, which causes the app start –debug to fail, and execute the following command in the 3T shell:

     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 win_03 install
     

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

   app start win03_install
   

8. If you have installed version 3.0.1 of the TurboGate PV drivers, click Start > Run > services.msc to disable the service gkservice.

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

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

   rm –f /appliance/passwd.stamp
   

   Note: We recommend that you set a complex administrator password so that no unauthorized users can log in to the appliance as an administrator.

   1. Set new complex password, such as net user administrator <complex_password>.
   2. Exit the ssh session.
   3. Securely log in to the appliance using SSH and execute the following command:

      rm –f ~/.bash_history 
      

      The password is cleared from the bash history.

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

    Note: Ensure that you have full access rights to the catalog. These rights are required to move the singleton.

5.0 Windows Server 2008 Base Server Class Installation Reference

Versions of CA AppLogic later than 2.9.1 include support for Windows Server 2008 appliances and applications. If you are using such a grid, you may follow the instructions in this topic to create Windows Server 2008 base classes.

This example installation is based on a DVD install of Windows Server 2008 Standard Edition without Hyper-V SP2 32-bit. These instructions have been tested with the following Windows Server versions:

Notes:

• The install size may change as Microsoft releases new updates to the OS.
• The contents of the X:\WINDOWS\SoftwareDistribution\Download folder can be removed if you need to save disk space.

  For the example, the ISO image used for the installation has been downloaded from Microsoft's MSDN site and copied to the impex volume of the grid as en_windows_server_2008_datacenter_enterprise_standard_without_hyper-v_sp2_x86_dvd_342334.iso. See the iso2class reference for other ways to specify an ISO image for the installation.

• The TurboGate PV drivers version 2.0 can be used with 32-bit versions of Windows Server 2008, but do not work with 64-bit versions of Windows Server 2008. Version 3.0.1 of these drivers work with both 32-bit and 64-bit versions of Windows Server 2008.
• In the following text of this topic, the y placeholder in WIN08y corresponds to the Windows edition that the appliance is based upon (S for Standard, E for Enterprise, DC for DataCenter, W for Web, and so on.)

To install and configure a WIN08y appliance

1. Open a 3T shell, execute the following command, and select the appropriate bits (32 or 64) and OS:

   util iso2class app_name=win08_install install_size=12G console_type=graphic iso_volume1=en_windows_server_2008_datacenter_enterprise_standard_without_hyper-v_sp2_x86_dvd_342334.iso virt_options=acpi=1 cpu=1 mem=1G
   

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

   Note: The volume size of 12 GB provides enough space for the OS installation and subsequent Windows updates, resulting in an appliance with approximately 1GB of free space when the process is complete. This size requirement may change as Microsoft introduces more updates to the OS. In CA AppLogic, the boot volume of a Windows Server 2008 appliance is formatted as ntfs08. You can only increase the size of an ntfs08 boot volume for a Windows Server 2008 appliance.

2. Access the graphic console of the singleton in one of the following two methods:

   • Select the application within the application list in the CA AppLogic GUI and click the icon for Login (graphic).
   • Open the application in the CA AppLogic editor and select the singleton iso2class. Use the pull-down Appliance menu to select Login (graphic).
3. After the graphical console appears, the Windows 2008 Server installation interface should be visible. Proceed to install the OS.

   • The singleton will reboot during installation, rendering the graphical console inoperative. When this happens, simply close and re-open the graphical console.
   • On rare occasion, when using Mozilla's Firefox to access the graphical console, it will give a repeatable error of Application is not started or graphical console misconfigured. If this should happen simply close and re-open Firefox.
   • The following instructions assume a full Installation of Windows with its more complete graphical interface. If you are installing a Server Core installation you will need to adjust your keyboard and mouse actions to accomplish these same steps.
   • During Windows installation on a VMware grid, due to absence of VMware tools, the mouse may not function as expected. 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.
4. When the installation is complete, the singleton will reboot itself and Windows will ask you to set new password. Type in your new password and press Enter. Windows will set a new password for Administrator and display a message indicating that the Administrator password is set successfully. Press OK and Windows will log into the administrator desktop automatically. Now 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 application editor in browser.
     • Right-click on the singleton appliance ‘iso2class’ and select ‘user volumes’.
     • Select volume ‘vmware_tools_windows’ for placeholder iso_volume1.
     • Save and start the application.
     • Log in through the graphical console.
     • Press “Ctrl+Alt+Del” button on center top of the graphical console window.
     • Click inside the graphical console window anywhere.
     • 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. Wait patiently. After reboot you have to reopen the graphical console and log in to the appliance.
   • Change the computer name: Open Server Manager, Change System Properties and set the computer name to WIN08y. Restart when requested and close the graphical console.
5. The singleton has two network interfaces: Local Area Connection and Local Area Connection 2. The first of these is the external interface while the second is the internal interface. Configure the external interface of the singleton to provide access to the World Wide Web:

   • Access Server Manager, View Network Connections, Local Area Connection, Properties, TCP/IPv4, Properties. Click Use the following IP address and enter usable values for your grid (IP Address, netmask, gateway, DNS server).
   • Or, 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] 
     

6. Install high priority and optional Windows updates:

   • Open IE and select Tools, Windows Update, Turn on Now and install updates. On 64-bit versions of Windows, Windows Update may be access with Start, Control Panel, System and Security, Windows Update, Change settings, Download updates but let me choose to install them then OK and Check for updates.
   • Reboot when prompted. Close the graphical console, and, after a minute, re-open the graphical console.
   • Repeat the above procedure until there are no more updates to install. The option in IE to select Windows Update may become available under Security, Windows Update.
7. Activate Windows: Access Control Panel, System, Change Product Key and enter a valid product key. On 64-bit versions of Windows: Access Control Panel, System and Security, System, Change Product Key.
8. Shut down the OS and continue the iso2class installation using the following steps:

   1. In the command shell, type the following command and press Enter:

      shutdown –s –t 0
      

   2. Wait five seconds.
   3. Within the 3tshell running the iso2class utility, press Enter, Y, Enter.

      The second volume becomes available to the singleton.

9. Wait a minute, reopen the graphical console, and log in to the Windows desktop.

   Note: If the graphical console starts up in the System Recovery Options dialog, perform the following steps:

   1. Select Next and log in as Administrator.
   2. Restart and wait a minute.
   3. Reopen the graphical console and log in to the Windows desktop.
10. To transform this singleton into a fully managed CA AppLogic appliance, execute the Windows Server exe installer. You can find this self-executing installer on the E drive of the singleton.

    1. In the command shell, navigate to the new folder on the E drive.
    2. Double-click the Server Windows exe file to perform the base class appliance installation.

       The Windows APK is installed as a pre-requisite.

11. If there are junction points on the volume, Windows appliance volume resizing fails. Delete junction points to prevent Windows volume resize failures. The following examples show junction points that you can find on a Windows boot volume.

    • WINDOWS\assembly\GAC_32\System.EnterpriseServices\2.0.0.0__b03f5f7f11d50a3a\
    • WINDOWS\assembly\GAC_MSIL\IEExecRemote\2.0.0.0__b03f5f7f11d50a3a\

    Note: The names on your volumes can be different.

    You can search for junction points using the Command Prompt. The output of the following command reports the path for any junction points that it finds:

    dir/S /A:L
    

12. If you intend to install the TurboGate PV drivers, execute the following command:

    copy E:\TurboGate-Tools-Setup-V3.0.1.exe C:\
    

    Note: Do not execute the Turbogate installer until after you have completed installation of the basic OS.

13. Shutdown the OS (to ensure required system configuration takes effect) using the following steps:

    1. In the command shell, type the following command and press Enter:

       shutdown –s –t 0
       

    2. Wait five seconds.
    3. 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 re-starts the application.

14. Change the resulting singleton into a WIN08y catalog appliance class using the following steps:

    Note: The resource table contains information about the resource setting for the correct edition.

    1. Stop the application.
    2. Open the application in the CA AppLogic editor.
    3. Right-click on the singleton and select Attributes. Change the instance name to WIN08y.
    4. Right-click on the singleton and select Modify Boundary.

       A dialog opens.

15. Perform the following steps in this dialog:

    1. Change the class name to WIN08y.
    2. Enter the following description:

       Windows Server Appliance – based on Windows Server 2008 Standard Edition without Hyper-V SP2 32-bit

       Note: Use the correct edition name.

    3. Use the Windows Server 2008 information in the resource table to change the resource settings based on the windows edition.
    4. Select the OS icon as Windows.
    5. Set the documentation URL to the following URL:

       http://doc.3tera.com/AppLogic35/index.htm?toc.htm?CatGenericWindows.html
       

    6. Save the application when prompted.
16. Complete the appliance.

Note: Review the Appliance Catalog Reference Guide for details about the behavior of the Windows APK that is required by all of the Windows MSIs.

5.1 Complete the Appliance (Windows Server 2008)

Completing the appliance includes making changes if you configure TurboGate PV drivers.

Note: Perform the steps in this procedure if you are installing the TurboGate PV drivers. If not, see the note at the end of this procedure.

Follow these steps:

1. In the modify boundary dialog for the singleton:

   1. 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.
   2. Add three placeholder volumes to the appliance; do not assign mount points for these volumes. This step, and the following related steps, are required to help ensure that new volumes added to an appliance are properly recognized and brought online.
2. Create three raw 50 MB volumes and configure the singleton instance to use these volumes for the placeholder volumes.
3. Save and start the application. SSH into the appliance and set the Administrator password (net user administrator new password).

   Note: Change the administrator password because the Server Windows EXE sets a new random password on initial boot and you must know the Administrator password before installing the TurboGate PV drivers.

4. Log in through the graphical console.
5. Execute diskpart in a cmd.exe shell in the graphical console to format and mount the three raw volumes. Within the diskpart command line interface, execute the command list disk.

   1. Execute the following commands for each disk (except the boot disk):

      • select disk # (use the appropriate number)
      • online disk # (if the disk is already online this can be skipped)
      • create partition primary
      • assign letter=D (use a different letter for each disk, for example, D, E, F)
   2. Exit from the diskpart interface.
   3. Format each volume in the cmd.exe shell, for example: format /fs:ntfs d:, and so on.
6. Execute the PV driver installer (for example, C:\TurboGate-Tools-Setup-V3.0.exe). Select Install Anyway as required. Do not reboot after the install.
7. Open a 3T shell and execute the following command:

   app restart win08_install –debug
   

8. Wait one minute after the application begins to start, log in using the graphical console and wait for a minute or so until the driver installation completes (this is indicated by the pop-up requesting a restart). Restart the appliance as indicated.

   Note: Perform one of the following sets of steps, depending on whether the app start has timed out:

   • If the application start has not timed out, it may complete normally; otherwise, shutdown the OS from within the graphical console, which causes the app start –debug to fail, and execute the following command in the 3T shell:

     app stop win08_install
     

   • If the application start has timed out, execute the following command in the 3T shell, followed by shutdown within the graphical console:

     app stop win08_install 
     

9. Within the 3T shell, execute app start win08_install and verify the appliance starts without error.
10. Log in through the graphical console:

    1. Verify all of the disks are online using diskpart in a cmd.exe shell:

       diskpart
       list disk
       exit
       

    2. If you have installed version 3.0.1 of the TurboGate PV drivers, click Start > Run > services.msc to disable the service 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.
11. In a bash shell on the appliance perform the following steps:

    1. Set a new complex password (for example, net user administrator pq398hpaowht0293j^LWOIFH9htfw9jfe).
    2. Exit the SSH session.
    3. SSH into the appliance and execute the following command:

       rm –f ~/.bash_history /cygdrive/c/TurboGate* /appliance/passwd.stamp
       

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

    Note: Ensure that you have full access rights to the catalog. These rights are required to move the singleton.

The WIN08y appliance is now ready for use.

Note: If you are not installing the TurboGate PV drivers, perform the following steps to complete the appliance:

1. Start the application and securely log in to the appliance using SSH.
2. Execute the following command:

   rm –rf /appliance/passwd.stamp ~/.bash_history
   

3. Exit, stop the application, and move the singleton into the /system_ms catalog.

   Note: Ensure that you have full access rights to the catalog. These rights are required to move the singleton.

6.0 Resources

• Windows Server 2003 Resources

32-bit appliances

64-bit appliances

• Windows Server 2008 Resources

• Windows Server 2008 Resources

The resource settings for the Windows Server 2008 base classes are listed as follows:

7.0 Automated Steps

The following steps are automated in AppWinCfg.vbs:

• Windows 2008

• Set the screen resolution and screen saver timeout.

  To perform this step manually:

  1. Right-click an empty area of the desktop and select Personalize.
  2. Set the screen resolution to 1024x768 and the screen saver timeout to 1000 minutes (or disable it).

  Note: On 64-bit versions of Windows Server 2008 R2, click Start, Control Panel, Appearance, Change screen resolution or right-click an empty area of the desktop and click Screen resolution.

• Disable the page file.

  To perform this step manually:

  1. Click Start, Control Panel, System, Advanced system settings, Advanced, Performance Settings, Advanced, Change Virtual Memory.
  2. Clear the check box Automatically manage paging file size for all drives and click No paging file.
  3. Click Set.
  4. Click Restart Later.
• Disable power management hibernation support.

  To perform this step manually:

  1. Click Start, Command Prompt.
  2. Enter powercfg –h off.
• Disable IE enhanced security.

  To perform this step manually:

  1. Open Server Manager, Configure IE ESC, and turn IE enhanced security off for both administrators and users.
• Clean up the leftover page file, if present.

  To perform this step manually:

  1. Open Windows explorer.
  2. Click Organize, Folder and search options, View and select Show hidden files and folders.
  3. Clear the checkbox, Hide protected operating system files.
  4. Delete the file C:\pagefile.sys if it is present.
  5. Restore the default settings under Organize, Folder and search options, View.
• Disable external network access.

  To perform this step manually:

  1. Open Server Manager, View Network Connections, Local Area Connection, Properties, TCP/IPv4, Properties.
  2. Click Obtain an IP Address automatically and Obtain DNS server address automatically.
• Disable Windows Firewall.

  To perform this step manually:

  1. Open Server Manager, and go to Windows Firewall, Windows Firewall properties.
  2. Set the firewall to Off for Domain Profile, Private Profile and Public Profile.
• Disable Windows Automatic Updates.

  To perform this step manually:

  1. Open Server Manager, Configure Updates, Change Settings.
  2. Click Never check for updates.
• Disable password complexity (if set).

  To perform this step manually:

  1. Open Start, Administrative Tools, Local Security Policy, Account Policies, Password Policy.
  2. Disable password complexity requirements.
• Set the Administrator password never to expire.

  To perform this step manually:

  1. Open Server Manager, Configuration, Local Users and Groups, Users, Administrator, Properties.
  2. Select Password Never Expires.
• Disable the shutdown event tracker.

  To perform this step manually:

  1. Open the Group Policy Editor (Run > gpedit.msc).
  2. Open Computer Configuration, Administrative Templates, System.
  3. Scroll down on the right pane and right-click Display Shutdown Event Tracker, Properties.

     Note: On 64-bit versions, click Display Shutdown Event Tracker, Edit.

  4. Select Disabled and click OK.
• Set the default Windows disk device timeout value to 60 seconds as required.

  To perform this step manually:

  1. Open the registry editor (Run > regedit.exe) and navigate to the key HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/Disk.
  2. If there is already an entry name TimeOutValue, set the timeout to 60 seconds as required. Otherwise add a new REG_DWORD value named TimeOutValue (if this value already exists, skip this step).
  3. Set the TimeOutValue to 60 decimal.
  4. Close the registry editor.
• Disable TCP checksum offload (for TurboGate PV drivers).

  To perform this step manually:

  1. In the registry editor, navigate to HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/Tcpip/Parameters.
  2. Right-click Parameters in the left pane and select New, DWORD.
  3. Type DisableTaskOffload and press Enter.
  4. Right-click DisableTaskOffload, click modify, and enter 1.
  5. Close the registry editor.

• Windows 2003

• Disable the page file.

  To perform this step manually:

  1. Click Start, Control Panel, System, Advanced, Performance Settings, Advanced, Virtual Memory, No Paging File, Set to disable the page file.
  2. Restart the application.
• Clean up the leftover page file, if present.

  To perform this step manually:

  1. Open Windows Explorer, Tools, Folder Options, View, and select Show hidden files and folders.
  2. Clear the checkbox, Hide protected operating system files.
  3. Verify the page file: C:\pagefile.sys has been deleted. If not, delete it manually.

     Note: To display protected operating system files in Windows Explorer, change the default settings by clicking Tools, Folder Options, View, and clear the checkbox, Hide protected operating system files.

• Disable WIndows Firewall.

  To perform this step manually:

  1. Open Control Panel and go to Windows Firewall.
  2. Set the firewall to Off.
• Disable Windows Automatic Updates

  To perform this step manually:

  1. Open Control Panel and go to Automatic Updates.
  2. Click Turn off Automatic Updates.
• Increase the default Windows disk device timeout value.

  To perform this step manually:

  1. Open the registry editor (Run > regedit.exe) and navigate to the key HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/Disk.
  2. If there is already an entry name TimeOutValue, set the timeout to 60 seconds as required. Otherwise add a new REG_DWORD value named TimeOutValue (if this value already exists, skip this step).
  3. Set the TimeOutValue to 60 decimal.
  4. Close the registry editor.
• Remove the restore files that are associated with the installation of SP2.

  To perform this step manually:

  1. In Windows Explorer, delete the folder C:\WINDOWS\$NtServicePackUninstall$ and empty the Recycle Bin.
• Compress contents for folder C:\Windows\ServicePackFiles.

  To perform this step manually:

  1. In Windows Explorer, right-click the folder and select Properties, Advanced, Compress contents. Compress all sub-directories too.
• Remove the restore files that are associated with the installation of high priority updates.

  To perform this step manually:

  1. In Windows Explorer, delete C:\WINDOWS\$*$ (approximately 30 folders) and empty the Recycle Bin.
• Prevent system shutdown dialogs from popping up.

  To perform this step manually:

  1. Open the Group Policy Editor (Run > gpedit.msc).
  2. Browse to Computer Configuration, Administrative Templates, and click System.
  3. In the right pane, double-click Display Shutdown Event Tracker.
  4. Click Disabled and click Apply.
• Configure external NIC to use DHCP.

  To perform this step manually:

  1. From Network Connections, click Local Area Connection, Properties, TCP/IPv4, Properties.
  2. Click Obtain an IP Address automatically and Obtain DNS server address automatically.
• On 64-bit Windows, copy shutdown.exe from C:\Windows\system32 to C:\Windows\SYSWOW64.

  If Windows Explorer does not copy the executable file and instead moves it, perform the following manual steps:

  1. In Windows Explorer, move shutdown.exe to C:\Windows.
  2. Open a bash shell and perform the following command:

     cp –p /cygdrive/c/WINDOWS/shutdown.exe cygdrive/c/WINDOWS/system32/shutdown.exe
     

     This command copies the file into the C:\WINDOWS\SYSWOW64 directory.

  3. Use Windows Explorer to move C:\WINDOWS\shutdown.exe to C:\WINDOWS\system32\shutdown.exe.
• If installing 64-bit localized version of W2K3, copy chcp.com from C:\Windows\system32 to C:\Windows\SYSWOW64.

  To perform this step manually:

  1. In Windows Explorer, move shutdown.exe to C:\Windows.
  2. Open a bash shell and perform the following command:

     cp –p /cygdrive/c/WINDOWS/shutdown.exe cygdrive/c/WINDOWS/system32/shutdown.exe
     

     This command copies the file into the C:\WINDOWS\SYSWOW64 directory.

  3. Use Windows Explorer to move C:\WINDOWS\shutdown.exe to C:\WINDOWS\system32\shutdown.exe.

8.0 Contact CA Technologies

Contact CA Support

For your convenience, CA Technologies provides one site where you can access the information that you need for your Home Office, Small Business, and Enterprise CA Technologies products. At http://ca.com/support, you can access the following resources:

• Online and telephone contact information for technical assistance and customer services
• Information about user communities and forums
• Product and documentation downloads
• CA Support policies and guidelines
• Other helpful resources appropriate for your product

Providing Feedback About Product Documentation

If you have comments or questions about CA Technologies product documentation, you can send a message to techpubs@ca.com.

To provide feedback about CA Technologies product documentation, complete our short customer survey which is available on the CA Support website at http://ca.com/docs.

Copyright © 2012 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.