Greetings -
Been struggling with this for a while and can't find an answer elsewhere.
Windows 2008 SP2 x64 running Hyper-V with all of the updates (that I'm aware of).
System Center Virtual Machine Manager 2008 running on a different Windows 2008 SP2 x64 box.
Created a new guest running Windows Server 2008 R2. Machine is running fine, even though the Server 2008 R2 is not an option for "operating system" of the guest's properties (I set it to Windows Server 2008 x64).
Anyways, trying to create a template from this machine. Each time it fails during the sysprep phase. I see it get to 99% of syspreping, then says "Error (13206) Vitual Machine Manager cannot locate the boot or system volume on the virtual machine NO_PARAM. The resulting virtual machine might not start or operate properly." This results in nothing created in the templates folder I specified. If I ignore the error on the original guest and start it, it appears to go through the sysprep mini setup.
If, while creating the template, I specify [Customization not required] for the guest operating system, it will create the template, but doesn't include the sysprep process, so I have to do that manually.
Of course, I could just sysprep the source guest, and copy the .vhd to my library, and build new guests from that. But I was really trying to just deploy using a template.
Am I missing something, or is this truly an issue with trying to use R2 guests to build the template?
Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.
Been struggling with this for a while and can't find an answer elsewhere.
Windows 2008 SP2 x64 running Hyper-V with all of the updates (that I'm aware of).
System Center Virtual Machine Manager 2008 running on a different Windows 2008 SP2 x64 box.
Created a new guest running Windows Server 2008 R2. Machine is running fine, even though the Server 2008 R2 is not an option for "operating system" of the guest's properties (I set it to Windows Server 2008 x64).
Anyways, trying to create a template from this machine. Each time it fails during the sysprep phase. I see it get to 99% of syspreping, then says "Error (13206) Vitual Machine Manager cannot locate the boot or system volume on the virtual machine NO_PARAM. The resulting virtual machine might not start or operate properly." This results in nothing created in the templates folder I specified. If I ignore the error on the original guest and start it, it appears to go through the sysprep mini setup.
If, while creating the template, I specify [Customization not required] for the guest operating system, it will create the template, but doesn't include the sysprep process, so I have to do that manually.
Of course, I could just sysprep the source guest, and copy the .vhd to my library, and build new guests from that. But I was really trying to just deploy using a template.
Am I missing something, or is this truly an issue with trying to use R2 guests to build the template?
Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.
