Windows MSI Upgrade Reference

If you have built a Windows appliance and wish at some point to install a newer version of the MSI used to create that appliance, thereby updating the Windows APK and any appliance specific scripts contained in the MSI, this topic provides step-by-step instructions for doing this. The instructions are segregated 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 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.net/AppLogic29/CatGenericWindows.html.
3. Save and then start the application.
4. From a 3t shell, ssh into the running singleton and do the following:
   • Set a new Administrator password, e.g. 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, e.g. wget http://ip-address:8080/download/Server_Windows-1.1.7-1.msi
   • chmod 755 *.msi
5. Open the graphic console for the singleton and log in as Administrator.
6. Execute the MSI installer, e.g. double click on the file Server_Windows-1.1.7-1.msi within Windows Explorer.
7. In the ssh session open on the singleton:
   • rm -f *.msi
   • Set a new complex Administrator password, e.g. net user administrator a3893hf092jfww.^JDFoi8hfwehohgw
   • exit and then ssh back into the running singleton
   • rm -f ~/.bash_history
   • exit
8. Stop the application. In the application editor drag the singleton into the user catalog.
9. In a 3t shell:
   • class destroy /system_ms:WIN08S --force (or move the existing class if you wish to preserve it).
   • class move /user:WIN08S /system_ms:WIN08S
10. 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 editor. Drag an instance of the WIN08S appliance from the system_ms catalog onto the canvas and branch the class instance.
2. Save and then start the application.
3. From a 3t shell, ssh into the running singleton and do the following:
   • Set a new Administrator password, e.g. 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, e.g. wget http://ip-address:8080/download/VDS_Windows-1.2.4-1.msi
   • chmod 755 *.msi
4. Open the graphic console for the singleton and log in as Administrator.
5. Execute the MSI installer, e.g. double click on the file VDS_Windows-1.2.4-1.msi within Windows Explorer.
6. In the ssh session open on the singleton:
   • rm -f *.msi
   • Set a new complex Administrator password, e.g. net user administrator a3893hf092jfww.^JDFoi8hfwehohgw
   • exit and then ssh back into the running singleton
   • rm -f ~/.bash_history
   • exit
7. Stop the application.
8. 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 maintainer, 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/AppLogic29/CatFilerWindows08.html.
4. If you are updating Filer_Windows08 on AppLogic 2.9.9 using a version of this appliance built on a version of AppLogic prior to 2.9.9 please note that the boundary of the Filer_Windows08 appliance has changed in AppLogic 2.9.9. In this case, please modify the boundary of the singleton as follows:
   • Change the dst volume so that it is not mandatory.
   • Change the property fs_type_dst so that it is not mandatory.
   • Change the Size in the Visual section of the General tab to Large.
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 then start the application.
7. From a 3t shell, ssh into the running singleton and do the following:
   • Set a new Administrator password, e.g. 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 Filer MSI from the grid controller using the IP address noted above, e.g. wget http://ip-address:8080/download/Filer_Windows-2.0.10-1.msi
   • chmod 755 *.msi
8. Open the graphic console for the singleton and log in as Administrator.
9. In the command shell execute the MSI installer: C:\cygwin\Filer_Windows-2.0.10-1.msi.
10. In the ssh session open on the singleton:
    • rm -f *.msi
    • Set a new complex Administrator password, e.g. net user administrator a3893hf092jfww.^JDFoi8hfwehohgw
    • exit and then ssh back into the running singleton
    • rm -f ~/.bash_history
    • exit
11. Stop the application. In the application editor drag the singleton into the user catalog.
12. As a maintainer:
    • 3t class destroy /system_ms:Filer_Windows08 --force (or move the existing class if you wish to preserve it).
    • 3t class move /user:Filer_Windows08 /system_ms:Filer_Windows08
    • 3t class lock /system_ms:Filer_Windows08
13. Destroy the application.

If you executed the boundary change in step #4, then you should also update the Sys_Filer_Windows08 template application. To do this, simply install the current version of the application from the 2.9.9 AppLogic distro:

1. In a 3t shell app destroy Sys_Filer_Windows08 --force
2. On the aldo server for your grid, within the directory of the 2.9.9 distro ./aldo ai applications=Sys_Filer_Windows08

Filer_Windows03 - Windows 2003 Filer Appliance

The following steps describe the process for upgrading the /system_ms:Filer_Windows03 appliance. Note that 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 a maintainer, 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, e.g. vol destroy app-name:WIN03S.boot --force.
   • Copy the windows volume from the Sys_Filer_Windows03 application to the boot volume of the singleton, e.g. 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, e.g. 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 Filer MSI from the grid controller using the IP address noted above, e.g. wget http://ip-address:8080/download/Filer_Windows-2.0.10-1.msi
   • chmod 755 *.msi
9. Open the graphic console for the singleton and log in as Administrator.
10. In the command shell execute the MSI installer: C:\cygwin\Filer_Windows-2.0.10-1.msi.
11. In the ssh session open on the singleton:
    • rm -f *.msi
    • Set a new complex Administrator password, e.g. net user administrator a3893hf092jfww.^JDFoi8hfwehohgw
    • exit and then ssh back into the running singleton
    • rm -f ~/.bash_history
    • exit
12. Stop the application.
13. In a 3t shell:
    • vol destroy Sys_Filer_Windows03:windows --force (first copy this volume to a global volume if you wish to preserve it).
    • vol copy app-name:WIN03S Sys_Filer_Windows03:windows
14. As a maintainer:
    • 3t app lock Sys_Filer_Windows03
15. Destroy the application used to create the singleton.

If you are updating Filer_Windows03 on AppLogic 2.9.9 using a version of this appliance built on a version of AppLogic prior to 2.9.9 please note that the boundary of the Filer_Windows03 appliance and the Sys_Filer_Windows03 application have changed in AppLogic 2.9.9. In this case:

1. As a maintainer:
   • 3t app rename Sys_Filer_Windows03 Sys_Filer_Windows03_old
   • 3t class move /system_ms:Filer_Windows03 /system_ms:FW03old
   • 3t cat rename /system_ms /system_ms_save
2. Install the current version of the Sys_Filer_Windows03 application from the 2.9.9 AppLogic distro, e.g. from within the directory of the 2.9.9 distro ./aldo ai applications=Sys_Filer_Windows03.
3. Install the current /system_ms catalog from the 2.9.9 AppLogic distro, e.g. from within the directory of the 2.9.9 distro ./aldo ci catalogs=system_ms.
4. As a maintainer:
   • 3t class move /system_ms:Filer_Windows03 /system_ms_save:Filer_Windows03
   • 3t cat destroy /system_ms --force
   • 3t cat rename /system_ms_save /system_ms
   • 3t class destroy /system_ms:FW03old (if you do not wish to preserve it)
   • 3t vol copy Sys_Filer_Windows03_old:windows Sys_Filer_Windows03:windows
   • 3t app destroy Sys_Filer_Windows03_old --force

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.net/AppLogic29/CatWebserversIIS.html.
3. Create a 100 MB ntfs08 volume (or ntfs03 volume for Windows Server 2003 based IIS appliancces) and configure the singleton to use this volume as its content volume.
4. Save and then start the application.
5. From a 3t shell, ssh into the running singleton and do the following:
   • Set a new Administrator password, e.g. 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, e.g. wget http://ip-address:8080/download/IIS_Windows-1.1.1-1.msi
   • chmod 755 *.msi
6. Open the graphic console for the singleton and log in as Administrator.
7. Execute the MSI installer, e.g. double click on the file IIS_Windows-1.1.1-1.msi within Windows Explorer.
8. In the ssh session open on the singleton:
   • rm -f *.msi
   • Set a new complex Administrator password, e.g. net user administrator a3893hf092jfww.^JDFoi8hfwehohgw
   • exit and then ssh back into the running singleton
   • rm -f ~/.bash_history
   • exit
9. Stop the application. In the application editor drag the singleton into the user catalog.
10. In a 3t shell:
    • class destroy /system_ms:IIS08S --force (or move the existing class if you wish to preserve it).
    • class move /user:IIS08S /system_ms:IIS08S
11. 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 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.net/AppLogic29/CatDatabaseAppliancesSQL.html.
3. Create a 3 GB raw volume and configure the singleton to use this volume as its data volume.
4. Save and then start the application.
5. From a 3t shell, ssh into the running singleton and do the following:
   • Set a new Administrator password, e.g. 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, e.g. wget http://ip-address:8080/download/SQL_Windows-1.1.1-1.msi
   • chmod 755 *.msi
6. Open the graphic console for the singleton and log in as Administrator.
7. Execute the MSI installer, e.g. double click on the file SQL_Windows-1.1.1-1.msi within Windows Explorer.
8. In the ssh session open on the singleton:
   • rm -f *.msi
   • Set a new complex Administrator password, e.g. net user administrator a3893hf092jfww.^JDFoi8hfwehohgw
   • exit and then ssh back into the running singleton
   • rm -f ~/.bash_history
   • exit
9. Stop the application. In the application editor drag the singleton into the user catalog.
10. In a 3t shell:
    • class destroy /system_ms:SQL08S_08 --force (or move the existing class if you wish to preserve it).
    • class move /user:SQL08S_08 /system_ms:SQL08S_08
11. Destroy the application

-- StephenQ - 05 Oct 2010