Jump to content


drew.sartorius

Established Members
  • Posts

    2
  • Joined

  • Last visited

drew.sartorius's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. A while back I was having some issues with getting PXE boot to work. After about a week of working on it, we finally got everything up and running and we were able to image machines through PXE. A few days ago, the power went out in our server room and caused a bunch of issues. Now we cannot get PXE to work. I have tried completely removing everything and starting over, but it still does not work. Here is what I have done: -Uncheck PXE box from DP (WDS removed) -Reboot -Uncheck Distribute for PXE in x86 and x64 boot images -Install WDS (no additional setup) -Check PXE box in DP and check "Allow distribution to rspond" and "Enable unknown support" -Check Distribute for PXE in x86 and x64. I also noticed that the files that should be in SMSBOOT\x64 and \x86 were not there, so I copied them from the BOOT folder. When I boot up into PXE, it finds the server and the WDSNBP file, but gets stuck at Contacting Server: [sccm2012 server]........ In the event log, it says: failed to copy E:\RemoteInstall\SMSTempBootFiles\OKE00004\WINDOWS\Boot\EFI\bootmgfw.efi to E:\RemoteInstall\SMSBoot\x64\bootmgfw.efi InstallBootFilesForImage failed. 0x80070003 Warning: Failed to copy the needed boot binaries from the boot image E:\RemoteInstall\SMSImages\OKE00004\boot.OKE00004.wim Failed adding image E:\RemoteInstall\SMSImages\OKE00004\boot.OKE00004.wim. Will retry. The system cannot find the path specified. There is also a long list of warnings that keep saying: Warning: Matching Processor Architecture Boot Image (6) not found I have confirmed that the E:\RemoteInsall\SMSImages\OKE00004.wim file exists.
  2. We recently upgraded to SCCM 2012 and we are trying to figure out if it is possible/a good idea to put the SCCM client on virtualized machines that boot fresh from a single VHD file. We are using Citrix PVS 6.1 for about half of our computers. It would be really nice to have the client on those machines for inventory and remote control. With SCCM 2007, we decided to keep the client off the machines to prevent software from getting pushed out to those machines every time they boot, but with the ability to use different clients in 2012, would this be the way to go? Thanks for any insight!
×
×
  • Create New...