Today I experienced an exotic behaviour, a client couldn’t access his Office365 page due he wasn’t able to login on the ADFS authentication prompt.
After googling and binging (just kidding, NERD) I found a simple solution.
While crawling the soundcloud newcomers and indie artists I felt in love with Sir Sly. They seem a little bit shy about publicising personal informations but that doesn’t really matter. Their music is simple and solid, nice to hear by day and night. You can follow them on youtube, twitter, facebook and instagram. https://soundcloud.com/sirsly
To alter the Exchange owa policies you can access them Using the Office365 administration site and navigate to the Exchange section. In the default policy editor are only limited options available.
Content and structure option was present in SharePoint Server 2007, if you are not able to see this option on your SharePoint site in SharePoint 2010 then don’t be surprised, this option still exist in this version as a feature.
There are two sections on which you can see this option, if you are missing this option then lets analyze which sections we are talking about.
The Managed Metadata feature in SharePoint 2010/2013/Office365 enables a new way to manage your documents and other company related informations. Yet most file systems store their files in an hierarchical structure, with SharePoint and the Managed Metadata Service you can setup a document management system. To get into this Managed Metadata Service thing, I’ve found a great video.
With Office365 connected with an ADFS you have to redesgin your Exchange distribution groups. ADFS only syncs distribution groups that have these definitions:
My idea was simple, I’m developing a script that creates for every OU and child OU I’m chosing in the ActiveDirectory structure a distribution list containing the users of the chosen OU recursively.
Since Exchange 2010 the graphical console doesn’t support the same functionality as the PowerShell Exchange console, it’s possible that there occur some exotic errors or a lack of functionality while working with the graphical console. I recommend to use only the Exchange PowerShell console for administrative work. For example: I had to update the offline address book, I’ve deleted some distribution groups, updated the address list and the offline book, all with the graphical console.
With over 350 users in the Office365 cloud as in my case it’s difficult being aware of which licenses I really need.
To help my out I’ve made an ActiveDirectory group which holds the allowed Office365 users. And with this PowerShell script I look up every Office365 user and his licenses and check if this users is allowed to use Office365.
This post is part of my Office365 experience. Today I’ve made a script to get startet with the ExchangeOnline PowerShell console.
Every time a user logged in for the first time into the Office365 Outlook webapp, he had to set his regional configuration.