为什么对 Sharepoint 2010 Developer VM 使用 sysprep？
我读过几篇有关创建 Sharepoint Developer VM 的文章。他们都说要“sysprep”它们。为什么（确切地）必须完成 sysprep？如果我们不进行 sysprep，我们会遇到什么样的问题（以及为什么）？
（我想我要问的是，执行“sysprep”和仅启动虚拟机、更改其名称/IP、重新启动然后安装 SP 有什么区别？）
I have read several articles about creating a Sharepoint Developer VM. They all say to "sysprep" them. Why (exactly) must the sysprep be done? What kind of problems (and why) will we run into if we don't sysprep them?
(I suppose what I am asking is, what would be the difference in doing "sysprep" and just bringing up the VM, changing its Name/IP, reboot then install SP?)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
过去，我仅通过复制 Hyper-V vhd 作为克隆虚拟机的方法就取得了成功，但是，现在我在克隆任何计算机时使用 sysprep，因为它在许多地方都被称为最佳实践。而且，它做了一些好事，例如允许您清理一堆我不想重复的东西，并让我在启动时为机器选择一个新名称。来自 MS Sysprep 技术参考：
您可能想阅读 Russinovich 的文章 机器 SID 复制神话（以及为什么 Sysprep 很重要） 更好地解释了 SID 的工作原理，最后一段还有走这条路的另一个原因：
祝你好运！
I've had success in the past with just copying Hyper-V vhd's as a method of cloning VM's - however, I now use sysprep when cloning any of my machines as it's been mentioned as a best practice in many places. And, it does some nice things like allowing you to cleaning up a bunch of stuff that I don't want to duplicate and letting me choose a new name for the machine on boot. From MS Sysprep Technical Reference:
And you may want to read Russinovich's post on The Machine SID Duplication Myth (and Why Sysprep Matters) for more good explanation of how SIDs work and the very last paragraph has another reason for going this route:
Good luck!