Real World Computing

I'm not a big fan of HTTPS. Don't get me wrong, I agree with all of the security and comfort that it provides. I just hate the whole renewal process. Domino 12 introduces a new way to do HTTPS and it's apparently much easier going forward.  That's great news. Unfortunately, we hit a couple of snags on the way in, and I wanted to warn everyone about them - especially since the workarounds are so simple.  Domino Needs to Generate the CSR You're probably thinking that that this is pretty obvious but if so, you're not thinking about wildcard certificates. We use a wildcard certificate *.mydomain.com.au - This allows us to use it across multiple systems, including Domino, Azure, some WordPress websites and a Drupal Website. We also use it in conjunction with several hosted services. The wildcard certificate allows us to use the same certificate on different subdomains. For example: www.mydomain.com.au domino.mydomain.com.au azure.mydomain.com.au othersite.mydomain.co

It's been five years since a decision was made to kill Notes and Domino at our organisation. Like many other organisations, we left for the Azure shores of Microsoft. Several changes of leadership later and Domino is still at the heart of our organisation and we're moving towards tighter integration with it than ever.  It occurred to me that now is as good a time as any to reflect on how our journey went.  The Low Hanging Fruit The low hanging fruit of any domino migration is mail. Email is an easily identifiable application which can generally be swapped out one-for-one. In our case, Notes client (and the lesser used Verse web application) for Outlook and Outlook Web Application (OWA).  We investigated several applications before finding one that worked and converted all of our .NSF mail files into .PSTs, then we imported these into outlook. Along the way, we discovered that Verse didn't safeguard our older mail quite as well as we'd hoped and we discovered that folder