There is currently a bug in SharePoint 2016 with regards to Outgoing Email and Exchange Receive Connectors. Prior to SharePoint 2016, generally no changes were required to send mail to a Receive Connector, but in SharePoint Server 2016, Microsoft switched to using the SmtpClient namespace for sending mail, and in doing so set UseDefaultCredentials to true. This means any Receive Connector which has an authentication mechanism attached to it, Shar
FoundationSync 2.71 has been released for SharePoint Foundation 2013. This solution is designed to keep User and Group information in the User Information List up-to-date across all Site Collections on a SharePoint Foundation farm. The solution will also pull pictures from Active Directory or Exchange Server (tested with Exchange Server 2013, but should also be compatible with Exchange Server 2016). The release is available from the FoundationSyn
As many SharePoint admins are aware, patching SharePoint typically isn’t fun, and can be downright slow. Russ Maxwell introduced the “5 hour” SharePoint patch script. Awhile back I released a version compatible with SharePoint Server 2016 and now I’ve updated the “5 hour” SharePoint Patch Script on my GitHub repo. This script facilitates patching of SharePoint Server 2013 and SharePoint Server 2016. There are s
The SharePoint 2016 March 2017 Updates have been released. SharePoint Server 2016 (sts-x-none): https://support.microsoft.com/en-us/help/3178672 SharePoint Server 2016 (wssloc): https://support.microsoft.com/en-us/help/3178675 Office Updates: https://support.microsoft.com/en-us/help/4013886/march-14-2017-update-for-microsoft-office Consider using the SharePoint Patch Cmdlets available at SharePoint Updates for your farm!
The SharePoint 2013 March 2017 Cumulative Updates have been released: SharePoint Foundation: https://support.microsoft.com/en-us/help/3172456 SharePoint Server 2013: https://support.microsoft.com/en-us/help/3172497 Project Server 2013: https://support.microsoft.com/en-us/help/3172462 Office Web Apps 2013: https://support.microsoft.com/en-us/help/3172457 Office Updates: https://support.microsoft.com/en-us/help/4013886/march-14-2017-update-for-micr
See title. Don’t put an @ in the sAMAccountName of the user. In fact, Active Directory Users and Computers will prevent you from doing so, converting the character to an underscore. But with PowerShell, we can add any symbol we want to. Here’s an example: What ends up happening in this scenario is while SharePoint can resolve the username in the People Picker itself (the user’s username becomes underlined), when the underlying C