Unity Migration Blog

Click on the thumbnail below to view the tentative schedule for shipping ITD's NAL applications and WolfPrep "apps" image for fall 2007.

Here are the important dates:

• Now - Tuesday 7/24:
  Microsys will build and test new and updated NAL applications for the fall 2007 semester.
• Tuesday 7/24:
  New applications "freeze" date. All application building must be completed on or before this date.
• Wednesday 7/18 - Tuesday 7/24:
  Microsys will build a new "No Apps" WolfPrep image.
• Wednesday 7/25 - Tuesday 7/31 (5 days):
  The apps image will be built and tested internally by Microsys.
• Wednesday 8/1:
  The apps image will be shipped and made the default image installed by WolfPrep.
• Wednesday 8/1 - Tuesday 8/21 (15 days):
  Departments can test and customize the image during this window. The image can be installed but summer final exams are not over until 8/9. If a workstation is installed using the new image, new apps will be available and the apps being replaced will not be available.
• Thursday 8/9:
  Summer final exams are over. New applications will be made the default. Old applications will be unassociated. Most departments wait until this date to begin reinstalling lab machines.
• Thursday 8/9 - Tuesday 8/21 (9 days):
  Classes are not in session. This is the window to reinstall lab machines.
• Wednesday 8/22:
  Fall semester begins.

App Configuration - 3 Phases
There are 3 phases of this schedule we need to be concerned with regarding the building and shipping of new apps. The applications need to be configured so they are available on the correct machines during these phases.

App Building Phase (Now - 7/24)
ShowTestApps Application:
The ShowTestApps app will be configured to apply the "Fall07=Yes" key.

New Applications:
Associate finished new applications to AppTest and Consultants.
Set a registry key requirement of "Fall07=Yes".
Set the normal registry key requirement (ex. "Maple=Yes"). Add a new key to ShowAllUnityApps if the application is completely new and a corresponding key does not already exist.

Existing Applications Being Replaced:
Do nothing.

Effect:
New apps being tested only show up on machines that have had ShowTestApps run for members of the AppTest or Consultants groups. Existing apps still show up on machines that have had ShowTestApps run. Other workstations are not affected.

Image Building & Waiting To Ship Phase (7/25 - 8/8)
This is the phase when the apps image is built but before the new apps are shipped. We need to wait until summer final exams are over to ship the new apps.

New Applications:
Replace the AppTest and Consultants associations with .Users.

Existing Applications Being Replaced:
Set a "value not exist" registry requirement for the "Fall07" key.

New Apps Image:
Build the image and prepopulate the "Fall07=Yes" key in the image. Also prepopulate the new image with the ShowAllUnityApps keys.

Effect:
Workstations either receive the new apps or the existing apps, but not both.

New apps are available in the new image because it contains the "Fall07=Yes" and ShowAllUnityApps keys. New apps continue to be available on machines that have had ShowTestApps run.

Existing apps are not available in the new image nor are they available on machines that had ShowTestApps run. We do not want the existing apps to be capable of overwriting the new apps. Existing apps are blocked because of the "value not exist" requirement that was added. The existing apps only show up on machines that DO NOT have the "Fall07" key.

Machines that were previously installed are not affected. Existing apps still appear in the NAL on these machines. The new apps are not yet available on because these machines do not have the "Fall07=Yes" key set.

New Applications Shipped Phase (8/9 - )
New Applications:
Remove the "Fall07=Yes" registry key requirement.

Existing Applications Being Replaced:
Remove associations.
Remove all registry key requirements.
Move app objects to Legacy.Apps.Users.

Effect:
New apps are available on all machines.

The existing apps are retired and no longer appear in the NAL on any machines. These retired apps can be associated to workstation objects if a department needs to use the old version.