如何使用 SharePoint、K2 和域控制器复制虚拟 PC
有谁知道复制和重命名运行 SharePoint、K2 并充当域控制器的虚拟 PC（可以是 MS VPC、VMWare 或 Virtual Box）的简单方法？ 我正在寻找一种创建图像的方法，该图像可以快速、轻松地复制并由同一网络上的多方同时运行，而不会发生名称冲突。 据我所知，要么就是这样，要么在每台机器上进行从头开始的构建。
Is anyone aware of an easy way of duplicating and renaming a virtual PC (can be MS VPC, VMWare or Virtual Box), which is running SharePoint, K2 and acting as a domain controller? I’m looking for a method of creating an image which can be quickly and easily copied and run by multiple parties on the same network simultaneously without name conflicts. It’s either that or go through a ground-up build on each and every machine as far as I can see.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（5）
我建议不要这样做.. 重命名已安装的 SharePoint 计算机肯定会给您带来无限期和意外的痛苦。 方法是使用脚本安装：
这一切都可以在无人值守的情况下完成。
作为安装短期开发机器的快捷方式，我使用了以下内容。 只需确保 SharePoint 配置向导在重命名后运行，应该不会有问题。
它的优点是您的开发计算机安装相同。 创建一个新的大约需要 10 分钟。 它没有 sysprep，但它们被重命名，以便您可以在网络上运行它们。 不运行 sysprep 从来没有让我感到悲伤，但我不会在生产环境中这样做。 运行 MOSS 脚本化配置可确保其在重命名的环境中正常工作（并且所有 MOSS 场的配置完全相同，相同的端口、SSP 设置等，耶！）
有关 MOSS 配置脚本，请参阅 h tt p://stsadm。 blogspot.com/2008/03/sample-install-script.html
那里也有大量 SQL 示例。
I'd advise against it.. renaming an installed SharePoint machine is sure to cause you pain indefinately and unexpectedly. The way to go is with scripted installs:
It can all be done unattended.
As a shortcut to install short-lived development machines I have used the following. Just make sure the SharePoint configuration wizard runs after the rename and there should be no problem.
It has the advantage of your development machines being identically installed. Takes about 10 minutes to create a fresh one. It doesn't have sysprep but they are renamed so you can run them all on your network. Not running sysprep has never caused me grief but I wouldn't do it for production environments. Running the configuration of MOSS scripted makes sure it will work on the renamed environment (and all MOSS farms are configured exactly the same, same ports, SSP setup, etc, yay!)
For MOSS configuration scripting see h tt p://stsadm.blogspot.com/2008/03/sample-install-script.html
Plently of samples for SQL out there too.
SharePoint 不喜欢从其脚下重新命名服务器（可以这么说）。 SQL Server 也没有（我假设您已将其安装在用于安装的虚拟机上）。 不确定 DC 是否被重命名，那里也可能存在问题...
话虽如此，我已经阅读了一些有关重命名 SharePoint 计算机和 SQL Server 计算机的说明，因此您可能会有所收获。
第三，我已经尝试过几次，但最终总是为 SharePoint 从头开始重建服务器，因为它可能会以并不总是立即显而易见的方式被巧妙地破坏（管理界面和共享服务似乎特别容易混淆）。 我发现这些天我可以很快地构建一个普通的 MOSS 安装......
SharePoint doesn't like having the server re-named from under it's feet (so to speak). Neither does SQL Server (which I assume you'd have installed on the VM for the installation). Not sure about a DC being renamed, there's probably problems there as well...
Having said that, there are some instructions I've read for renaming both SharePoint machines and SQL Server machines, so you might get somewhere.
On the third hand, I've tried it a few times and always ended up rebuilding the server from the ground up for SharePoint as it can get subtly mangled in ways which aren't always apparent straight away (the admin interface and shared services seem to be especially easy to confuse). I've found that I can build a vanilla MOSS install pretty quickly these days...
Sharepoint 将服务器的名称写入 SQL Server 中的配置表。 因此，如果您更改服务器的名称，事情就会停止工作。
您可以做的就是仅安装操作系统。 然后每次需要新机器时都复制一份。 运行 sysprep
为计算机指定一个新名称。 然后安装 SQL Server 和 MOSS。
这并不完全是您想要的，但它应该可以节省您一些时间。
Sharepoint writes the name of the server into configuration tables in SQL Server. So if you change the name of the server, things stop working.
What you can do, is to install just the OS. Then take a copy each time you need a new machine. Run sysprep
to give the machine a new name. Then install SQL Server and MOSS.
This is not exactly what you are after but it should save you some time.
我已经做到了这一点，而且还不错。
首先重命名 SharePoint 服务器，然后重命名 Windows 服务器。
这篇文章有一个很好的清单。
不要忘记从虚拟机的设置文件中删除 NIC 节点，否则会因重复的 MAC 地址而出现名称冲突。 这里是操作方法。
I've done this, and it wasn't too bad.
Rename the SharePoint-server first, then rename the Windows server.
This posting has a nice checklist.
Don't forget to remove the NIC node from the settings file of the virtual machine, otherwise you get name collision due to duplicate MAC addresses. Here's a how-to.
我相信上面的解决方案确实很好。 但我建议另一种选择...
如果这是一个开发虚拟PC，我建议您执行以下操作
您可能希望跳过步骤 2 并位于同一网络上。 但更改主机文件仍然会指向您。 例如，您的服务器名称是“myserver”，它指向 192.168.1.100，这是本地 ip（具有主机文件条目），那么如果您复制服务器，则给它 ip 192.168.1.150 并编辑主机文件并将 myserver 指向 192.168 .1.150，系统仍能完美运行。 机器的事件日志中会出现一些域名冲突的情况，但不会影响您的开发。
I believe the solutions above are really good. But I would suggest an alternative ...
If this is a development virtual PC I would suggest that you do the following
You might want to skip the step 2 and be on the same network. But changing the hosts file will still point back to you. For example you server name was "myserver" and it was pointed 192.168.1.100 which was the local ip (has hosts file entry) , then if you copy the server give it ip 192.168.1.150 and edit the hosts file and point myserver to 192.168.1.150, the system will still work flawlessly. There will some domain name collisions in the event log of the machine, but it wont affect your development.