This post is part of my PowerShell PowerUp project.
The only way to deploy SharePoint default settings for site collections and sites manually is using predefined site templates or an ugly third party tool.
And in case you’ll do that with site templates it’ll cost a lot of the time to update settings which were already set.
However with PowerShell it’s possible to deploy SharePoint default settings automatically and it’s a lot easier than you might think.
Recently I’ve change the url for one of my GitHub projects.
- Old: https://github.com/janikvonrotz/PowerShell-Profile
- New: https://github.com/janikvonrotz/PowerShell-PowerUp
As you might know, I’ve used this url in several posts.
In order to make this obsolete links I have to replace them in every posts.
It could happen that the directory sync service (DirSync) doesn’t sync the users UserPrincipalName correctly.
I had an issue where the UserPrincipalName from a user in the Office 365 windows azure directory has been made based on the user’s sAMAccountname. This wouldn’t be problem if as long the sAMAccountname is the as same as the UserPrincipalName, but as you can guess this is not everywhere the case.
When the name of an Active Directory group has been changed, this change won’t affect the display name showed in the SharePoint permission editor.
To update the the name for all Active Directory groups you can run this snippet on the SharePoint server: