Jump to content


Cahij

Established Members
  • Posts

    4
  • Joined

  • Last visited

Everything posted by Cahij

  1. Hi, Folks, I'm used to muddling through ConfigMgr problems on my own but I've hit the wall. Here's my situation: I am migrating from an old ConfigMgr hierarchy to a new install (1702). I am trying to get PXE boot working in the new environment. All of our clients and 64 bit UEFI devices. Here is what happens: * WinPE loads and immediately after "preparing network connections", the system reboots (every single time) * I press F8 and ipconfig /all shows a valid IP address and all other parameters ... DHCP server, DNS servers, etc. (so it is NOT a NIC driver issue) * I can map a network drive and copy a file from the root of C: to a share on the DP, and vice versa (so it is NOT a storage driver issue) * I can ping the FQDN of the DP * the date and time are correct * smsts.log contains these three suspicious entries: "Failed to download pxe variable file. Code(0x00000001)", "PxeGetPxeData failed with 0x80004005", and "TS environment is not initialized" I have no idea what to do next!
  2. Hi, Niall, thanks for all your work. I actually upgraded prior to reading your guide unfortunately and have noticed these two issues: 1) My USMT was pointing to the correct new datasource location but wasn't renamed like your post said. I simply renamed it, but the Win8.1 version is still installed. Am I good to go or do I need to fix this? You said I would have problems deploying Win10 if I don't uninstall USMT for Win8.1 - which I haven't. What should I do? 2) After upgrade my USMT and boot images are at version 10.0.10586.0 (although Control Panel says USMT is v10.1.10586.0!) but in your guide they are at version 10.0.10240.16384. Is this a problem? Why is this? Thanks, again. John.
  3. Hi, Niall, Thanks for your response. Only 64 bit boot image in use. Not really getting any error message just nothing when trying to PXE boot the surface - no indication about trying for IP4 or IP6 address - just straight through to a normal boot. However, I have managed to get it working and it must have been (at least) one of these things: 1) removed DHCP option 67 2) configured the PXE options in WDS - it was a new install and I'd overlooked this 3) injected the recent Surface 3 firmware updates into the boot image All good now! Thanks!
  4. Hi, Niall. I am getting mixed messages and having trouble PXE booting Surface Pro 3 with SCCM 2012 R2 (on Server 2012 R2). Do I need to use IP Helper Table entries? We have a mix of BIOS and UEFI-based clients? Thanks in advance.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.