WDS 2008 R2 / 2012 Discovery client not asking for the correct architecture The 2019 Stack Overflow Developer Survey Results Are InMultiple PXE boots on the same subnet for RIS and WDSWhy can I not get a WDS-originated PXE boot to progress past the first file download?WDS - Clients receive Error: PXE-E53: No boot filename receivedWDS discovery image not working - Failed to discover WDS ServerDeploying custom image on PXE client by WDS gives me 0c0000428 errorWDS 2012: UEFI Client Network Boot results in error 0x102Using WDS, where are the log files located on the CLIENT trying to capture an image?PXE Client-Error via WDS: 'bootx64wdsmgfw.efi' not foundWDS ERROR on some workstations (Error retrieving network information (0x80072743))
Is this app Icon Browser Safe/Legit?
What is the closest word meaning "respect for time / mindful"
Can a flute soloist sit?
What is the motivation for a law requiring 2 parties to consent for recording a conversation
The difference between dialogue marks
Pokemon Turn Based battle (Python)
If a Druid sees an animal’s corpse, can they Wild Shape into that animal?
Feature engineering suggestion required
Why is the maximum length of OpenWrt’s root password 8 characters?
Why can Shazam fly?
What is the meaning of Triage in Cybersec world?
Reference request: Oldest number theory books with (unsolved) exercises?
Worn-tile Scrabble
Interpreting the 2019 New York Reproductive Health Act?
Does the shape of a die affect the probability of a number being rolled?
What does Linus Torvalds mean when he says that Git "never ever" tracks a file?
Why isn't the circumferential light around the M87 black hole's event horizon symmetric?
Is bread bad for ducks?
Why hard-Brexiteers don't insist on a hard border to prevent illegal immigration after Brexit?
Origin of "cooter" meaning "vagina"
Delete all lines which don't have n characters before delimiter
Are spiders unable to hurt humans, especially very small spiders?
Right tool to dig six foot holes?
Why is the Constellation's nose gear so long?
WDS 2008 R2 / 2012 Discovery client not asking for the correct architecture
The 2019 Stack Overflow Developer Survey Results Are InMultiple PXE boots on the same subnet for RIS and WDSWhy can I not get a WDS-originated PXE boot to progress past the first file download?WDS - Clients receive Error: PXE-E53: No boot filename receivedWDS discovery image not working - Failed to discover WDS ServerDeploying custom image on PXE client by WDS gives me 0c0000428 errorWDS 2012: UEFI Client Network Boot results in error 0x102Using WDS, where are the log files located on the CLIENT trying to capture an image?PXE Client-Error via WDS: 'bootx64wdsmgfw.efi' not foundWDS ERROR on some workstations (Error retrieving network information (0x80072743))
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
Background info: we're running on a network where we don't control DNS or DHCP, but we run a domain within it. We are trying to use WDS with a discovery image pointing to our WDS server.
Odd issue -- we started with WDS running on Windows 2012, properly configured and verified working on our older test machines. The machine boots up, reads the boot image off of the USB drive, and brings us to the 'Choose your language' page, then prompts for credentials before showing the list of available images.
We then moved to our computer labs, where the machines are a little newer. This time, it boots, pulls an IP, and then gets to the generic "WdsClient: There was a problem initializing wds mode". We checked the server logs, and it seems to be failing because there is no boot image available for "x86uefi" architecture. The thing is, we're using an x64 WinPE image to start a Windows 7 x64 boot image, and trying to deploy Windows 7 x64. We don't want x86uefi, but can't seem to find a way to force it to ask for that.
We've tried an x86 WinPE image and an x86 boot image, but we get the same error.
We then tried using WDS running on 2008 R2, and are having the same problem.
When we hit shift+F10, we can see that the clients are pulling IPs from DHCP and are pinging the server just fine. It just doesn't want to run. The event logs show that it asks 10 or so times before it craps out.
wds
asked Sep 26 '13 at 14:30
atmarxatmarx
135129
add a comment |
Background info: we're running on a network where we don't control DNS or DHCP, but we run a domain within it. We are trying to use WDS with a discovery image pointing to our WDS server.
Odd issue -- we started with WDS running on Windows 2012, properly configured and verified working on our older test machines. The machine boots up, reads the boot image off of the USB drive, and brings us to the 'Choose your language' page, then prompts for credentials before showing the list of available images.
We then moved to our computer labs, where the machines are a little newer. This time, it boots, pulls an IP, and then gets to the generic "WdsClient: There was a problem initializing wds mode". We checked the server logs, and it seems to be failing because there is no boot image available for "x86uefi" architecture. The thing is, we're using an x64 WinPE image to start a Windows 7 x64 boot image, and trying to deploy Windows 7 x64. We don't want x86uefi, but can't seem to find a way to force it to ask for that.
We've tried an x86 WinPE image and an x86 boot image, but we get the same error.
We then tried using WDS running on 2008 R2, and are having the same problem.
When we hit shift+F10, we can see that the clients are pulling IPs from DHCP and are pinging the server just fine. It just doesn't want to run. The event logs show that it asks 10 or so times before it craps out.
wds
asked Sep 26 '13 at 14:30
atmarxatmarx
135129
On 2008 R2, the architecture it thinks it's looking for is "Arch: 6" which seems to be EFI IA32 -- again, it wants EFI, but we want regular x64.
– atmarx
Sep 26 '13 at 14:31
add a comment |
Background info: we're running on a network where we don't control DNS or DHCP, but we run a domain within it. We are trying to use WDS with a discovery image pointing to our WDS server.
Odd issue -- we started with WDS running on Windows 2012, properly configured and verified working on our older test machines. The machine boots up, reads the boot image off of the USB drive, and brings us to the 'Choose your language' page, then prompts for credentials before showing the list of available images.
We then moved to our computer labs, where the machines are a little newer. This time, it boots, pulls an IP, and then gets to the generic "WdsClient: There was a problem initializing wds mode". We checked the server logs, and it seems to be failing because there is no boot image available for "x86uefi" architecture. The thing is, we're using an x64 WinPE image to start a Windows 7 x64 boot image, and trying to deploy Windows 7 x64. We don't want x86uefi, but can't seem to find a way to force it to ask for that.
We've tried an x86 WinPE image and an x86 boot image, but we get the same error.
We then tried using WDS running on 2008 R2, and are having the same problem.
When we hit shift+F10, we can see that the clients are pulling IPs from DHCP and are pinging the server just fine. It just doesn't want to run. The event logs show that it asks 10 or so times before it craps out.
wds
asked Sep 26 '13 at 14:30
atmarxatmarx
135129
Background info: we're running on a network where we don't control DNS or DHCP, but we run a domain within it. We are trying to use WDS with a discovery image pointing to our WDS server.
Odd issue -- we started with WDS running on Windows 2012, properly configured and verified working on our older test machines. The machine boots up, reads the boot image off of the USB drive, and brings us to the 'Choose your language' page, then prompts for credentials before showing the list of available images.
We then moved to our computer labs, where the machines are a little newer. This time, it boots, pulls an IP, and then gets to the generic "WdsClient: There was a problem initializing wds mode". We checked the server logs, and it seems to be failing because there is no boot image available for "x86uefi" architecture. The thing is, we're using an x64 WinPE image to start a Windows 7 x64 boot image, and trying to deploy Windows 7 x64. We don't want x86uefi, but can't seem to find a way to force it to ask for that.
We've tried an x86 WinPE image and an x86 boot image, but we get the same error.
We then tried using WDS running on 2008 R2, and are having the same problem.
When we hit shift+F10, we can see that the clients are pulling IPs from DHCP and are pinging the server just fine. It just doesn't want to run. The event logs show that it asks 10 or so times before it craps out.
wds
wds
asked Sep 26 '13 at 14:30
atmarxatmarx
135129
asked Sep 26 '13 at 14:30
atmarxatmarx
135129
asked Sep 26 '13 at 14:30
atmarxatmarx
135129
asked Sep 26 '13 at 14:30
atmarxatmarx
135129
asked Sep 26 '13 at 14:30
atmarxatmarx
135129
135129
On 2008 R2, the architecture it thinks it's looking for is "Arch: 6" which seems to be EFI IA32 -- again, it wants EFI, but we want regular x64.
– atmarx
Sep 26 '13 at 14:31
add a comment |
On 2008 R2, the architecture it thinks it's looking for is "Arch: 6" which seems to be EFI IA32 -- again, it wants EFI, but we want regular x64.
– atmarx
Sep 26 '13 at 14:31
On 2008 R2, the architecture it thinks it's looking for is "Arch: 6" which seems to be EFI IA32 -- again, it wants EFI, but we want regular x64.
– atmarx
Sep 26 '13 at 14:31
On 2008 R2, the architecture it thinks it's looking for is "Arch: 6" which seems to be EFI IA32 -- again, it wants EFI, but we want regular x64.
– atmarx
Sep 26 '13 at 14:31
add a comment |
1 Answer
1
active
oldest
votes
Have you tried changing from UEFI mode to legacy BIOS or BIOS-compatibility mode on the PC? The TechNet article ‘Boot a PC in UEFI Mode or Legacy BIOS-compatibility mode’ should help.
You may also want to read more about UEFI Firmware, as more machines will be made with UEFI and you will want to incorporate this into your deployment strategy.
Hope this helps,
answered Sep 26 '13 at 18:13
dwoltersdwolters
1,225711
Thanks for the suggestion. These are on Optiplex 960s with UEFI disabled and boot mode set to legacy. We are not interested in pushing out UEFI yet. On our test bench we have DHCP and WDS, and have no issue getting these to boot and pull the correct architecture. It's only when using the discovery image that it can't get find the right image.
– atmarx
Sep 27 '13 at 16:43
@Andrew Have you updated the BIOS on those machines? There is a BIOS update dated 9/3/2013 on the Dell website, hopefully that will help.
– dwolters
Oct 4 '13 at 13:28
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f541888%2fwds-2008-r2-2012-discovery-client-not-asking-for-the-correct-architecture%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Have you tried changing from UEFI mode to legacy BIOS or BIOS-compatibility mode on the PC? The TechNet article ‘Boot a PC in UEFI Mode or Legacy BIOS-compatibility mode’ should help.
You may also want to read more about UEFI Firmware, as more machines will be made with UEFI and you will want to incorporate this into your deployment strategy.
Hope this helps,
answered Sep 26 '13 at 18:13
dwoltersdwolters
1,225711
Thanks for the suggestion. These are on Optiplex 960s with UEFI disabled and boot mode set to legacy. We are not interested in pushing out UEFI yet. On our test bench we have DHCP and WDS, and have no issue getting these to boot and pull the correct architecture. It's only when using the discovery image that it can't get find the right image.
– atmarx
Sep 27 '13 at 16:43
@Andrew Have you updated the BIOS on those machines? There is a BIOS update dated 9/3/2013 on the Dell website, hopefully that will help.
– dwolters
Oct 4 '13 at 13:28
add a comment |
Have you tried changing from UEFI mode to legacy BIOS or BIOS-compatibility mode on the PC? The TechNet article ‘Boot a PC in UEFI Mode or Legacy BIOS-compatibility mode’ should help.
You may also want to read more about UEFI Firmware, as more machines will be made with UEFI and you will want to incorporate this into your deployment strategy.
Hope this helps,
answered Sep 26 '13 at 18:13
dwoltersdwolters
1,225711
Thanks for the suggestion. These are on Optiplex 960s with UEFI disabled and boot mode set to legacy. We are not interested in pushing out UEFI yet. On our test bench we have DHCP and WDS, and have no issue getting these to boot and pull the correct architecture. It's only when using the discovery image that it can't get find the right image.
– atmarx
Sep 27 '13 at 16:43
@Andrew Have you updated the BIOS on those machines? There is a BIOS update dated 9/3/2013 on the Dell website, hopefully that will help.
– dwolters
Oct 4 '13 at 13:28
add a comment |
Have you tried changing from UEFI mode to legacy BIOS or BIOS-compatibility mode on the PC? The TechNet article ‘Boot a PC in UEFI Mode or Legacy BIOS-compatibility mode’ should help.
You may also want to read more about UEFI Firmware, as more machines will be made with UEFI and you will want to incorporate this into your deployment strategy.
Hope this helps,
answered Sep 26 '13 at 18:13
dwoltersdwolters
1,225711
Have you tried changing from UEFI mode to legacy BIOS or BIOS-compatibility mode on the PC? The TechNet article ‘Boot a PC in UEFI Mode or Legacy BIOS-compatibility mode’ should help.
You may also want to read more about UEFI Firmware, as more machines will be made with UEFI and you will want to incorporate this into your deployment strategy.
Hope this helps,
answered Sep 26 '13 at 18:13
dwoltersdwolters
1,225711
answered Sep 26 '13 at 18:13
dwoltersdwolters
1,225711
answered Sep 26 '13 at 18:13
dwoltersdwolters
1,225711
answered Sep 26 '13 at 18:13
dwoltersdwolters
1,225711
1,225711
Thanks for the suggestion. These are on Optiplex 960s with UEFI disabled and boot mode set to legacy. We are not interested in pushing out UEFI yet. On our test bench we have DHCP and WDS, and have no issue getting these to boot and pull the correct architecture. It's only when using the discovery image that it can't get find the right image.
– atmarx
Sep 27 '13 at 16:43
@Andrew Have you updated the BIOS on those machines? There is a BIOS update dated 9/3/2013 on the Dell website, hopefully that will help.
– dwolters
Oct 4 '13 at 13:28
add a comment |
Thanks for the suggestion. These are on Optiplex 960s with UEFI disabled and boot mode set to legacy. We are not interested in pushing out UEFI yet. On our test bench we have DHCP and WDS, and have no issue getting these to boot and pull the correct architecture. It's only when using the discovery image that it can't get find the right image.
– atmarx
Sep 27 '13 at 16:43
@Andrew Have you updated the BIOS on those machines? There is a BIOS update dated 9/3/2013 on the Dell website, hopefully that will help.
– dwolters
Oct 4 '13 at 13:28
Thanks for the suggestion. These are on Optiplex 960s with UEFI disabled and boot mode set to legacy. We are not interested in pushing out UEFI yet. On our test bench we have DHCP and WDS, and have no issue getting these to boot and pull the correct architecture. It's only when using the discovery image that it can't get find the right image.
– atmarx
Sep 27 '13 at 16:43
Thanks for the suggestion. These are on Optiplex 960s with UEFI disabled and boot mode set to legacy. We are not interested in pushing out UEFI yet. On our test bench we have DHCP and WDS, and have no issue getting these to boot and pull the correct architecture. It's only when using the discovery image that it can't get find the right image.
– atmarx
Sep 27 '13 at 16:43
@Andrew Have you updated the BIOS on those machines? There is a BIOS update dated 9/3/2013 on the Dell website, hopefully that will help.
– dwolters
Oct 4 '13 at 13:28
@Andrew Have you updated the BIOS on those machines? There is a BIOS update dated 9/3/2013 on the Dell website, hopefully that will help.
– dwolters
Oct 4 '13 at 13:28
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f541888%2fwds-2008-r2-2012-discovery-client-not-asking-for-the-correct-architecture%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
On 2008 R2, the architecture it thinks it's looking for is "Arch: 6" which seems to be EFI IA32 -- again, it wants EFI, but we want regular x64.
– atmarx
Sep 26 '13 at 14:31