Microsoft Purview Sensitivity Labels: Sensitivity label grouping modernization coming this fall (?)

on
There is a change coming to Microsoft Purview Information Protection that simplifies sensitivity label architecture. The goal is to make label management easier, more scalable, and less rigid for organizations. The new model will only include standalone labels and sublabels. Parent labels will be replaced by label groups, which act as organizational containers. These groups cannot be applied to content and have no actions or scope, but they retain color and priority for visual organization. Hopefully, this change will make it much easier to move labels around and make other changes in production: for example, converting a standalone label into a sublabel or moving sublabels between groups without breaking dependencies.  From my experience, this update solves one of the biggest challenges in large environments: rigid label hierarchies. The new dynamic model gives admins the agility they need to adapt quickly as compliance and business needs evolve. For admins, migration will be quic...

Still installing OCS, and getting grey hairs

on
I admit it, I guess I was a bit quick on that last post, when I said I did not run into any serious problems. Well, I did. Biggest problems though, were all related to naming conventions, certificates, and a very aggressive firewall on the brand new 2008 windows server.

- First of all the Firewall:
I was fooled by how easy the installation is, and I was not prompted for any errors. The databases and files were created as expected. The only problem was when I started to run the verification tools, and got error messages. I tried to Google the messages, and the answers indicated certificate problems. So I started all over again, being very careful about names and certificates (By the way; If your CA is a 2003 server, and the client is a Vista or 2008 machine. Make sure to search TechNet for CA updates to the website. And enable ssl on the CA site). After rebuilding the pool 3 times, I was pretty sure certificates weren’t the thing, even though the error message indicated the certificate. So what else could it be? In what way did this installation differ from the OCS 2007 installations I had made on 2003 servers? No...! It can't be that simple? Yes it was. As it turns out: Windows 2008 comes with the firewall turned on by default. Pretty nice actually. But if you're not aware of this, you're in for some grey hairs like me. 

Once the appropriate rules were enabled, the validation came through like a charm. Now most of the features are up and running.

My next project is to integrate the Exchange 2007, and really create that UC environment we need in the demo/lab here.