Blog

Blog Search

Search this site

Advertisements

Everything Else

Sponsor

Wood Watch Review

Google Custom Searches

Custom Blogger Search
Custom Sametime Search
Custom XPages Search

Subscribe

Subscribe via RSS

Recent Tweets

Hosting by

You are here: Home › Blog

Google Apps Migration for Lotus Notes (GAMLN) - part 2


Tags :


Yesterday I concentrated on some of the email migration portions that were of concern as we entered into the migration testing.  Calendaring does have a tool as well and is supposed to support all meetings, reminders, events, recurring and even privacy.  Calendaring will be later and separate.  Today we focus on personal moving contacts and groups

So to move a users personal address book and/or groups we had a couple options to make this happen.

  • Server side - the first thing we noticed is that the user must have synchronized all of their contacts into their mailfile.  Unfortunately, this has either never been done.  Due to it previously being manual, then in a policy that was never set, or worse yet it was done long ago and would totally screw them up if it was done now.  So the server side feature is only one, via an agent that runs, that should be considered if your environment has actively been synchronizing already.
    - The other portion is that users must enter their Google Apps passwords into the GAMLN system itself.  Not something we would have all the users do.  This whole idea of server based it borked it seems.
  • User driven with a Notes form - This form actually gets emailed to users.  So now we expect them to fill this out.  The good news is it pulls their local names.nsf information, no sync necessary and they feel more in control and are able to enter their password directly into the form to upload their contacts.  The user being prompted gives a good feeling but then we rely on users to actually perform this step.  A catch-22.
  • User driven with a web form - This only is needed if the user does not have Lotus Notes for email anymore.  So I am so confused.   It also tries to pull from their web mailfile.  Which means they had to sync before or have entered info now via the web only.  My guess is that this is made directly for iNotes.
    Something I did notice is that if the site forces SSL with a self-signed certificate then Google had issues connecting since it couldn't read the cert.  The only answer?  Remove the SSL for the migration of iNotes users.

All this above migrated content is not emailed in any way.  It is all direct upload via SSL to Google so the user must be connected to Google at the time.

Ok, that is enough for today..

History of postings on the Google Apps Migration for Lotus Notes (GAMLN) series: