Real World Computing

In the Domino world, we used to just change the access controls on NSFs and copy or replicate them directly from the server to a PC but since we've moved to Outlook, and specifically  to Office 365, getting those mail files from the cloud has been an increasingly difficult business.  To be fair, this was difficult under IBM as well, once we moved into the Verse cloud.  Your Current Procedures aren't Working When I first started trying to get backups of files, I had a lot of people tell me how easy it was. I followed their advice -- and yes, it was easy.  After all, there's a menu option inside outlook that lets you export directly to a PST file. It was too easy. I was suspicious though. Suspicious that a person with a 10 year occupation could have a mail file that was a mere 400 MB. I looked into it and sure enough, the outlook method only gives you a recent subset of your data. If you've been backing up PSTs from the cloud using outlook, you're missing a

We started moving over to Office 365 quite a while before we decided to ditch Notes mail and move to Outlook. It was also my plan to get rid of our internal active directory server and rely solely on the cloud for authentication.  As it turned out, management wanted to keep the AD server a little longer, so we've had to synchronise our onsite accounts with the Office 365 ones. The synchronisation processes immediately created duplicates (and sometimes triplicates) of users.  The journey to resolve this issue was time consuming and data destructive, so I thought I'd let everyone know how to fast-track it. What Causes the Problems Microsoft's Office 365 users have unique ID's much like the objects in the Active Directory. When you create a user from scratch on Office 365, you create them with a unique ID. While there are tools that will let you change these unique IDs, we've found that they generally do more damage than good. Deleted people are another pa