garethEds Posted September 28, 2009 Author Posted September 28, 2009 Here's a weird one. I've changed the boot option in WDS to show: boot\x86\wdsnbp.com When the Celeron machine boots up it is reporing as a 64 bit machine. This is a celeron!!! No wonder there are no images being shown. Why would an image captured on a 32bit Celeron be reporting as a 64 bit machine? Am I correct in assuming wdnsbp.com looks at the machine and loads accordingly the correct boot image? GJE So I've made the changes advised here. This is where I am: I press F12 twice and the boot\x86\wdsnbp.com loads up and detect the machine as 64bit. Is then proceeds to load boot\x64\pxeboot.com I've set the boot\x86\wdsnbp.com in DHCP as option 67. Under Scope Options and Server Options -= would this be correct? Or is it only one of them I need to complete. GJE
jsnetman Posted September 28, 2009 Posted September 28, 2009 (edited) Have you disabled architecture discovery in the registry and then restarted the WDS service, aslo in my boot settings is this: boot\x86\pxeboot.com Edited September 28, 2009 by jsnetman
garethEds Posted September 28, 2009 Author Posted September 28, 2009 Have you disabled architecture discovery in the registry and then restarted the WDS service Yes. GJE
garethEds Posted September 28, 2009 Author Posted September 28, 2009 Have you disabled architecture discovery in the registry and then restarted the WDS service, aslo in my boot settings is this: boot\x86\pxeboot.com Is that in the WDS or within DHCP Option 67
jsnetman Posted September 28, 2009 Posted September 28, 2009 My boot settings are this: boot\x86\pxeboot.com in the wds setting
jsnetman Posted September 28, 2009 Posted September 28, 2009 I also have only option 60 in DHCP. My DHCP is the same server as the WDS.
garethEds Posted September 28, 2009 Author Posted September 28, 2009 I also have only option 60 in DHCP. My DHCP is the same server as the WDS. We don't have Option 60 - this is because our DHCP is on another server. We have the necessary boxes in WDS unticked. GJE
garethEds Posted October 4, 2009 Author Posted October 4, 2009 Moving this along - we now have our DHCP moved onto our Windows 2008 server - which is also the WDS server. The LEA did this for us as they look to help us as well with out WDS issues. Following advice on here I used the wdsutil command to pre-stage a machine in the AD. I used the full command with the AD stuff in there. The good news was that it created the machine. The image deployed and picked up the pre-staged machine name. Now what is confusing me is why the UI part isn't working. I've tried it on many computers using the AD Users and Computers Snapin in the MMC. I still get that error about the server not being recognised as a Remote Installation Server. It's sooo strange. I've asked about this on several forums and even within the LEA - nobody seems to be able to explain it. GJE
Finch7 Posted January 28, 2011 Posted January 28, 2011 Moving this along - we now have our DHCP moved onto our Windows 2008 server - which is also the WDS server. The LEA did this for us as they look to help us as well with out WDS issues. Following advice on here I used the wdsutil command to pre-stage a machine in the AD. I used the full command with the AD stuff in there. The good news was that it created the machine. The image deployed and picked up the pre-staged machine name. Now what is confusing me is why the UI part isn't working. I've tried it on many computers using the AD Users and Computers Snapin in the MMC. I still get that error about the server not being recognised as a Remote Installation Server. It's sooo strange. I've asked about this on several forums and even within the LEA - nobody seems to be able to explain it. GJE Did you resolve the UI issue?
garethEds Posted January 28, 2011 Author Posted January 28, 2011 HI Finch7, No - never sorted this out. It then went on the back burner as we got to a stage were all our machines were pre-staged with a batch file. I will be looking at it again when we upgrade our WDS server to 2008R2 later in the year and moving to MDT. Sorry about that Gareth
Finch7 Posted January 28, 2011 Posted January 28, 2011 I just setup WDS on 2008R2 after enjoying many years of RIS. I get the same UI trouble however I just installed the AD tools on our WDS server and they aren't throwing up the error. Just testing now to see if our test client gets named correctly and joins the domain. I find it odd that the only 3 results in google are all yours asking the same question in 3 different places. No other reference.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now