anyweb

which version of MDT are you using ?

it's the MDT Toolkit package, created when you create your first MDT Integrated task sequence in CM12

amongst the many errors (such as running the media twice and from different drives (d:,e:) I think the actual error is here can you tell us how you've prepared your client operating system ? does it have the configuration manager client installed ? if so what version >? can you try uninstalling it using the command below then reboot once done and try again ccmsetup /uninstall

try this one.

does the fix mentioned here work ? http://h20566.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/mostViewedDisplay?javax.portlet.begCacheTok=com.vignette.cachetoken&javax.portlet.endCacheTok=com.vignette.cachetoken&javax.portlet.prp_efb5c0793523e51970c8fa22b053ce01=wsrp-navigationalState%3DdocId%253Dmmr_kc-0108200-6%257CdocLocale%253Den_US&javax.portlet.tpst=efb5c0793523e51970c8fa22b053ce01&sp4ts.oid=5177961&ac.admitted=1402212562009.876444892.199480143

the 0x80008013 error is a return result failing to detect that the dependency was installed. E_FAIL_DEPENDENCY_NOT_RUN 0x80008013 http://technet.microsoft.com/en-us/library/bb632794.aspx what log are you generating when installing IE10 ? review it to see what dependancy you are missing...

well there are a few things to check, have any software updates been deployed to your clients ? are the Configuration Manager client agents working on your clients ? are the folders you showed above populated with updates ? what do your logs tell you on your Configuration Manager server...

Microsoft won't be delivering a new Start Menu for Windows 8 with its coming Windows 8.1 Update 2, after all. That recent change in plans comes courtesy of a couple of my sources who've had good track records on Windows information. Up until recently, Microsoft was hoping to make a new "Mini" Start Menu part of a second update to Windows 8.1. Windows 8.1 Update 2 was -- and still is, last I heard -- slated to arrive in August of this year. Microsoft's operating systems group has decided to hold off on delivering a Microsoft-developed Start Menu until Threshold, the next "major" release of Windows. Threshold, which may or may not ultimately be called Windows 9, is expected to be released in April 2015. I'm not clear whether the postponement is because the feature won't be fully baked in time, or if there's another reason for the change in plans. Microsoft still is moving full steam ahead with plans to try to make Windows 8.x more palatable and usable by those using mice and keyboards, as well as those used to previous Windows iterations. That strategy hasn't changed. The new Microsoft-developed Start Menu isn't going to be the same as the Windows XP/Vista/Windows 7 Start Menus; it's expected to offer some familiarity, but also integrate Windows 8's Metro-Style Start screen concept. (For those who prefer the more traditional Windows Start Menu experience, there are a few third-party-developed Start Menus for Windows 8 on the market including Start8 from Stardock and the Pokki Windows 8 Start Menu.) Terry Myerson, the Microsoft Executive Vice President who runs the unified operating system group, showed off a Start Menu mock-up during Microsoft's Build conference in early April, noting that Microsoft was going to bring a Start Menu back to Windows as part of the "next iteration" of the operating system. He didn't specify whether that meant Windows 8.1 Update 2 or Threshold, but based on leaks later in April, the internal plan was to make the Start Menu part of Update 2. Myerson also showed off in early April a new option to run Metro-Style/Windows Store apps to run in windows on the Desktop. I'm still hearing that windowed Metro-Style apps functionality remains a Threshold deliverable, not a Windows 8.1 Update 2 deliverable. So now what's going to be in Windows 8.1 Update 2? Will there be any user-interface changes or will it be more a vehicle for under-the-covers programming interface and reliability improvements? I don't know at this point. via Zdnet > http://www.zdnet.com/no-microsoft-start-menu-for-windows-8-until-2015-sources-7000030100/

you could use standalone media (usb or cd/dvd)

can you attach your smsts.log please so i can take a look

well you can prove that nic drivers are needed by opening a command prompt during OSD just before the setup windows and configmgr step, does it have an ip address, if so good, what about after the reboot after setup windows and configmgr, if it has no ip at this point then there's your problem as it's then that it tries to join the domain. why not use hyperV. no network drivers are needed at all for hyperV and it's free with Windows 8, Windows 8.1

it's no problem, you can always decide which index of the captured image (1 or 2) you wish to apply in the Apply Operating System step.

did you deploy both task sequences ?

yes you'll need drivers as Windows 7 requires lots of drivers on modern hardware, examine the SMSTS.log file to find out why your virtual machine is failing, could be nic driver related, also check c:\windows\debug\netsetup.log to see why domain join failed, a local dp would be advantageous, and you should use separate Apply Driver Package steps which are WMI based to target the correct hardware with the correct drivers, see this post. how can I target applications (and drivers) to specific hardware? target hardware

easy, use x86 to capture (scanstate) and x64 to restore (loadstate) in terms of USMT.

interesting i havn't seen this behaviour, right now i'm using the bitlocker frontend HTA (which incorporates this functionality), and i've not noticed any padlocks, can you show me a screenshot and are you using Configuration Manager 2012 or 2007 for this ?

same problem, i'll dig into it tomorrow and come back to you...

ok i got the same failure, i guess that was one of those things i didn't test, I've copied the CheckDriveLetter and set OSPART step to be the first step in the Backup Local group, then replaced all references to C: with %OSPART%, i'll test it now and report back in a few minutes.

i'll do a quick test of the backup functionality that you are using and come back to you.

what version of mdt are you using ? the error doesnt tell me much, i'd prefer to see the whole smsts.log so that i can see what has succeeded or failed prior to this.. is your computername being detected correctly by the webservice a few steps up ? that's where the name of the backup file is located and that could be the cause of your error

can you attach the smsts.log so i can see exactly where it's failing

raise a ticket with Microsoft CSS and see what they advise

where is the log file ? i dont see it anywhere

glad to here it !

I'm curious why you want to temporarily disable it, can you share the reason ? you could uninstall it using scepinstall.exe /u /s then reinstall it when needed.