Using CA AppLogic® › Appliance Developer Guide › OS Installation › Distribution Installations › Windows Appliance Installation › Windows Installation Reference › Windows Halsign TurboGate PV Drivers Upgrade Reference

Windows Halsign TurboGate PV Drivers Upgrade Reference

This document details the method used to upgrade the Halsign TurboGate PV drivers from a previous version to the latest. The v3.0.1 version of the drivers offers support for 64-bit Windows Server 2008 which was lacking in the v2.0 version of the drivers. So, in general, this upgrade is optional. Existing appliances which use the v2.0 TurboGate PV drivers will continue to work and upgrading to the v3.0.1 version of the drivers does not offer significant performance gains. If you want to upgrade these PV drivers in your existing appliances, this topic provides step-by-step instructions for doing so. The instructions are organized by type of appliance.

WIN03* / WIN08* - Generic Windows Server Appliances

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

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/AppLogic35/CatGenericWindows.html.
   • Add sufficient terminals such that the total terminal count, plus the internal interface, equals 8.
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.

VDS_Win* - Windows VDS Singleton Appliances

We recommend that you first update the PV drivers in the generic Windows server appliance used to create the VDS singleton. You may then update the boot volume of the VDS singleton using its base class. The following steps describe the process for upgrading the singleton in a Windows VDS application, using the application VDS_Win08S_r2 as an example.

1. Create a new application and open it in the infrastructure editor. Drag an instance of the WIN08S appliance (with updated TurboGate PV drivers) from the system_ms catalog onto the canvas and branch the class instance.
2. Save and start the application.
3. 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 Windows VDS MSI from the grid controller using the IP address noted above, for example wget http://ip-address:8080/download/VDS_Windows-2.0.4-1.msi
   • chmod 755 *.msi
4. Open the graphic console for the singleton and log in as Administrator.
5. Execute the MSI installer, for example double-click the file VDS_Windows-2.0.4-1.msi within Windows Explorer.
6. In the ssh session, open on the singleton:
   • rm -f *.msi
   • 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
7. Stop the application.
8. Execute the following commands in a 3t shell:

   vol destroy VDS_Win08S_r2:VDS_WIN08S.boot --force 
   vol copy app-name:WIN08S.boot VDS_Win08S_r2:VDS_WIN08S.boot where app-name is the name of the application you have created
   

9. Destroy the application app-name.

Filer_Windows08 - Windows 2008 Filer Appliance

The following steps describe the process for upgrading the /system_ms:Filer_Windows08 appliance:

1. As a administrator, unlock the existing Windows 2008 filer class: 3t class unlock /system_ms:Filer_Windows08.
2. Create a new application and open it in the editor. Drag an instance of Filer_Windows08 from the system_ms catalog onto the canvas and branch the class instance.
3. Modify the boundary of the singleton as follows:
   • Set the documentation URL to http://doc.3tera.net/AppLogic35/CatFilerWindows08.html.
4. Create two volumes of type ntfs08 and size 50 MB to use for the placeholder volumes. Configure the singleton instance and set the src and dst placeholder volumes to use the created volumes.
5. Configure the singleton instance and set the following property values:
   • mode = manual
   • debug_options = sshd=1 no_op=1 (the value of the debug_options property is a space separated list of variable=value pairs)
6. Save and start the application.
7. 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
8. Open the graphic console for the singleton and log in as Administrator.
9. Use the command shell to execute C:\Program Files\Halsign TurboGate\uninst.exe. The OS will blue screen mid-way through the program removal.
10. Restart the application --debug, open the graphic console for the singleton, log in as Administrator and execute the uninstaller again if the first uninstallation did not complete. This time, there should not be a BSOD (blue screen of death). Do not reboot when requested.
11. Restart the application using the --debug option.
12. Open the graphic console for the singleton and log in as Administrator.
13. Install the v3.0.1 TurboGate PV drivers using the command shell. Do not reboot when prompted. Delete the PV driver installer.
14. Restart the application using the --debug option.
15. Open the graphic console for the singleton and log in as Administrator. As required, complete the PV driver installation. 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).
16. 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.
17. Restart the application using 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 the possible disks. If this is the case:
    • Open the graphic console for the singleton and log in as Administrator. In the command shell 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.
18. From a 3t shell ssh to the singleton and execute:
    • rm -f /*.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
19. Stop the application. In the infrastructure editor drag the singleton into the user catalog.
20. As an administrator, execute the following commands:

    3t class destroy /system_ms:Filer_Windows08 --force 
    

    (or move the existing class if you want to preserve it).

    3t class move /user:Filer_Windows08 /system_ms:Filer_Windows08 
    3t class lock /system_ms:Filer_Windows08 
    

21. Destroy the application.

Filer_Windows03 - Windows 2003 Filer Appliance

The following steps describe the process for upgrading the /system_ms:Filer_Windows03 appliance. The Windows boot volume of this appliance is a local application volume named windows in the Sys_Filer_Windows03 application. This Windows boot volume is upgraded.

1. As an administrator, unlock the existing Sys_Filer_Windows03 application: 3t app unlock Sys_Filer_Windows03.
2. Create a new application and open it in the editor. Drag an instance of WIN03S from the system_ms catalog onto the canvas and branch the class instance.
3. Modify the boundary of the singleton as follows:
   • Add a property mode of type string.
   • Add a property fs_type_src of type string.
   • Add a property fs_type_dst of type string.
   • Add a property debug_options of type string.
4. Configure the singleton instance and set the following property values:
   • mode = manual
   • fs_type_src = ntfs03
   • fs_type_dst = ntfs03
   • debug_options = sshd=1 no_op=1 (the value of the debug_options property is a space separated list of variable=value pairs)
5. Save the application.
6. In a 3t shell:
   • Destroy the boot volume of the singleton, for example vol destroy app-name:WIN03S.boot --force.
   • Copy the windows volume from the Sys_Filer_Windows03 application to the boot volume of the singleton, for example vol copy Sys_Filer_Window03:windows app-name:WIN03S.
7. Start the application.
8. 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
9. Open the graphic console for the singleton and log in as Administrator.
10. Use the control panel to remove the existing version 2.0 TurboGate PV drivers. The OS will blue screen mid-way through the program removal.
11. Restart the application --debug, open the graphic console for the singleton, log in as Administrator and use the control panel to remove the existing version 2.0 TurboGate PV drivers again. This time, there should not be a BSOD (blue screen of death). Do not reboot when requested.
12. Restart the application using the --debug option.
13. Open the graphic console for the singleton and log in as Administrator.
14. Install the v3.0.1 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.
15. Restart the application using the --debug option.
16. Open the graphic console for the singleton and log in as Administrator. As required, complete the PV driver installation. 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.
17. 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.
18. Restart the application using the --debug option (you may have to wait for the previous restart to timeout).
19. 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
20. Stop the application.
21. Execute the following commands in a 3t shell:

    vol destroy Sys_Filer_Windows03:windows --force 
    

    (first copy this volume to a global volume if you want to preserve it).

    vol copy app-name:WIN03S Sys_Filer_Windows03:windows 
    

22. As an administrator, execute the following command:

    3t app lock Sys_Filer_Windows03 
    

23. Destroy the application used to create the singleton.

IIS03* / IIS08* - Windows IIS Web Server Appliance

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

1. Create a new application and open it in the editor. Drag an instance of the IIS08S 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/AppLogic35/index.htm?toc.htm?1978955.html.
   • 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.
3. Create sufficient volumes of type ntfs08 (ntfs03 for Windows Server 2003 based appliances) and size 50 MB to use for the placeholder volumes.
4. Configure the singleton instance and set the placeholder volumes to use the created volumes.
5. Save and start the application using 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.
6. Save and start the application.
7. 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
8. Open the graphic console for the singleton and log in as Administrator.
9. Use the control panel to remove the existing version 2.0 TurboGate PV drivers. The OS will blue screen mid-way through the program removal.
10. Restart the application --debug, open the graphic console for the singleton, log in as Administrator and use the control panel to remove the existing version 2.0 TurboGate PV drivers again. This time, there should not be a BSOD (blue screen of death). Do not reboot when requested.
11. Restart the application using the --debug option.
12. Open the graphic console for the singleton and log in as Administrator.
13. Install the v3.0.1 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.
14. Restart the application using the --debug option.
15. 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).
16. 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.
17. Restart the application using 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 the placeholder volumes. 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.
18. 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
19. Stop the application. In the infrastructure editor drag the singleton into the user catalog.
20. Execute the following commands in a 3t shell:

    class destroy /system_ms:IIS08S --force 
    

    (or move the existing class if you want to preserve it).

    class move /user:IIS08S /system_ms:IIS08S 
    

21. Destroy the application.

SQL08* - Windows SQL Server Appliance

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

1. Create a new application and open it in the infrastructure editor. Drag an instance of the SQL08S_08 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/AppLogic35/index.htm?toc.htm?CatDatabaseAppliancesSQL.html.
   • Add sufficient terminals such that the total terminal count, plus the internal interface, equals 8.
   • 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.
3. Create a 3 GB raw volume and configure the singleton to use this volume as its data volume.
4. Create 50 MB ntfs08 (ntfs03 for Windows Server 2003 appliances) volumes to use for the remaining placeholder volumes and configure the singleton to make use of them.
5. Save and start the application.
6. 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
7. Open the graphic console for the singleton and log in as Administrator.
8. Use the control panel to remove the existing TurboGate PV drivers. The OS will blue screen mid-way through the program removal.
9. Restart the application --debug, open the graphic console for the singleton, log in as Administrator and use the control panel to remove the existing TurboGate PV drivers again. This time, there should not be a BSOD (blue screen of death). Do not reboot when requested.
10. Restart the application using the --debug option.
11. Open the graphic console for the singleton and log in as Administrator.
12. Install the v3.0.1 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.
13. Restart the application using the --debug option.
14. 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).
15. 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.
16. Restart the application using 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 the placeholder volumes. 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.
17. 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
18. Stop the application. In the infrastructure editor drag the singleton into the user catalog.
19. Execute the following commands in a 3t shell:

    class destroy /system_ms:SQL08S_08 --force 
    

    (or move the existing class if you want to preserve it).

    class move /user:SQL08S_08 /system_ms:SQL08S_08 
    

20. Destroy the application