LDN - Luminis Developer Network

I've been spending a fair bit of time with Luminis migrations. Here's some notes:

Migrate to a development box.
I've managed to get a migration of production data to a development box. This meant that the ldap entries needed to be fiddled first. This isn't as onerous as it seems but it did take a few passes. In fact, I think this is what the migrator script is doing in the 'Transform PDS' section.

I had to change the ldap entries from something like o=myschool.bc.ca,o=myschool to o=lumdev.myschool.bc.ca,o=myschool. You need to 'unfold' the .ldif files (see the DS manual), then replace the phrases. You need some scripting or perling expertise(I did mine in c).

Migrate to production box (not ready to go for a while yet...)
The migration itself seems to go ok. It always blows up in the same place (Transforming PDS with and end-of-file error. Similar to item 3) in the known issues 1-2KB6HZ), so I upped the error threshold. Remember the migration book is WRONG on page 3.18. Run as lmadmin, not as root.

Calendar
The Calendar migration, however is a mess. Doesn't work as root or lmadmin. I ended up running the ImportCalendar commands in the migrator script by hand. The cs5migrate command must be run as root. The rest must be run as lmadmin. Nice. As well, there are many problems with calendar data so far. Still working on this.

Email
We have integration to Messenger Express. The Communication Express client with combined email and calendar looks promising. SSO to calendar express works in Firefox, not in IE, and browser doesn't close on logout for either.

Colours.
The colour/logo/image scheme is supposed to migrate. It didn't. Nor do I see the XP skin that is supposed to be provided.

Other.
One of the most frustrating parts of the upgrade is whenever I type 'migrator' in MS-Word to record my steps, it changes it to 'migratory'.