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-XXXXXXXXXXXXXXX}.
* 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”
.
C does not work. Tested on lab. Does not enable the “next” button.
B works.
Does D & B work then?
I think it is B & D as well. After readling on the web and this presentation of the whole process i can determine that you need to remove the dashes from GUID.
B & D
http://www.windows-noob.com/forums/index.php?/topic/506-how-can-i-prestage-a-computer-for-wds/
https://technet.microsoft.com/en-us/library/cc754469.aspx
answer is correct
The tech net article says to put it in the format {XXXXXXXX-XXXX-XXXX-XXX-XXXXXXXXXXXX}, but all the online guides say to put it in without the dashes. I do believe B is the right answer
You can use dashes if you use the brackets. Without brackets you can’t use dashes.
Incorrect. Testing revealed that only alphanumeric GUIDs work. Any special characters such as hyphens or curly braces breaks it.
In WDS console,
I create a prestaged device user B as device ID, and it work.
but when I see the properties,
I see the ID:BF089797-XXXX-…
not:979708BF-XXXX-…
so, anything wrong?
experienced the same, which tells me B is wrong
https://morgansimonsen.wordpress.com/2010/06/19/windows-deployment-service-pre-staging-and-guids/
tested on lab, answers C and D correct (B not accepted by gui)
i check in my lab B and D
The answer is C & D. As if you input B into the GUI it would reorder it as shown in this link which is posted above, an extract is shown below for your reference.
If you want to pre-stage a Hyper-V VM in Active Directory using this GUID you have to enter it with braces and with hyphens. This prevents ADUC from converting it, which it would do with a normal (octet string) GUID. So the braces probably mean ‘literal’ string or something.
From : https://morgansimonsen.wordpress.com/2010/06/19/windows-deployment-service-pre-staging-and-guids/
funny you guys writing about different answers but all tested in your labs 😉
I just tested also, and I think it’s maybe just good to know HOW to test.
So I did it this way: adding a prestaged device using the wizard. I filled in a GUID that looked the way like in answer C. Then I verified by taking a look at the new device’s properties where I saw the same value but surrounded by {} symbols…so for me answer C worked!
maybe you like to tell us how you guys tested?
ok, I have to admin, after I tested further trying to get the PXE boot working, that I was wrong and answer B is correct!
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 then Windows converts that GUID to a DUID and eventually the PXE boot works…
So indeed it’s B (not C), and D
i noticed something in the the options apart from your quarrel over B OR C.i will definitely go for B over C because the GUID does not match with the option see urself.and i tested this on lab if write without hyphens then only next option will appear and only when u write in brackets.So there is no such brackets seen in the options.so it makes a +2 to go for B
Cheers
Hi,I noticed a difference between the given GUID:979708BF-C04B-4525-9FE0-C4150BB6C618 in the question with the choices provided with C:979708BF-C04B-452S-9FE0-C4150BB6C618.The reason that “C” is not being accepted is in part of “452S” while on the question its “4525” so if we try to change it to “4525” the answer “C” is accepted.
Personally did some testing on some VMs. The client did not network boot when Answer C. was used. Using Answer B. or Answer D. both allowed the client to boot off the network. All the IDs were copied and pasted into the server VM verbatim from the document (albeit with the fix achang pointed out.
It is confirmed that B and D are the correct answers.
the question is messed up!
MAC address part is easy, its D
but, the guid part is very messed up, because :
C has a typo in the third part (452S) instead of (4525) otherwise it works,
If you test B in your lab , after you click Next and save, you will find out that it changes the guid to “{BF089797-4BC0-2545-9FE0-C4150BB6C618}”
so B is wrong, but C also have a typo “S” instead of “5” if I assume that whoever wrote this question down on aiotestking did a typo error, C would be the correct guid format.
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 “-“.