Using CA AppLogic › Appliance Developer Guide › Appliance OS Installations › Common Components › Windows APK › Halsign TurboGate PV Drivers › Upgrade Halsign TurboGate PV Drivers › Upgrade PV Drivers in Windows 2008 Filer Appliance

Upgrade PV Drivers in Windows 2008 Filer Appliance

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

Follow these steps:

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/AppLogicxx/CatFilerWindows08.html.

     where xx is the current version of CA AppLogic

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.
20. In the infrastructure editor drag the singleton into the user catalog.
21. 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 
    

22. Destroy the application.