0
0 Comments

I wanted to post an open question out to the community on how the rest of you are handling this.

In previous versions of SharePoint if you create a Site collection on an Enterprise edition farm and then attempted to deploy that to a Standard edition farm it was painful (content database migration in most cases). Even if you had not used any enterprise features, the site was still stamped with enterprise guids and this cause problems.

In our case as an organization that needs to work with many different clients, we create multiple integration servers (one enterprise and one Standard). We then did the design, development and Information architecture, etc on the correct version and then bypassed any conflict.

In SharePoint 2013, MSDN does not provide a Standard key, only an Enterprise key. I do know that volume licensing does have different keys (we have a client that only had a standard key). This creates a dilema, if I only have a MSDN enterprise farm available, how do I efficiently do a content database migration to at Standard farm.

I have some thoughts on how I may accomplish this, but I wanted to see if anyone else already has a process for this that they would care to share.

Thanks,

(Visited 29 times, 1 visits today)
Add a Comment