2 Comments

  1. I agree, and we’ve been able to structure our Windows templates this way. But it’s all that easy, since it is not sufficient just to place the pagefile on a second disk in the template. When you deploy from the template, at least if you use a customization spec, the pagefile is moved to C:. Also, if you wanted to customize the second drive letter (say to Z:, as we do), that is also undone and the second drive becomes D:.

    We work around such issues by using the run-once function of the customization spec to execute a script we place on the templates. The script handles all the post-deployment tasks to bring the VM’s end-state into compliance with our standards.

  2. Heh, that second sentence should read, “it’s *not* all that easy…”

Comments are closed.