Jump to content


Established Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Jin597

  • Rank
  1. I have multiple DPs in my environment, but one in particular seems to be having issues with OSD. Right at the very start of the Task Sequence, it calls to download MDT Toolkit and immediately fails (log snippets below). I have uninstalled the DP and reinstalled it a couple of times, but this DP just can't seem to get past the MDT Toolkit. I have even redistributed the MDT Toolkit numerous times. On my other DPs, which followed the same procedures for setup, do not have this issue. Does anyone have any ideas? What worries me is these lines in the logs: socket 'connect' failed; 80072724d sending with winhttp failed; 80072efd Download() failed. 80072efd. Failed to resolve the source for SMS PKGID=LBT000D3, hr=0x80070002 Install Software failed to run command line, hr=0x80070002 Failed to run the action: Use Toolkit Package. The system cannot find the file specified. (Error: 80070002; Source: Windows) The system does have an active IP and can access the DP, so I am not sure why these are failing.
  2. Yes, there was the default unattend file that was created during the MDT Task Sequence creation. I rebuild all packages and recreated the TS. This solved the issue.
  3. Hi Everyone, I've been stuck for the past few days. After upgrading SCCM 2012 to R2, I have been having issues with OSD. I recreated my Task Sequence after the update and recreated all dependencies (MDT Toolkit, USMT, CM Client, boot images, etc). The Task Sequence itself still follows the same flow as I had before (which was working). Now, after completing the "Setup Windows and ConfigMgr" TS, the computer reboots to OS (as it should by default), and then Windows stops during boot with the message: "Windows could not configure one or more system components. To install Windows, restart the computer and then restart the installation." As this is not in WinPE environment, I cannot F8 to see what happened here. Googling this error, I saw many people point to KMDF 1.11 not being in the base image. I checked my image and do have this in place, so this is not the culprit. I do not believe it to be driver related either, as I am using the same driver packs as I did previously which worked. I do not see any errors in SMSTS.log either. Anyone run into this problem or can provide some advice of what might be going on?
  4. First up, forgive me if I missed a post elsewhere. I have been searching around without much luck. I am deploying windows in an environment where I have various keyboard locales I saw Niall's various posts on doing this with an HTA, but as I really only need to collect the keyboard locale, I am not sure a full HTA is the way to go as I am trying to keep this as zero-touch as possible. So, my questions are: 1. Is there anyway to auto-detect the keyboard's locale and mapping during the WinPE phase (or other phases) 2. If #1 is not possible, is there a way that I can prompt for locale without an HTA? (my thought here is a VBscript that would popup during PE phase to get the input from user, then set OSDUILanguage and other variables accordingly based on response). I would prefer option #1 to keep it zero-touch, but if not, #2... and failing that, HTA or individual TS for the various systems. Thanks, Jonathan
  • Create New...