Support Blog


Feature Pack 8 Summary for Notes and Domino

Feature Pack 8 (FP8) was released yesterday and is available for download from IBM’s Fix Central . IBM has ensured that the upcoming feature packs will still have a high focus on addressing high impacting defects. Also, they will have the same packaging, architecture and install kits used in previous fix packs. IBM has released a Preliminary Fix/Feature List with contents that are still subject to quality engineering tests. The status of these fixes and features can be tracked on the Notes/Domino Fix List website on developerWorks. Feature pack 8 will address defects in the Client, Server, and the Domino OpenSocial component.

What’s new in IBM Domino 9.0.1 Social Edition Feature Pack 8

  • Move views out of databases
  • Increase the document summary data limit to 16 MB
  • Java JRE version 1.8 provided with Domino
  • Enable the Group By Date feature in all mail files
  • Enable the Show Beginning of Message feature in all mail files
  • Retain MIME formatting when forwarding or replying to internet messages
  • Notes browser plug-in is no longer part of Notes package
  • ADFS 3.0 now supported as a SAML federated identity provider

More information

What’s new in IBM Notes Feature Pack 8?

  • Display internet style names
  • Show beginning of message
  • Maintain read-only MIME email content for Reply/Forward

 More information

Fixes contained in this Feature Pack

A plus symbol (+) before the SPR number indicates a fix for a regression bug. A regression bug is an issue that was introduced in a Maintenance Release but did not exist in previous releases of that code stream. For example, a bug that appears in 9.0.1 but did not exist in 9.0.0 is a regression.
If an APAR exists for the corresponding SPR, the APAR number will appear in parentheses next to the SPR number. For example, SPR #nnnnnnnnnn (LO12345).

The Fix List database on developerWorks contains the description of each fix in this Feature Pack, and indicates which platform(s) have been fixed.

9.0.1 Feature Pack 8 Preliminary Fix List descriptions:


Domino Server

  • CSYL9VBRVE (LO84524) – Fix an issue where calendar updates do not update the notes invitee’s calendar If autoprocessing is enabled.
  • GMAA7YUHGZ (LO47397) – Allow users the option to disable password history.
  • +KGEW7QNV85 (LO39186) – Fixed a problem where Notes is unable to send an internet email message if the address is enclosed in single-quotes. This was a regression introduced in 9.0.1.
  • BBSZAB5DFH (LO89375) – Fix an issue where a vaulted NSL user is not able to get new keys when public key checking is enabled.
  • +KBRNAEMPX2 (LO90491) – Fix a threading mismatch issue resulting in problems with cluster replication on Linux64/zLinux64 systems. This was a regression introduced in 9.0.1 FP7.
  • MJBC9EBVCN (LO78311) – Fix an issue where new documents are lost when compact -REPLICA is running in a mail database.
  • ALSR8ZZR5J (LO72622) – Fix an LDAP search authentication issue with special characters.
  • MJTMA8J3MU (LO88473) – Fix a server crash issue.
  • +MKIN9Z6S5D (LO89583) – Fix an intermittent database issue preventing users from opening a database resulting in the following error “This database is currently in use by another person or process, and cannot be accessed at this time”. This was a regression introduced in 9.0.


  • ARBQ9Q5HR9 (LO82463) – Fix an issue where messages sent from clients to external recipients will move addresses from the CC field to the TO field on replies.
  • ADONADJUDF (LO90147) – Fix an issue with the dialog prompting “How Do You Want To Open This File?” when opening a jpg or bmp file.
  • JGRN84PJJF (LO45099) – Fix intermittent client crashes using the Notes Client together with OLE apps.
  • GFAL9V7UQ2 (LO84501) – Fix the error “Your Public Key Does Not Match The One Stored In The Address Book” when the user’s person document has been updated with their new public key but not the local/vaulted ID file.
  • PEDSA7QK9P (LO87584) – Fix an issue where the Notes Client SSO connection expires after the user’s IBM notes client is left inactive for some time.
  • AYAVACYBSJ (LO90045) – Fix an issue where an XML attachment is rendering as part of the message body.
  • +RGAUADUM59 (LO90248) – Fix duplicate attachment icons when using LS embedobject to attach files to a notesrichtextitem. This was a regression introduced in 9.0.1 FP7.



Managing Access Control Lists to Improve Domino Security

An Access Control List is the front door of a Domino database.  It controls whether access to the database is allowed or denied.  After a user or server is able to access the database the Access Control List further dictates what actions may be taken, i.e. the ability to read particular documents, create documents, modify documents, tweak the database design and even delete the database.  Overall, the Access Control List ensures database and document integrity.  If you do not already have a set of database Access Control List standards for your Domino databases, you need to create one.  Further, you need to audit your mail and application database to ensure they adhere to the defined standards.

For mail and application databases use the following as a best practice guideline for a foundation ACL.  Naturally, there are databases in your environment that will be exceptions.

    • + Default – No Access
    • + Anonymous – No Access, Unspecified
    • + LocalDomainAdmins Manager, Person Group
    • + LocalDomainServers – Manager, Server Group
    • + OtherDomainServers – No Access, Server Group
    • + Use group names instead of explicit user names to provide application access
    • + Maximum end user or developer access of Editor
    • + Define an Administration server for every database

RPR Wyatt’s Essential Tools product can assist you with ACL management.

    • + Quickly deploy a standard Access Control List to your Notes databases
    • + Audit Access Control Lists to confirm they are in compliance
    • + Enforce Access Control Lists on an ongoing basis – if someone changes an Access Control List, Essential Tools will change it back and notify you

If you wish to learn more about how Essential Tools can assist you with wrangling database ACLs, drop me an email at

Time is Running Out: IBM Connect 2017 begins next week! If you can not make it to the conference, sign up to receive our post show report: Claim Your Report!


Domino Security Enhancement

Secure your Domino Environment with these quick and easy tips!

With the New Year many of us are creating both professional and personal goals. Consider making a goal to fortify your Domino servers. There are some steps you can take to quickly and easily increase the security of your infrastructure.

One setting that has baffled me over the years is the default HTTP behavior. Out of the box, HTTP is configured to not honor server access settings. For example, as administrators we have all received a request to place a user in Deny Access but retain the account for a period of time to receive new email. While there are multiple ways to do this, a common method is to simply keep the person document and mail file as is.

Unfortunately, if the server’s HTTP security settings have not been modified, the terminated user will still be able to access the Domino server using their Internet password. Yes, some of you will say change the password stored in the respective Person document. However, a better option is change the Enforce server access settings field in the server document to have a Yes value. Moving forward, the Deny Access field will be followed by the HTTP task. My recommendation is to change this value on all of your Domino servers that run HTTP.

Security domino


Domino Replication Troubleshooting Tip

The other day I had a client request assistance with determining why mail file data was not replicating between cluster members. We started by reviewing the usual suspects – ACL enforcement, replication disabled, and log file data. In the end we discovered the problem was due to the deletion stub purge interval being a 0 value and PIRC being enabled.

Purge Interval Replication Control, (PIRC)

Domino 8.5.3 introduced a new replication control method called Purge Interval Replication Control, PIRC. Overall, PIRC prevents older documents from being replicated, commonly called “ghost” documents. For example, a server is offline for a long period of time and when it is restarted the next replication cycle results in a a number of deleted documents returning. This causes end user confusion and time has to be spent deleting unwanted documents again. PIRC stops this from happening.

PIRC uses an algorithm to calculate the replication cut off date, using the value in the replication settings Remove documents not modified in the last (days) field. This number is used to purge deletion stubs. At some point, most Domino administrators have set this value to 0 to remove the deletion stubs from a replica in order to prevent accidental deletions from replicating to other servers and allowing replication to restore those documents. With the purge interval set to a 0 value the PIRC time date is the current time, which means virtually no documents will replicate.

To allow the documents to start replicating between the replicas the purge interval simply needs to be set to a value higher than 0 on all replicas. However, take caution with how the database may look after the next replication cycle. For example, in a case where two replicas have not synchronized in a year, a number of previously deleted documents will return and documents not available in the one replica being used will suddenly appear – both causing the end user to wonder what just happened. Ensure good backups of the databases exist and communicate what will happen to ensure a successful mitigation process.

List of Connections reports continues to grow

connections-reportsGoing forward VitalSigns monitoring will focus on reporting, and ultimately assuring a high level of data quality with a long range goal of assuring successful business performances.  In that vein, the list of reports that VitalSigns can produce related to IBM Connections continues to expand.   We now offer reports on

  • Activities
  • Bookmarks
  • Communities
  • Community Activity
  • Files
  • Forums
  • Profiles
  • Tags
  • User Activity
  • User Adoption Metrics
  • Wikis

user-adoption-reportCritical investments usually require monitoring to assure a quality performance. Technology is no different. In software, acceptance and mastery are the goals for the users and those goals are only achieved through continued utilization. VitalSigns takes you beyond logins to measure true utilization. There are key features in every software solution and VitalSigns monitors and reports on those key functions for frequency of use.  VitalSigns reporting provides detailed, delineated specifics on individual utilization patterns, and will identifying the key thought leaders in an organization. These are the individuals that will harness the technology to achieve organizational success.

Source: VitalSigns Support Blog

See us in Toronto at Social Connections 10

screen shot

I’m happy report that both Alan Forbes and Jim Engle will be manning the RPR Wyatt booth at Social Connections 10.  This is a great show for those of you rolling out or supporting IBM Connections in your organization.  We’ll be showing off all the latest monitoring and usage reporting for IBM Connections recently introduced in VitalSigns 3.4


Source: VitalSigns Support Blog


Next Webinar: We Switched to Microsoft Exchange – Now What?

Discover a resolution for the most unstable Exchange server environments.
Increasing productivity and cost effectiveness.
Learn more about the new era of Hybrid monitoring for Domino and Exchange .
Discover how to procure manageability with one single interface.

Date and time of webinar:

Thursday, March 31st
10 AM Pacific Time – 12 PM Central Time – 1 PM Eastern Time

Sign up here

Source: VitalSigns Support Blog