Using CA AppLogic › Appliance Developer Guide › Appliance OS Installations › Common Components › Windows APK › Halsign TurboGate PV Drivers › Upgrade Halsign TurboGate PV Drivers › Upgrade Halsign TurboGate PV Drivers in Generic Windows Server Appliances

Upgrade Halsign TurboGate PV Drivers in Generic Windows Server Appliances

The following steps describe the process for upgrading a generic Windows server appliance, using /system_ms:WIN08S as an example.

Follow these steps:

1. Create a new application and open it in the Infrastructure Editor. Drag an instance of the WIN08S appliance from the system_ms catalog onto the canvas and branch the class instance.
2. Modify the boundary of the singleton as follows:
   • Set the documentation URL to

     http://doc.3tera.com/AppLogicxx/CatGenericWindows.html

     where xx is the CA AppLogic version

   • Add sufficient terminals such that the total terminal count, plus the internal interface, equals 8 for XEN and equals 10 for ESX.
3. If you are updating an appliance based on Windows Server 2008:
   • Add sufficient placeholder volumes such that the total volume count, including the boot volume, equals 4. Configure the new placeholder volumes to mount using drive letters, for example, K:\, L:\, M:\ as required.
   • Create sufficient volumes of type ntfs08 and size 50 MB to use for the placeholder volumes.
   • Configure the singleton instance and set the placeholder volumes to use the created volumes.
4. Save and start the application with the --debug option. If the appliance is based on Windows Server 2008 and was not prepared using a total of 4 volumes, then the appliance start may fail. Hence, the --debug option is used. An appliance start fail in this regard may be ignored.
5. From a 3t shell, ssh into the running singleton and do the following:
   • Set a new Administrator password, for example net user administrator newpwd.
   • ipconfig /all | grep 'DHCP Server' and note the IP address of the DHCP server for the internal interface.
   • cd / and then use wget to obtain the current TurboGate PV drivers installer from the grid controller using the IP address noted above, for example wget http://ip-address:8080/download/TurboGate-Tools-Setup-V3.0.1.exe
   • chmod 755 *.exe
6. Open the graphic console for the singleton and log in as Administrator.
7. Use the control panel to remove the outdated version of TurboGate PV drivers. The OS will blue screen mid-way through the program removal.
8. Restart the application --debug, open the graphic console for the singleton, log in as Administrator and use the control panel to remove the outdated version of TurboGate PV drivers. This time, there should not be a BSOD (blue screen of death). Do not reboot when requested.
9. Restart the application using the --debug option.
10. Open the graphic console for the singleton and log in as Administrator.
11. Install the latest Turbogate PV drivers by double-clicking on the installer in Windows Explorer. Do not reboot when prompted. Delete the PV driver installer and empty the recycle bin.
12. Restart the application using the --debug option.
13. Open the graphic console for the singleton and log in as Administrator. As required, complete the PV driver installation, for example, click through the hardware setup wizard. On Windows Server 2003 this typically means clicking through the Found New Hardware Wizard for each virtual network interface: No, not this time, Next, Install the software automatically, Next, Continue Anyway, Finish. On Windows Server 2008 this typically means waiting until all the new devices are recognized and installed and a pop-up appears on the desktop asking to restart (select Restart Later).
14. 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.
15. Restart the application with the --debug option (you may have to wait for the previous restart to timeout). If you do not have a successful start, it is most likely the case that you are installing the PV drivers on a version of Windows Server 2008 and the original appliance was not properly prepped to include all four possible disks. If this is the case:
    • Open the graphic console for the singleton and log in as Administrator. Open a cmd.exe shell and start diskpart. For each disk which is offline:
      • sel disk # (use the appropriate number)
      • online disk
      • attr disk remove read-only (this attribute may not be set and therefore failure can be ignored)
    • Restart the application using the --debug option.
16. From a 3t shell ssh to the singleton and execute:
    • rm -f /TurboGate*.exe
    • Set a new complex Administrator password, for example net user administrator a3893hf092jfww.^JDFoi8hfwehohgw
    • Exit and then ssh back into the running singleton
    • rm -f ~/.bash_history
    • Exit
17. Stop the application.
18. In the infrastructure editor modify the boundary of the singleton and remove any extra terminals or placeholder volumes you may have added. Drag the singleton into the user catalog.
19. Execute the following commands in a 3t shell:

    class destroy /system_ms:WIN08S --force (or move the existing class if you want to preserve it). 
    class move /user:WIN08S /system_ms:WIN08S 
    

20. Destroy the application.