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
Cross Origin Resource Sharing (CORS) HTTP header values in SharePoint Server 2016 has been hard coded by the SharePoint Product Group. Since SharePoint only accepts OAuth for CORS requests, and not user authentication such as cookies, Cross Site Request Forgery is a non-issue as origin validation does not need to take place when using OAuth. As such, setting Allow-Cross-Origin-Request to ‘*’ becomes a non-issue. Here is the code used
Microsoft Identity Manager required the use of the NoILMUsed property on the User Profile Service Application in SharePoint Server 2016 due to a bug that has now been fixed with the release of the February 2017 Public Update. There’s a catch, though… the required timer job isn’t installed due to a bug. With the February 2017 Public Update release, a new timer job named ExternalIdentityManagerMembershipsAndRelationshipsJob is inc
The SharePoint 2016 February 2017 Updates have been released. SharePoint Server 2016 (sts-x-none): https://support.microsoft.com/en-us/help/3141515/february-14-2017-update-for-sharepoint-server-2016-kb3141515 SharePoint Server 2016 (wssloc): https://support.microsoft.com/en-us/help/3141517/february-21-2017-update-for-sharepoint-server-2016-kb3141517 Office Updates: Consider using the SharePoint Patch Cmdlets available at SharePoint Updates for yo
The SharePoint 2013 January 2017 Cumulative Updates have been released: SharePoint Foundation: https://support.microsoft.com/en-us/kb/3141479 SharePoint Server 2013: https://support.microsoft.com/en-us/kb/3141481 Project Server 2013: https://support.microsoft.com/en-us/kb/3141480 Office Updates: https://support.microsoft.com/en-us/kb/3214449 Consider using the SharePoint Patch Cmdlets available at SharePoint Updates for your farm!