Forum Discussion
Solved
Upgrade user profile service from SharePoint 2013 to SharePoint 2016
As said I’m planning an upgrade to SharePoint 2016. We have about 1000 users in our old SharePoint 2013 farm and everyone is using my sites. For user profile information we are using Use SharePoint Profile Synchronization feature.
I know the basic idea behind the update.
- Take the databased form old farm and attach those to the new farm
- First upgrade the managed metadata service and then user profile service
My overall question is that what the right way to do the upgrade is and what things to consider here?
- If we use the Active Directory Import on the new farm what will we lose?
- Sure the sync is then only unidirectional but that might be okay to us.
- But will we lose the possible custom AD attribute connection with this option?
- If we decide to go with Microsoft Identity Manager (MIM) what is the correct way to do the upgrade?
- Do I have to configure the MIM before attaching and upgrading the user profile databases?
- If so, what is the correct way? The Technet instructions is saying “This is the URL of the SharePoint Server running the User Profile Service application”. But isn’t it so that the service is running only after the database based upgrade is done?
You've got the upgrade path down pat.
For what you lose with AD Import, here's the laudry list of stuff that doesn't work or has different behavior - https://technet.microsoft.com/EN-US/library/jj219646.aspx (more at https://blogs.msdn.microsoft.com/spses/2015/03/04/sharepoint-2013-active-directory-import-and-known-behaviors/).
You can still import custom attributes.
For MIM, you want to upgrade the UPSA databases first, as MIM will need an active UPSA in order to function. As for the URL, you point MIM at the Central Administration URL. I've also blogged about this at https://thesharepointfarm.com/microsoft-identity-manager-series/.
I'm sorry to push this one year old topic to the top but maybe someone could state on the fact that there's no "official" upgrade path from UPS 2013 to UPS 2016, if you stick to Microsoft's official technet post.
Can anybody tell me why it is like that? For the previous version step the description about upgrading UPS from 2010 to 2013 was included in the article.
- Probably just an oversight. It is fully supported and detailed here: https://technet.microsoft.com/EN-US/library/ee731990(v=office.16).aspx
The link below from MS does not include the portion for Upgrade the User Profile service application. Why?
After upgrade the user profile service application from SPS2010 to SPS2013 then SPS2016 using procedure for SPS2013, I got error "No User Profile Application available to service the request" when try to configure Self-Service Creation and Office 365 Configure hybrid OneDrive. I associated the UPS proxy to my web application. Also added permissions. Thanks!
You've got the upgrade path down pat.
For what you lose with AD Import, here's the laudry list of stuff that doesn't work or has different behavior - https://technet.microsoft.com/EN-US/library/jj219646.aspx (more at https://blogs.msdn.microsoft.com/spses/2015/03/04/sharepoint-2013-active-directory-import-and-known-behaviors/).
You can still import custom attributes.
For MIM, you want to upgrade the UPSA databases first, as MIM will need an active UPSA in order to function. As for the URL, you point MIM at the Central Administration URL. I've also blogged about this at https://thesharepointfarm.com/microsoft-identity-manager-series/.
