Tag Archives: Domino

…for those who missed it: IBM Connections 4.5 and Notes/Domino 9 release dates announced

  By dennis ruddigkeit | March 13, 2013 - 18:05 | Connections, Domino
5 Comments

IBM Notes and Domino 9.0 Social Edition will be available on March 21 and IBM Connections 4.5 is planned to be delivered on March 29.

While I am still searching for the big “WOW”in Domino 9 (SAML support might be one), Notes 9 will have a lot of usability improvements, UI beautifications (OneUI) and iNotes enhancements.

IBM Connections 4.5 will be enhanced with IBM Connections Content Manager 4.5, which will significantly improve file and document handling in IBM Connections (hopefully). I wonder what happened to IBM Docs? Will it be included?

Details:

 

Caution when enabling PIRC by default

  By dennis ruddigkeit | July 19, 2012 - 17:59 | Domino
Leave a comment

Beginning with Domino 8.5.3, IBM introduced the long-awaited PIRC (Purge Interval Replication Control) feature to prevent old or deleted documents to be replicated back.

While PIRC is really helpful and works like a charm there is currently no way to enable it by default – which means that PIRC is enabled automatically after creating a new database or creating a new replica.

(more…)

Lockout ID has no effect when using security policies

  By dennis ruddigkeit | April 24, 2012 - 19:24 | Domino
Leave a comment

If you are using Domino security policies – e.g. to define password quality or password change interval - and the “Lockout ID” functionality to prevent users from accessing the Lotus Notes environment, you should pay attention to the following technote:

-> Global policy setting ignores ‘Lockout ID’ setting in Person document

From what I have tested so far it doesn’t matter whether it’s a global / organizational or explicit policy. As soon as you assign a policy including a security setting document to a user, setting the “Check password” field to “Lockout ID” has no effect and the user can still access the Domino server.

I bet there are many Domino administrators out there who wrongly trust the “Lockout ID” feature :-)