Config Mangler

Yes you need ADK 10 and therefore WinPE 10 for the driver detection to work properly.

Had some problems with these. Needed a BIOS update to v1.05 as Win 7 (32-bit) OSD was constantly failing on reboot and was getting ACPI blue screens. This may not affect Win7 x64 but worth a try. I added all the HP softpaq KB's, USB and SSD drivers which didn't make any difference.

Jon, If you change the applicability then make sure you have updated the distribution point for those driver packages. If that still doesn't work then use applications or packages to install them. AMT drivers often don't want to play on any OS. Install them with an application later in the TS using the supplied setup.exe If the SD card driver is definitely Windows 10 but won't install, again use an application or package later in the TS using dpinst64 to point at the .INF file. I have at least 15 driver installs done like this in my Window 10 TS for ones that will not auto detect. @Alewoodrum - you're a bit stuck with no NIC driver in Windows. Are you sure it's the NDIS 6.5 driver you have?

As an update on the driver issue, I have found that the Windows 10 drivers get installed if I use driver packages. This is not a solution for us as we need the auto apply drivers phase to work. This won't affect most users but we use Nomad caching software so this means that every driver package would have to be cached locally before they could be installed by the PC. For 20 models of hardware this could add 5-10Gb and an hour of processing to the build.

alt-tab then :-) I installed the VMware tools during my task sequence. This might get you around the mouse problem.

Hi zeze. I could use silent installers later on however SCCM should be doing this for me! I'm already using Pnputil to add some of them which don't want to play nice. I have about 20 more models of hardware to integrate for Windows 10 and the first three are all failing to use the Windows 10 drivers so I don't want to get in to lots of additional packages. It seems to be drivers which have only Windows 10 listed in the description which don't install, so if a driver lists several OS's it will use it. I will log that support call tomorrow.

I am having problems too. SCCM is 2012R2 SP1 CU2 so fully up to date. I thought the driver install was working as most drivers are installed but they are not the W10 ones I have added. It is picking older drivers in preference to newer W10 drivers in some but not all cases. This is across 3 models of hardware so far, Surface 3, Lenovo X240 and HP 800 G1. All of these have manufacturer support for Windows 10. I am about to log a Premier call on this so will report back.

Once you upgrade ADK it upgrades WinPE to version 10. Once you have done that, the old PE images version 6.3.9600... are no longer editable and the drivers tab is removed. All you need to do is add your NIC drivers to the new WinPE 10 images labelled "Boot image (x64) WinPE 10" and x86 is you use that.

It's missing a lot of drivers so maybe not installing the NIC. From the larger SMSTS.log "Failed to find a suitable device driver for device 'Intel® PRO/1000 MT Network Connection" Is it joining the domain and do you have an IP address when it fails?

Still getting problems with driver installs in this environment on various models. It's now patched to CU2. If I include all drivers, I get a 1hr:15 minute delay before a reboot completes. If I remove the display and audio drivers there is no delay. At 12:53 it schedules a reboot, at 14:09 it actually happens. Any thoughts? SMS Client is not installed OSDSetupWindows 01/12/2015 12:53:01 1832 (0x0728) Unloading offline SOFTWARE registry hive OSDSetupWindows 01/12/2015 12:53:01 1832 (0x0728) Unloading offline SYSTEM registry hive OSDSetupWindows 01/12/2015 12:53:01 1832 (0x0728) Exiting with code 0x00000000 OSDSetupWindows 01/12/2015 12:53:01 1832 (0x0728) Process completed with exit code 0 TSManager 01/12/2015 12:53:01 1400 (0x0578) !--------------------------------------------------------------------------------------------! TSManager 01/12/2015 12:53:01 1400 (0x0578) Successfully completed the action (Setup Windows and Configuration Manager) with the exit win32 code 0 TSManager 01/12/2015 12:53:01 1400 (0x0578) MP server http://SPROMGT02.domain.com. Ports 80,443. CRL=false. TSManager 01/12/2015 12:53:01 1400 (0x0578) Setting authenticator TSManager 01/12/2015 12:53:01 1400 (0x0578) Set authenticator in transport TSManager 01/12/2015 12:53:01 1400 (0x0578) Sending StatusMessage TSManager 01/12/2015 12:53:01 1400 (0x0578) Setting message signatures. TSManager 01/12/2015 12:53:01 1400 (0x0578) Setting the authenticator. TSManager 01/12/2015 12:53:01 1400 (0x0578) CLibSMSMessageWinHttpTransport::Send: URL: SPROMGT02.domain.com:80 CCM_POST /ccm_system/request TSManager 01/12/2015 12:53:01 1400 (0x0578) Request was successful. TSManager 01/12/2015 12:53:01 1400 (0x0578) Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 01/12/2015 12:53:01 1400 (0x0578) Set a global environment variable _SMSTSLastActionSucceeded=true TSManager 01/12/2015 12:53:01 1400 (0x0578) Expand a string: %_SMSTSMDataPath%\Logs TSManager 01/12/2015 12:53:01 1400 (0x0578) Clear local default environment TSManager 01/12/2015 12:53:01 1400 (0x0578) The action (Setup Windows and Configuration Manager) requested a retry TSManager 01/12/2015 12:53:01 1400 (0x0578) Reboot to local harddisk TSManager 01/12/2015 12:53:01 1400 (0x0578) _OSDGinaIsConfigured variable set to TRUE TSManager 01/12/2015 12:53:01 1400 (0x0578) _SMSTSServiceStartType variable set to TSManager 01/12/2015 12:53:01 1400 (0x0578) Command line for extension .exe is "%1" %* TSManager 01/12/2015 12:53:01 1400 (0x0578) Set command line: "bcdedit.exe" TSManager 01/12/2015 12:53:01 1400 (0x0578) Executing command line: "bcdedit.exe" TSManager 01/12/2015 12:53:01 1400 (0x0578) Process completed with exit code 0 TSManager 01/12/2015 12:53:01 1400 (0x0578) Calling RebootSystem() TSManager 01/12/2015 12:53:01 1400 (0x0578) OSD type of task sequence. ignore the service window setting TSManager 01/12/2015 12:53:01 1400 (0x0578) Updated security on object C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca. TSManager 01/12/2015 12:53:01 1400 (0x0578) Updated security on object S:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca. TSManager 01/12/2015 12:53:01 1400 (0x0578) Updated security on object C:\_SMSTaskSequence. TSManager 01/12/2015 12:53:01 1400 (0x0578) Set a global environment variable _SMSTSNextInstructionPointer=20 TSManager 01/12/2015 12:53:01 1400 (0x0578) Set a TS execution environment variable _SMSTSNextInstructionPointer=20 TSManager 01/12/2015 12:53:01 1400 (0x0578) Set a global environment variable _SMSTSInstructionStackString=19 TSManager 01/12/2015 12:53:01 1400 (0x0578) Set a TS execution environment variable _SMSTSInstructionStackString=19 TSManager 01/12/2015 12:53:01 1400 (0x0578) Save the current environment block TSManager 01/12/2015 12:53:01 1400 (0x0578) Expand a string: %_SMSTSMDataPath%\Logs TSManager 01/12/2015 12:53:01 1400 (0x0578) ==============================[ OSDSetupHook.exe ]============================== OSDSetupHook 01/12/2015 06:04:16 2540 (0x09EC) Logging successfully initialized to C:\_SMSTaskSequence\Logs OSDSetupHook 01/12/2015 06:04:16 2540 (0x09EC) Executing task sequence OSDSetupHook 01/12/2015 06:04:16 2540 (0x09EC) !sVolumeID.empty(), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,476) OSDSetupHook 01/12/2015 06:04:16 2540 (0x09EC) Loading the Task Sequencing Environment from "C:\_SMSTaskSequence\TSEnv.dat". OSDSetupHook 01/12/2015 06:04:16 2540 (0x09EC) Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00350031004100300031003600420036002D0046003000440045002D0034003700350032002D0042003900370043002D003500340045003600460033003800360041003900310032007D00' OSDSetupHook 01/12/2015 06:04:16 2540 (0x09EC) Environment scope successfully created: Global\{51A016B6-F0DE-4752-B97C-54E6F386A912} OSDSetupHook 01/12/2015 06:04:16 2540 (0x09EC) Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00420041003300410033003900300030002D0043004100360044002D0034006100630031002D0038004300320038002D003500300037003300410046004300320032004200300033007D00' OSDSetupHook 01/12/2015 06:04:16 2540 (0x09EC) Environment scope successfully created: Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03} OSDSetupHook 01/12/2015 06:04:16 2540 (0x09EC) Reading logging settings from TS environment to set TS logging OSDSetupHook 01/12/2015 06:04:16 2540 (0x09EC) Setting LogMaxSize to 2097152 OSDSetupHook 01/12/2015 06:04:16 2540 (0x09EC) Setting LogMaxHistory to 2 OSDSetupHook 01/12/2015 06:04:16 2540 (0x09EC) Setting LogLevel to 0 OSDSetupHook 01/12/2015 06:04:16 2540 (0x09EC) Setting LogDebug to 1 OSDSetupHook 01/12/2015 06:04:16 2540 (0x09EC) Setting LogEnabled to 1 OSDSetupHook 01/12/2015 06:04:16 2540 (0x09EC) Saving existing desktop wallpaper settings. OSDSetupHook 01/12/2015 06:04:16 2540 (0x09EC) Setting desktop wallpaper. OSDSetupHook 01/12/2015 06:04:16 2540 (0x09EC) Debug shell is enabled OSDSetupHook 01/12/2015 06:04:16 2540 (0x09EC) Spawning system message loop thread. OSDSetupHook 01/12/2015 06:04:16 2540 (0x09EC) Waiting for system message loop to initialize. OSDSetupHook 01/12/2015 06:04:16 2540 (0x09EC) Signaling initialized event. OSDSetupHook 01/12/2015 06:04:16 2560 (0x0A00) Successfully enabled debug command shell support. OSDSetupHook 01/12/2015 06:04:16 2540 (0x09EC) Configuring local administrator account OSDSetupHook 01/12/2015 06:04:16 2540 (0x09EC) Entering system message loop. OSDSetupHook 01/12/2015 06:04:16 2560 (0x0A00) Enabling local administrator account OSDSetupHook 01/12/2015 06:04:16 2540 (0x09EC) Account was already enabled OSDSetupHook 01/12/2015 06:04:16 2540 (0x09EC) Re-assign all drive letters... OSDSetupHook 01/12/2015 06:04:16 2540 (0x09EC) Partition without driver letter: 0-1;0-3 OSDSetupHook 01/12/2015 06:04:16 2540 (0x09EC) Partition with driver letter: 0-2 OSDSetupHook 01/12/2015 06:04:16 2540 (0x09EC) Active partition is 0-1. New OS partition info: 0-2. OSDSetupHook 01/12/2015 06:04:16 2540 (0x09EC) Do not remove drive letter for new OS partition 0-2 OSDSetupHook 01/12/2015 06:04:16 2540 (0x09EC) Do not re-assign drive letter for new OS partition 0-2 OSDSetupHook 01/12/2015 06:04:16 2540 (0x09EC) Executing diskpart script: select volume D remove letter=D OSDSetupHook 01/12/2015 06:04:16 2540 (0x09EC) Command line for extension .exe is "%1" %* OSDSetupHook 01/12/2015 06:04:16 2540 (0x09EC) Set command line: "C:\WINDOWS\system32\diskpart.exe" /s "C:\WINDOWS\TEMP\DiskPartScript.txt" OSDSetupHook 01/12/2015 06:04:16 2540 (0x09EC) Executing command line: "C:\WINDOWS\system32\diskpart.exe" /s "C:\WINDOWS\TEMP\DiskPartScript.txt" OSDSetupHook 01/12/2015 06:04:16 2540 (0x09EC) Process completed with exit code 0 OSDSetupHook 01/12/2015 06:04:25 2540 (0x09EC) Installing SMS client OSDSetupHook 01/12/2015 06:04:25 2540 (0x09EC) Setting variable to indicate client installation attempted OSDSetupHook 01/12/2015 06:04:25 2540 (0x09EC) Clearing existing client configuration. OSDSetupHook 01/12/2015 06:04:25 2540 (0x09EC) Cleaning existing client certificates from SMS certificate store OSDSetupHook 01/12/2015 06:04:25 2540 (0x09EC) Restoring SMS client identity. OSDSetupHook 01/12/2015 06:04:25 2540 (0x09EC) The client certificates were not found in the environment. New certificates will be generated. OSDSetupHook 01/12/2015 06:04:25 2540 (0x09EC) Successfully restored the client identity. OSDSetupHook 01/12/2015 06:04:25 2540 (0x09EC) Using CRL: true OSDSetupHook 01/12/2015 06:04:25 2540 (0x09EC) Unable to read SMS client cert from environment. Not restoring SMS client cert. OSDSetupHook 01/12/2015 06:04:25 2540 (0x09EC) Succeeded loading resource DLL 'C:\WINDOWS\system32\_SMSOSDSetup\1033\TSRES.DLL' OSDSetupHook 01/12/2015 06:04:25 2540 (0x09EC) Command line for extension .exe is "%1" %* OSDSetupHook 01/12/2015 06:04:25 2540 (0x09EC) Set command line: "C:\WINDOWS\system32\_SMSOSDSetup\TsProgressUI.exe" /Register:WinPE OSDSetupHook 01/12/2015 06:04:25 2540 (0x09EC) Executing command line: "C:\WINDOWS\system32\_SMSOSDSetup\TsProgressUI.exe" /Register:WinPE OSDSetupHook 01/12/2015 06:04:25 2540 (0x09EC) ==========[ TsProgressUI started in process 2904 ]========== TsProgressUI 01/12/2015 06:04:25 2908 (0x0B5C) Command line: "C:\WINDOWS\system32\_SMSOSDSetup\TsProgressUI.exe" /Register:WinPE TsProgressUI 01/12/2015 06:04:25 2908 (0x0B5C) Registering COM classes TsProgressUI 01/12/2015 06:04:25 2908 (0x0B5C) sbModulePath = C:\WINDOWS\system32\_SMSOSDSetup\TsProgressUI.exe TsProgressUI 01/12/2015 06:04:25 2908 (0x0B5C) Unregistering class objects TsProgressUI 01/12/2015 06:04:25 2908 (0x0B5C) Shutdown complete. TsProgressUI 01/12/2015 06:04:25 2908 (0x0B5C) Process completed with exit code 0 OSDSetupHook 01/12/2015 06:04:25 2540 (0x09EC) Successfully registered TS Progress UI. OSDSetupHook 01/12/2015 06:04:25 2540 (0x09EC) Executing C:\_SMSTaskSequence\OSD\00100002\ccmsetup.exe /useronly /source:C:\_SMSTaskSequence\OSD\00100002 /config:MobileClient.TCF /status:608 OSDSetupHook 01/12/2015 06:04:26 2540 (0x09EC) Command line for extension .exe is "%1" %* OSDSetupHook 01/12/2015 06:04:26 2540 (0x09EC) Set command line: "C:\_SMSTaskSequence\OSD\00100002\ccmsetup.exe" /useronly /source:C:\_SMSTaskSequence\OSD\00100002 /config:MobileClient.TCF /status:608 OSDSetupHook 01/12/2015 06:04:26 2540 (0x09EC) Executing command line: "C:\_SMSTaskSequence\OSD\00100002\ccmsetup.exe" /useronly /source:C:\_SMSTaskSequence\OSD\00100002 /config:MobileClient.TCF /status:608 OSDSetupHook 01/12/2015 06:04:26 2540 (0x09EC) Process completed with exit code 0 OSDSetupHook 01/12/2015 14:09:17 2540 (0x09EC) Install succeeded. Blocking other instances of ccmsetup. OSDSetupHook 01/12/2015 14:09:17 2540 (0x09EC) Installed Client OSDSetupHook 01/12/2015 14:09:17 2540 (0x09EC) Backing up current global client logging settings that are read from registry OSDSetupHook 01/12/2015 14:09:17 2540 (0x09EC) Overwrote client global logging setting in registry with OSD logging settings. OSDSetupHook 01/12/2015 14:09:17 2540 (0x09EC) Start to cleanup TS policy OSDSetupHook 01/12/2015 14:09:17 2540 (0x09EC) TS Deleted 0 instances OSDSetupHook 01/12/2015 14:09:17 2540 (0x09EC) TS Policy cleanup done OSDSetupHook 01/12/2015 14:09:17 2540 (0x09EC) End TS policy cleanup OSDSetupHook 01/12/2015 14:09:17 2540 (0x09EC) Setting variable to indicate a client installation was done OSDSetupHook 01/12/2015 14:09:17 2540 (0x09EC) Registering the task sequence with the execution manager in the newly installed operating system. OSDSetupHook 01/12/2015 14:09:17 2540 (0x09EC) Active request handle is empty, registering with new active request handle. This is expected if the TS was started from a media/PXE. OSDSetupHook 01/12/2015 14:09:17 2540 (0x09EC) Saving the new active request handle for the task sequence: {CCFF3486-1331-4312-91F4-B11D80BF6114} OSDSetupHook 01/12/2015 14:09:17 2540 (0x09EC) Failed to create instance for IMTCTokenHandler interface, hr=0x80070005 OSDSetupHook 01/12/2015 14:09:17 2540 (0x09EC) Waiting for ccmexec process to start OSDSetupHook 01/12/2015 14:09:17 2540 (0x09EC) Failed to create instance for IMTCTokenHandler interface, hr=0x80070005 OSDSetupHook 01/12/2015 14:09:22 2540 (0x09EC) Waiting for ccmexec process to start OSDSetupHook 01/12/2015 14:09:22 2540 (0x09EC) CoCreateInstance succeeded OSDSetupHook 01/12/2015 14:09:28 2540 (0x09EC) Succesfully registered the tasksequence with the execution manager OSDSetupHook 01/12/2015 14:09:28 2540 (0x09EC) Command line for extension .exe is "%1" %* OSDSetupHook 01/12/2015 14:09:29 2540 (0x09EC) Set command line: "C:\WINDOWS\system32\_SMSOSDSetup\TsProgressUI.exe" /Unregister OSDSetupHook 01/12/2015 14:09:29 2540 (0x09EC) Executing command line: "C:\WINDOWS\system32\_SMSOSDSetup\TsProgressUI.exe" /Unregister OSDSetupHook 01/12/2015 14:09:29 2540 (0x09EC) ==========[ TsProgressUI started in process 1132 ]========== TsProgressUI 01/12/2015 14:09:29 3432 (0x0D68) Command line: "C:\WINDOWS\system32\_SMSOSDSetup\TsProgressUI.exe" /Unregister TsProgressUI 01/12/2015 14:09:29 3432 (0x0D68) Unregistering COM classes TsProgressUI 01/12/2015 14:09:29 3432 (0x0D68) Unregistering class objects TsProgressUI 01/12/2015 14:09:29 3432 (0x0D68) Shutdown complete. TsProgressUI 01/12/2015 14:09:29 3432 (0x0D68) Process completed with exit code 0 OSDSetupHook 01/12/2015 14:09:29 2540 (0x09EC)

I have exactly the same problem. It joins the domain, does all the drivers, downloads the SCCM client then sits at "Setup will continue after restarting your computer" for 1hr 15m, completes the reboot and continues the build. One model of hardware works fine - HP 800 G1 DM. A different form factor of HP 800 G1 does not work and a Lenovo T440 does not work. I was thinking drivers but they all install and two near identical models behave differently. This is SCCM 2012 R2 SP1 CU1. I'll post the smsts.log soon but there's not much to see beyond a big pause.

I think that's fixed in CU2 https://support.microsoft.com/en-us/kb/3100144

Sure you did an update content on the original SCCM client package? Mine was doing the same until I did that.

I got the patch method working this very morning :-) Command in the TS is: PATCH="%_SMSTSMDataPath%\OSD\00100002\x64\PATCH\configmgr2012ac-sp2r2sp1-kb3074857-x64.msp" I made a directory called PATCH referenced above and copied the MSP in there The path is under the client install folder - so for x64 this was: \\sccmserver\sms_site\client\x64\PATCH - obviously use your own server and site name here.......... Ensure you distribute the content for the patch under Applications/ Packages/ Configuration Manager updates The final missing link for me was to Update Content on the original SCCM client package - this has the Package ID 00100002 as in the command above. It will probably be the same reference for you so should work.

Premier support think this is by design but will escalate it.

I think it's related to Store access for Cortana in particular. If I give the machine unrestricted access to the Store the Start Menu is there for any user. We had a similar problem with Windows 8 but it didn't take out the start menu, maybe as there was none! As ever, it appears that MS just test with full access to everything. I'll take it further with MS as I have a call logged.

Have now updated production and still have the problem. If I log in as a basic user I get the start menu. Log in as admin and it's not there. Log I as the basic user again and it's gone. I tried the batch file linked to above but that didn't fix it. I'll cut down the task sequence to just the OS. After that it's time to log a Premier support call....

I had this problem with the preview builds and was surprised to see it carried over to the full release. None of the suggested fixes worked, but I'll try the services one you linked to. I have noticed that since installing 2012 R2 SP1 - CU1 in my LAB I haven't had the problem. I also installed KB3084568 + KB3089193 I'm about to install these in production so I'll see what happens.

Does the TPM have a Panasonic driver or Microsoft one? I found TPM commands / bitlocker doesn't work if you use a manufacturers driver, you have to let it use the Microsoft one.

Yeah I got past that. Add the Windows PE 5.0 x64 driver to your boot image and you will get an IP so you can start the TS. You also need to import the Windows 7 driver (NDIS 6.3) so it will continue the TS once it's out of PE and in Windows. http://support.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-x-series-laptops/thinkpad-x250/downloads/DS102312 If your SCCM server is 2008R2 you need to add two hotfixes or you will get errors importing them - see here: http://www.windows-noob.com/forums/index.php?/topic/12545-network-driver-issue/

Got past this with a new task sequence. We just installed R2 SP1 and the partitioning is different so could have been that. Means building my TS back up again but it's a start. Also answered my other question through the power of Google. You can't boot x64 and then install a x86 .WIM

I'm having problems with the X250 too building Windows 7 x64. Are you getting an IP address in WinPE? I added the Lenovo Win PE 5.0 driver to the x64 boot image and now I get an address. I can start the TS and it runs through "Applying Operating System" to 100% then fails with an unknown error. Logs aren't telling anything and I still have an IP at this point. Windows 8.1 x64 TS works fine on the same model so must be something fundamental with Windows 7. Does anyone know if it's possible to boot x64 but apply a x86 image? I actually want to install W7 x86 on this model, but have to boot x64 as there is no 32-bit PE NIC driver for this model. If I boot x64 and install the x86 Windows 7 image it fails at the very start of "Apply Operating System" so I suspect this is incompatible.

I can mix modes within the same domain so I can have Edge on www.bbc.co.uk/news and Document mode 5 on www.bbc.co.uk/sport Not quite what you're asking though you could test in a lab setup. Make sure you have the enterprise mode hotfixes installed: KB2929437 KB2956283

The ASIX88772 is the correct driver for the dock but you need to add it to the x64 boot image. Find the ASIX driver in the SCCM drivers list / right-click / Edit / boot images and add it to the x64 one.

Thanks. I do have the pre boot keyboard reg fix in place. It works and the drive is encrypted it just won't take the PIN. It only gives one attempt then offers recovery mode. If I clear the TPM it then accepts the pin, which is odd and I can then enter a wrong PIN as many times as I like and it doesn't lock out. Manage-bde status says it's all good. My understanding was that if you clear the TPM the drive is no longer encrypted with those keys so it shouldn't offer the PIN prompt after a TPM clear.