Refer to the Exhibit.
An administrator has implemented a new vSphere 5 environment and is deploying their first Windows 2008 R2 template. When running the Deploy Template wizard, the error shown in the exhibit appears.
What can be done to correct the problem?
A.
Select the correct guest OS setting for the virtual machine.
B.
Windows 2003 x64 cannot be customized.
C.
Download and install the Microsoft Sysprep tool into the virtual machine to be customized.
D.
Download the Microsoft Sysprep tool to the appropriate vCenter Server directory.
I think the correct answer is D.
I agree. The correct answer should be D as the sysprep tools re used for creating the answer file for customisation
The correct answer is D.
for w2k3,yes, you need Sysprep.
I deployed many w2k8 VMs. never had to deal with Sysprep. there is an option to check for a new SID.
and check out this blog, it should be back me up.
http://jeremywaldrop.wordpress.com/2008/10/28/how-to-build-a-windows-2008-vmware-esx-vm-template/
A is correct.
See also the table at:
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1005593
sysprep is not applicable for Windows vista/2008/7
The correct answer is D. I spent 3 nights to figure out why my SysPrep files weren’t being picked up from the right directory. Once I placed the SysPrep files in the correct directory, the options were not greyed out anymore. You can even try and choose Linux after that and this wizard will be enabled (it won’t do anything on Linux).
A – can never be the answer as choosing the guest has nothing to do with these options being greyed out.
Try this in your lab. Place the SysPrep files in the correct directory of your vSphere install and run the wizard. Then remove the files and then once again try to run it. You will notice this time, the wizard is greyed out ..simplez 🙂
I have agree with the person who selected A. This is a trick question.
SC noted that they got a similar problem when the Sysprep files were not put in the proper location on the vSphere server. This being vSphere 5, these files are assumed to already be there. Also, when you pick an OS that is not deployable these options should be greyed out.
Whenever you see a question with two possible correct you have to exclude the one that assumes that something was damaged or misconfigured. In this case, that leaves A.
Vista and Windows 2008 do not require sysprep.
http://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.vsphere.install.doc%2FGUID-7C9A1E23-7FCD-4295-9CB1-C932F2423C63.html#com.vmware.vsphere.vm_admin.doc/GUID-F6646EF7-E217-4F56-A64E-3A621D5C6D6E.html?resultof=%2522%2573%2579%2573%2570%2572%2565%2570%2522%2520
The correct answer is A.
System Preparation tools are built into the Windows Server 2008 operating system and do not have to be downloaded.
A must be correct.
from kb.vmware.com:
“Activate the guest operating system with a valid Microsoft Volume License Key, so that the operating system is activated and can convert the virtual machine to a template.”
There is nothing about sysprep.
Guys, D is correct.
here they are showing the error, not the O.S which one is used? So based on common sense, the error do occurs with 2k3 or earlier windows, which require a sysprep !!
the answer is A.
see: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1005593
“Windows Server 2008 R2
System Preparation tools are built into the Windows Server 2008 R2 operating system and do not have to be downloaded.”
so D is incorrect.