SMS&MOM : ConfigMgr

SQL Server 2005 SP3 is now supported for SMS 2003 and ConfigMgr 2007

J.C. Hornbeck — Tue, 06 Jan 2009 22:08:10 GMT

Just an FYI that I posted a note about SQL Server 2005 SP3 on our new ConfigurationMgr blog:

http://blogs.technet.com/configurationmgr/archive/2009/01/06/sql-server-2005-sp3-is-now-supported-for-sms-2003-and-configmgr-2007.aspx

Enjoy!

J.C. Hornbeck | Manageability Knowledge Engineer

ConfigMgr 2007: How to inventory mapped drives

J.C. Hornbeck — Fri, 19 Dec 2008 02:20:05 GMT

I was asked a few days ago if ConfigMgr or SMS could inventory mapped drives, and while the answer is yes we don't do it by default. In effect we report the logical disk but not mapped drives.

In order to inventory mapped drives we first need to extend the sms_def.mof. Mapped drives are in the user context so we need to gather this information from every user. We also need a repository to collect this information; this would be a class in WMI.

So here is how we accomplish this. Add the following lines to the end of the SMS_def.mof:

//======================================================================================

// Mapped Drives Reporting

// Note: The class is created using a advertised vbscript (mapdrives.vbs)

//======================================================================================

#pragma namespace("\\\\.\\root\\CIMV2\\SMS")

#pragma deleteclass("CX_mappeddrives", NOFAIL)

[

SMS_Report(TRUE),

SMS_Group_Name("CX Mapped Drives"),

SMS_Class_ID("CX_mappeddrives"),

Namespace("\\\\\\\\.\\\\root\\\\cimv2")]

class CX_mappeddrives : SMS_Class_Template

{

[SMS_Report(TRUE), Key]

string user;

[SMS_Report(TRUE), key]

string Letter;

[SMS_Report(TRUE), Key]

string Path;

};

// <:[-<>>>>>>>>>>>>>>>>>>>>>>>>>>END>>-Mapped drives Reporting-<<END<<<<<<<<<<<<<<<<<<<<<<<>-]:>

This will extend the mof and create the necessary stored procedures and tables in the SMS database. After compiling the mof on the site server restart the SMS_executive and the component manager. We will need to compile this sms_def.mof on the clients as well to extend WMI and create the repository to store the mapped drive information. You can do this by a logon script or advertisement.

We now need to gather the mapped drive information. Here is the script to do so. I named it mapdrives.vbs

' This code is provided "as-is" and not supported by Microsoft

option explicit

on error resume next

Dim wbemCimtypeSint16

Dim wbemCimtypeSint32

Dim wbemCimtypeReal32

Dim wbemCimtypeReal64

Dim wbemCimtypeString

Dim wbemCimtypeBoolean

Dim wbemCimtypeObject

Dim wbemCimtypeSint8

Dim wbemCimtypeUint8

Dim wbemCimtypeUint16

Dim wbemCimtypeUint32

Dim wbemCimtypeSint64

Dim wbemCimtypeUint64

Dim wbemCimtypeDateTime

Dim wbemCimtypeReference

Dim wbemCimtypeChar16

wbemCimtypeSint16 = 2

wbemCimtypeSint32 = 3

wbemCimtypeReal32 = 4

wbemCimtypeReal64 = 5

wbemCimtypeString = 8

wbemCimtypeBoolean = 11

wbemCimtypeObject = 13

wbemCimtypeSint8 = 16

wbemCimtypeUint8 = 17

wbemCimtypeUint16 = 18

wbemCimtypeUint32 = 19

wbemCimtypeSint64 = 20

wbemCimtypeUint64 = 21

wbemCimtypeDateTime = 101

wbemCimtypeReference = 102

wbemCimtypeChar16 = 103

Dim oLocation, oServices, oInstances, oObject, oDataObject, oNewObject, oRptObject

Set oLocation = CreateObject("WbemScripting.SWbemLocator")

'Remove class

Set oServices = oLocation.ConnectServer(, "root\cimv2")

set oNewObject = oServices.Get("CX_mappeddrives")

oNewObject.Delete_

'Create data class structure

Set oServices = oLocation.ConnectServer(, "root\cimv2")

Set oDataObject = oServices.Get

oDataObject.Path_.Class = "CX_mappeddrives"

oDataObject.Properties_.add "Letter", wbemCimtypeString

oDataObject.Properties_.add "Path", wbemCimtypeString

oDataObject.Properties_.add "user", wbemCimtypeString

oDataObject.Properties_("Letter").Qualifiers_.add "key", True

oDataObject.Properties_("Path").Qualifiers_.add "key", True

oDataObject.Properties_("user").Qualifiers_.add "key", True

oDataObject.Put_

'Add Instances to data class

Set oServices = oLocation.ConnectServer(, "root\cimv2")

Dim sComputerName, sUsername, sQuery

Set oInstances = oServices.ExecQuery("SELECT UserName FROM Win32_ComputerSystem")

for each oObject in oInstances

sUserName = oObject.UserName

next

sQuery = "select * from win32_MappedLogicalDisk"

Set oInstances = oServices.ExecQuery(sQuery)

for each oObject in oInstances

Set oNewObject = oServices.Get("CX_mappeddrives").SpawnInstance_

oNewObject.Letter = oObject.DeviceID

oNewObject.Path = oObject.ProviderName

oNewObject.user = sUserName

oNewObject.Put_

next

'--------------------------------- FUNCTIONS -----------------------------------

Function ParseComp(Stg,Pat)

Dim tmpCS, p, q

tmpCS = ""

p = 1

Do while p < len(Stg)

if mid(Stg,p,len(Pat)) = Pat Then

q = p + len(Pat) + 1

Do while mid(Stg,q,1) <> chr(34) and q < len(Stg)

tmpCS = tmpCS + mid(Stg,q,1)

q = q + 1

Loop

Exit do

Else

p = p + 1

end if

Loop

ParseComp = tmpCS

End Function

Now this script can be executed through a logon script.

A few gotchas on the whole process is that the user has to have write access to root/CIMV2 class. We can over come this by explicitly adding the domain user group to CIMV2 using the MMC or you can use a free tool called wmisecurity.exe(http://www.codeproject.com/KB/system/WmiSecurity.aspx )

Once the script is run the class would get populated with the letter and path and user who ran the script.

Then when hardware inventory is run it will populate information in the database that can be used later to create reports. To verify that it worked fine verify Resource explorer for one machine. It will have a new class named cx_mappeddrives:

Here is a sample report you can use to view the data:

select v_R_System.Name0,v_GS_Cx_Mapped_Drives0.Letter0, v_GS_Cx_Mapped_Drives0.Path0, v_GS_Cx_Mapped_Drives0.user0 from v_R_System inner join v_GS_Cx_Mapped_Drives0 on v_GS_Cx_Mapped_Drives0.ResourceId = v_R_System.ResourceId where v_GS_Cx_Mapped_Drives0.Letter0 like '%' and v_GS_Cx_Mapped_Drives0.Path0 like '%' and v_GS_Cx_Mapped_Drives0.user0 like '%'

The report will look like this:

A good use of this script is to determine a valid drive letter for a new server share or what are your clients mapping to.

I hope these steps help to gather information and special thanks to Jason Alanis for creating the vbs script.

Alvin Morales - Senior Support Engineer

New Knowledge Base articles for 12-7 through 12-13

J.C. Hornbeck — Mon, 15 Dec 2008 19:40:00 GMT

For the week of 12-7 through 12-13 we had three new Knowledge Base articles: Two on OpsMgr 2007 and one on ConfigMgr 2007. Links and titles are below:

========

http://support.microsoft.com/?kbid=957135
You cannot change the alert resolution state of any alert in the Active Alerts view in System Center Operations Manager 2007 Service Pack 1
Sys Center Ops Mgr 2007

http://support.microsoft.com/?kbid=955955
A task sequence that contains many packages may take longer to run after you install System Center Configuration Manager 2007 Service Pack 1 or hotfix 949225
Sys Center Config Manager 2007

http://support.microsoft.com/?kbid=958170
Description of System Center Operations Manager 2007 Service Pack 1 support for Microsoft SQL Server 2008
Sys Center Ops Mgr 2007

========

Enjoy!

J.C. Hornbeck | Manageability Knowledge Engineer

ConfigMgr 2007: The Transfer Site Settings Wizard fails to transfer client installation methods

J.C. Hornbeck — Fri, 12 Dec 2008 01:05:04 GMT

Here's one that's probably going to be relatively uncommon but I came across it the other day and thought it would be worth a mention here:

========

Issue: The Transfer Site Settings Wizard in System Center Configuration Manager 2007 SP1 fails to transfer client installation methods from one secondary site to another secondary site. The error message reported is:

(Reason:Skipping the setting because it is unique to a primary site and target site <sitecode> is secondary.)

This error comes up for all settings:

General
   System types (Servers, Workstations, Domain controllers)
   Enable client push installation to site systems
   Enable client push installation to assigned resources

Other
Client push installation accounts
Installation properties

Software Update Point Client Installation
Enable Software Update Point Client Installation

Cause: This is a known issue with the wizard.

Resolution: To work around this issue, after transferring all of the settings from one secondary site to another secondary site via the Transfer Site Settings Wizard, simply configure the “Client Push Installation Properties” on the site manually.

========

J.C. Hornbeck | Manageability Knowledge Engineer

ConfigMgr 2007: New Product Feature Quizzes for your enjoyment

J.C. Hornbeck — Thu, 11 Dec 2008 17:10:54 GMT

Looks like the System Center Configuration Manager 2007 User Assistance (UA) team has created a set of quizzes to help you assess your understanding of the dependencies and requirements for key features of Configuration Manager 2007. Once you complete these quizzes you'll no longer have to suffer the embarrassment of having nothing to contribute when party or bar conversation turns to ConfigMgr prerequisites. If you're a sucker for quizzes like I am then this should provide hours of lunchtime fun (and education) for you and your colleagues:

========

The System Center Configuration Manager 2007 User Assistance team has created a set of quizzes to help you assess your understanding of the dependencies and requirements for key features of Configuration Manager. These quizzes help to raise your level of awareness of the some of the nuances of these features before you configure and use them. They can also be used to help train other Configuration Manager administrators within your organization. Each quiz consists of 10 questions that can be answered Yes or No. Regardless of your answer, the quiz will display the correct information, and include one or more links to the corresponding related content located in the Configuration Manager 2007 Documentation Library located on the Configuration Manager TechCenter. This new version of the quiz application is built using Microsoft Silverlight to provide a more interactive experience.

The following quizzes are available:
Configuration Manager 2007 Client Installation Quiz
Configuration Manager 2007 Client Management Quiz
Configuration Manager 2007 Client Site Assignment Quiz
Configuration Manager 2007 Desired Configuration Management Quiz
Configuration Manager 2007 Internet-Based Client Management Quiz
Configuration Manager 2007 Native Mode Quiz
Configuration Manager 2007 Network Access Protection Quiz
Configuration Manager 2007 Wake On LAN Quiz
Configuration Manager 2007 Software Updates Operations Quiz
Configuration Manager 2007 OSDeployment Quiz
Configuration Manager 2007 What’s New Quiz
Configuration Manager 2007 Software Updates Configuration Quiz
Configuration Manager 2007 Mobile Device Management Quiz
Configuration Manager 2007 Fundamentals Quiz
Configuration Manager 2007 Client Roaming Quiz
Configuration Manager 2007 Software Updates Interop Quiz
Configuration Manager 2007 Setup Quiz
Configuration Manager 2007 Software Distribution Quiz
Configuration Manager 2007 Service Pack 1 Quiz
Configuration Manager 2007 R2 Quiz

For more information and to download the quizzes visit http://www.microsoft.com/downloads/details.aspx?FamilyID=b9fb478a-ec98-47f2-b31e-57443a8ae88f&DisplayLang=en.

J.C. Hornbeck | Manageability Knowledge Engineer

ConfigMgr 2007: Task Sequence may fail to run with error code 0x80072ee7

J.C. Hornbeck — Tue, 09 Dec 2008 16:38:56 GMT

Here's another neat tip from Clifton Hughes in our Irving, Texas site. If you're PXE booting machines and they're throwing 0x80072ee7 errors along with getting APIPA addresses then you might try turning on portfast if you're using a Cisco Spanning Tree Protocol (STP) enabled switch to see if that helps:

========

Issue: When attempting to PXE Boot and install an Operating System Image with System Center Configuration Manager 2007, the Task Sequence may error out and reboot the machine. The SMSTS.LOG files may show error code 0x80072ee7 that points to a name resolution and/or networking issue. Additionally, you may notice that WINPE boots and gets an IP address from the DHCP server initially, however, once it gets to the Graphical User Interface portion of WINPE and try and run the Task Sequence it reverts to an Automatic Private IP Address (APIPA) of 169.354.x.x.

Note: If you use Task Sequence Boot Media and manually configure a static IP address and subnet mask, etc. then the Task Sequence runs as expected.

Cause: This can occur if portfast is not enabled on your SPT enable Cisco switch. If portfast is not enabled then the port using STP may remain in blocking mode long enough to prevent the client computer from communicating over the network.

Resolution: To resolve this issue you can turn on "spanning tree portfast enable" on the Cisco switch. For more information on this feature contact your switch manufacturer or see the following article on Cisco.com's website:

http://www.cisco.com/en/US/tech/tk648/tk361/technologies_tech_note09186a00800f0804.shtml

========

Thanks Clifton! Personally I've only seen this feature on Cisco switches but I image there are others out there using SPT that have a similar feature as well. I guess the ultimate takeaway is that if you're seeing problems that may be networking related and you're using Spanning Tree on a directly connected switch you might investigate the options to force that port online immediately.

J.C. Hornbeck | Manageability Knowledge Engineer

New and updated Knowledge Base articles for 11-23 through 11-29

J.C. Hornbeck — Wed, 03 Dec 2008 16:35:40 GMT

For the week of 11-23 through 11-29 we had five updated and two new Knowledge Base articles on everything from SMS 2.0 to Configuration Manager 2007. Links and titles are below:

========

Sys Mgmt Svr 2.0 SP2 EN
273476 - SMS: Buffer Overrun Problem in Several Network Monitor Parsers
Published - Updated

Sys Mgmt Svr Ent Ed 2003 EN
830019 - "Unable to get scan program path - verify scan tool package and program name in Scan.ini is correct" error message is sent to Systems Management Server 2003 or Systems Management Server 2.0 Service Pack 5 clients
Published - Updated

Sys Mgmt Svr Ent Ed 2003 EN
886060 - You receive a "Failed to download" error message when you install Systems Management Server (SMS) 2003 Scan Tools
Published - Updated

Sys Mgmt Svr Ent Ed 2003 EN
273734 - How to set up unattended installation scripts in SMS
Published - Updated

MOM Ops Mgr Serv Ent Ed 2005 EN
924043 - Active Directory Management Pack reports contain incorrect data after you install Multiple Management Group Rollup Solution Accelerator in a Microsoft Operations Manager 2005 environment
Published - Updated

MOM Ops Mgr Serv Ent Ed 2005 EN
957559 - Support policy for running Microsoft Operations Manager 2005 Service Pack 1 on hardware virtualization software
Published - New

Sys Center Config Mnger 2007 AL
958021 - Error message in the Configuration Manager console when you create a new task sequence: "The task sequence cannot be created"
Published - New

========

Enjoy!

J.C. Hornbeck | Manageability Knowledge Engineer

ConfigMgr 2007: WUAHandler.log - Failed to Add Update Source for WUAgent - Error = 0x80040692

J.C. Hornbeck — Wed, 03 Dec 2008 00:46:25 GMT

Here's a great tip on an issue you may run into if your using WSUS and ConfigMgr 2007 for updates and defining settings via a Group Policy. This one comes from Anjana Kaku Tyagi, a Support Engineer in our Manageability group:

========

Issue: While trying to configure Software Update Point in SCCM we get following error in WUAHandler.log

*******************************************************************************
Its a WSUS Update Source type ({63897A13-E330-463A-B09E-101151D25935}), adding it.
Enabling WUA Managed server policy to use server: :8530">:8530">http://<server>:8530
Waiting for 2 mins for Group Policy to notify of WUA policy change...
Group policy settings were overwritten by a higher authority (Domain Controller) to: Server ">">http://<server> and Policy ENABLED
Failed to Add Update Source for WUAgent of type (2) and id ({63897A13-E330-463A-B09E-101151D25935}). Error = 0x80040692.
*******************************************************************************

Cause: This can happen when there is a Group policy set in the domain that is managing updates and patching machines in the domain.

Resolution: We have two options for resolving this issue:

1. Remove the group policy at the domain level

2. Use the same WSUS server as the Software Update Point for the SCCM as well

In this particular case we opted for the second workaround: To configure the WSUS server and the software update point server to be the same server with the same port number as well so that both the group policy and the SCCM use the same server as the update point. To do this follow these steps:

1. Configure the software update point to use a particular server and port #

2. Configure the group policy to use the same port and server name for the updates to be distributed.

a. We can do the same by configuring the policy “Specify intranet Microsoft update service location” at Computer Configuration -> Administrative Templates -> Windows Components -> Windows Update to the same server and port as used by SCCM

or

b. Re-configure the group policy, such that the Configuration Manager clients are not assigned part of the container that has Active Directory Group Policy object that specifies a WSUS server other than their active software update point

For more information please refer to Troubleshooting Group Policy Configuration for Software Updates

Here's a snippet from the above article:

"The software updates feature automatically configures a local Group Policy setting for the Configuration Manager 2007 client so that it is configured with the software update point source location and port number. Both the server name and port number is required for the software updates client to find the software update point. If an Active Directory Group Policy setting is applied to computers for software update point client installation, this overrides the local Group Policy setting. Unless the value of the setting is exactly the same (server name and port), this causes the Configuration Manager 2007 software updates feature to fail on the client."

========

Thanks Anjana!

J.C. Hornbeck | Manageability Knowledge Engineer

New and updated Knowledge Base articles for 11-16 through 11-22

J.C. Hornbeck — Tue, 02 Dec 2008 17:18:35 GMT

Sorry for the delay in posting the new KB's but I took a couple days for Thanksgiving and I'm just now getting caught back up. For the week of 11-16 through 11-22 we had twelve updated and four new Knowledge Base articles on everything from SMS 2.0 to Mobile Device Manager 2008. Links and titles are below:

========

Sys Mgmt Svr 2.0 SP2 EN
233389 - SMS: Cannot Communicate with NetWare 5 Servers
Published - Updated

Sys Mgmt Svr 2.0 SP2 EN
269345 - Systems Management Server 2.0 technical resources
Published - Updated

Sys Mgmt Svr 2.0 SP2 EN
297857 - SMS: French SMS 2.0 SP3 Contains an Incorrect Ccm.dll File
Published - Updated

Sys Mgmt Svr 2.0 SP2 EN
231489 - Using Wildcard with Install File Script Item Forces Restart
Published - Updated

Sys Mgmt Svr 2.0 SP2 EN
281829 - SMS: How to Obtain and Install Systems Management Server 2.0 Service Pack 3
Published - Updated

Sys Mgmt Svr 2.0 SP2 EN
295035 - SMS: Charting in the Web Reporting Tool Requires that Office Web Components Run Locally
Published - Updated

Sys Mgmt Svr 2.0 SP2 EN
311457 - SMS: How to Obtain and Install Systems Management Server 2.0 Service Pack 4
Published - Updated

MOM Operations Mgr Base 2000 EN
300304 - Microsoft Operations Manager Reporting Logs Event 1025 With Unregistered Event Source
Published - Updated

MOM Operations Mgr Base 2000 EN
297604 - How to manually configure IIS 4.0 to use the Web console server in MOM
Published - Updated

MOM Operations Mgr Base 2000 EN
297771 - How to move a MOM 2000 OnePoint database to a new location
Published - Updated

SMS Installer
192498 - SMS: Repackage of Netscape Communicator 4.03 Fails to Show Icons
Published - Updated

Sys Center Operation Mgr 2007 EN
957565 - You cannot reinstall the Microsoft System Center Operations Manager 2007 management server role on a computer on which the role has been installed and removed
Published - New

Sys Center Config Mnger 2007 AL
955842 - The System Center Configuration Manager 2007 Service Pack 1 hardware inventory may recognize an x64-based client as an x86-based client
Published - New

Sys Center Config Mnger 2007 AL
958808 - User data from the USMT may be deleted unexpectedly by the task sequence engine during the operating system deployment process in System Center Configuration Manager 2007 SP1
Published - New

Sys Center Config Mnger 2007 AL
957325 - The Inventory Data Loader component cannot process hardware inventory data from System Center Configuration Manager 2007 Service Pack 1 clients if one or more properties contain more than 256 characters in the NOIDMIF files
Published - New

Sys Ctr Mobile Dvc Mgr 2008 EN
951840 - Attempts to validate Windows Mobile device certificates and to authenticate System Center Mobile Device Manager 2008 fail
Published - Updated

========

Enjoy!

J.C. Hornbeck | Manageability Knowledge Engineer

ConfigMgr 2007: OSD Task Sequence fails to join the PC to the domain during Windows setup

J.C. Hornbeck — Mon, 01 Dec 2008 17:57:00 GMT

I'm sure you all noticed a remarkable lack of activity over the past week but I'll be cranking things up again very soon. I've been out since November 20th on a much needed vacation to celebrate Thanksgiving with friends and family but I'm back in the office now and working to get caught up. It was great taking a few days off as it gave me the chance to get caught up on a few things around the house and spend some time with the wife and kids, but at the same time I'm excited to get back and see what's new since I was out and start posting again on all the cool things we're up to.

To start things off, here's a tip from long time contributor Frank Rojas on an issue you may see when you try to join your machines to the domain during an OS Deployment:

========

Issue: When running a SCCM 2007 OSD Task Sequence deployment to a PC, the PC will be successfully download the image, however when it runs through Windows Setup, the PC will eventually fail to join the domain and the Task Sequence will fail. Inspecting the "Apply Network Settings" task in the Task Sequence shows that all settings and accounts being used in the task are correct.

Looking at the SMSTS.log, the following error message will be repeat throughout the log:

Sending StatusMessage
Formatted header:
<Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>1dc5ca47-2e4e-42ef-9c32-231959eb878e</SourceID><SourceHost/><TargetAddress>mp:[http]MP_StatusManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2008-11-03T21:10:05Z</SentTime><Protocol>http</Protocol><Body Type="ByteRange" Offset="0" Length="2070"/><Hooks/><Payload Type="inline"/><TargetHost/><TargetEndpoint>StatusReceiver</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg>

CLibSMSMessageWinHttpTransport::Send: URL: <MP_Server>:80 CCM_POST /ccm_system/request
Error. Received 0x80072ee7 from WinHttpSendRequest.
unknown host (gethostbyname failed)
hr, HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,7714)
sending with winhttp failed; 80072ee7
Will retry in 5 second(s)
Retrying...
CLibSMSMessageWinHttpTransport::Send: URL: <MP_Server>:80 CCM_POST /ccm_system/request
Error. Received 0x80072ee7 from WinHttpSendRequest.
unknown host (gethostbyname failed)
hr, HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,7714)
sending with winhttp failed; 80072ee7
Will retry in 10 second(s)
Retrying...
CLibSMSMessageWinHttpTransport::Send: URL: <MP_Server>:80 CCM_POST /ccm_system/request
Error. Received 0x80072ee7 from WinHttpSendRequest.
unknown host (gethostbyname failed)
hr, HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,7714)
sending with winhttp failed; 80072ee7
Will retry in 22 second(s)
Retrying...
CLibSMSMessageWinHttpTransport::Send: URL: <MP_Server>:80 CCM_POST /ccm_system/request
Error. Received 0x80072ee7 from WinHttpSendRequest.
unknown host (gethostbyname failed)
hr, HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,7714)
sending with winhttp failed; 80072ee7
Will retry in 45 second(s)
Retrying...
CLibSMSMessageWinHttpTransport::Send: URL: <MP_Server>:80 CCM_POST /ccm_system/request
Error. Received 0x80072ee7 from WinHttpSendRequest.
unknown host (gethostbyname failed)
hr, HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,7714)
sending with winhttp failed; 80072ee7
End of retries
Send (pReply, nReplySize), HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,2052)
failed to send the request
DoRequest (sReply, false), HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,3835)
Failed to send status message (80072ee7)
smStatusMessage.Send(), HRESULT=80072ee7 (e:\nts_sms_fre\sms\client\tasksequence\executionengine\utility.cxx,529)

Cause: This is caused by a missing NIC driver in the Windows installation. Either the NIC driver was missing or not available during the driver injection (Apply Device Drivers, Auto Apply Drivers, or Apply Driver Package tasks) of the Task Sequence and driver installation portion of Windows Setup. Because of this reason, the PC has no network connectivity, cannot join the domain, and the Task Sequence eventually fails. However, a NIC driver was present as part of the WinPE Boot Image, which allowed the deployment to get far along enough in the deployment process where it dropped the image down on the PC.

Resolution: To correct the problem follow the steps below:

1) Make sure that the appropriate NIC drivers for the model PC, Windows OS version, and architecture have been imported into the Operating System Deployment --> Drivers node in the SCCM 2007 Admin console.

2) Make sure that the imported NIC drivers from step 1 have been added to a Driver Package under the Operating System Deployment --> Driver Packages node in the SCCM 2007 Admin console.

3) Make sure that the Driver Package from step 2 has been copied to distribution points (DPs) that are accessible to the PC during the OSD Task Sequence deployment.

4) If using the "Apply Driver Package" task in the Task Sequence, make sure that Driver Package that contains the NIC driver is selected in the "Apply Driver Package" task next to the field "Driver Package". If filtering Driver Package by model using WMI queries under the Options tab of the "Apply Driver Package" task, ensure that the WMI query is correct and you choose the correct model PC.

========

Thanks Frank!

J.C. Hornbeck | Manageability Knowledge Engineer