Upgrade notes

Here's what you need when upgrading to Lab Management 2.4.

Pre-upgrade steps:

To upgrade to Lab Management 2.4, the Active Directory for the Lab Management domain needs to be at least at Service Pack 2. You should take this opportunity to install all Microsoft security updates as well. You can do this well in advance of the upgrade -- say a week ahead or earlier, as convenient.
- Arrange for a down time of 6-8 hours for patching the Active Directory server before upgrading. Except for the brief periods when it reboots, the server should be up for most of this time.
- You need to temporarily add the Active Directory user "Cubit Admin" (login id: __cubitadmin) to the "Schema Admin" group. When the upgrade is finished, you can remove this user from the "Schema Admin" group.
Install VMware OVF Tool:
- Download VMware OVF Tool 2.0.1 from VMware's web site: Open Virtualization Format Tool. You can also access the pre-downloaded package from our own file system -- on the Lab Management Manager node, you can find this package at /public/package/cubit/VMware-ovftool-2.0.1-260188-lin.i386.sh.
- Install the tool at its default location at the /opt/vmware/ovftool directory.

Post-upgrade steps:

After the upgrade to Lab Management 2.4, perform these steps to update profiles:

Check out the current profiles.
- svn co http://localhost/svn/ai/profiles /tmp/profiles
Update any RHEL or CentOS 5.x customer profiles that contain a downgraded autofs RPM.
1. Remove these lines:
```
     <rpms action="remove">
       <rpm>autofs</rpm>
     </rpms>
```
2. Remove the line specifying the older autofs RPM:
  - <rpm>autofs-5.0.1-0.rc2.55.i386.rpm</rpm>
Commit the changes.
- svn ci -m "Updated all rhel/centos 5.x profiles to use stock autofs rpm"