Posted December 7, 201113 yr I am attempting to create a sysprepped template of a virtual machine running 2008R2 Data Center in Vsphere 4.1 My unattend file processes correctly, but is producing an unexpected result: When the machine first boots after sysprep I get an error message that Windows has created a temporary paging file, and when I check my Virtual Memory settings I see that I have no paging file. Prior to running sysprep I had the paging file on a dedicated swap volume E: for example... and after running sysprep I see that the volume has disappeared and is no longer connected. Is there any way around this? Is there a way I can set my unattend to specify/prevent changes to the Virtual Memory settings, or another step I can take to prevent the settings from changing?
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.