Bruce's Blog

    To set the stage.  We have been on Domino 7.02 for awhile.  Recently updated our servers to 8.02 then 8.5.  Clients are all running 7.02 with 7.02 template except me, I'm now on 8.5.  I'm the admin.  We've been using an explicit policy that used the registration and archive policy settings for awhile, bit have never implemented any of the others.  After upgrading to 8.5, I decided to started plating with all the other policy settings again.  I had another explicit policy (called test) for this.

  So far so good.  After discussion with my boss, we decided it was time to start seriously considering implementing the other policy settings.  I created a brand new explicit policy and assigned the test desktop, mail, and security settings to it.  Now for the mayhem part - I called it the same as our domino domain because after some testing, we were going to make it an organizational policy.  Looks like this is a BAD idea.  Even though all my policies were explicit, it looks like it treated the new one as organizational and rolled it out to all my users (without warning).

   So now, they were getting configuration changes made which were very obvious (like popping up new message warnings, locking client every 15 minutes, etc) and were set to not allow the individual to change them (these were test polict settings after all, not what we would actually necessarily want to use in production).  OOPS!!!!!!  To make it worse, one of those horrible bugs that is going around caught me and I've been home sick as a dog part ofg this week while we're trying to work our way out of this one.

   Looks like (hopefully) the worst is over and next week will be better.