I'm in the process of configuring SCCM's OSD feature to replace our current imaging via Acronis, but in building the base image via Build and Capture I'm running into an issue with Office 2010. 

Once the Build and Capture process has been completed I'll launch each application that was installed via the task sequence.  All applications appear to be working just fine, except for Office 2010 x64.  When launching any Office application I get the "Please wait while Windows configures Microsoft Professional Plus 2010", and then receive the following error:

"Error 1324.  The folder path "Program Files" contains an invalid character."

Looking up this error, the solutions I find are by fixing it via registry, but I'm trying to figure out what's causing it.  For kicks, I did a search through the registry, but didn't find the culprit. 

My initial thought was that there was something wrong with the Office application deployment, but when I run the installer manually, using the OCT file, it works just fine.  It also doesn't appear to be an issue if I deploy the application via software deployment.  It only appears to be an issue with OSD. 

The OS is Windows 7 Enterprise x64 and Office is 2010 x64.  Let me know if there is anything more you'd like to know.

Any advice as to where to look?  Office, of course, is a critical application to the image, so I'm stuck until I can get it figured out.

Hello,

After installing sp1 on my sccm 2012 server when I pxe boot a server to capture an image I get the message

PXE-E53: No boot filename received.

PXE-MOF: Exiting Intel PXE Rom

smspxe.log Failed to load global logging configuration. Useing defaults.

I have tried to deploy to all unkown computers and checked the settings for dp and boot image, etc.

I would greatly appreciate your help!!!!

Thanks,

Mark

Hello, I have installed and configuredSCCM2012SP1inmy customer.ScenariosBareMetaandrefreshworks fine. In theReplacescenario, I installedmymigration Point,I createdmycomputer association thenIcreate a taskcaptureincludes:

For the TaskSequenceCapture, I have

1.RequestStateStore

2.CaptureUser State

3.ReleaseStateStore

For the RestoreState
1. Bare Metal Task Sequence

2.Restart theComputer Task(useCurrently installedO /S)

3.RequestStateStore

4.RestoreUser State

5.ReleaseStateStore

When I capture the sequence backup is work very good and the data  are in the folder on the SMP. Sowhen I run the restore Task Sequence, when the step is Request State Store I have 0x80004005 error.Why?

SMSTS.log on client who have this error:

SMP request to "http://domain.com" failed with error: E_SMPERROR_ROOTSTOREDIR_NOTAVAILABLE (210) OSDSMPClient 2013-07-24 08:51:54 2880 (0x0B40)
Request to SMP http://domain.com' failed with error (Code 0x80004005). Trying next SMP. OSDSMPClient 2013-07-24 08:51:54 2880 (0x0B40)
Failed to find an SMP that can serve request after trying 3 attempts. OSDSMPClient 2013-07-24 08:51:54 2880 (0x0B40)
ExecuteCaptureRequestSMP failed (0x80004005). OSDSMPClient 2013-07-24 08:51:54 2880 (0x0B40)
ExecuteCaptureRequest failed (0x80004005). OSDSMPClient 2013-07-24 08:51:54 2880 (0x0B40)

This is very strange, we deployed a task sequence to All Unknown Computers that fails for one reason or another. Now the computer account is not in the All Unknown Computers collection even though it is named unknown, it appears in the All Systems collection. We delete the computer account from SCCM. We then try to PXE boot and deploy Deploy the OS image again and it will not get past the PXE stage. The contents of the SMSPXE.log show that the computer is in fact unknown and not found in the SCCM DB but does not have a valid advertisement... The contents of the log file are as follows:

Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
	SMSPXE	8/20/2013 4:50:27 PM	3332 (0x0D04)
B8:CA:3A:94:26:0F, 4C4C4544-0044-5110-8051-B4C04F375931: device is not in the database.	SMSPXE	8/20/2013 4:50:27 PM	3332 (0x0D04)
Getting boot action for unknown machine: item key: 2046820352	SMSPXE	8/20/2013 4:50:27 PM	3332 (0x0D04)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName="" ServerRemoteName=""><Machine><ClientID>b8704fe9-d45b-4243-9842-5e707d77d347</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="02920007" OfferIDTime="8/20/2013 4:47:00 PM" PkgID="02900009" PackageVersion="" PackagePath="http://Path/SMS_DP_SMSPKG$/02900005" BootImageID="02900005" Mandatory="1"/></ClientIDReply>
	SMSPXE	8/20/2013 4:50:27 PM	3332 (0x0D04)
B8:CA:3A:94:26:0F, 4C4C4544-0044-5110-8051-B4C04F375931: using advertisement 02920007	SMSPXE	8/20/2013 4:50:27 PM	3332 (0x0D04)
Getting boot action for unknown machine: item key: 2046820352	SMSPXE	8/20/2013 4:50:29 PM	3332 (0x0D04)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName="" ServerRemoteName=""><Machine><ClientID>b8704fe9-d45b-4243-9842-5e707d77d347</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="02920007" OfferIDTime="8/20/2013 4:47:00 PM" PkgID="02900009" PackageVersion="" PackagePath="http://path/SMS_DP_SMSPKG$/02900005" BootImageID="02900005" Mandatory="1"/></ClientIDReply>
	SMSPXE	8/20/2013 4:50:29 PM	3332 (0x0D04)
B8:CA:3A:94:26:0F, 4C4C4544-0044-5110-8051-B4C04F375931: using advertisement 02920007	SMSPXE	8/20/2013 4:50:29 PM	3332 (0x0D04)
Getting boot action for unknown machine: item key: 2046820353	SMSPXE	8/20/2013 4:50:33 PM	3332 (0x0D04)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820353" ServerName="" ServerRemoteName=""><Machine><ClientID>57c4c583-1392-4dba-add1-50c0b16c8fa0</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="02920007" OfferIDTime="8/20/2013 4:47:00 PM" PkgID="02900009" PackageVersion="" PackagePath="http://path/SMS_DP_SMSPKG$/02900005" BootImageID="02900005" Mandatory="1"/></ClientIDReply>
	SMSPXE	8/20/2013 4:50:33 PM	3332 (0x0D04)
B8:CA:3A:94:26:0F, 4C4C4544-0044-5110-8051-B4C04F375931: using advertisement 02920007	SMSPXE	8/20/2013 4:50:33 PM	3332 (0x0D04)
Looking for bootImage 02900005	SMSPXE	8/20/2013 4:50:33 PM	3332 (0x0D04)
Report Body: <ReportBody><ClientID>57c4c583-1392-4dba-add1-50c0b16c8fa0</ClientID><StateMessage MessageTime="20130820215034.000000+000" SerialNumber="1"><ClientID>57c4c583-1392-4dba-add1-50c0b16c8fa0</ClientID><Topic ID="PXE Boot Adv Status" Type="600" IDType="600"/><State ID="100" Criticality="0"/><UserParameters Flags="32" Count="4"><Param>B8:CA:3A:94:26:0F</Param><Param>4C4C4544-0044-5110-8051-B4C04F375931</Param><Param>02920007</Param><Param>029</Param></UserParameters></StateMessage></ReportBody>
	SMSPXE	8/20/2013 4:50:34 PM	3332 (0x0D04)
B8:CA:3A:94:26:0F, 4C4C4544-0044-5110-8051-B4C04F375931: Updating Device Cached LastAdv Time. Time=20/08/2013 21:50:34 LastAdvID=02920007	SMSPXE	8/20/2013 4:50:34 PM	3332 (0x0D04)

Any ideas?

Thanks!

Tony

Good Afternoon!

I have had much experience with SCCM 2007, but am still getting used to SCCM 2012.  Today, I set up and deployed my first test OSD deployment.  

Everything worked fine except one little thing - the computer did not join to the domain.

Below is what I've tried to get this resolved...

- Verified credentials in TS were correctly entered

- Tested and was able to join the same computer TS was run on to the domain using the same credentials (including their formatting) which are in the TS.

- Checked the NetSetup.log in C:\Windows\Debug - It didn't exist.  After joining the domain manually in the step above, it did, though.

- I didn't see anything that stood out in the smsts.log.

I'll be happy to attach any log files if needed.   Any suggestions?  THanks!

Ben K.

After upgrading to SP1 I can no longer schedule Windows updates on an operating system image. The Scheduled Updates Status goes from Processing, to "Failed to mount the image on the system". This feature did work prior to upgrading to SP1.

I have made sure that Endpoint Protection has C:\ConfigMgr_OfflineImageServicing as an exception.

I've uninstalled WSUS 3.0 SP2 and reinstalled it.

When I look at the OfflineServicingMgr.log file I can see the following:

Thank you for any suggestions on getting this figured out.

Someone help me i want build & reference image from reference computer i mean my computer having windows7 x64 sp1, software etc so i want to build reference image from reference computer  using  MDT not via operating system installers

sccmghost@hotmail.com

Got an issue where the TS bombs out after the software update steps completes.

I can see that the machine is rebooting a few times in between next boot.

Anybody come across this?????

<![LOG[Failed to set log directory. Some execution history may be lost. 
The system cannot find the file specified. (Error: 80070002; Source: Windows)]LOG]!><time="17:58:13.348-60" date="07-09-2013" component="OSDSetupHook" context="" type="3" thread="984" file="osdsetuphook.cpp:192"><![LOG[Executing task sequence]LOG]!><time="17:58:13.365-60" date="07-09-2013" component="OSDSetupHook" context="" type="1" thread="984" file="osdsetuphook.cpp:279"><![LOG[!sVolumeID.empty(), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,478)]LOG]!><time="17:58:13.365-60" date="07-09-2013" component="OSDSetupHook" context="" type="0" thread="984" file="resolvesource.cpp:478"><![LOG[!sTSMDataPath.empty(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,1414)]LOG]!><time="17:58:13.365-60" date="07-09-2013" component="OSDSetupHook" context="" type="0" thread="984" file="resolvesource.cpp:1414"><![LOG[Task Sequence environment not found.]LOG]!><time="17:58:13.365-60" date="07-09-2013" component="OSDSetupHook" context="" type="1" thread="984" file="basesetuphook.cpp:1420"><![LOG[Attempting to get active request.]LOG]!><time="17:58:13.365-60" date="07-09-2013" component="OSDSetupHook" context="" type="1" thread="984" file="basesetuphook.cpp:48"><![LOG[Failed to create instance if Software Execution Request Managerr. 0x80070005]LOG]!><time="17:58:13.442-60" date="07-09-2013" component="OSDSetupHook" context="" type="1" thread="984" file="basesetuphook.cpp:57"><![LOG[Waiting for ccmexec process to start.]LOG]!><time="17:58:13.442-60" date="07-09-2013" component="OSDSetupHook" context="" type="1" thread="984" file="basesetuphook.cpp:58"><![LOG[Failed to create instance if Software Execution Request Managerr. 0x80070005]LOG]!><time="17:58:18.458-60" date="07-09-2013" component="OSDSetupHook" context="" type="1" thread="984" file="basesetuphook.cpp:57"><![LOG[Waiting for ccmexec process to start.]LOG]!><time="17:58:18.458-60" date="07-09-2013" component="OSDSetupHook" context="" type="1" thread="984" file="basesetuphook.cpp:58"><![LOG[Failed to create instance if Software Execution Request Managerr. 0x80070005]LOG]!><time="17:58:23.504-60" date="07-09-2013" component="OSDSetupHook" context="" type="1" thread="984" file="basesetuphook.cpp:57"><![LOG[Waiting for ccmexec process to start.]LOG]!><time="17:58:23.504-60" date="07-09-2013" component="OSDSetupHook" context="" type="1" thread="984" file="basesetuphook.cpp:58"><![LOG[Failed to create instance if Software Execution Request Managerr. 0x80070005]LOG]!><time="17:58:28.520-60" date="07-09-2013" component="OSDSetupHook" context="" type="1" thread="984" file="basesetuphook.cpp:57"><![LOG[Waiting for ccmexec process to start.]LOG]!><time="17:58:28.520-60" date="07-09-2013" component="OSDSetupHook" context="" type="1" thread="984" file="basesetuphook.cpp:58"><![LOG[Failed to create instance if Software Execution Request Managerr. 0x80070005]LOG]!><time="17:58:33.535-60" date="07-09-2013" component="OSDSetupHook" context="" type="1" thread="984" file="basesetuphook.cpp:57"><![LOG[Waiting for ccmexec process to start.]LOG]!><time="17:58:33.535-60" date="07-09-2013" component="OSDSetupHook" context="" type="1" thread="984" file="basesetuphook.cpp:58"><![LOG[Failed to create instance if Software Execution Request Managerr. 0x80070005]LOG]!><time="17:58:38.551-60" date="07-09-2013" component="OSDSetupHook" context="" type="1" thread="984" file="basesetuphook.cpp:57"><![LOG[Waiting for ccmexec process to start.]LOG]!><time="17:58:38.551-60" date="07-09-2013" component="OSDSetupHook" context="" type="1" thread="984" file="basesetuphook.cpp:58"><![LOG[Failed to create instance if Software Execution Request Managerr. 0x80070005]LOG]!><time="17:58:43.566-60" date="07-09-2013" component="OSDSetupHook" context="" type="1" thread="984" file="basesetuphook.cpp:57"><![LOG[Waiting for ccmexec process to start.]LOG]!><time="17:58:43.566-60" date="07-09-2013" component="OSDSetupHook" context="" type="1" thread="984" file="basesetuphook.cpp:58"><![LOG[Failed to create instance if Software Execution Request Managerr. 0x80070005]LOG]!><time="17:58:48.581-60" date="07-09-2013" component="OSDSetupHook" context="" type="1" thread="984" file="basesetuphook.cpp:57"><![LOG[Waiting for ccmexec process to start.]LOG]!><time="17:58:48.581-60" date="07-09-2013" component="OSDSetupHook" context="" type="1" thread="984" file="basesetuphook.cpp:58"><![LOG[Failed to create instance if Software Execution Request Managerr. 0x80070005]LOG]!><time="17:58:53.596-60" date="07-09-2013" component="OSDSetupHook" context="" type="1" thread="984" file="basesetuphook.cpp:57"><![LOG[Waiting for ccmexec process to start.]LOG]!><time="17:58:53.596-60" date="07-09-2013" component="OSDSetupHook" context="" type="1" thread="984" file="basesetuphook.cpp:58"><![LOG[Failed to create instance if Software Execution Request Managerr. 0x80070005]LOG]!><time="17:58:58.612-60" date="07-09-2013" component="OSDSetupHook" context="" type="1" thread="984" file="basesetuphook.cpp:57"><![LOG[Waiting for ccmexec process to start.]LOG]!><time="17:58:58.612-60" date="07-09-2013" component="OSDSetupHook" context="" type="1" thread="984" file="basesetuphook.cpp:58"><![LOG[Failed to create instance if Software Execution Request Managerr. 0x80070005]LOG]!><time="17:59:03.674-60" date="07-09-2013" component="OSDSetupHook" context="" type="1" thread="984" file="basesetuphook.cpp:57"><![LOG[Waiting for ccmexec process to start.]LOG]!><time="17:59:03.674-60" date="07-09-2013" component="OSDSetupHook" context="" type="1" thread="984" file="basesetuphook.cpp:58"><![LOG[Failed to create instance if Software Execution Request Managerr. 0x80070005]LOG]!><time="17:59:08.689-60" date="07-09-2013" component="OSDSetupHook" context="" type="1" thread="984" file="basesetuphook.cpp:57"><![LOG[Waiting for ccmexec process to start.]LOG]!><time="17:59:08.689-60" date="07-09-2013" component="OSDSetupHook" context="" type="1" thread="984" file="basesetuphook.cpp:58"><![LOG[Failed to create instance if Software Execution Request Managerr. 0x80070005]LOG]!><time="17:59:13.704-60" date="07-09-2013" component="OSDSetupHook" context="" type="1" thread="984" file="basesetuphook.cpp:57"><![LOG[Waiting for ccmexec process to start.]LOG]!><time="17:59:13.704-60" date="07-09-2013" component="OSDSetupHook" context="" type="1" thread="984" file="basesetuphook.cpp:58"><![LOG[Failed to create instance if Software Execution Request Managerr. 0x80070005]LOG]!><time="17:59:18.720-60" date="07-09-2013" component="OSDSetupHook" context="" type="1" thread="984" file="basesetuphook.cpp:57"><![LOG[Waiting for ccmexec process to start.]LOG]!><time="17:59:18.720-60" date="07-09-2013" component="OSDSetupHook" context="" type="1" thread="984" file="basesetuphook.cpp:58"><![LOG[pISoftwareExecutionRequestMgr->GetActiveRequest (&pIExecutionRequest), HRESULT=87d01012 (e:\nts_sccm_release\sms\client\osdeployment\osdgina\basesetuphook.cpp,66)]LOG]!><time="17:59:25.704-60" date="07-09-2013" component="OSDSetupHook" context="" type="0" thread="984" file="basesetuphook.cpp:66"><![LOG[GetActiveRequest failed with error code 0x87d01012]LOG]!><time="17:59:25.704-60" date="07-09-2013" component="OSDSetupHook" context="" type="3" thread="984" file="basesetuphook.cpp:66"><![LOG[GetActiveRequest failed. 0x87D01012.]LOG]!><time="17:59:25.704-60" date="07-09-2013" component="OSDSetupHook" context="" type="3" thread="984" file="basesetuphook.cpp:83"><![LOG[GetActiveRequest (sHandle), HRESULT=87d01012 (e:\nts_sccm_release\sms\client\osdeployment\osdgina\basesetuphook.cpp,94)]LOG]!><time="17:59:25.736-60" date="07-09-2013" component="OSDSetupHook" context="" type="0" thread="984" file="basesetuphook.cpp:94">

Hi All, I've been having a very difficult time with getting MDT integration working. I am able to successfully integrate, but when I attempt to create my first MDT task sequence I get the errors below at the end of the task sequence wizard.

I'm trying to create the TS from my machine with the SCCM administration console installed. I've also got Windows ADK and MDT 2012 update 1 installed locally. We are running SCCM 2012 SP1.

Started processing.
Creating boot image.
Copying WIM file.
Mounting WIM file.
WIM file mounted.
Setting Windows PE system root.
Set Windows PE system root.
Set Windows PE scratch space.
Adding standard components.
Adding component: winpe-mdac
Adding extra content from: C:\Users\matkins\AppData\Local\Temp\zfkwe5j2.gic
Unmounting WIM.
Copying WIM to the package source directory.
Creating boot image package.
Error while importing Microsoft Deployment Toolkit Task Sequence. 

Failed to insert OSD binaries into the WIM file

Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException: The SMS Provider reported an error. ---> System.Management.ManagementException: Generic failure 
   at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
   at System.Management.ManagementObject.Put(PutOptions options)
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport)
   --- End of inner exception stack trace ---
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport)
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put()
   at Microsoft.BDD.Wizards.SCCM_ImportTaskSequenceTask.DoWork(SmsPageData smspageData, Dictionary`2 data)

SMSProv.log file on the server contains these errors:

I would like to start “playing” with Windows OS deployment in ConfigMgr 2012 SP1. Since my OS deployment experience is very limited I’m going through the Kent Agerlund book (System Center 2012 Configuration Manager – Mastering the Fundamentals) Chapter 10 Operation System Deployment.

It is look like that I have to enable PXE support for clients in ConfigMgr 2012. Problem here is that we already have PXE server setup on our network. This PXE server is used for our HP thin clients boot ups and reimaging.

What would be the best possible andsimplest scenario to run two PXE servers on the same network?!

Thanks in advance

I'm installing the SCCM 2012 secondary site but in the middle the secondary site server is rebooted  due to hardware issues. Maybe the installation in instalation of sql express or configuring side

My concern now, how do I cleanup the failed installation by starting from start again .

Because I'm afradi if the delete some folder duing failed deployment will create issue

Please advise

Hi,

I want to copy files to a package on th eusb-stick in the first ts step.

there for I need the driveletter from the USB-device the tasksequence is started from ?

_SMSTSMediaRootPath is appeartly a smsts variable but it is no availbale in the beginning of the TS, only in a later stage this var gets filled in .

Anybody an idea if there is a variable available ?

or if it is possible to translate the

_SMSTSSMBUMI00003=file:VOL001:\SMS\PKG\UMI00003

to a path I can use to copy to ?

Thanks

Jeroen

Info:

in the x:\windows\temp\smstslog\smsts.log this letter is known...

=========TSBOOTSHELL.EXE==========

RAM boot disk Path  MULTI(0)DISK(0)PARTITION(1)\sources\boot.wim

WinPE boot path : d:\sources\boot.wim

Hi,

Just a quick question. All my application deployments work fine but not when I add them in my task sequence.
I can try to check logfiles but just wonder if this is a know issue that can be solved in task sequence by configuring certain steps(?)

J.

Jan Hoedt

I have seen this issue back in SCCM 2007 but for the life of me I cannot find a reference to the issue.  I have a Windows 7 TS that has been working for days now but today out of the blue (or because of some change I made) the following happens:

I choose the OSD Task Sequence from the list after PXE booting...

...after resolving dependencies the TS downloads the boot image and prompts with:

Ready to Start
Remove the CD and do not boot from CD

<Name of Task Sequence>

Click Finish to start the task sequence

Does anyone recall how to resolve this issue?

Thanks

Before anyone mentions anything about "allow this program to run whether or not a user is logged in", it's already checked.  Also "install for System", "whether a user is logged on or not", and hidden are the other settings but I have also changed to "normal" installation as well just to test.  I had set the "allow content to be downloaded locally if needed" as well thinking that could be the issue, but no dice.

I created three applications, each with a deployment type that only calls cmd to create/modify a registry key.  Then to each I added a lot of application dependencies.  The reason is so that I can have a "Laptop Apps" application and let it install all the applications needed through dependencies.  Then on the task sequence options tab I was going to simply add a filter for laptops only.  Same for desktops, departments, etc.

The issue is that I can select any of those three.  After checking the option above was turned on, I checked for other applications that had dependencies and they show up just fine.  I was thinking of using powershell to compare them with such applications but the properties flags are numbers so I don't know how that will help, considering I could simply corrupt them if I start copying numbers from one app to another.

I understand this is a unique and ambiguous case so here is my question:  Is there a log or a way to see why those are filtered out?  Logs, turning on debug on the console somewhere?  Anything that will show me "verbose" what happens when I click on the add application button in the Tasksequence step?

I tested the applications using regular deployment and they work fine.

Any other troubleshooting steps?

Thank you,

MR

Hi all,

I have SCCM 2012 SP1. One primary site server with a DP on the same box and then one other DP on a separate box. I have successfully enabled multicasting on the DP on my primary site server and have been able to mutlicast a WIM as part of an OSD deployment.

Now I need to enable multicasting on my other DP which is on a separate box so that I can multicast a WIM that is only on this DP.

I have WDS installed which looks healthy. I enabled multicasting on the DP settings and watched it install OK in the logs. The stumbling point I seem to have is when I tick the box for the WIM to be multicasted. When I did this to my other WIM the mcsmgr.log shows: Handling control manager registry Changes succeeded AND the McsPrv.log shows the namespace being created and added. But nn my other DP I don't see these logs getting updated when I enable the WIM for multicasting. So it does not look like a namespace is being created.

Any ideas?

Thanks,

Jay

There are so many posts on this topic I'm a little embarassed to have not found an answer I could make sense of.  I'm hoping someone in the forums can help-

I'm working to deploy SCCM 2012 in my environment and keep getting an abortpxe.com error while trying to deploy my Windows 7 reference image to a VM.  Specifically, I get this error:

The details given below show the information relating to the PXE boot request for
this computer. Please provide these details to your Windows Deployment Services
Administyrator so that this request can be approved.

Pending Request ID: 35

Contacting Server: 192.168.20.59.
TFTP Download: smsboot\x64\abortpxe.com

PXE Boot aborted. Booting to next device...

The VM is also on a Windows 2012 Hyper-V host (a different host, not that it should matter).  The VM has a legacy NIC installed.  When I look at my SMSPXE.log, I don't see any clear errors. 

DHCP message:
 Operation: BootRequest (1)
 Hardware Address type: 1
 Hardware Address Length: 6
 Hop Count: 0
 Transaction ID: 3402145E
 Seconds Since Boot: 4
 Client IP Address: 000.000.000.000
 Your IP Address: 000.000.000.000
 Server IP Address: 000.000.000.000
 Relay Agent IP Address: 000.000.000.000
 Hardware Address: 00:15:5d:14:02:34:
 Magic Cookie: 63538263
 Options:
    Type = 53 DHCP Message Type: 1=DHCPDiscover
    Type = 55 Paramerter Request List: 01020305060b0c0d0f1011122b363c438081828384858687
    Type = 57 Max DHCP Message Size: 04ec
    Type = 97 UUID: 00f58256df80e25e42ab2071be1e5c09b7
    Type = 93 Client system Arch: IA x86 PC
    Type = 94 UNDI: 010201
    Type = 60 ClassIdentifier: PXEClient:Arch:00000:UNDI:002001 SMSPXE 8/19/2013 10:21:13 AM 2788 (0x0AE4)
CLibSMSMessageWinHttpTransport::Send: URL: BG-SCCM.whitenoise.local:80  GET /SMS_MP/.sms_aut?MPKEYINFORMATIONEX SMSPXE 8/19/2013 10:21:13 AM 2176 (0x0880)
CLibSMSMessageWinHttpTransport::Send: URL: BG-SCCM.whitenoise.local:80  CCM_POST /ccm_system/request SMSPXE 8/19/2013 10:21:13 AM 2176 (0x0880)
Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777293" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
 SMSPXE 8/19/2013 10:21:13 AM 2176 (0x0880)
00:15:5D:14:02:34, DF5682F5-E280-425E-AB20-71BE1E5C09B7: device is in the database. SMSPXE 8/19/2013 10:21:13 AM 2176 (0x0880)
CLibSMSMessageWinHttpTransport::Send: URL: BG-SCCM.whitenoise.local:80  GET /SMS_MP/.sms_aut?MPKEYINFORMATIONEX SMSPXE 8/19/2013 10:21:13 AM 2176 (0x0880)
CLibSMSMessageWinHttpTransport::Send: URL: BG-SCCM.whitenoise.local:80  CCM_POST /ccm_system/request SMSPXE 8/19/2013 10:21:13 AM 2176 (0x0880)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777293" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
 SMSPXE 8/19/2013 10:21:13 AM 2176 (0x0880)
00:15:5D:14:02:34, DF5682F5-E280-425E-AB20-71BE1E5C09B7: no advertisements found SMSPXE 8/19/2013 10:21:13 AM 2176 (0x0880)
CLibSMSMessageWinHttpTransport::Send: URL: BG-SCCM.whitenoise.local:80  GET /SMS_MP/.sms_aut?MPKEYINFORMATIONEX SMSPXE 8/19/2013 10:21:13 AM 2176 (0x0880)
Sending StatusMessage SMSPXE 8/19/2013 10:21:13 AM 2176 (0x0880)
CLibSMSMessageWinHttpTransport::Send: URL: BG-SCCM.whitenoise.local:80  CCM_POST /ccm_system/request SMSPXE 8/19/2013 10:21:13 AM 2176 (0x0880)
00:15:5D:14:02:34, DF5682F5-E280-425E-AB20-71BE1E5C09B7: No boot action. Aborted. SMSPXE 8/19/2013 10:21:13 AM 2176 (0x0880)
DHCP message:
 Operation: BootReply (2)
 Hardware Address type: 1
 Hardware Address Length: 6
 Hop Count: 0
 Transaction ID: 3402145E
 Seconds Since Boot: 4
 Client IP Address: 000.000.000.000
 Your IP Address: 000.000.000.000
 Server IP Address: 192.168.020.059
 Relay Agent IP Address: 000.000.000.000
 Hardware Address: 00:15:5d:14:02:34:
 Magic Cookie: 63538263
 Options:
    Type = 53 DHCP Message Type: 2=DHCPOffer
    Type = 54 Server idenitifier: 192.168.020.059
    Type = 97 UUID: 00f58256df80e25e42ab2071be1e5c09b7
    Type = 60 ClassIdentifier: PXEClient SMSPXE 8/19/2013 10:21:13 AM 2176 (0x0880)
00:15:5D:14:02:34, DF5682F5-E280-425E-AB20-71BE1E5C09B7: Not serviced. SMSPXE 8/19/2013 10:21:13 AM 2176 (0x0880)
DHCP message:
 Operation: BootRequest (1)
 Hardware Address type: 1
 Hardware Address Length: 6
 Hop Count: 0
 Transaction ID: 3402145E
 Seconds Since Boot: 4
 Client IP Address: 000.000.000.000
 Your IP Address: 000.000.000.000
 Server IP Address: 000.000.000.000
 Relay Agent IP Address: 000.000.000.000
 Hardware Address: 00:15:5d:14:02:34:
 Magic Cookie: 63538263
 Options:
    Type = 53 DHCP Message Type: 3=DHCPRequest
    Type = 50 Requested IP: 192.168.020.076
    Type = 55 Paramerter Request List: 01020305060b0c0d0f1011122b363c438081828384858687
    Type = 57 Max DHCP Message Size: 04ec
    Type = 54 Server idenitifier: 192.168.020.003
    Type = 97 UUID: 00f58256df80e25e42ab2071be1e5c09b7
    Type = 93 Client system Arch: IA x86 PC
    Type = 94 UNDI: 010201
    Type = 60 ClassIdentifier: PXEClient:Arch:00000:UNDI:002001 SMSPXE 8/19/2013 10:21:17 AM 2788 (0x0AE4)
DHCP message:
 Operation: BootRequest (1)
 Hardware Address type: 1
 Hardware Address Length: 6
 Hop Count: 0
 Transaction ID: 3402145E
 Seconds Since Boot: 4
 Client IP Address: 192.168.020.076
 Your IP Address: 000.000.000.000
 Server IP Address: 000.000.000.000
 Relay Agent IP Address: 000.000.000.000
 Hardware Address: 00:15:5d:14:02:34:
 Magic Cookie: 63538263
 Options:
    Type = 53 DHCP Message Type: 3=DHCPRequest
    Type = 55 Paramerter Request List: 01020305060b0c0d0f1011122b363c438081828384858687
    Type = 57 Max DHCP Message Size: 04ec
    Type = 97 UUID: 00f58256df80e25e42ab2071be1e5c09b7
    Type = 93 Client system Arch: IA x86 PC
    Type = 94 UNDI: 010201
    Type = 60 ClassIdentifier: PXEClient:Arch:00000:UNDI:002001 SMSPXE 8/19/2013 10:21:17 AM 2788 (0x0AE4)
DHCP message:
 Operation: BootReply (2)
 Hardware Address type: 1
 Hardware Address Length: 6
 Hop Count: 0
 Transaction ID: 3402145E
 Seconds Since Boot: 4
 Client IP Address: 192.168.020.076
 Your IP Address: 000.000.000.000
 Server IP Address: 192.168.020.059
 Relay Agent IP Address: 000.000.000.000
 Hardware Address: 00:15:5d:14:02:34:
 BootFileName: smsboot\x86\wdsnbp.com
 Magic Cookie: 63538263
 Options:
    Type = 53 DHCP Message Type: 5=DHCPAck
    Type = 54 Server idenitifier: 192.168.020.059
    Type = 97 UUID: 00f58256df80e25e42ab2071be1e5c09b7
    Type = 60 ClassIdentifier: PXEClient
    Type = 250 0201010504000001d003020014040200ba0626506c6561736520776169742e20534d53206973206c6f6f6b696e6720666f7220706f6c6963790b0101 SMSPXE 8/19/2013 10:21:17 AM 2176 (0x0880)
DHCP message:
 Operation: BootRequest (1)
 Hardware Address type: 1
 Hardware Address Length: 6
 Hop Count: 0
 Transaction ID: 3402145E
 Seconds Since Boot: 0
 Client IP Address: 192.168.020.076
 Your IP Address: 000.000.000.000
 Server IP Address: 000.000.000.000
 Relay Agent IP Address: 000.000.000.000
 Hardware Address: 00:15:5d:14:02:34:
 Magic Cookie: 63538263
 Options:
    Type = 53 DHCP Message Type: 3=DHCPRequest
    Type = 60 ClassIdentifier: PXEClient
    Type = 97 UUID: 00f58256df80e25e42ab2071be1e5c09b7
    Type = 93 Client system Arch: IA x86 PC
    Type = 250 0d0208000e0101010200060504000001d0ff
    Type = 55 Paramerter Request List: 03013c8081828384858687 SMSPXE 8/19/2013 10:21:17 AM 2764 (0x0ACC)
CLibSMSMessageWinHttpTransport::Send: URL: BG-SCCM.whitenoise.local:80  GET /SMS_MP/.sms_aut?MPKEYINFORMATIONEX SMSPXE 8/19/2013 10:21:17 AM 2176 (0x0880)
CLibSMSMessageWinHttpTransport::Send: URL: BG-SCCM.whitenoise.local:80  CCM_POST /ccm_system/request SMSPXE 8/19/2013 10:21:17 AM 2176 (0x0880)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777293" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
 SMSPXE 8/19/2013 10:21:17 AM 2176 (0x0880)
00:15:5D:14:02:34, DF5682F5-E280-425E-AB20-71BE1E5C09B7: no advertisements found SMSPXE 8/19/2013 10:21:17 AM 2176 (0x0880)
CLibSMSMessageWinHttpTransport::Send: URL: BG-SCCM.whitenoise.local:80  GET /SMS_MP/.sms_aut?MPKEYINFORMATIONEX SMSPXE 8/19/2013 10:21:17 AM 2176 (0x0880)
Sending StatusMessage SMSPXE 8/19/2013 10:21:17 AM 2176 (0x0880)
CLibSMSMessageWinHttpTransport::Send: URL: BG-SCCM.whitenoise.local:80  CCM_POST /ccm_system/request SMSPXE 8/19/2013 10:21:17 AM 2176 (0x0880)
DHCP message:
 Operation: BootReply (2)
 Hardware Address type: 1
 Hardware Address Length: 6
 Hop Count: 0
 Transaction ID: 3402145E
 Seconds Since Boot: 0
 Client IP Address: 192.168.020.076
 Your IP Address: 000.000.000.000
 Server IP Address: 192.168.020.059
 Relay Agent IP Address: 000.000.000.000
 Hardware Address: 00:15:5d:14:02:34:
 BootFileName: smsboot\x64\abortpxe.com
 Magic Cookie: 63538263
 Options:
    Type = 53 DHCP Message Type: 5=DHCPAck
    Type = 54 Server idenitifier: 192.168.020.059
    Type = 97 UUID: 00f58256df80e25e42ab2071be1e5c09b7
    Type = 60 ClassIdentifier: PXEClient SMSPXE 8/19/2013 10:21:17 AM 2176 (0x0880)
DHCP message:
 Operation: BootRequest (1)
 Hardware Address type: 1
 Hardware Address Length: 6
 Hop Count: 0
 Transaction ID: 6880D61E
 Seconds Since Boot: 64
 Client IP Address: 000.000.000.000
 Your IP Address: 000.000.000.000
 Server IP Address: 000.000.000.000
 Relay Agent IP Address: 000.000.000.000
 Hardware Address: 00:22:19:d6:80:68:
 Magic Cookie: 63538263
 Options:
    Type = 53 DHCP Message Type: 1=DHCPDiscover
    Type = 55 Paramerter Request List: 01020305060b0c0d0f1011122b363c438081828384858687
    Type = 57 Max DHCP Message Size: 04ec
    Type = 97 UUID: 0044454c4c5800104d804dc2c04f564831
    Type = 93 Client system Arch: IA x86 PC
    Type = 94 UNDI: 010201
    Type = 60 ClassIdentifier: PXEClient:Arch:00000:UNDI:002001 SMSPXE 8/19/2013 10:21:46 AM 2764 (0x0ACC)
Getting boot action for unknown machine: item key: 2046820352 SMSPXE 8/19/2013 10:21:46 AM 2176 (0x0880)
CLibSMSMessageWinHttpTransport::Send: URL: BG-SCCM.whitenoise.local:80  GET /SMS_MP/.sms_aut?MPKEYINFORMATIONEX SMSPXE 8/19/2013 10:21:46 AM 2176 (0x0880)
CLibSMSMessageWinHttpTransport::Send: URL: BG-SCCM.whitenoise.local:80  CCM_POST /ccm_system/request SMSPXE 8/19/2013 10:21:46 AM 2176 (0x0880)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName="" ServerRemoteName=""><Machine><ClientID>0f741346-6f03-446e-8433-2d44b4996247</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="BG120004" OfferIDTime="8/18/2013 9:07:00 PM" PkgID="BG100011" PackageVersion="" PackagePath="http://BG-SCCM.whitenoise.local/SMS_DP_SMSPKG$/BG10000D" BootImageID="BG10000D" Mandatory="0"/></ClientIDReply>
 SMSPXE 8/19/2013 10:21:46 AM 2176 (0x0880)
00:22:19:D6:80:68, 4C4C4544-0058-4D10-804D-C2C04F564831: found optional advertisement BG120004 SMSPXE 8/19/2013 10:21:46 AM 2176 (0x0880)
DHCP message:
 Operation: BootReply (2)
 Hardware Address type: 1
 Hardware Address Length: 6
 Hop Count: 0
 Transaction ID: 6880D61E
 Seconds Since Boot: 64
 Client IP Address: 000.000.000.000
 Your IP Address: 000.000.000.000
 Server IP Address: 192.168.020.059
 Relay Agent IP Address: 000.000.000.000
 Hardware Address: 00:22:19:d6:80:68:
 Magic Cookie: 63538263
 Options:
    Type = 53 DHCP Message Type: 2=DHCPOffer
    Type = 54 Server idenitifier: 192.168.020.059
    Type = 97 UUID: 0044454c4c5800104d804dc2c04f564831
    Type = 60 ClassIdentifier: PXEClient SMSPXE 8/19/2013 10:21:46 AM 2176 (0x0880)
DHCP message:
 Operation: BootRequest (1)
 Hardware Address type: 1
 Hardware Address Length: 6
 Hop Count: 0
 Transaction ID: 6880D61E
 Seconds Since Boot: 64
 Client IP Address: 000.000.000.000
 Your IP Address: 000.000.000.000
 Server IP Address: 000.000.000.000
 Relay Agent IP Address: 000.000.000.000
 Hardware Address: 00:22:19:d6:80:68:
 Magic Cookie: 63538263
 Options:
    Type = 53 DHCP Message Type: 3=DHCPRequest
    Type = 50 Requested IP: 192.168.020.072
    Type = 55 Paramerter Request List: 01020305060b0c0d0f1011122b363c438081828384858687
    Type = 57 Max DHCP Message Size: 04ec
    Type = 54 Server idenitifier: 192.168.020.003
    Type = 97 UUID: 0044454c4c5800104d804dc2c04f564831
    Type = 93 Client system Arch: IA x86 PC
    Type = 94 UNDI: 010201
    Type = 60 ClassIdentifier: PXEClient:Arch:00000:UNDI:002001 SMSPXE 8/19/2013 10:21:50 AM 2764 (0x0ACC)
DHCP message:
 Operation: BootRequest (1)
 Hardware Address type: 1
 Hardware Address Length: 6
 Hop Count: 0
 Transaction ID: 6880D61E
 Seconds Since Boot: 64
 Client IP Address: 192.168.020.072
 Your IP Address: 000.000.000.000
 Server IP Address: 000.000.000.000
 Relay Agent IP Address: 000.000.000.000
 Hardware Address: 00:22:19:d6:80:68:
 Magic Cookie: 63538263
 Options:
    Type = 53 DHCP Message Type: 3=DHCPRequest
    Type = 55 Paramerter Request List: 01020305060b0c0d0f1011122b363c438081828384858687
    Type = 57 Max DHCP Message Size: 04ec
    Type = 97 UUID: 0044454c4c5800104d804dc2c04f564831
    Type = 93 Client system Arch: IA x86 PC
    Type = 94 UNDI: 010201
    Type = 60 ClassIdentifier: PXEClient:Arch:00000:UNDI:002001 SMSPXE 8/19/2013 10:21:50 AM 2764 (0x0ACC)
DHCP message:
 Operation: BootReply (2)
 Hardware Address type: 1
 Hardware Address Length: 6
 Hop Count: 0
 Transaction ID: 6880D61E
 Seconds Since Boot: 64
 Client IP Address: 192.168.020.072
 Your IP Address: 000.000.000.000
 Server IP Address: 192.168.020.059
 Relay Agent IP Address: 000.000.000.000
 Hardware Address: 00:22:19:d6:80:68:
 BootFileName: smsboot\x86\wdsnbp.com
 Magic Cookie: 63538263
 Options:
    Type = 53 DHCP Message Type: 5=DHCPAck
    Type = 54 Server idenitifier: 192.168.020.059
    Type = 97 UUID: 0044454c4c5800104d804dc2c04f564831
    Type = 60 ClassIdentifier: PXEClient
    Type = 250 0201010504000001d103020014040200ba0626506c6561736520776169742e20534d53206973206c6f6f6b696e6720666f7220706f6c6963790b0101 SMSPXE 8/19/2013 10:21:50 AM 2176 (0x0880)
DHCP message:
 Operation: BootRequest (1)
 Hardware Address type: 1
 Hardware Address Length: 6
 Hop Count: 0
 Transaction ID: 6880D61E
 Seconds Since Boot: 0
 Client IP Address: 192.168.020.072
 Your IP Address: 000.000.000.000
 Server IP Address: 000.000.000.000
 Relay Agent IP Address: 000.000.000.000
 Hardware Address: 00:22:19:d6:80:68:
 Magic Cookie: 63538263
 Options:
    Type = 53 DHCP Message Type: 3=DHCPRequest
    Type = 60 ClassIdentifier: PXEClient
    Type = 97 UUID: 0044454c4c5800104d804dc2c04f564831
    Type = 93 Client system Arch: IA x86 PC
    Type = 250 0d0208000e0101010200060504000001d1ff
    Type = 55 Paramerter Request List: 03013c8081828384858687 SMSPXE 8/19/2013 10:21:50 AM 2764 (0x0ACC)
Getting boot action for unknown machine: item key: 2046820353 SMSPXE 8/19/2013 10:21:50 AM 2176 (0x0880)
CLibSMSMessageWinHttpTransport::Send: URL: BG-SCCM.whitenoise.local:80  GET /SMS_MP/.sms_aut?MPKEYINFORMATIONEX SMSPXE 8/19/2013 10:21:50 AM 2176 (0x0880)
CLibSMSMessageWinHttpTransport::Send: URL: BG-SCCM.whitenoise.local:80  CCM_POST /ccm_system/request SMSPXE 8/19/2013 10:21:50 AM 2176 (0x0880)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820353" ServerName="" ServerRemoteName=""><Machine><ClientID>1047174c-9491-4ee7-8c8c-ecf4ca53f5f0</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="BG120004" OfferIDTime="8/18/2013 9:07:00 PM" PkgID="BG100011" PackageVersion="" PackagePath="http://BG-SCCM.whitenoise.local/SMS_DP_SMSPKG$/BG10000D" BootImageID="BG10000D" Mandatory="0"/></ClientIDReply>
 SMSPXE 8/19/2013 10:21:50 AM 2176 (0x0880)
00:22:19:D6:80:68, 4C4C4544-0058-4D10-804D-C2C04F564831: found optional advertisement BG120004 SMSPXE 8/19/2013 10:21:50 AM 2176 (0x0880)
Looking for bootImage BG10000D SMSPXE 8/19/2013 10:21:50 AM 2176 (0x0880)
CLibSMSMessageWinHttpTransport::Send: URL: BG-SCCM.whitenoise.local:80  GET /SMS_MP/.sms_aut?MPKEYINFORMATIONEX SMSPXE 8/19/2013 10:21:50 AM 2176 (0x0880)
Sending StatusMessage SMSPXE 8/19/2013 10:21:51 AM 2176 (0x0880)
CLibSMSMessageWinHttpTransport::Send: URL: BG-SCCM.whitenoise.local:80  CCM_POST /ccm_system/request SMSPXE 8/19/2013 10:21:51 AM 2176 (0x0880)
DHCP message:
 Operation: BootReply (2)
 Hardware Address type: 1
 Hardware Address Length: 6
 Hop Count: 0
 Transaction ID: 6880D61E
 Seconds Since Boot: 0
 Client IP Address: 192.168.020.072
 Your IP Address: 000.000.000.000
 Server IP Address: 192.168.020.059
 Relay Agent IP Address: 000.000.000.000
 Hardware Address: 00:22:19:d

Anyone have a suggestion on what might be wrong or where I should start looking?

Thanks,

Jeffrey