New Recruitment for Solutions2Share

We are proud to announce that we hired two new employees, joining our team. Our new colleagues are starting this month and are currently passing a specific training.

Markus Weißfloch will strengthen our support team. After finishing his three-year apprenticeship as an IT-specialist, focused on SharePoint, Markus Weißfloch gained five years of post-qualification experience in second level support. His daily business was to take care of several thousand costumers. Now, Markus Weißfloch is looking forward to his new tasks and is motivated to deliver the best service to our customers and partners.

We may also announce a new apprentice to join our team. David Papaja started his career at Solutions2Share, qualifying as our marketing communications assistant. After he left the Nuremberg University of Applied Sciences he now joined our company to reinforce our marketing team. David Papaja is enthusiastic and excited about the diverse experiences he will gain during his apprenticeship at Solutions2Share.

We are glad to welcome our new colleagues and hope to maintain our excellent service and customer satisfaction.

Our team is present at many SharePoint conferences and usergroups in Europe. Check our event page for further information.

Migration from SharePoint 2013 to 2016


Assume you’re migrating from SharePoint 2013 to 2016. In this article we discuss the general steps while focusing on our products.



The only way to do a Migration is to setup a new environment in parallel. Looking at SharePoint 2016 please make sure that Collaboration Manager runs on a server using MinRole “Custom”. Later on this is needed because a Service Instance will run on it and the new SharePoint MinRoles other than “Custom” would disable our Service Instance after 24h at the latest. Also please make sure that this server runs on a Web Frontend Server (important for Webparts).

Collaboration Manager needs to run on a server MinRole “Custom” and the service “SharePoint Foundation Web Application” started.



In this step you should have a special look at the source environment, especially customizations. Each Migration is always a chance to cleanup and for changes and at the same time the impact for the business user needs to be minimized.

In case of our products mentioned before, there are no special considerations to do before running the migration. This means please install our products in the destination before running the migration.

    • Collaboration Manager: Install Farm Solutions (including Modules) and do the setup in Central Administration according to our manual
    • Meeting Manager: If the Provider Hosted App is running on its own server already, you don’t need to do anything. Just make sure that the App settings within the Central Administration – Apps are the same. Also, please upload the .App File into the App Catalog.
    • Template Hub: For this SharePoint Hosted App you only need to upload the .App File into the App Catalog.



Please run the Migration using database detach/attach according to:

Afterwards all the content is transferred into the new environment. Our products are part of the Content Database. Next is QA while generally you should have a look into the logs for any errors or warnings (e.g. missing Farm Features).

For Collaboration Manager, after successful database attach , please go to the Central Admin – Collaboration Manager – Web Application and disable / enable Collaboration Manager on the original Site Collection. Complete this step by running “iisreset /noforce”


    • Apps (Meeting Manager, Template Hub) uninstall / install
        • Unfortunately Apps won’t be migrated correctly using the previously mentioned Microsoft Migration practices or they’re often unusable as the Security Token is invalid. For this reason you need to uninstall and install the Apps.
        • Our Apps are saving all the configuration – reinstalling them just recreates the Security Token Trust in SharePoint.
        • In conjuction with Collaboration Manager, please run these steps in the Template
        • After successful re-installation, you can go ahead and these Apps functionality like creating / editing Meetings or creating templates.
    • Collaboration Manager
        • Create a new template: OK = Service Application works
        • Create a new Workspace using the previous template
        • Sync the new Workspace
        • Delete the Test-Workspace and its Template
        • Adjust the URL’s in the Workspace List (either manually or using a script), if the Web Application URL’s have been changed.
        • Test Permissions (random sample)
        • Save an existing Template: If OK, then save all existing templates – again
        • Sync each Template with one Workspace
        • Optional: Sync all Workspaces

If you have any questions, your Support will be happy to help you. Of course one of our Senior Consultants could help you running the whole Migration from A to Z. In this case, please contact us for a personal offer at