You manage a server that runs Windows Server 2012 R2. The server has the Windows Deployment Services
server role installed.
You have a desktop computer that has the following configuration:
Computer name: Computer1
Operating system: Windows 8
MAC address: 20-CF-30-65-D0-87
GUID: 979708BF-C04B-4525-9FE0-C4150BB6C618
You need to configure a pre-staged device for Computer1 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.
20CF3065D08700000000000000000000
B.
979708BFC04B45259FE0C4150BB6C618
C.
979708BF-C04B-452S-9FE0-C4150BB6C618
D.
0000000000000000000020CF306SD087
E.
00000000-0000-0000-0000-C41S0BB6C618
Explanation:
In the text box, type the client computer’s MAC address preceded with twenty zeros or the globally unique
identifier (GUID) in the format: {XXXXXXXX-XXXX-XXXX-XXX-XXXXXXXXXXXX}.
* To add or remove pre-staged client to/from AD DS, specify the name of the computer or the device ID, which
is a GUID, media access control (MAC) address, or Dynamic Host Configuration Protocol (DHCP) identifier
associated with the computer.
* Example: Remove a device by using its ID from a specified domain
This command removes the pre-staged device that has the specified ID. The cmdlet searches the domain
named TSQA.contoso.com for the device.
Windows PowerShell
PS C:\> Remove-WdsClient -DeviceID “5a7a1def-2e1f-4a7b-a792-ae5275b6ef92” -Domain -DomainName
“TSQA.contoso.com”
Why the answer isn’t B & D?
I just tested it by adding a prestaged device using the wizard. I filled in a GUID that looked the way like in answer C, and it worked! I verified by taking a look at the new device’s properties where I saw the same value but surrounded by {} symbols…
So, provided answer is correct
I have to admit, after I tested further trying to get the PXE boot working, that I was wrong and answer B is correct!
Explanation
When you use the format like in C then indeed you see the same value in the device properties afterwards, but it just does not work. After examining the DeploymentServices Eventlog I noticed that it’s because I entered the GUID, but Windows wants a DUID here (wtf). Once you omit the minuses in the wizard then Windows converts that GUID to a DUID and eventually the PXE boot works…
So indeed it’s B (not C), and D
Agree with answer
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}.
https://technet.microsoft.com/en-us/library/cc754469.aspx
I agree with B and D.
From what I’ve read, you can have the dashes in the GUID, but you must had {} before an after it. If not, then just enter it with no dashes.
https://morgansimonsen.wordpress.com/2010/06/19/windows-deployment-service-pre-staging-and-guids/
http://www.windows-noob.com/forums/topic/506-how-can-i-prestage-a-computer-for-wds/
https://technet.microsoft.com/en-us/library/cc754469.aspx – step 5
I have to agree that it is B & D. If you read the Technet article carefully it says for Step 5:
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}.
Note that answer C does not include the brackets. So it can be ruled out on that basis, leaving answer B as the only valid answer for the GUID.
It’s definitely C and D. The question says that you need to configure a pre-staged device for Computer1 in the Windows Deployment Services console, not in the ADUC. WDS Console can apply dashes in the GUID.
Exactly!
YOU enter:
979708BFC04B45259FE0C4150BB6C618
and WDS Console will automatically change it to:
979708BF-C04B-452S-9FE0-C4150BB6C618
So the answer is B (NOT C).
If you enter 979708BFC04B45259FE0C4150BB6C618 in wds console, then guid will be bf089797-etc. So the answer must be C.
It is C and D.
I spun up WDS and put in both
979708BF-C04B-4525-9FE0-C4150BB6C618
and
979708BFC04B45259FE0C4150BB6C618
only 979708BF-C04B-4525-9FE0-C4150BB6C618 shows up correctly when getting properties on the staged device as the Device ID
Ok, so after googling about this subject and testing in lab, i came to this conclusion, B is correct because on the C option, this part of the GUID “452S” doesn’t match the correct GUID provided in the question which is “4525”.
If you correct that part ins option C, when you’re adding the device using “Add Prestaged Device Wizard”, then C answer would also be correct. I’m no sure if that’s a typo or it’s in that way in purpose to make the answer B the only correct answer. Otherwise the 2 answers would be correct.
So in the exam you must pay attention to every detail.
http://www.windows-server-2012-r2.com/designing-a-server-deployment-infrastructure-with-wds.html
Computer name: Computer1
Operating system: Windows 8
MAC address: 20-CF-30-65-D0-87
GUID: 979708BF-C04B-4525-9FE0-C4150BB6C618
Tested in lab,
The answers are C and D.
A) 20CF3065D08700000000000000000000 => false option
WDS considers it for an DUID and convert it an GUID {…..}
B) 979708BFC04B45259FE0C4150BB6C618 is an DUID format => false option
If you use this once for add, it’s automatically converted in GUID, displays = {979708BF-C04B-4525-9FE0-C4150BB6C618}
C) 979708BF-C04B-452S-9FE0-C4150BB6C618 => correct answer
With “-” in the string, WDS considers that it’s GUID and adds “{” before string and “}” after the string.
When you look properties new added device, you see {979708BF-C04B-4525-9FE0-C4150BB6C618}
D) 0000000000000000000020CF3065D087 => correct answer
There are 20 zeros before Mac address, WDS considers it for an Mac.
You see on added pre staged device : 20-CF-30-65-D0-87
E) totally false option
After many tests, WORKS in WDS :
GUID format :
– 979708BF-C04B-4525-9FE0-C4150BB6C618 (C option)
– {979708BF-C04B-4525-9FE0-C4150BB6C618}
Mac address format :
– 0000000000000000000020CF3065D087 (D option)
– 20CF3065D087
– 20-CF-30-65-D0-87
All computer displays DUID in format with “-“.
For add an DUID format, you must ignore “-“.
WDS convert it automatically an GUID with “-” and “{}”.
Be careful, vM displays GUID format directly, so, you must keep all “-“.
https://morgansimonsen.com/2010/06/19/windows-deployment-service-pre-staging-and-guids-2/