Any of the stock driver steps won't work for upgrade scenario. Your options are:
1. Use the inbox Windows class drivers. (It's technically an option...didn't say they're necessarily good options...) 2. Enable DynamicUpdate (DU) which should get the latest drivers from WU. This won't work if you're using SCCM to manage software updates, but we do provide an option in vNext upgrade step to temporarily send the client out to WU for DU, but that may not scale too well for enterprise consumption. 3. Specify /InstallDrivers parameter with the path and let setup find them itself. It is recursive. See https://msdn.microsoft.com/en-us/library/windows/hardware/dn938368.aspx for slightly more detail. a. This is likely your best bet with SCCM task sequence. NOTE: we integrate this with driver packages in the vNext integrated upgrade task sequence. b. While on that MSDN page also check out the MigrateDrivers parameter... 4. Run a driver installer during the task sequence in the Post-Processing group (once upgrade completes). Aaron From: [email protected] [mailto:[email protected]] On Behalf Of Michael Niehaus Sent: Monday, October 12, 2015 10:01 AM To: [email protected] Subject: RE: [MDT-OSD] Windows 10 in Place Upgrade It would be better to provide a folder of drivers to SETUP.EXE and let it handle it. There is another switch that you can use to specify the path to the folder. Thanks, -Michael From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Vann, Gerry Sent: Monday, October 12, 2015 7:56 AM To: [email protected]<mailto:[email protected]> Subject: RE: [MDT-OSD] Windows 10 in Place Upgrade Thank you for the response. I figured it out this morning. We still have the Altiris Dagent on our desktops for some legacy software that has not been moved to ConfigMan yet. The Dagent is blocking the execution of the SetupComplete.cmd. In fact if I attempted to copy the SetupCoplete.cmd to c:\windows\setup\scripts, as soon as the Dagent service started it would delete that file. I'm disabling that service in the PreSetup.ps1 file and enabling in the SetupComplete.ps1. Now on to drivers, got any good tips on injecting Windows 10 drivers post upgrade? I'm going to try the Apply Drivers step in my task sequence. If that doesn't work I was going to use DPinst.exe at least until vNext comes out. Thanks again, Gerry From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Michael Niehaus Sent: Friday, October 9, 2015 11:14 PM To: [email protected]<mailto:[email protected]> Subject: RE: [MDT-OSD] Windows 10 in Place Upgrade What SKU of Windows are you upgrading, and what media are you using? The switches as specified are correct; it's an enhancement in Windows 10 to be able to tell SETUP where to find the batch files to execute after the upgrade completes. There are some scenarios, e.g. OEM, where the batch files aren't called. In those cases, you should see a log entry in setupact.log to that effect. Thanks, -Michael From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Vann, Gerry Sent: Friday, October 9, 2015 3:34 PM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] Windows 10 in Place Upgrade Hey all, Probably like most of you I've been playing around with the Windows 10 in place upgrade task sequence found here http://blogs.technet.com/b/configmgrteam/archive/2015/06/16/revised-content-for-the-win10-in-place-upgrade-via-task-sequence-for-configmgr.aspx#pi168308=4 . The upgrade step never launches the SetupComplete.cmd file in the /PostOobe switch. So as a result no steps after the Upgrade Windows step every get executed because the SCCM client is disabled. Guess I should mention the SCCM client is disabled via a PS script ran in the PreSetup step. I've tried manually launching the SetupComplete.cmd file from the upgraded computer (path is %SystemDrive%\_vNextUpgrade\) and it works then finishes the task sequence. Here is the command line from the TS step: Setup.exe /Auto Upgrade /Quiet /NoReboot /DynamicUpdate Disable /PostOobe %SystemDrive%\_vNextUpgrade\setupcomplete.cmd /PostRollback %SystemDrive%\_vNextUpgrade I read a few articles stating the SetupComplete.cmd file had to located here %WINDIR%\Setup\Scripts\SetupComplete.cmd, but those were all for Vista and Windows 7. Not sure if this is a limitation and if it still exists. Looking over the comments in the above blog post I see a lot of people having the same issue so I thought I would put the questions to the experts here. I have been able to deploy Windows 10 as a wipe and load task sequence, just not an upgrade task sequence. Thanks, Gerry
