如何通过 Windows 更新使 VM 快照树保持最新？
为了测试我们产品的安装程序，我维护了一个包含不同先前安装版本的虚拟机快照树。 在每个虚拟机上执行 Windows 更新、重新快照、删除父快照是一项繁琐的任务。
是否有一种自动化解决方案可以使一组虚拟机保持最新状态？ 我使用 VirtualBox，但可以访问 VMware Workstation，如果维护工作得到改进，我会切换。
For testing our product's installer, I maintain a tree of virtual machine snapshots with different previous versions installed. It is a tedious task to do Windows Update, re-snapshot, delete parent snapshot on each VM.
Is there an automated solution for keeping a group of VMs up-to-date? I use VirtualBox but have access to VMware Workstation and would switch if maintenance would improve.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我们在某种库中保存虚拟机的基线。 它们大约有 20 多个（其中混合了不同版本的 Java、DB2、WAS 等），开发和测试团队可以复制出来供自己使用。
图书管理员（开发人员，兼职做这件事）负责让它们保持最新状态。 他们要做的就是每周左右复制一个虚拟机，启动它并安装所有更新，然后将更新后的虚拟机复制回原始虚拟机。 这意味着除非正在完成复制操作，否则它可以用于签出。 此外，由于虚拟机是共享的，因此需要更新的虚拟机数量得以最小化。
这就是我们制作快照的方式，通过复制目录部分是因为它更容易管理，但主要是因为我们太紧张而无法购买工作站版本:-)我们改用播放器。
它大部分是自动化的，因为所有虚拟机都从我们的 SUS 服务器获取更新，并且我们知道它们何时准备好更新。 图书馆员通过脚本通知哪些虚拟机需要更新，只需运行另一个脚本来复制虚拟机并启动副本。
一旦图书馆员对副本是最新的感到满意，他们就会将其关闭，然后另一个脚本将该虚拟机复制回图书馆并更新其状态。
We keep a baseline of VMs in a library of sorts. They're are about 20-odd (with mixtures of different versions of Java, DB2, WAS and so on) that the development and test teams can copy out for their own use.
The librarian (developer, doing this part-time) is responsible for keeping them up to date. What they'll do is copy one of the VMs every week or so, boot it and install all updates, then copy the updated VM back over the original. This means it's available for checking out except when the copy operation is being done. Additionally, the number of VMs that need to be updated is minimized by virtue of the fact that they're shared.
That's how we do our snapshots, by copying the directories partially because it's easier to manage but mostly because we're too tight to buy the workstation version :-) We use the player instead.
It's mostly automated since all the VMs grab their updates from our SUS server and we know when they have updates ready to go. The librarian is notified by a script which VMs need to be updated and just has to run another script which copies the VM and starts the copy.
Once the librarian is satisfied the copy is up to date, they shut it down and yet another script copies that VM back into the library and updates its status.
我不知道适用于所有虚拟机的自动化解决方案，但我建议使用 Windows Server 更新服务用于跟踪每个虚拟机的更新状态并提供本地 Windows 更新存储库以加快更新过程。
我想您可以结合使用 WSUS 和组策略来执行这些更新，设置自动更新安装，并在给定时间内打开所有虚拟机以确保它们都获得更新。
但这并不能解决管理快照等问题。 我想知道VMWare是否有API...
I don't know of an automated solution for all of your VMs, but I would recommend using Windows Server Update Services to keep track of the update status of every VM and provide a local Windows Update repository to speed up the updating process.
I suppose you could use a combination of WSUS and Group Policy to do these updates, setting up automatic update installation, and just turning on all of your VMs for a given period to make sure they all get the updates.
That doesn't solve the problem with managing snapshots etc though. I wonder if VMWare has an API...