This is a very interesting and compelling document that you should read before buying into Microsoft’s never ending falsehood that “IBM Notes and IBM Domino is dead”.
Indeed, the opposite is true. Of course, everyone acknowledges that there have been no counter-messages from IBM to Microsoft’s claims and IBM have underinvested in Notes/Domino over the last 10 years but there is change in the air – Notes/Domino V10 has a huge number of improvements and new features (some of which are very compelling) and with V11 coming out in 2019, it’s a very exciting time for the product.
Notes/Domino has now been repositioned as an “Application Development Platform” by IBM which is admittedly, an acknowledgement of the market reality. Although, migrating to Microsoft isn’t always the nirvana it’s claimed to be – many power users only realise what they have when it’s gone. Microsoft will promise everything will integrate better but how about pre-existing Domino applications you’ve spent years developing? How many of your current Domino applications integrate with mail? Generally it’s much more disturbing change than the sales people will tell you, with an unsatisfactory ending. Want a flexible mail workflow rapidly deployed? It’s not going to happen with Outlook.
Another huge piece of the jigsaw is that if you do decide to migrate away from Domino, you are looking at a massive capital investment plus a proven higher cost of ownership. We have seen this happen time and time again with more and more funds ploughed into migration projects with no real return at the end (other than users have Outlook). Bottom line is, budget for your migration, double it and then triple that to get the “real” budget. (e.g. from a real migration – 3 clustered Domino Servers running mail for 1300 users each with 8GB of RAM. Now migrated to Exchange on prem – 4 Exchange servers with 1.4 times the storage each with 64GB RAM and crashing constantly due to insufficient RAM and no answers from MicroSoft – better right?)
So, onto the purpose if this post, yes it’s a report commissioned by IBM and yes it’s partisan but I’ve read through this carefully and cannot see any flaws in the data. Domino really does provide excellent ROI (or TEI) compared to other platforms – have a read and please do drop me an email if you would like to discuss any of the findings or would like more information on Domino V10 and what it can offer your enterprise.
Thanks for reading,
Every Domino Admin worth their salt will have experienced incidents with unread marks not working correctly and will have “fixed” these in variety of ways, mainly either marking all documents as read, or exchanging unread marks between replicas
There’s another type of unread marks issue, where someone wants to audit unread marks (i.e. find out who has read a document and when). Well IBM can provide with a free auditing tool that does just that (amongst other useful Developer type functions).
From the about page of application:
“Welcome to the Toolbox Database
The Toolbox database (toolbox.nsf) is designed to help administrators or advanced users troubleshoot issues with Unread Marks in a Lotus® Notes® database. It can also be used for troubleshooting replication issues and design template issues. Currently there are six major features in the Toolbox database. These are as follows:
- Dump design documents: This feature enables users to dump information about all design documents in the database. Toolbox provides information on these attributes: NoteID, UNID, Sequence Time, Sequence, and UpdatedBy. The output is sorted by Class Name and UNID. This feature enable users to quickly identify who updated design documents, when they where updated, and how many times the documents were updated.
- Dump design documents (long format) : This feature is the same as “Dump design documents” but provides more detailed information about each design document. Additional information includes the document Title, Creation Time, and Last Modification Time.
- Dump the NoteID and UNID : This feature dumps the NoteID, UNID, Create time and Last Modified time for a database, database view, or single document to a log file. This log enables the user to take a quick inventory of the documents in the database or view. Then, when unread marks or replication issues are suspected, the user can dump the NoteID and UNID log again and compare the two logs to identify which document was changed.
- Dump unread activity logs (local db only) : This feature dumps the user’s unread activity log for a database, database view, or a single document to a log file. This feature works only on a local database that is not encrypted. Also, the database must be enabled for unread replication.
- Dump unread mark list : This feature dumps the unread mark list for a database, database view, or a single document into a log file. This feature works for any accessible local or remote database. This feature works only on a database that is not encrypted. Also, the database must be enabled for unread replication.
- Toolbox Add-in Menu : This feature adds the following Toolbox menu items to the Actions menu: “Display info on selected Document”, “Dump design documents”, “Dump design documents (long format)”. These menus are enabled whenever the user is in a view to execute the action.”
There isn’t an Internet link per se for for the tool, but if you ask IBM Support nicely for it in a PMR they will provide it for you and it is intuitive to use. IBM should probably have a technote on this as I think people would use it if they knew about it and it was freely downloadable (IBM take note !).
Please let us know if you end up using the application as a result of this post!
Cormac McCarthy – Domino People Ltd.
We recently upgraded our clients to Notes R8.5.3 which included the Admin and Domino Designer clients.
One of our developers is a real keyboard shortcut nut and is complaining bitterly about what may be a bug or “feature” in this new release.
Previously, when pressing Ctrl+Shift, he was able to select words and upon releasing Ctrl and clicking the down arrow, select lines.
Now (when editing Script Libraries) when you press Ctrl+Shift (right-hand-side of keyboard)it changes the text from left-to-right (default) to right-to-left ! To get back to normal you have to press Ctrl+Shift of the left-hand side of the keyboard. It’s driving him mad.
To explain better, here is a script library from the mail file:
Now, I press Ctrl+Shift (the right side of the keyboard) and I get this:
You need to press Ctrl+Shift on the left side of the keyboard to get it back again.
The developer in question is blaming me personally for making him upgrade to R8.5.3 – anyone know how to make my life easy again ?