You manage a server that runs Windows Server 2012 R2. The server has the Windows
Deployment Services server role installed.
You start a virtual machine named VM1 as shown in the exhibit. (Click the Exhibit button.)
You need to configure a pre-staged device for VM1 in the Windows Deployment Services
console.
Which two values should you assign to the device ID? (Each correct answer presents a
complete solution. Choose two.)
A.
979708BFC04B45259FE0C4150BB6C618
B.
979708BF-C04B-4525-9FE0-C4150BB6C618
C.
00155D000F1300000000000000000000
D.
0000000000000000000000155D000F13
E.
00000000-0000-0000-0000-C4150BB6C618
Explanation:
Use client computer’s media access control (MAC) address preceded with twenty zeros or
the globally unique identifier (GUID) in the format: {XXXXXXXX-XXXX-XXXX-XXXXXXXXXXXXXXX}.
http: //technet. microsoft. com/en-us/library/cc754469. aspx
.
0
0
You may actually use one of them, not both. the MAC address preceded with 20 zeros or the GUID with dashes.
0
0
This is a tricky question. If it was in AD Users and computers, the answer is here:
https://technet.microsoft.com/en-us/library/cc754469.aspx
In the text box, type the client computer’s media access control (MAC) address preceded with twenty zeros or the globally unique identifier (GUID) in the format: {XXXXXXXX-XXXX-XXXX-XXX-XXXXXXXXXXXX}.
However WDS accepts all of the combinations. If it is 32 chars either with no dashes or with dashes in sets of 8-4-4-4-12 chars. Apparently C is wrong, but it seems A,B,D and E all can be valid.
0
0
First, the explanation given by “Aiotestking” is flawed, as it states this :
{XXXXXXXX-XXXX-XXXX-XXXXXXXXXXXXXXX} but it should be this :
{XXXXXXXX-XXXX-XXXX-XXX-XXXXXXXXXXXX} according to the document in technet.
When you actually do the test, in AD Users and Computers, in Windows 2012 R2, you can enter:
A: and hit next
C: and hit next
D: and hit next
C: is not the answer,as the MAC ADDRESS needs to be preceeded with 20 zeroes (to make 32 digits).
So answer is:
A and D:
Unless I’m doing something wrong, but this is what a test has given me.
0
0
Yeah, I’ve actually encountered this problem in the real world. If you enter the dashes in the GUID, you will get errors- at least, if you’re using ADUC to stage the account.
As the answers are stated, B and E would not work in ADUC. You cannot hit NEXT if there are dashes in the ID.
However, since the question specifies WDS console, the correct answer is B and D.
In WDS, you can enter the GUID without dashes and it WILL NOT work, but WDS won’t tell you it’s invalid. The MAC can be 00000000000000000000AABBCCDDEEFF, AABBCCDDEEFF, or AA-BB-CC-DD-EE-FF. But the GUID must have dashes.
0
0
funny in the other question about this they said you need to add it in the WDS console without dashes or you need to enclose it with the brackets {}.
I go for A and D.
0
0
no, the GUID must not have dashes when entered using the wizard.
You only use dashes when you want to enter a DUID. When you enter the GUID omitting the dashes then it gets converted to a DUID and only then PXE boot will work.
I verified this in my lab with an AD integrated WDS, a test vm. Eventually the test vm PXE booted even without using Microsoft DHCP but using a PXE-options-pimped VMware DHCP service…
0
0
what do you mean by “and hit next”?
0
0
B and D
0
0
read, test, verify!
It’s A, not B
0
0
B and D
Microsoft states:
In the text box, type the client computer’s media access control (MAC) address preceded with twenty zeros or the globally unique identifier (GUID) in the format: {XXXXXXXX-XXXX-XXXX-XXX-XXXXXXXXXXXX}.
0
0
The correct answer is B & D as the question states you are using the WDS console rather than ADUC.
In the WDS console, if you enter the GUID without the dashes it accepts it, but if you then open up the computer you’ll see that the GUID has been corrupted. If it is entered with the dashes then it is correct in the properties. You could also enter it with the curly brackets and dashes, but that’s not one of the available options in the answers.
0
0
Absolutely correct. In WDS console UI, if GUID is entered without dashes like 979708BFC04B45259FE0C4150BB6C618, it will accept it, but if computer reopened, then ID looks like {BF089797-4BC0-2545-9FE0-C4150BB6C618}.
0
0