Jump to content


Established Members
  • Posts

  • Joined

  • Last visited

mcalliso's Achievements


Newbie (1/14)



  1. and, my logpath when I go into the registry and look is still not listing a full path to the SMSPXE.log file, just the filename itself and it is NOT being created. I've completely removed SCCM and started from scratch and it is still doing this once I install WDS via enabling PXE. This software is still buggy glad MS hasn't released it yet
  2. Awesome thanks! I thought though my bootfile name (according to my DHCP server) should should be SMSboot\x64\wdsnbp.com and not what you have? Am I mistaken?
  3. here's something interesting and i need help with. In the reg, under HKLM\SOFTWARE\Microsoft\CCM\Logging\SMSPXE the key 'LogPath' is set to 'SMSPXE.log' No full path, and no file can be located. If I change the path, say, to 'C:\Logs\SMSPXE.log', and then reboot the server OR simply restart the WDS service, it changes the path back to the original key. So, i cannot troubleshoot my Boot\BCD error because I have to log to reference. Any ideas?
  4. can you post the path to your boot image (you can blank out whatever you need to)? Can you also post what you are seeing at bootup on your virtual machine? That may help me solve my issue. Thanks!
  5. I am having a similar issue as well, only difference is my Status is a 0xc000000f error
  6. I've had this problem in the past as well. It seems it just takes time for it to show up in the collection. I'm using the same setup as you (VMWare ESX 4.1). Delete the VM, recreate it, note the MAC address and add it as a resources into the collection. Also, what I did was actually turn the (no OS installed) VM on and just let it sit after adding it to SCCM. I wonder if SCCM goes out and checks the network for that MAC address somehow and once it confirms it shows it in the list?
  7. OK that makes more sense. I'm still getting the 0xc000000f error at after pressing F12. I have removed passwords for PXE. Note of interest when I created my boot images and distribute them it creates a second WIM file in the \\share\SMS_XXX\OSD\boot\i386 and x64 folders. Is that normal? So, in the i386 folder I have boot.wim and boot.12300015.wim
  8. I do not have to press F12 twice (where does it say to do that?). I get the same screen in your quoted response, the 'Press F12 for Network boot'. After that I get the same error screen the other user posted but my status id is different (noted in previous post).
  9. I believe the user is since they posted a screenshot before that one. I'm interested in your response since this user is having similar (but not exact) issues that I too am having
  10. Thanks for the guide first off, it's very helpful. However, I am having issues with part of Part 7 of this guide. When I create my task sequence and deploy it to my test collection, I get the following error after pressing F12 to PXE boot my machine: Windows Boot Manager (Server IP :W.X.Y.Z.) WIndows Failed to start. A recent hardware or software change might be the cause. To fix the problem: 1. Insert your Windows installation disc and restart your computer. 2. Choose your language settings, and then click 'Next.' 3. Click "Repair your computer." If you do not have this disc, contact your system administrator or computer manufacturer for assistance. File: \Boot\BCD Status: 0xc000000f Info: An error occurred while attempting to read the boot configuration data I have no idea what is causing this and I believe I have things set up correctly. I have already tried removing the PXE password requirement but that did not resolve the issue.
  • Create New...