SCCM 2012 SP1 W7 OSD Issue

[Norphy]

I've got SCCM 2012 SP1 in a virtual environment. I'm setting it up to try and find the pitfalls and problems with it before I start to set it up in the main production environment. We'll be upgrading from 2007 R3 but that's by the bye right now.

I'm having a problem with OSD. I've got the DP which is PXE enabled set up on the same server as the MP. DHCP is on a seperate virtual server. I have a Windows 7 x64 Enterprise installer, a Windows 8 x64 Enterprise installer and a Windows 7 image created with SCCM 2007 last year assigned to it along with the ConfigMgr client package and the SCCM boot images. I've installed KB2801987 which resolves another problem.

I can deploy W8 using the installer just fine. I can install Windows 7 using the image just fine as well. However, when I attempt to deploy Windows 7 using the boot disk, it errors. The task sequence boots the machine, formats the hard disk, downloads the os installer and runs it, gets to the end of the installer where it wants to reboots then throws an error (0x80070002 IIRC). Examining the logs, it looks like it can't find the ConfigMgr client on the DP which I'm somewhat confused about considering that the W8 installer and the W7 image both work and install the client.

The host hardware is running HyperV on Windows Server 2012 so I wondered if it was a driver issue but adding the drivers made it worse (The installer decided they weren't signed so refused to install them). I tried it on a piece of physical hardware too, same result.

Any suggestions gratefully received.

Cheers!

[FN-GM]

Just so i have got this correct. You are not sending down an WIM file but your sending down a default Windows 7 Installer?

[Gatt]

Any chance we can see the SMSTS.log file from the OSD client ?

[Norphy]

Just so i have got this correct. You are not sending down an WIM file but your sending down a default Windows 7 Installer?

Correct. Installing from a WIM seems to work. However installing from a W7 installer doesn't.


Please find log attached. Renamed to .txt as this board won't let us attach .log files for some reason!

[FN-GM]

AH i have never done it from the installer. I always installed from a disc, setup the image and then captured it to a WIM file. Cant be much help sorry

[Gatt]

Thanks for the log file..

a few things are jumping out at me (mainly in the form of red bars..)

1) a whole section about it failing to find suitable drivers:

Failed to find a suitable device driver for device 'System board'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)Failed to find a suitable device driver for device 'Motherboard resources'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'Motherboard resources'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'System speaker'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'VMBUS\{32412632-86CB-44A2-9B5C-50D1417354F5}\{00000000-0000-8899-0000-000000000000}'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'Floppy disk drive'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'Volume Manager'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'Microsoft PS/2 Mouse'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'VMBUS\{0E0B6031-5213-4934-818B-38D90CED39DB}\{B6650FF7-33BC-4840-8048-E0676786F393}'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'Microsoft Hyper-V Virtual Machine Bus'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'Microsoft Basic Display Driver'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'System timer'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'VMBUS\{DA0A7802-E377-4AAC-8E77-0558EB1073F8}\{5620E0C7-8062-4DCE-AEB7-520C7EF76171}'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'Intel 21140-Based PCI Fast Ethernet Adapter (Emulated)'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'IDE Channel'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'IDE Channel'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'Microsoft Virtual Drive Enumerator'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'Microsoft Storage Spaces Controller'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'ACPI\PNP0501\1'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'ACPI\PNP0501\2'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'Microsoft Kernel Debug Network Adapter'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'Disk drive'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'Intel(R) 82371AB/EB PCI Bus Master IDE Controller'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'Generic volume'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'VMBUS\{F912AD6D-2B17-48EA-BD65-F927A61C7684}\{D34B2567-B9B6-42B9-8778-0A4EC0B955BF}'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'Intel 82371AB/EB PCI to ISA bridge (ISA mode)'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'RamDisk'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'Standard floppy disk controller'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'VMBUS\{9527E630-D0AE-497B-ADCE-E80AB0175CAF}\{2DD1CE17-079E-403C-B352-A1921EE207EE}'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'ACPI x64-based PC'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'HID-compliant mouse'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'PCI bus'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'Microsoft ACPI-Compliant System'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'System CMOS/real time clock'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'Microsoft Basic Render Driver'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'Programmable interrupt controller'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'Standard PS/2 Keyboard'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'ACPI Fixed Feature Button'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'Microsoft Hyper-V Input'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'Direct memory access controller'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'Intel Processor'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'ACPI\HYPER_V_GEN_COUNTER_V1\0'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'Microsoft Hyper-V SCSI Controller'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'Video Controller (VGA Compatible)'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
Failed to find a suitable device driver for device 'VMBUS\{57164F39-9115-4E78-AB55-382F3BD5422D}\{FD149E91-82E0-4A7D-AFA6-2A4166CBD7C0}'.    OSDDriverClient    23/01/2013 15:33:03    1840 (0x0730)
<snip>

Then near the bottom we are getting:

!sPackageLocation.empty(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,3348)    OSDSetupHook    23/01/2013 15:40:46    1328 (0x0530)Empty location for package: _SMSTSUSU00002    OSDSetupHook    23/01/2013 15:40:46    1328 (0x0530)
ResolveSource(pszSource, sSourceDirectory, dwFlags, 0, 0, 0), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,3221)    OSDSetupHook    23/01/2013 15:40:46    1328 (0x0530)
TS::Utility::ResolveSource(sClientPackageID, sClientPackagePath), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\osdgina\basesetuphook.cpp,1655)    OSDSetupHook    23/01/2013 15:40:46    1328 (0x0530)
Failed to resolve package source "USU00002"    OSDSetupHook    23/01/2013 15:40:46    1328 (0x0530)
Exiting ConfigureEx: 0x80070002    OSDSetupHook    23/01/2013 15:40:46    1328 (0x0530)
BaseSetupHook::configure(sWindowsDir), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\osdgina\osdsetuphook.cpp,292)    OSDSetupHook    23/01/2013 15:40:46    1328 (0x0530)
Failed to configure OSD setup hook (0x80070002)    OSDSetupHook    23/01/2013 15:40:46    1328 (0x0530)
Process completed with exit code 2147942402    OSDSetupWindows    23/01/2013 15:40:46    1872 (0x0750)
exitCode, HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\setupwindows\setupwindows.cpp,635)    OSDSetupWindows    23/01/2013 15:40:46    1872 (0x0750)
Configure hook failed with error code (80070002).    OSDSetupWindows    23/01/2013 15:40:46    1872 (0x0750)
this->configureGina(this->sysDir), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\setupwindows\setupwindows.cpp,780)    OSDSetupWindows    23/01/2013 15:40:46    1872 (0x0750)
this->installSetupHook(), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\setupwindows\setupwindows.cpp,452)    OSDSetupWindows    23/01/2013 15:40:46    1872 (0x0750)
Failed to install setup hook (80070002)    OSDSetupWindows    23/01/2013 15:40:46    1872 (0x0750)
setup.run(), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\setupwindows\setupwindows.cpp,1668)    OSDSetupWindows    23/01/2013 15:40:46    1872 (0x0750)
Exiting with code 0x80070002    OSDSetupWindows    23/01/2013 15:40:46    1872 (0x0750)
Process completed with exit code 2147942402    TSManager    23/01/2013 15:40:46    2020 (0x07E4)
!--------------------------------------------------------------------------------------------!    TSManager    23/01/2013 15:40:46    2020 (0x07E4)
Failed to run the action: Setup Windows and Configuration Manager. 
The system cannot find the file specified. (Error: 80070002; Source: Windows)    TSManager    23/01/2013 15:40:46    2020 (0x07E4)

Before it finally bombs out completely with

Failed to run the action: Setup Windows and Configuration Manager. The system cannot find the file specified. (Error: 80070002; Source: Windows)    TSManager    23/01/2013 15:40:46    2020 (0x07E4)
The execution of the group (Setup Operating System) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)    TSManager    23/01/2013 15:40:46    2020 (0x07E4)
Failed to run the last action: Setup Windows and Configuration Manager. Execution of task sequence failed.
The system cannot find the file specified. (Error: 80070002; Source: Windows)    TSManager    23/01/2013 15:40:46    2020 (0x07E4)

It looks like the client can connect to the network as it successfully find package USU00006 - which I suspect is Windows 7 itself, but then fails to even find USU00002

can you check that this is correctly published to the DP? try redistributing it

Software Library\Overview\Application Management\Packages
Data Source: \\Server.mydomain.com\SMS_xyz\Client
Distrib Settings: Automatically download content when packages are assigned to DP's

Also check its status under "\Monitoring\Overview\Distribution Status\Content Status\<Configuration Manager Client Package>" to make sure it is green and listed as "Content was distributed to the DP"

[Norphy]

You've come to the same conclusion as me, it can't find the ConfigMgr client. USU00002 is the client. It's definitely been distributed to the DP as it gets picked up when when you install W7 from a WIM or install Windows 8 from the installer.

The DP reports that it's been distributed successfully. I can't remove it and re-distribute it as the option is greyed out! I'll try the redistribute button again and see what happens. It's probably worth making a new package and telling the task sequence to use that too

Thanks for looking!

[Gatt]

Are you per chance deploying any ConfMgr Client hotfixes too?
I have found in the past that it fails if you try this..

[Norphy]

No, just the client so far.

I've just worked out what the problem is, it appears to be share permissions! It looks like WinPE is attempting to connect anonymously to the DP instead of using the network access account (which is the domain admin account ATM, it won't be in production!). Giving "everyone" read access to the SMSPKGC$ and SCCMContentLib$ share appears to fix it.

[Gatt]

Sodding permissions!

[Norphy]

Indeed! Quite why it was only the W7 installer that was complaining is a mystery but to be honest I don't care. It's just another thing I'll have to put into my deployment notes.