This is part two of my experience in handling the password change office365 architecture issue.
Last time I’ve built a simple script to notificate the users about the status of their passwords. In the mean time we (me and another employ of the “vbl Informatik”) built a simple website for the office365 users to change their password.
To manage my code snippets I’m using GitHubGist connected with Gistbox.
Sadly none of this services providing a backup nor a download function for the gist files. That’s why I came upwith the idea to download them with PowerShell script.
For first my script only can download public gists, because I don’t know how to implement an authentication, luckily each of my gists is public. I recommend you to do the same, it’s the idea of OpenSource.
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. Result the address book still wasn’t up to date in the Outlook client after downloading the offline address book.