Jump to content


Established Members
  • Posts

  • Joined

  • Last visited

  • Days Won


SlcStan last won the day on November 10 2014

SlcStan had the most liked content!

SlcStan's Achievements


Newbie (1/14)



  1. The client is on the PC, yes - would you suggest removing it? Re the unknown entities - when I enter "unknown" into the "look for" box on the console, no results are reported back. Is this what you were asking? Thanks for the assistance, btw.
  2. BIOS clock is correct There is no duplicate entry for PC - I have went so far as to remove the PC from SCCM, Active Directory, DNS and the DHCP entry, then rejoin the domain, add to sccm using the OSD/Computer Association/MAC Address method. Still the same result - didn't see the OSD advert & not picking up the correct IP Address
  3. I am having lots of problems trying to run an oeprating system deployment to one particular PC using sccm osd with mdt The PC accepts the PXE advet, loads the boot-file, runs windows PE, then, after failing to find an advertised Task Sequence, reboots into normal windows XP. The smsts,log file has the following entries: Failed to download pxe variable file. Code(0x00000001) PxeGetPxeData failed with 0x80004005 When I press F8 as the PC is running Windows PE, and run ipconfig, the PC reports an ip address of 169.254.x.x (the subnet it is connected to should be 150.2.x.x) The network connectivity of the PC is fine - in XP, I can map drives, access the internet etc. The boot image has all the correct drivers loaded. What makes this really frustrating is that I can take a PC of the exact same model (lenovo M71), plug it into the same data-point, with the same OSD advert, and it will successfulyl run the OS deployment. It only seems to be this PC which is the issue. The problem is similar to that described in the forum/blog links below: http://www.windows-noob.com/forums/index.php?/topic/1644-osd-task-sequence-fails-after-installing-sccm-sp2/ http://blogs.technet.com/b/smsandmom/archive/2008/08/26/configmgr-2007-osd-deployment-errors-out-within-a-few-seconds-after-winpe-loads-and-then-automatically-reboots.aspx http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/939103e1-2850-4672-9676-0228dcf762ab I've tried pretty much everything suggested in these forums - restarting WDS service, refreshing the boot image on the distribution points, etc; the only thing I've not tried is uninstalling/reinstalling on WDS, which I'm reluctant to do as it works fine for all other PCs - it just seems to be the one unit which refuses to pick up a valid IP address from PXE. Any ideas what might be causing this....???? smsts.log file attached smsts.log
  4. I am having issues with my Task Sequence for deploying Windows 7 Ultimate to out Lenovo Laptops. The TS used has been working successfully; however, this is now failing with an error code of 0x80004005. Within the smsts.log, there are a number of error & warning lines, so I'm not sure exactly what the root cause of this failure is, however, near the beginning of the logfile, there is the following entry: Found network adapter "1x1 11b/g/n Wireless LAN PCI Express Half Mini Card Adapter" with IP Address I am wondering if this is what is ultimately causing the TS to fail; the main NIC card is an IntelĀ® 82579LM Gigabit Network card, connected via cable. Is this likely to be the root cause of the TS failure? Is there a way to "force" the TS to use the 82579LM card? smsts.log file attached Stan smsts-20121017-160511.log
  5. I am having difficulties running User State Migration to capture User State from XP SP3 for an upgrade to Windows 7; I have created the Computer Association, and created a simple Task Sequence with just 2 steps - Request State Store & Capture User State. After advertising this TS to the XP PC, it failed with message ID of 10018 & status of "Program rejected (wrong platform)". Note - the TS is configured with the "This Task Sequence can run on any Platform" option. I've also recreated the USMT package, as per instructions at the technet forum links below; this has made no difference - same error is generated http://social.technet.microsoft.com/Forums/en/configmgrosd/thread/a84df39d-dd55-4a88-a904-d046d358128c http://social.technet.microsoft.com/Forums/en/configmgrosd/thread/15d8aa7a-6774-49da-bc5a-d68c385ebbc6 Any ideas what might be causing this?
  6. Guys: I now have this working. The DHCP servers are configured to point to \smsboot\x64\wdsnbp.com However, this kept displaying an error: TFTP download \smsboot\x64\abortpxe.com PXEBoot aborted I found this link on another forum which seemed to do the trick: http://www.myitforum.com/forums/How-to-get-around-abortpxecom-issue-m186323.aspx the "clear last PXE advertisement" option seems to be a bit flaky. I deleted the TS advert, reset the "clear last PXE..." flag, then re-advertised the TS. The PC is now booting from PXE and successfully having Windows 7 deployed. Regards Stan
  7. Hi there. Looking for some advise regarding Windows 7 deployment & PXE Booting. Background - we are using sccm 2007 & mdt 2010, and are currently in the middle of a project to migrate our OS to Windows 7. We have a server (sccmbr01) which has been added as an sccm site-system, which contains the OS images & runs the WDS role; within sccm this is configured as a PXE Service Point. The server had been happily sitting on its own subnet, happily deploying OS images, and providing both DHCP & PXE services. However, Management have now, in their wisdom, decided to move this server onto the main ip subnet where our general server population are located. This still worked ok, as long as sccmbr01 was providing dhcp service, with the scope set to a single subnet unused by any other devices. Our problem at the moment is that we are looking to extend the OSD service - including PXE boot - throughout the organisation, so that we can perform "in situ" rebuilds & refreshes, etc. (estate - approx 5000 pcs, approx 200 subnets, many geographic locations etc). The Comms team want to configure this so that DHCP for PXE boot/OSD is provided by our regular domain DHCP servers - their argument is that if we extend the DHCP scopes provided by sccmbr01, the addresses will be used up by the general PC population, i.e., this will become just another regular DHCP server on the WAN. Comms have configured "ip helper" on the routers, etc; however, after several attempts, using different permutations, we have not been able to successfulyl PXE boot client. When sccmbr01 had dhcp active, the files/paths displayed after F12 network boot were as follows, in order of appearance \smsboot\x64\pxeboot.com \smsboot\boot.sdi \smsimages\smspkg\pr10022b\winpe.pr10022b.wim We have tried to configure the DHCP servers to point to the above files, without success. \smsboot\x64\pxeboot.com - launches "Windows Boot Manager" console, with the following error - "file - \bbot\bcd status - 0xc000000f info - an error occurred while attempting to read the boot configuration data" \smsboot\boot.sdi - displays error "too big to fit in memory" \smsimages\smspkg\pr10022b\winpe.pr10022b.wim - displays TFTP error When we leave DHCP unconfigured, using only IP Helper (this seems to be the recommended method), an error 53 (boot file not found) is displayed. Do you have any suggestions what we could try next, or something we may be missing? I found this thread which seems to be quite similar: http://www.windows-noob.com/forums/index.php?/topic/890-bootbcd-error/ Any suggestions would be gratefully sppreciated. Regards Stan
  • Create New...