Using CA AppLogic® › Appliance Developer Guide › Creating Appliances › Distribution Installations › Windows Installation Reference › Windows MSI Upgrade Reference

Windows MSI Upgrade Reference

You can update the Windows APK and any appliance specific scripts contained in the MSI. For example, if you built a Windows appliance and want to install a newer version of the MSI that created that appliance.

To begin, locate the type of appliance, then perform the steps.

Note: The Server Windows exe contains the APK. The APK performs an automated prep script prior to installing the APK. You can disable the automated prep script, if you have already prepared the machine. During the Install, elect Custom and disable the Prep script. You can then manually perform the APK prep script. To review the manual steps, refer to Manually Perform APK Prep Script.

WIN03* / WIN08* - Generic Windows Server Appliances

Perform the following steps to upgrade a generic Windows server appliance, using /system_ms:WIN08S as an example.

1. Create a new application and open it in the infrastructure editor.
2. Drag an instance of the WIN08S appliance 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.com/AppLogic35/en/index.htm?toc.htm?CatGenericWindows.html.
4. Save and start the application.
5. From a 3t shell, ssh into the running singleton and perform the following steps:
   • Set a new Administrator password, such as 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 Server MSI from the grid controller using the IP address noted above. For example, wget http://ip-address:8080/download/Server_Windows-1.1.7-1.msi
   • chmod 755 *.msi
6. Open the graphical console for the singleton and log in as Administrator.
7. Execute the MSI installer by double clicking the file Server_Windows-1.1.7-1.msi in Windows Explorer.
8. In the ssh session open on the singleton:
   • rm -f *.msi
   • Set a new complex Administrator password, such as net user administrator a3893hf092jfww.^JDFoi8hfwehohgw
   • Exit and then ssh back into the running singleton
   • rm -f ~/.bash_history
   • Exit
9. Stop the application.
10. In the infrastructure editor, drag the singleton into the user catalog.
11. 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 
    

12. Destroy the application.

VDS_Win* - Windows VDS Singleton Appliances

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.
2. Drag an instance of the WIN08S appliance from the system_ms catalog onto the canvas and branch the class instance.
3. Save and start the application.
4. From a 3t shell, ssh into the running singleton and do the following:
   • Set a new Administrator password, such as 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-1.2.4-1.msi
   • chmod 755 *.msi
5. Open the graphical console for the singleton and log in as Administrator.
6. Execute the MSI installer by double-clicking the file VDS_Windows-1.2.4-1.msi in Windows Explorer.
7. In the ssh session open on the singleton:
   • rm -f *.msi
   • Set a new complex Administrator password, such as net user administrator a3893hf092jfww.^JDFoi8hfwehohgw
   • Exit and then ssh back into the running singleton
   • rm -f ~/.bash_history
   • Exit
8. Stop the application.
9. 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. 
   

10. Destroy the application app-name.

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 infrastructure editor.
2. Drag an instance of the IIS08S appliance 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.com/AppLogic35/index.htm?toc.htm?1978955.html.
4. Create a 100 MB ntfs08 volume (or ntfs03 volume for Windows Server 2003 based IIS appliances) and configure the singleton to use this volume as its content volume.
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, such as 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 IIS MSI from the grid controller using the IP address noted above. For example, wget http://ip-address:8080/download/IIS_Windows-1.1.1-1.msi
   • chmod 755 *.msi
7. Open the graphical console for the singleton and log in as Administrator.
8. Execute the MSI installer by double-clicking the file IIS_Windows-1.1.1-1.msi in Windows Explorer.
9. In the ssh session, open on the singleton:
   • rm -f *.msi
   • Set a new complex Administrator password, such as net user administrator a3893hf092jfww.^JDFoi8hfwehohgw
   • Exit and then ssh back into the running singleton
   • rm -f ~/.bash_history
   • Exit
10. Stop the application.
11. In the infrastructure editor, drag the singleton into the user catalog.
12. 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 
    

13. 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.
2. Drag an instance of the SQL08S_08 appliance 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.com/AppLogic35/CatDatabaseAppliancesSQL.html.
4. Create a 3 GB raw volume and configure the singleton to use this volume as its data volume.
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, such as 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 SQL MSI from the grid controller using the IP address noted above, for example wget http://ip-address:8080/download/SQL_Windows-1.1.1-1.msi
   • chmod 755 *.msi
7. Open the graphical console for the singleton and log in as Administrator.
8. Execute the MSI installer by double-clicking the file SQL_Windows-1.1.1-1.msi in Windows Explorer.
9. In the ssh session, open on the singleton:
   • rm -f *.msi
   • Set a new complex Administrator password, such as net user administrator a3893hf092jfww.^JDFoi8hfwehohgw
   • Exit and then ssh back into the running singleton
   • rm -f ~/.bash_history
   • Exit
10. Stop the application.
11. In the infrastructure editor, drag the singleton into the user catalog.
12. 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 
    

13. Destroy the application