I don't think this is a cm2012 issue but I need to prove this before I throw it back to the networking team :-)   Over the weekend a new 4500 switch was added to our network.  Now, we are not able to build any workstations via OSD from any site.  We have 8 DPs in different offices and nothing builds.  when you do build here is what happens.

F12 to boot from network (working)

Then it will not connect to any DP.  we see this error each time.    Can a new switch cause this on all DPs?  

What do you see in the smspxe.log?

Did IP helpers get set up properly once the new switch was put in place (assuming the switch is doing routing as well)?

Jeff

Actually, looking at your screenshot again, PXE is working. . .it is failing to find policy (but the smspxe.log should confirm that).  Is the machine(s) in question in a collection to which the task sequence is deployed?

Jeff

I don't know about IPHelpers.  I know that before the switch was added everything worked.  last week we could image machines via OSD.  On Saturday the switch was added and now we can't image machines.   The smsts.log says this:

End TS policy evaluation TSManager 5/14/2015 10:24:54 AM 1736 (0x06C8)
Policy evaluation initiated TSManager 5/14/2015 10:24:54 AM 1736 (0x06C8)
Sending success status message TSManager 5/14/2015 10:24:54 AM 1736 (0x06C8)
MP server http://MGH-SCCM12-01.maringeneral.org. Ports 80,443. CRL=false. TSManager 5/14/2015 10:24:54 AM 1736 (0x06C8)
Setting authenticator TSManager 5/14/2015 10:24:54 AM 1736 (0x06C8)
Set authenticator in transport TSManager 5/14/2015 10:24:54 AM 1736 (0x06C8)
Sending StatusMessage TSManager 5/14/2015 10:24:54 AM 1736 (0x06C8)
Setting message signatures. TSManager 5/14/2015 10:24:54 AM 1736 (0x06C8)
Setting the authenticator. TSManager 5/14/2015 10:24:54 AM 1736 (0x06C8)
CLibSMSMessageWinHttpTransport::Send: URL: MGH-SCCM12-01.maringeneral.org:80  CCM_POST /ccm_system/request TSManager 5/14/2015 10:24:54 AM 1736 (0x06C8)
Request was successful. TSManager 5/14/2015 10:24:54 AM 1736 (0x06C8)
::RegQueryValueExW(hSubKey, szReg, NULL, NULL, NULL, &dwSize), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,811) TSManager 5/14/2015 10:24:54 AM 1736 (0x06C8)
RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram TSManager 5/14/2015 10:24:54 AM 1736 (0x06C8)
GetTsRegValue() is unsuccessful. 0x80070002. TSManager 5/14/2015 10:24:54 AM 1736 (0x06C8)
End program: TSManager 5/14/2015 10:24:54 AM 1736 (0x06C8)
Finalize logging request ignored from process 1732 TSManager 5/14/2015 10:24:54 AM 1736 (0x06C8)
Waiting for CcmExec service to be fully operational TSManager 5/14/2015 10:24:54 AM 1736 (0x06C8)
CcmExec service is up and fully operational TSManager 5/14/2015 10:24:54 AM 1736 (0x06C8)
Access handle will be read from _SMSTSActiveRequestHandle TSManager 5/14/2015 10:24:54 AM 1736 (0x06C8)
Access handle: {49DCA3E6-0069-4BBA-8A39-B24C1FBC3AFE} TSManager 5/14/2015 10:24:54 AM 1736 (0x06C8)
Attempting to release request using {49DCA3E6-0069-4BBA-8A39-B24C1FBC3AFE} TSManager 5/14/2015 10:24:54 AM 1736 (0x06C8)
CoCreateInstance succeeded TSManager 5/14/2015 10:24:54 AM 1736 (0x06C8)
pISoftwareExecutionRequestMgr->ReleaseRequest(ActiveRequestGUID), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmanager\tsmanagerutils.cpp,136) TSManager 5/14/2015 10:24:56 AM 1736 (0x06C8)
ReleaseRequest failed with error code 0x80004005 TSManager 5/14/2015 10:24:56 AM 1736 (0x06C8)
Task Sequence Manager could not release active TS request. code 80004005 TSManager 5/14/2015 10:24:56 AM 1736 (0x06C8)
Process completed with exit code 0 TSMBootstrap 5/14/2015 10:24:56 AM 1660 (0x067C)
Exiting with return code 0x00000000 TSMBootstrap 5/14/2015 10:24:56 AM 1660 (0x067C)
Process completed with exit code 0 OSDSetupHook 5/14/2015 10:24:56 AM 764 (0x02FC)
Task sequence completed 0x00000000 OSDSetupHook 5/14/2015 10:24:56 AM 764 (0x02FC)
Resume SCCM Client. OSDSetupHook 5/14/2015 10:24:56 AM 764 (0x02FC)
Uninstalling Setup Hook OSDSetupHook 5/14/2015 10:24:58 AM 764 (0x02FC)
Removing setup hook from registry. OSDSetupHook 5/14/2015 10:24:58 AM 764 (0x02FC)
Successfully removed C:\WINDOWS\system32\OSDGINA.DLL OSDSetupHook 5/14/2015 10:24:58 AM 764 (0x02FC)
Successfully removed C:\WINDOWS\system32\OSDSETUPHOOK.EXE OSDSetupHook 5/14/2015 10:24:58 AM 764 (0x02FC)
Successfully removed C:\WINDOWS\system32\_SMSOSDSetup OSDSetupHook 5/14/2015 10:24:58 AM 764 (0x02FC)
RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram OSDSetupHook 5/14/2015 10:24:58 AM 764 (0x02FC)
GetTsRegValue() is unsuccessful. 0x80070002. OSDSetupHook 5/14/2015 10:24:58 AM 764 (0x02FC)
End program: OSDSetupHook 5/14/2015 10:24:58 AM 764 (0x02FC)

I was looking for info from the smspxe.log, not the smsts.log actually.

Jeff

OK, I discovered the problem.    We have a Dell Latitude E7250 laptop.  It does not play nice with the CM2012 OSD.  So I reached out to our Dell rep and they pointed me to a Dell tech who said to do this:

1) Install Windows ADK (www.microsoft.com/.../details.aspx), selecting WinPE

2)Take the WinPE.wim file from the install directory (C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\en-us)  and place in an easy to remember directory

3)Download the drivers direct from intel (https://downloadcenter.intel.com/download/23073/Network-Adapter-Driver-for-Windows-Server-2012-R2) and run the installer.

4)Extract the network drivers from the temporary folder that is created. You are looking for the NDIS63 and 64 folders

5)Copy these drivers to an easy to remember location

6)Using DISM mount WinPE and import the network drivers from the driver location

7)Unmount the WinPE Wim image, and from there import into SCCM 2012

8)Apply the Image to the relevant task sequence and boot

I did this.  I used DISM to inject to NIC drivers into this .wim.  I then added this .WIM to the BOOT IMAGES.  I deployed it to all DPs.  I then did a COPY of our task sequence and then had this new copy use the new .wim file.   I then advertised this new task sequence to All Unknown computers and to All Systems.  Once I did that the error I showed above happens.  When I delete the new advertisements the errors go away and we can build machines.

What the heck!?!?!   why would doing this cause our whole OSD process to break?  

All that ADK/DISM stuff would not have been needed at that point. abortpxe just tells you that there is no task sequence deployment available for that machine (=MAC address). smspxe.log should tell you exactly what was going on.
dism and driver related stuff is only needed when WinPE is downloaded (so a little bit later in the process).

I looked in the smspxe.log and it says:

Looking for bootImage MH100183 SMSPXE 5/19/2015 1:01:26 PM 5040 (0x13B0)
00:50:56:B3:16:9C, AAAD3342-E126-FB65-EE68-7BF89D6FEA84: could not find boot image MH100183 SMSPXE 5/19/2015 1:01:26 PM 5040 (0x13B0)
00:50:56:B3:16:9C, AAAD3342-E126-FB65-EE68-7BF89D6FEA84: Not serviced. SMSPXE 5/19/2015 1:01:26 PM 5040 (0x13B0)
Looking for bootImage MH100183 SMSPXE 5/19/2015 1:01:46 PM 5040 (0x13B0)
00:50:56:B3:16:9C, AAAD3342-E126-FB65-EE68-7BF89D6FEA84: could not find boot image MH100183 SMSPXE 5/19/2015 1:01:46 PM 5040 (0x13B0)
00:50:56:B3:16:9C, AAAD3342-E126-FB65-EE68-7BF89D6FEA84: Not serviced. SMSPXE 5/19/2015 1:01:46 PM 5040 (0x13B0)

Now what is strange is I have deployed this boot image to all DPs.     Why would it not find the boot image when it is on all of the DPs?

Redistribute it to that DP and monitor distmgr.log and smspxe.log

For your new boot image, you distributed the content to the DPs (I think you said that, but I want to clarify)?

Jeff

Hi,

Please also verify your boundary group.