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.
In certain cases SharePoint alerts are more useful than workflows, f.e. having the possibility to let users manager their alerts is not possible with workflows.
To manager alerts for a couple of users on specific lists I’ve written a script that handles the whole cycle of alerts. It let me delete, update and create alerts based on predefined configuration.
Wish you all the best, 2014 is going to be great :) Hope you’ve enjoyed my blogging in 2013 ;)
When deploying a published SharePoint 2013 on-premise installation or a Office 365 installation or a SharePoint Online installation, it’s highly recommended to update your Microsoft Office 2013 installation.
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:
To change an Active Directory users password expiration mode you can use this PowerShell snippet: Import-Module ActiveDirectory Get-ADGroupMember "Group1" -Recursive | Get-ADUser -Properties PasswordNeverExpires | where {$_.enabled -eq $true -and $_.PasswordNeverExpires -eq $false} | select -First 50 | %{ Write-Host $_.UserPrincipalName Set-ADUser $_ -PasswordNeverExpires $true } Latest version of this snippet: https://gist.github.com/7913696
To get a users member shipments recursively I’ve written an extended function based on the already existing function Get-ADPrincipalGroupMembership it simply loops through the users member shipments and outputs the data in tree styled list.