Making the most of Lotus Notes Managed Replicas

One of the best features to be added to Notes 8.5.2 client was the ability to have a managed replica of your mail.  Put simply, a Managed Replica is a local copy of your mail which you use as your primary copy of your mail but which is automatically synchronized and updated wherever you are and whenever you send or receive mail.

Obviously to die-hard Notes-folks a local replica of your mail is hardly anything new, in fact is some institutions its the default practice.  What’s new about this, though, is the fact that the Notes client doesn’t forget to switch around mail replicas when you are on and off the server.  You are permanently working on the local replica, but you don’t notice any lag like you would when you were using scheduled replication to synchronize your mail.

The upshot is a win-win situation for the user.  You get all the speed improvements of a local replica, plus all the immediacy of the server.  Your Domino Administrator will thank you too – as you’re connected to the server for a fraction of the time you would be normally.

Now that long anticipated server upgrade might just get postponed because, with everyone using managed replicas suddenly the server is a good deal faster.

If you are using Notes 8.5.2 client you could consider adding the following lines to your NOTES.INI file (and restarting Notes) to get managed replicas going:

CacheMail=3
OutgoingMailSendThreshold=1
ReplicateOnNewMail=1
CacheDBInitialFullDoc=30
DocAutoRetrieve=2
FailoverSilent=1
($PrefRepIDDefFullText)=1

Alternatively ask your Domino Administrator to set up a policy to enable this.

Full details of all these settings plus much more on how managed replicas work can be found here.

Outlook to Notes Migration – Week One

Week one of an Exchange to Domino migration is hopefully the toughest. The best laid plans get put into action, the understandings formed of the customer’s environment are challenged and the architecture you’ve built is tested to the extreme. This particular customer is going from a mixture of Exchange 2000 and 2003 to Domino 8.5.2 in a clustered (two site) infrastructure. What have we learned so far?

Domino Clustering is Great
Domino clustering really is a fantastic feature of the product. Resilience built in to the product, multi-site disaster recovery across operating systems (if you need it) and a client solution which comes out of the box aware of the cluster topology. It’s also surprisingly easy to set up. Like Lotus Traveler, “it just works”. It’s another part of the system which you would think had been designed by Apple because of its simplicity yet power.

Notes Client Windows Login Integration is a Black Art
The customer is keen to minimise the differences for users between their previous environment and their new one. Thus, eliminating the need to login to Lotus Notes is a good thing to do. We opted to enable the “shared login” feature of the 8.5.2 client on the principle that it would do just that. We’ve had our problems as it seems to misbehave when we have rolled out user profiles with the ID Vault.

User Feedback has been Good
We anticipated resistance to the deployment of Notes and hence went to some lengths to emulate the behaviour of Outlook as far as possible. This excellent developerWorks article has proved to be very useful. Some settings, however, need to be set manually on the workstations and although we anticipated this, we’d like it to be much more automatic for the next 400 users. We thought people would be deeply entrenched in the ways of Outlook, but the feedback so far as been that Notes is reasonably intuitive and it has some appealing features over Outlook.

Co-Existence Tools Work Well
In the good-old-bad-old-days the MSExchange-Lotus Notes connector was the workhorse that kept the two systems talking during the migration. We’ve opted for SMTP mail routing and remote LDAP lookups between the servers to achieve the same, or at least, similar results. There are some limitations, of course, such as the fact that Outlook users can’t look up Notes user’s calendars and can’t share resources but most people seem content to accept that this is a transient issue. Using Directory Assistance in Domino, Notes users can get the email addresses of the Outlook users simply by typing in part of a name and pressing F9. Domino does the hard work of looking up Active Directory and returning the email address.

Web Mail vs Notes Client
We’ve also learned that for a green-field site, the benefits of Notes client vs web mail are wafer-thin. The quality of the iNotes implementation is such that it is quite acceptable for all day use and not a temporary-use after thought. We’ve found people more IT-savvy than we expected because they inevitably have their own Gmail, Hotmail or Whatevermail account and are used to sending and receiving mail through a browser. On the other hand the extra benefits of Notes for laptop and power users as well as the sidebar plugins with Sametime and Connections still make the Notes client a compelling choice.

Good Value
The deployment of Notes and Domino represents great value for the customer. They get (albeit limited use) access to Instant Messaging (Sametime), Personal File Sharing (Quickr), Social Files and Profiles (Connections) as well as all the stuff that comes with Notes. They’re happy (so far!) and so are we!

Flies in the Ointment
So is it all good news? No, of course not, but the issues have not been significant. We’re wrestling with migrating lots of PST files in to Notes archives and occasionally getting the feared Red Box of Death (we have to use Notes 7 client to use the CMT migration tool) but have tracked this down to corrupt data in Outlook. Weird things happen from time to time and occasionally the Windows/Notes shared login steadfastly refuses to play ball, but in general, its going fine.

Making the most of Lotus Notes Managed Replicas

One of the best features to be added to Notes 8.5.2 client was the ability to have a managed replica of your mail.  Put simply, a Managed Replica is a local copy of your mail which you use as your primary copy of your mail but which is automatically synchronized and updated wherever you are and whenever you send or receive mail.

Obviously to die-hard Notes-folks a local replica of your mail is hardly anything new, in fact is some institutions its the default practice.  What’s new about this, though, is the fact that the Notes client doesn’t forget to switch around mail replicas when you are on and off the server.  You are permanently working on the local replica, but you don’t notice any lag like you would when you were using scheduled replication to synchronize your mail.

The upshot is a win-win situation for the user.  You get all the speed improvements of a local replica, plus all the immediacy of the server.  Your Domino Administrator will thank you too – as you’re connected to the server for a fraction of the time you would be normally.

Now that long anticipated server upgrade might just get postponed because, with everyone using managed replicas suddenly the server is a good deal faster.

If you are using Notes 8.5.2 client you could consider adding the following lines to your NOTES.INI file (and restarting Notes) to get managed replicas going:

CacheMail=3
OutgoingMailSendThreshold=1
ReplicateOnNewMail=1
CacheDBInitialFullDoc=30
DocAutoRetrieve=2
FailoverSilent=1
($PrefRepIDDefFullText)=1

Alternatively ask your Domino Administrator to set up a policy to enable this.

Full details of all these settings plus much more on how managed replicas work can be found here.

Time to leave the Notes client behind?

I have recently started using the Developer Preview of Apple OS X 10.7 (Lion) and have been surprised by the huge advances in the operating system and in particular with Apple’s own web browser – Safari.  In many respects it has become an internet client more than an internet browser.  With the advent of HTML5 and Apple’s well-known adversity towards Adobe Flash it seems that web browsers (including Firefox and Chrome) are now basically the place where a full day’s work can be done.

The impact of this never ending rush towards cloud computing and HTML in particular is both a good and bad thing.

For us as users it means that we can more or less turn up to any computer in the world and get access to the things we use on our laptops, tablet or home computers.  No longer are we chained to using a bespoke or proprietary client application to access some specific business application.

For IT departments in organisations they no longer have to maintain complicated pre-built images for desktop computers and rolling out updates to client applications is no longer a six-month project and a major undertaking.

The downside to this innovation is of course the dependency on network.  If you’re not connected you’re not working.  OK, getting connected is easier than ever but for those of us who grew up marvelling at the ability of a computer to talk down a telephone line to another computer at apparently dazzling speeds, the concept of always requiring a network connection to do anything seems downright wasteful.  And that’s not to consider the fact that processor speeds are always going up, RAM on board is always greater yet the one thing that seems to throttle our experience is beyond most of our control – the speed of our internet connection.  It’s like having a Bugatti Veyron and driving it around school zones – sure it’s nice to sit in, but a bit of a waste when you can only do 20 mph.

Coming back to the Mac for a moment, but it is true of Linux and Windows, the new operating system from Apple is documented as not including a java virtual machine (or a flash plugin).  Both of these can be downloaded but clearly Mr Jobs has decided to follow suit with the others (who never included it anyway) that code like Java is outmoded for desktop computers and is something which is consigned to developers who will run it as part of an application on a server.

This brings into sharp focus, therefore, IBM’s decision to use the Eclipse framework for the Notes client.  Underneath all of the IBMness is a java virtual machine (or several if you’re running Sametime Connect and Symphony too).  On the Mac this is well know to be slow and very un-Mac-like.  Lotus Notes on the Mac sticks out like a sore thumb from any other application on the platform.  Although IBM have gone to enormous lengths to make it look like other Notes clients out there it is still very slow, prone to crash and consumes enormous amounts of RAM.

So with all these innovations in browsers (including full screen mode for Safari – hooray), the disappearance or non-existence in the base operating systems of Java and the poor user experience performance-wise of the Notes client, is it time to abandon our native client and move to a browser solution?

GBS have recently announced their latest iteration of their Transformer application which converts Notes databases into XPages applications and therefore browser-based solutions.  IBM’s own efforts are clearly heading towards a browser world with the latest release of Sametime 8.5.2 providing client-less presence awareness and meetings.  Indeed the whole Project Vulcan offering from IBM uses HTML not a Notes client.

If there is anyone out there who has not experienced iNotes 8.5.2 as a possible contender to their Notes client experience then I strongly urge them to consider it.  You will find it responsive, complete and a joy to use.  When you ask your admin to implement Transformer to convert those long-loved Notes apps to a browser and implement Single Sign On across your server estate you will wonder why you ever bothered installing software on your computer.

The only question remaining for you will be what you will do with your Bugatti Veyron of a computer on a ropey 3G internet connection at that airport!

Follow

Get every new post delivered to your Inbox.

Join 823 other followers

%d bloggers like this: