Problem completing OSD TS - winhttp
Hi all
I hope this hasn't been covered before - I did check through the forum but didn't fnd anything quite the same. I am having a problem with an OSD task sequence failing every time I run it. The task sequence runs as follows:
Capture Windows Settings
Capture Network Settings
Restart in Windows PE
Format and Partition Disk 0
Apply Operatin System
Apply Windows Settings
Apply Network Settings
Auto Apply Drivers
Setup Windows and Configmgr
The TS gets as far as Auto Apply Drivers and fails. When I check the status messages for the advertisement, I see the following:
The task sequence execution engine failed executing the action (Auto Apply Drivers) in the group (Install Operating System) with the error code 2147954402
Action output: e2 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,2052)
driverMatchRequestMessage.DoRequest( sResponseBody, true ), HRESULT=80072ee2 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\onlinedrivercatalog.cpp,428)
pDriverCatalog->match( deviceList, m_fpCallbackProc, m_pvCallbackData, matchResultMap ), HRESULT=80072ee2 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\driverinstaller.cpp,854)
pDriverInstaller->AutoInstallDrivers( pDriverCatalog, bBestMatch ), HRESULT=80072ee2 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\osddriverclient.cpp,286)
ProcessAutoProvision( pDriverInstaller, bBestMatch ), HRESULT=80072ee2 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\osddriverclient.cpp,415)
Exiting with return code 0x80072EE2
failed to receive response with winhttp; 80072ee2
failed to send the request
Failed to execute driver match request. Code 0x80072ee2
Failed to auto provision driver. Code 0x80072ee2
Failed to auto provision drivers. Code 0x80072ee2.
When I get back to the machines I can't log in - they haven't been joined to the domain, even though this is specified in "Apply Network Settings", and the local Administrator account is disabled even though it should be enabled during "Apply Windows Settings"
- neither of these tasks show any errors, no errors show up until the TS reaches Auto Apply Drivers.
Incidentally, I have an identical Task Sequence, minus the "Capture Windows Settings" and "Capture Network Settings" tasks, that I run from a USB stick and this works perfectly!
I'm pretty stuck with this... can anybody help, or tell me where to start troubleshooting!
Thanks in advance
Phil
May 10th, 2011 9:22am
Error code 80072ee2 = "The operation timed out"
Have you reviewed the smsts.log?
Are your driver packages on an accessible DP and are they above source version 1?Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
May 10th, 2011 10:42am
Thanks for replying.
The drivers are on the same DP as the .wim image that is being applied successfully, so as far as I can see there is no problem accessing the DP. I have just checked through all of the packages and they are all above source version 1.
I'm having trouble reviewing the smsts.log because I can't log on to the machines - the local admin password is not enabled for some reason, and the machines have not been added to the domain. Is there a log on the server that might give me a clue?
After reading a similar thread I have checked that the PE image has the correct NIC drivers, and this is confirmed by the fact that the TS can apply the OS image from the DP... also if I press F8 within the PE environment during the TS the machine has a
valid IP address... it's just when it tries to connect to look for drivers that the connection seems to time out and thows up this error.
May 10th, 2011 11:04am
Nothing on the server will really help.
You don't need to log into the deployed OS to check the log file though, just drop to the command-prompt before the error occurs and then check the log file. It'll be in x:\Windows\Temp and you can copy it to a share if you want. The system won't reboot
if you have the command-prompt open.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
May 10th, 2011 11:40am
I suggest you insert the network adapter driver for the special model of computers into the Windows 7 image. Consider using DISM to finish the work.
Add and Remove Drivers Offline
http://technet.microsoft.com/en-us/library/dd744355(WS.10).aspxPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
May 12th, 2011 3:10am
Philrm,
In your task sequences, try limiting the auto apply drivers step to only installing drivers for a few categories (hopefully you created categories when you imported your drivers!). Perhaps it is getting stuck on a particular driver, or installing an incorrect
network driver that disconnects it from the network. Please also check that you have specified a network access account in your computer client agent properties under your SCCM primary site settings.
For troubleshooting, make sure that you enable command prompt support under your boot image properties. That way when the TS errors, you can press F8 for a command prompt and check network connectivity such as IP, DNS and if you can map a drive to your DP
etc. You can also read log files from the command prompt by opening them with notepad (e.g. notepad smsts.log). Most of the log files that you need will be at c:\_SMSTaskSequence\Logs
Good luck!
Free Windows Admin Tool Kit Click here and download it now
May 13th, 2011 1:11am
Hi
Thanks for your replies. The F8 command prompt support is enabled, and I have checked that the PCs get valid IP information while in the PE environment, so it appears that the correct NIC drivers are installed.
I did set up categories when I imported drivers, but I confess I don't really get how they work, or if they can be used in my scenario. We have about 6 or 7 different PC models and I have imported drivers for all of them, and created a category for each
model. I use the same task sequence for imaging every machine though, so I would assume that if I specified a certain driver category within the task sequence, then machines not relevent to the specified category would fail to install drivers. Is there
a way to prompt for the relevant driver category to use during the task sequence? Or is best practice to use a different task sequence for each model of PC?
Thanks again
Phil
May 13th, 2011 5:54am
Without reviewing the log (and possibly posting relevant sections here), we're not going to be able to offer much.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
May 13th, 2011 9:17am