What is the risk of deleting the /mysite collection in sharepoint 2013 ?

Greg Booth 1,296 Reputation points

We want to make some changes to our sharepoint 2013 environment ( to facilitate the upgrade to sharepoint 2016).

Are there any risks associated ? Are any of these changes likely to have any unitended consequences ?

The changes are

  1. Generate a new key for the secure store.
  2. Delete the /mysite site collection
  3. remove features reported as "missing"
  4. remove features that have been installed on a web application in sharepoint 2013, but wont be required in sharepoint 2016
  5. Delete orphan features (either by allowing the health analyser to resolve, or removing sites containing "missing" features. Note: Features would be removed via STSADM -o deactivatefeature -id <feature-id> -url <site-url> -force stsadm -o uninstallfeature -id <ID>
SharePoint Server
SharePoint Server
A family of Microsoft on-premises document management and storage systems.
2,253 questions
0 comments No comments
{count} votes

Accepted answer
  1. AllenXu-MSFT 16,796 Reputation points Microsoft Vendor

    Hi @Greg Booth ,

    It is fine to deploy changes you list above:

    1. It's ok to generate a new key. As SharePoint doesn't store the key, if you lost the old one, just generate a new key.
    2. If you don't want to migrate the mysite, you can do this. And you can set up new my sites for users after migration.
    3. it's OK. When encountering missing feature issue during migration, it is recommended to de-activate & Un-install the faulty/missing feature.
    4. It's up to you and generally there is no risk.
    5. No risk.

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful