SharePoint - 从企业版迁移到标准版
我们已经在 MOSS 2007 Enterprise 上愉快地运行了一段时间。然而，我们面临着将 2007 实例迁移到不同的服务器场运行标准的需要。
我应该在现有的实施中寻找什么会阻止我们完成这一壮举？我意识到有图表提供了两种产品之间的比较，但我需要快速进行评估，并且我不需要在本周之前比较这两个版本。
基本上，我将查看我们的关键站点，以确定它们是否使用了任何会阻止我们达到标准的内容。
还可以接受的答复是，将内容/功能从现有的 MOSS 2007 Enterprise 场移动到新的 MOSS 2007 Standard 场是不可行的（并详细说明了为什么会出现这种情况）。我已将我们的生产内容/功能复制到一个新的农场运行的企业，但从未复制到一个运行的标准。
We've been happily running on MOSS 2007 Enterprise for quite a while. However, we're faced with the need to move our 2007 instance to a different farm running standard.
What should I be looking for in our existing implementation that would prevent us from accomplishing this feat? I realize there are charts offering comparisons between the two products, but I need to make this assessment quickly and I haven't needed to compare the two editions before this week.
Basically, I'm going to be looking at our critical sites to determine if they use anything that would prevent us from going to standard.
Also acceptable is a response stating that moving content/functionality from an existing MOSS 2007 Enterprise farm to a new MOSS 2007 Standard farm is not feasible (along with elaboration on why this is the case). I've copied our production content/functionality to a new farm running Enterprise but never to one running Standard.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
尝试使用虚拟机进行试运行并找出可靠的流程，直到您熟悉迁移。
考虑一下 Chris O'brien 的 SP 部署向导，它可能会让您的事情变得更轻松：http://www.codeplex.com /SP部署向导
Try doing a dry-run with a VM and figure out a reliable process until you've got the migration cold.
Consider Chris O'brien's SP Deployment Wizard, which might make things easier for you: http://www.codeplex.com/SPDeploymentWizard
KPI Web 部件是另一种仅限企业使用的部件。需要在要移动的网站集中禁用一些企业功能（并启用其标准类似功能）才能正确进行移动。
KPI Web Parts is another one that is Enterprise only. There are a few Enterprise Features that will need to be disabled in the site collections that you want to move (and have their Standard analogs enabled) for things to work out correctly for the move.
你确实不应该很快做出这个评估。如果你错过了什么，你真的可能会搬起石头砸自己的脚。
主要的企业功能是 BDC、表单、Excel 服务和其他专业功能。
如果您不使用这些区域，则可能没问题，但您需要更详细的评估。
You really shouldn't make this assessment quickly. If you miss something you could really be shooting yourself in the foot.
The major enterprise functionality is the BDC, forms, excel services and other specialized functionality.
If you're not using those areas, you're probably fine, but you need a more detailed assessment.
将内容从企业版移动到标准版是很昂贵的，但是，您肯定会收到导入或恢复错误，根据我的经验，您将花费相当多的时间来查找这些错误。例如，当您尝试导出和导入站点时，源版本和目标版本必须具有相同的功能；如果某个功能在目标上不可用，导入将会失败。从长远来看，您可以通过禁用甚至卸载源子网站上的功能来解决此问题，但是，您可能会禁用正在使用的 Excel Service 或 Forms 组件。此外，任何第三方产品很可能仍然在标准版与企业版中运行，但您需要在导入到旧站点之前安装它们。
比较图表很有用，但我通常告诉客户的是，他们将失去 InfoPath Forms Services、BDC 和 Excel Services。有些人愿意承担损失，有些人则不愿意。随着越来越多的公司利用工作流程，他们经常希望利用 Forms Services 作为 Web 前端，因此这通常是降级阻止程序。
It is feesible to move content from Enterprise to Standard, however, you will certainly receive import or restore errors and in my experience you are going to spend quite a bit of time hunting these errors down. For example, when you attempt to export and import a site, the source and target versions must have the same features; if a feature is not available on the target the import will fail. In the long run you can work around this by disabling or even uninstalling features on the source subwebs, however, you might disable an Excel Service or Forms component that you were using. Also, any third party products will most likely still behave in Standard Vs Enterprise but you will need to install them prior to importing to old sites.
The comparison chart is useful but what I usually tell clients is that they will lose InfoPath Forms Services, the BDC, and Excel Services. Some are willing to take the loss and others are not. With more and more companies leveraging workflow, they very often want to take advantage of Forms Services as the web front end so this is often the downgrade blocker.