Yes. NIC drivers are installed and the system gets and IP address. As well, I'm able to ping all Management Points.
From: [email protected] [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Thursday, May 29, 2014 7:48 PM To: [email protected] Subject: RE: [MDT-OSD] Failed to Query MP while booted to OSD WinPE Boot Image Have they verified that the current NIC drivers are even in the boot image by doing a simple ipconfig once in WinPE? This should always be the first first thing checked. J From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Brian Marobella Sent: Thursday, May 29, 2014 1:01 PM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] Failed to Query MP while booted to OSD WinPE Boot Image Hello, We are running into an issue when booting to the OSD Boot image to install OSD images. The issue is the client is failing to contact the MP when booted to WinPE. I get the following error in the smsts.log MP Location returned an empty site code CCM::SMSMessaging::CLibSMSMPLocation::RequestMPLocation failed; 0x80004005 MPLocation.RequestMPLocation (szTrustedRootKey, sIPSubnets.c_str(), sIPAddresses.c_str(), sSiteCode, sAssignedSiteCode, sMP, sMPCertificates, sX86UnknownMachineGUID, sX64UnknownMachineGUID), HRESULT=80004005 (e:\qfe\nts\sms\framework\osdmessaging\libsmsmessaging.cpp,9583) CCM::SMSMessaging::GetMPLocation failed; 0x80004005 Failed to query https://ourserver.domain.com for MP location Here are some notes/facts: 1. Client is in a remote location with a Secondary MP 2. Can deploy and install OSD images to existing SCCM clients in the same site via Software Center. This only fails when booting to the OSD Boot Iso. 3. We use HTTPS for all client communication 4. Added the ConfigMgr Distribution Point Certificate and also tried adding the ConfigMgr Client Certificate to OSD Boot image 5. Site Boundaries are configured properly 6. Boot image is set to Dynamic 7. ConfigMgr Version is 2012 SP1 CU2 The only Management Point that I can select when creating the boot ISO is the Primary MP. Should I have the option to select the Secondary MP? At the moment, remote admins have to do a default Windows build, add client to domain, then I push the OSD image to the client to install our custom image. Any advices, help would be much appreciated. Thanks
