Jump to content


Recommended Posts

When i try to pxe boot a client, i only get PXE-E53 "No boot filename received"

 

I have tried to reinstall wds/pxe several times.. searched trough a lot of post with similar problems..tried lot of solutions.. but still stuck..

I really dont know where to begin to troubleshoot this..

 

SMSPXE:

 

reply has no message header marker SMSPXE 27.04.2012 12:36:19 3936 (0x0F60)

PXE::DB_LookupDevice failed; 0x80004005 SMSPXE 27.04.2012 12:36:19 3936 (0x0F60)

Set enterpirse certificate in transport SMSPXE 27.04.2012 12:36:19 3936 (0x0F60)

Set media certificate in transport SMSPXE 27.04.2012 12:36:19 3936 (0x0F60)

Set authenticator in transport SMSPXE 27.04.2012 12:36:19 3936 (0x0F60)

In SSL, but with no client cert SMSPXE 27.04.2012 12:36:19 3936 (0x0F60)

Set authenticator in transport SMSPXE 27.04.2012 12:36:19 3936 (0x0F60)

In SSL, but with no client cert SMSPXE 27.04.2012 12:36:19 3936 (0x0F60)

reply has no message header marker SMSPXE 27.04.2012 12:36:19 3936 (0x0F60)

Failed to send status message (80004005) SMSPXE 27.04.2012 12:36:19 3936 (0x0F60)

Failed to send the status message SMSPXE 27.04.2012 12:36:19 3936 (0x0F60)

PXE::DB_ReportStatus failed; 0x80004005 SMSPXE 27.04.2012 12:36:19 3936 (0x0F60)

PXE Provider failed to process message.

Unspecified error (Error: 80004005; Source: Windows) SMSPXE 27.04.2012 12:36:19 3936 (0x0F60)

 

 

 

Edit: also tried to add option 66/67 in dhcp.. i get past the pxe boot.. but recieve a \boot\bcd error

And the same lines of errors in SMSPXE

post-11792-0-27642300-1335436344_thumb.jpg

Share this post


Link to post
Share on other sites


I have the same issue. SCCM 2007 works great. I installed SCCM 2012 and a new server R2. Did a site by site migration and got everything moved over.

 

SCCM 2012 Site is the DP, MP, State Migration. I want to be able to pxe boot my images. I get the same error.

 

If I configure WDS I get the \boot\bcd error.

 

So what i have done is uninstall WDS and deleted the DP

couple reboots later

I install WDS and do nothing to it.

I add the DP back to the site server.

I then added PXE to it.

I can see that my server under WDS is not configured.

the REMIST folder is showing up

The WDS service is running.

 

I also have images in the right folder

 

E:\RemoteInstall\SMSImages\MID00003\boot.MID00003.wim

Share this post


Link to post
Share on other sites

My WDS seems to have gotten configured by CM atleast.. But i dont have a folder called "REMINST".. to me its "RemoteInstall"

 

I also have a working CM 2007 system with pxe boot.

 

If i dont configure dhcp with option 66 (CM ip) and 67 with \Boot\x64\wdsnbp.. i get a PXE-E53 "No boot filename received

Share this post


Link to post
Share on other sites

oh.. just noticed.. just before i press F12 the second time, its a message that says "No response from windows deployment service, launching pxeboot.com"

Share this post


Link to post
Share on other sites

I'm having this issue as well.

 

I have created a remote DP and in the CM console it shows the DP has the boot images. When trying to boot pxe I get the same error, TFTP, no file found.

 

Anyone have a fix for this? I'd rather keep PXE on my remote DP instead of my primary site box.

Share this post


Link to post
Share on other sites

I have it on my primary and was going to put it on a remote. i ended up shutting down my 2012 box and started the 2007 back up. Had a boundry issue and had to delete the all the old sms stuff from the system management in ad and let it all come back and then it worked... so i thought I would turn off my 2007, delete all the AD items in system management and turn on my 2012. Still nothing.

 

Change the boundaries to AD instead of IP range and nothing.\

WDS service is running and not configured.

 

I do notice when I uncheck the pxe on my DP and hit apply and ok, I can open it back up and it's still checked.

Share this post


Link to post
Share on other sites

Exactly the same thing that's happening to me. I also noticed that when booting a virtual machine via PXE, the DHCP server's address is the address of my primary site's box not the remote DP box.

Share this post


Link to post
Share on other sites

Fixed my issue.

 

All i wanted to see was the pxe come up and then I would continue and after it didn't work I made a trigger disk and could boot into PE, but it said I had no TS, so I made one. Advertised it to all computer and all unknown and then the pxe started working.

 

guess i should have made the ad before trying to see if pxe was going to work.

 

The old site site was turned back on and it had a new boot image on it, so i thought it was the 2012 sccm. Once powered off, no PXE boot found again.

Share this post


Link to post
Share on other sites

After doing some research with Wireshark, I see that the client receives an ip address from our DHCP server but I never see any traffic either in or out to the PXE server. UDP helpers in switches are set so I'm stumped

 

 

 

PXE Successful now.

 

Now i have another problem, says the package can't be found on the distribution point.

Share this post


Link to post
Share on other sites

What was the fix for this? I'm having the same issue.

 

I made a thread on technet and they said it was certificate issues. But I made a whole new WDS server for this and I still have the same problem.

Share this post


Link to post
Share on other sites

After doing some research with Wireshark, I see that the client receives an ip address from our DHCP server but I never see any traffic either in or out to the PXE server. UDP helpers in switches are set so I'm stumped

 

 

 

PXE Successful now.

 

Now i have another problem, says the package can't be found on the distribution point.

 

You should check the package ID and confirm which package is failing. If it's the boot image it's probably some issue with your network access account or your boundary group.

Share this post


Link to post
Share on other sites

I am getting similar error message when I try to PXE boot from my test laptop.

 

PXE-E53: No boot filename received

PXE-M0F: Exiting Intel Boot Agent. No boot device found.

 

No errors are showing up in my SMSPXE.log file.

 

Set media certificate in transport SMSPXE 7/18/2012 1:23:43 PM 3112 (0x0C28)

Set authenticator in transport SMSPXE 7/18/2012 1:23:43 PM 3112 (0x0C28)

Set authenticator in transport SMSPXE 7/18/2012 1:23:43 PM 3112 (0x0C28)

Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777263" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>

SMSPXE 7/18/2012 1:23:43 PM 3112 (0x0C28)

PXE::CBootImageManager::FindMatchingArchitectureBootImage SMSPXE 7/18/2012 1:23:43 PM 3112 (0x0C28)

Set media certificate in transport SMSPXE 7/18/2012 1:23:44 PM 3112 (0x0C28)

Set authenticator in transport SMSPXE 7/18/2012 1:23:44 PM 3112 (0x0C28)

Set authenticator in transport SMSPXE 7/18/2012 1:23:44 PM 3112 (0x0C28)

Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777263" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>

SMSPXE 7/18/2012 1:23:44 PM 3112 (0x0C28)

Client Identity: 57f02fbf-aa03-4668-922d-99270f69d0a6 SMSPXE 7/18/2012 1:23:44 PM 3112 (0x0C28)

Set media certificate in transport SMSPXE 7/18/2012 1:23:44 PM 3112 (0x0C28)

Set authenticator in transport SMSPXE 7/18/2012 1:23:44 PM 3112 (0x0C28)

Set authenticator in transport SMSPXE 7/18/2012 1:23:44 PM 3112 (0x0C28)

PXE::CBootImageManager::FindMatchingArchitectureBootImage SMSPXE 7/18/2012 1:23:47 PM 3112 (0x0C28)

Set media certificate in transport SMSPXE 7/18/2012 1:23:47 PM 3112 (0x0C28)

Set authenticator in transport SMSPXE 7/18/2012 1:23:47 PM 3112 (0x0C28)

Set authenticator in transport SMSPXE 7/18/2012 1:23:47 PM 3112 (0x0C28)

Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777263" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>

SMSPXE 7/18/2012 1:23:47 PM 3112 (0x0C28)

Client Identity: 57f02fbf-aa03-4668-922d-99270f69d0a6 SMSPXE 7/18/2012 1:23:47 PM 3112 (0x0C28)

Set media certificate in transport SMSPXE 7/18/2012 1:23:48 PM 3112 (0x0C28)

Set authenticator in transport SMSPXE 7/18/2012 1:23:48 PM 3112 (0x0C28)

Set authenticator in transport SMSPXE 7/18/2012 1:23:48 PM 3112 (0x0C28)

PXE::CBootImageManager::FindMatchingArchitectureBootImage SMSPXE 7/18/2012 1:23:55 PM 3112 (0x0C28)

Set media certificate in transport SMSPXE 7/18/2012 1:23:55 PM 3112 (0x0C28)

Set authenticator in transport SMSPXE 7/18/2012 1:23:55 PM 3112 (0x0C28)

Set authenticator in transport SMSPXE 7/18/2012 1:23:55 PM 3112 (0x0C28)

Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777263" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>

SMSPXE 7/18/2012 1:23:55 PM 3112 (0x0C28)

Client Identity: 57f02fbf-aa03-4668-922d-99270f69d0a6 SMSPXE 7/18/2012 1:23:55 PM 3112 (0x0C28)

Set media certificate in transport SMSPXE 7/18/2012 1:23:55 PM 3112 (0x0C28)

Set authenticator in transport SMSPXE 7/18/2012 1:23:55 PM 3112 (0x0C28)

Set authenticator in transport SMSPXE 7/18/2012 1:23:56 PM 3112 (0x0C28)

PXE::CBootImageManager::FindMatchingArchitectureBootImage SMSPXE 7/18/2012 1:24:11 PM 3112 (0x0C28)

Set media certificate in transport SMSPXE 7/18/2012 1:24:11 PM 3112 (0x0C28)

Set authenticator in transport SMSPXE 7/18/2012 1:24:11 PM 3112 (0x0C28)

Set authenticator in transport SMSPXE 7/18/2012 1:24:11 PM 3112 (0x0C28)

Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777263" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>

SMSPXE 7/18/2012 1:24:11 PM 3112 (0x0C28)

Client Identity: 57f02fbf-aa03-4668-922d-99270f69d0a6 SMSPXE 7/18/2012 1:24:11 PM 3112 (0x0C28)

Set media certificate in transport SMSPXE 7/18/2012 1:24:12 PM 3112 (0x0C28)

Set authenticator in transport SMSPXE 7/18/2012 1:24:12 PM 3112 (0x0C28)

Set authenticator in transport SMSPXE 7/18/2012 1:24:12 PM 3112 (0x0C28)

 

 

Anyone have suggestions? I am a NOOB at this and just started to touch SCCM 2012, never seen 2007 before.

Share this post


Link to post
Share on other sites

Ok I finally got it to prompt me for F12 to start Boot.

 

Changes I made:

DHCP Server I enabled option 66 and 67. This is on another server than SCCM.

In WDS I changed options:

Respond to all client Computers (known and unknown)

Multicast IP Address: Obtain IP address from DHCP

 

However when it starts the initializing Windows PE - Windows is starting up... then it restarts the PC.

 

Here is a sample of my SMSPXE.log file:

 

Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777264" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>

SMSPXE 7/18/2012 3:54:14 PM 2908 (0x0B5C)

PXE::CBootImageManager::FindMatchingArchitectureBootImage SMSPXE 7/18/2012 3:54:14 PM 2908 (0x0B5C)

Set media certificate in transport SMSPXE 7/18/2012 3:54:14 PM 2908 (0x0B5C)

Set authenticator in transport SMSPXE 7/18/2012 3:54:14 PM 2908 (0x0B5C)

Set authenticator in transport SMSPXE 7/18/2012 3:54:14 PM 2908 (0x0B5C)

Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777264" ServerName="" ServerRemoteName=""><Machine><ClientID>GUID:9A8A28D5-3795-4CC0-9137-F4A4D5BAF239</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="CLA2000B" OfferIDTime="7/18/2012 3:50:00 PM" PkgID="CLA00016" PackageVersion="" PackagePath="http://<u><span styl...MSPKG$/CLA00013" BootImageID="CLA00013" Mandatory="0"/></ClientIDReply>

SMSPXE 7/18/2012 3:54:14 PM 2908 (0x0B5C)

Client Identity: 57f02fbf-aa03-4668-922d-99270f69d0a6 SMSPXE 7/18/2012 3:54:14 PM 2908 (0x0B5C)

PXE::CBootImageManager::FindMatchingArchitectureBootImage SMSPXE 7/18/2012 3:54:18 PM 2908 (0x0B5C)

Set media certificate in transport SMSPXE 7/18/2012 3:54:18 PM 2908 (0x0B5C)

Set authenticator in transport SMSPXE 7/18/2012 3:54:18 PM 2908 (0x0B5C)

Set authenticator in transport SMSPXE 7/18/2012 3:54:18 PM 2908 (0x0B5C)

Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777264" ServerName="" ServerRemoteName=""><Machine><ClientID>GUID:9A8A28D5-3795-4CC0-9137-F4A4D5BAF239</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="CLA2000B" OfferIDTime="7/18/2012 3:50:00 PM" PkgID="CLA00016" PackageVersion="" PackagePath="http://<u><span styl...MSPKG$/CLA00013" BootImageID="CLA00013" Mandatory="0"/></ClientIDReply>

SMSPXE 7/18/2012 3:54:18 PM 2908 (0x0B5C)

Client Identity: 57f02fbf-aa03-4668-922d-99270f69d0a6 SMSPXE 7/18/2012 3:54:18 PM 2908 (0x0B5C)

PXE::CBootImageManager::FindMatchingArchitectureBootImage SMSPXE 7/18/2012 3:54:18 PM 2908 (0x0B5C)

PXE::CBootImageManager::FindBootImage: CLA00013 SMSPXE 7/18/2012 3:54:18 PM 2908 (0x0B5C)

Looking for bootImage CLA00013 SMSPXE 7/18/2012 3:54:18 PM 2908 (0x0B5C)

PXE::CBootImageCache::FindImage SMSPXE 7/18/2012 3:54:18 PM 2908 (0x0B5C)

PXE::CBootImageInfo::UpdateAccessTime SMSPXE 7/18/2012 3:54:18 PM 2908 (0x0B5C)

Set media certificate in transport SMSPXE 7/18/2012 3:54:18 PM 2908 (0x0B5C)

Set authenticator in transport SMSPXE 7/18/2012 3:54:18 PM 2908 (0x0B5C)

Set authenticator in transport SMSPXE 7/18/2012 3:54:18 PM 2908 (0x0B5C)

PXE::CBootImageManager::FindMatchingArchitectureBootImage SMSPXE 7/18/2012 3:55:01 PM 2908 (0x0B5C)

Set media certificate in transport SMSPXE 7/18/2012 3:55:01 PM 2908 (0x0B5C)

Set authenticator in transport SMSPXE 7/18/2012 3:55:01 PM 2908 (0x0B5C)

Set authenticator in transport SMSPXE 7/18/2012 3:55:01 PM 2908 (0x0B5C)

Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777264" ServerName="" ServerRemoteName=""><Machine><ClientID>GUID:9A8A28D5-3795-4CC0-9137-F4A4D5BAF239</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="CLA2000B" OfferIDTime="7/18/2012 3:50:00 PM" PkgID="CLA00016" PackageVersion="" PackagePath="http://<u><span styl...MSPKG$/CLA00013" BootImageID="CLA00013" Mandatory="0"/></ClientIDReply>

SMSPXE 7/18/2012 3:55:01 PM 2908 (0x0B5C)

Client Identity: 57f02fbf-aa03-4668-922d-99270f69d0a6 SMSPXE 7/18/2012 3:55:01 PM 2908 (0x0B5C)

PXE::CBootImageManager::FindMatchingArchitectureBootImage SMSPXE 7/18/2012 3:55:05 PM 2908 (0x0B5C)

Set media certificate in transport SMSPXE 7/18/2012 3:55:05 PM 2908 (0x0B5C)

Set authenticator in transport SMSPXE 7/18/2012 3:55:05 PM 2908 (0x0B5C)

Set authenticator in transport SMSPXE 7/18/2012 3:55:05 PM 2908 (0x0B5C)

Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777264" ServerName="" ServerRemoteName=""><Machine><ClientID>GUID:9A8A28D5-3795-4CC0-9137-F4A4D5BAF239</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="CLA2000B" OfferIDTime="7/18/2012 3:50:00 PM" PkgID="CLA00016" PackageVersion="" PackagePath="http://<u><span styl...MSPKG$/CLA00013" BootImageID="CLA00013" Mandatory="0"/></ClientIDReply>

SMSPXE 7/18/2012 3:55:05 PM 2908 (0x0B5C)

Client Identity: 57f02fbf-aa03-4668-922d-99270f69d0a6 SMSPXE 7/18/2012 3:55:05 PM 2908 (0x0B5C)

PXE::CBootImageManager::FindMatchingArchitectureBootImage SMSPXE 7/18/2012 3:55:05 PM 2908 (0x0B5C)

PXE::CBootImageManager::FindBootImage: CLA00013 SMSPXE 7/18/2012 3:55:05 PM 2908 (0x0B5C)

Looking for bootImage CLA00013 SMSPXE 7/18/2012 3:55:05 PM 2908 (0x0B5C)

PXE::CBootImageCache::FindImage SMSPXE 7/18/2012 3:55:05 PM 2908 (0x0B5C)

PXE::CBootImageInfo::UpdateAccessTime SMSPXE 7/18/2012 3:55:05 PM 2908 (0x0B5C)

Set media certificate in transport SMSPXE 7/18/2012 3:55:05 PM 2908 (0x0B5C)

Set authenticator in transport SMSPXE 7/18/2012 3:55:05 PM 2908 (0x0B5C)

Set authenticator in transport SMSPXE 7/18/2012 3:55:06 PM 2908 (0x0B5C)

Set media certificate in transport SMSPXE 7/18/2012 3:57:27 PM 2908 (0x0B5C)

Set authenticator in transport SMSPXE 7/18/2012 3:57:27 PM 2908 (0x0B5C)

Set authenticator in transport SMSPXE 7/18/2012 3:57:27 PM 2908 (0x0B5C)

Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777264" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>

SMSPXE 7/18/2012 3:57:27 PM 2908 (0x0B5C)

PXE::CBootImageManager::FindMatchingArchitectureBootImage SMSPXE 7/18/2012 3:57:27 PM 2908 (0x0B5C)

Set media certificate in transport SMSPXE 7/18/2012 3:57:27 PM 2908 (0x0B5C)

Set authenticator in transport SMSPXE 7/18/2012 3:57:27 PM 2908 (0x0B5C)

Set authenticator in transport SMSPXE 7/18/2012 3:57:27 PM 2908 (0x0B5C)

Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777264" ServerName="" ServerRemoteName=""><Machine><ClientID>GUID:9A8A28D5-3795-4CC0-9137-F4A4D5BAF239</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="CLA2000B" OfferIDTime="7/18/2012 3:50:00 PM" PkgID="CLA00016" PackageVersion="" PackagePath="http://ServerName/SM...MSPKG$/CLA00013" BootImageID="CLA00013" Mandatory="0"/></ClientIDReply>

SMSPXE 7/18/2012 3:57:27 PM 2908 (0x0B5C)

Client Identity: 57f02fbf-aa03-4668-922d-99270f69d0a6 SMSPXE 7/18/2012 3:57:27 PM 2908 (0x0B5C)

PXE::CBootImageManager::FindMatchingArchitectureBootImage SMSPXE 7/18/2012 3:57:31 PM 2908 (0x0B5C)

Set media certificate in transport SMSPXE 7/18/2012 3:57:31 PM 2908 (0x0B5C)

Set authenticator in transport SMSPXE 7/18/2012 3:57:31 PM 2908 (0x0B5C)

Set authenticator in transport SMSPXE 7/18/2012 3:57:31 PM 2908 (0x0B5C)

Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777264" ServerName="" ServerRemoteName=""><Machine><ClientID>GUID:9A8A28D5-3795-4CC0-9137-F4A4D5BAF239</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="CLA2000B" OfferIDTime="7/18/2012 3:50:00 PM" PkgID="CLA00016" PackageVersion="" PackagePath="http://<u><span styl...MSPKG$/CLA00013" BootImageID="CLA00013" Mandatory="0"/></ClientIDReply>

SMSPXE 7/18/2012 3:57:31 PM 2908 (0x0B5C)

Client Identity: 57f02fbf-aa03-4668-922d-99270f69d0a6 SMSPXE 7/18/2012 3:57:31 PM 2908 (0x0B5C)

PXE::CBootImageManager::FindMatchingArchitectureBootImage SMSPXE 7/18/2012 3:57:31 PM 2908 (0x0B5C)

PXE::CBootImageManager::FindBootImage: CLA00013 SMSPXE 7/18/2012 3:57:31 PM 2908 (0x0B5C)

Looking for bootImage CLA00013 SMSPXE 7/18/2012 3:57:31 PM 2908 (0x0B5C)

PXE::CBootImageCache::FindImage SMSPXE 7/18/2012 3:57:31 PM 2908 (0x0B5C)

PXE::CBootImageInfo::UpdateAccessTime SMSPXE 7/18/2012 3:57:31 PM 2908 (0x0B5C)

Set media certificate in transport SMSPXE 7/18/2012 3:57:31 PM 2908 (0x0B5C)

Set authenticator in transport SMSPXE 7/18/2012 3:57:31 PM 2908 (0x0B5C)

Set authenticator in transport SMSPXE 7/18/2012 3:57:31 PM 2908 (0x0B5C)

 

here is my SMSTS log, I think it is a driver issue with the Dell laptop but I added the drivers to my boot file and updated to DP, recreated my TS, same issue.

 

I looked further into the Dell drivers for my NIC but looks like they all pertain to WLAN and not the LAN driver.

Currently I am going to add the LAN driver that I believe pertains to this model: E6410 and try again.

 

LOGGING: Finalize process ID set to 776 TSBootShell 7/19/2012 10:23:34 AM 780 (0x030C)

==============================[ TSBootShell.exe ]============================== TSBootShell 7/19/2012 10:23:34 AM 780 (0x030C)

Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL' TSBootShell 7/19/2012 10:23:34 AM 780 (0x030C)

Debug shell is enabled TSBootShell 7/19/2012 10:23:34 AM 780 (0x030C)

Waiting for PNP initialization... TSBootShell 7/19/2012 10:23:34 AM 812 (0x032C)

Executing command line: X:\WINDOWS\system32\cmd.exe /k TSBootShell 7/19/2012 10:23:35 AM 780 (0x030C)

The command completed successfully. TSBootShell 7/19/2012 10:23:35 AM 780 (0x030C)

Successfully launched command shell. TSBootShell 7/19/2012 10:23:35 AM 780 (0x030C)

Booted from network (PXE) TSBootShell 7/19/2012 10:23:35 AM 812 (0x032C)

Found config path X:\sms\data\ TSBootShell 7/19/2012 10:23:35 AM 812 (0x032C)

Booting from removable media, not restoring bootloaders on hard drive TSBootShell 7/19/2012 10:23:35 AM 812 (0x032C)

Executing command line: wpeinit.exe -winpe TSBootShell 7/19/2012 10:23:35 AM 812 (0x032C)

The command completed successfully. TSBootShell 7/19/2012 10:23:52 AM 812 (0x032C)

Starting DNS client service. TSBootShell 7/19/2012 10:23:52 AM 812 (0x032C)

Executing command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\ TSBootShell 7/19/2012 10:23:53 AM 812 (0x032C)

The command completed successfully. TSBootShell 7/19/2012 10:23:53 AM 812 (0x032C)

==============================[ TSMBootStrap.exe ]============================== TSMBootstrap 7/19/2012 10:23:53 AM 712 (0x02C8)

Command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\ TSMBootstrap 7/19/2012 10:23:53 AM 712 (0x02C8)

Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL' TSMBootstrap 7/19/2012 10:23:53 AM 712 (0x02C8)

Succeeded loading resource DLL 'X:\sms\bin\x64\TSRESNLC.DLL' TSMBootstrap 7/19/2012 10:23:53 AM 712 (0x02C8)

PXE Boot with Root = X:\ TSMBootstrap 7/19/2012 10:23:53 AM 712 (0x02C8)

Executing from PXE in WinPE TSMBootstrap 7/19/2012 10:23:53 AM 712 (0x02C8)

Loading TsPxe.dll from X:\sms\bin\x64\TsPxe.dll TSMBootstrap 7/19/2012 10:23:53 AM 712 (0x02C8)

TsPxe.dll loaded TSPxe 7/19/2012 10:23:53 AM 712 (0x02C8)

Device has PXE booted TSPxe 7/19/2012 10:23:53 AM 712 (0x02C8)

Variable Path: \SMSTemp\2012.07.19.09.01.12.0002.{59BF2C52-8C47-42B9-88BA-B1D5F1339DA3}.boot.var TSPxe 7/19/2012 10:23:53 AM 712 (0x02C8)

Succesfully added firewall rule for Tftp TSPxe 7/19/2012 10:23:53 AM 712 (0x02C8)

Executing: X:\sms\bin\x64\smstftp.exe -i 172.16.0.117 get \SMSTemp\2012.07.19.09.01.12.0002.{59BF2C52-8C47-42B9-88BA-B1D5F1339DA3}.boot.var X:\sms\data\variables.dat TSPxe 7/19/2012 10:23:53 AM 712 (0x02C8)

Command line for extension .exe is "%1" %* TSPxe 7/19/2012 10:23:53 AM 712 (0x02C8)

Set command line: "X:\sms\bin\x64\smstftp.exe" -i 172.16.0.117 get \SMSTemp\2012.07.19.09.01.12.0002.{59BF2C52-8C47-42B9-88BA-B1D5F1339DA3}.boot.var X:\sms\data\variables.dat TSPxe 7/19/2012 10:23:53 AM 712 (0x02C8)

Executing command line: "X:\sms\bin\x64\smstftp.exe" -i 172.16.0.117 get \SMSTemp\2012.07.19.09.01.12.0002.{59BF2C52-8C47-42B9-88BA-B1D5F1339DA3}.boot.var X:\sms\data\variables.dat TSPxe 7/19/2012 10:23:53 AM 712 (0x02C8)

Process completed with exit code 1 TSPxe 7/19/2012 10:23:53 AM 712 (0x02C8)

Succesfully removed firewall rule for Tftp TSPxe 7/19/2012 10:23:53 AM 712 (0x02C8)

uExitCode == 0, HRESULT=80004005 (e:\nts_sccm_release\sms\server\pxe\tspxe\tspxe.cpp,185) TSPxe 7/19/2012 10:23:53 AM 712 (0x02C8)

Failed to download pxe variable file. Code(0x00000001) TSPxe 7/19/2012 10:23:53 AM 712 (0x02C8)

PxeGetPxeData failed with 0x80004005 TSPxe 7/19/2012 10:23:53 AM 712 (0x02C8)

HRESULT_FROM_WIN32(dwError), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstraputil.cpp,1370) TSPxe 7/19/2012 10:23:53 AM 712 (0x02C8)

TSMBootstrapUtil::PxeGetPxeData(&bPxeBooted, sVariablesFile, sPxePasswd), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2545) TSPxe 7/19/2012 10:23:53 AM 712 (0x02C8)

oTSMediaWizardControl.Run( sMediaRoot, true, true ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,915) TSPxe 7/19/2012 10:23:53 AM 712 (0x02C8)

Execute( eExecutionEnv, sConfigPath, sTSXMLFile, uBootCount, &uExitCode ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1020) TSPxe 7/19/2012 10:23:53 AM 712 (0x02C8)

Exiting with return code 0x80004005 TSPxe 7/19/2012 10:23:53 AM 712 (0x02C8)

hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,191) TSPxe 7/19/2012 10:23:53 AM 712 (0x02C8)

m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337) TSPxe 7/19/2012 10:23:53 AM 712 (0x02C8)

this->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,549) TSPxe 7/19/2012 10:23:53 AM 712 (0x02C8)

Execution complete. TSBootShell 7/19/2012 10:23:53 AM 812 (0x032C)

Finalizing logging from process 776 TSBootShell 7/19/2012 10:23:53 AM 812 (0x032C)

Finalizing logs to root of first available drive TSBootShell 7/19/2012 10:23:53 AM 812 (0x032C)

LOGGING: Setting log directory to "X:\SMSTSLog". TSBootShell 7/19/2012 10:23:53 AM 812 (0x032C)

Share this post


Link to post
Share on other sites

options 67 and 60 should only be configured if the dhcp server is on the same server as your WDS/SCCM and not in your enviornment as you say the DHCP server is on a remote server. I had similar problems but all is fine now

 

can you post the exact steps you are doing when trying to PXE boot clients for eg: the collection you are deploying TS to the model etc...???

and also the setup steps you have undergone to set up PXE?

Share this post


Link to post
Share on other sites

Ok, I got it to stop restarting when trying to do the build and capture TS.

I had to add the drivers for the laptop, Dell E6410, but it fails to capture the image.

 

It installs the OS, says it is installing the Apps that I added to the TS but it is not installed after windows loads to desktop.

 

During the TS build/cap phase it says running Sysprep then it says the following error:

 

Task sequence: build and cap win 7 x64 has failed with the error code (0x00000002).

For more information, contact your system adminstrator or helpdesk operator.

 

 

I am assuming it is wiping out the drivers for the NIC but I am not sure.

 

Once I get back into windows I will try to locate the SMSTS.log file and post results here.

Share this post


Link to post
Share on other sites

Can you not just capture....any reason as to why you are building and capturing....sounds like way too much work......build your reference machine manually and install apps + updates, create a task sequence capture media and just capture the machine....You still have a custom image at the end of the day without the headache of having to repetitively trying to B&C unsuccessfully..

 

On another note have you tried to individually deploy your bundled apps via program deployment or TS??

 

Have you configured your programs/apps to be allowed to be deployed via a Task sequence?? (it is in the properties of the actual program in the advanced tab i think)?

 

And you are probably correct in saying that sysprep has wiped the NIC drivers...if you had to inject them into the boot.wim to get it to connect after pxe boot, then it more than likely has wiped them again after sysprep and is unable to connect to your network share as the NIC is inactive.

 

Try creating a capture media and just capture this model using your new boot.wim that you have added your NIC drivers to and see what happens?? If this fails to capture then the NIC drivers have been wiped, this could be a work around for this particular model.

Share this post


Link to post
Share on other sites

Thanks Rocket, but if I capture the media after I configure the PC for the baseline image I want would I have to burn a disc to deploy to other machines?

 

Reason I am asking this is because the Capture media in SCCM 2012 makes it into an ISO.

 

How would I be able to deploy that via PXE Boot?

Share this post


Link to post
Share on other sites

yes you are right the capture media is an ISO, which you will burn to CD, run on a live custom built machine and there will be some steps that you will have to initially set for instance the path to your network share where you want the capture image to be captured to....your network access account credentials...it is pretty self explanatory....after this it will sysprep and capture......make sure and choose the boot.wim that you injected the drivers into when creating the capture media.

 

If successful then you can create an operating system image from it which you can deploy to any amount of machines.....

 

the secret to a good deployment is to have the bare minimum of an OS so that it can suit all models and then attach your model specific drivers as needed with WMI queries....

 

I have just an install.wim and then add all my software packages i:e IE9, java, Adobe FP, SW, Reader, Office etc with desired driver package.........

I also have a custom image with the bare essential software installed as above

 

It seems to work fine so far but i do have some problems at some remote sites due to flaky comms links..

 

The articles provided by anyWeb on this site are very good for learning how to deploy OS, software and fully install SCCM......I have followed them by the book and so far everyting is good, bar just the forementioned...

 

If you need more info drop a post

 

Rocket man

Share this post


Link to post
Share on other sites

run on a live custom built machine and there will be some steps that you will have to initially set for instance the path to your network share where you want the capture image to be captured to....your network access account credentials...it is pretty self explanatory....after this it will sysprep and capture......make sure and choose the boot.wim that you injected the drivers into when creating the capture media.

 

If successful then you can create an operating system image from it which you can deploy to any amount of machines.....

 

If you need more info drop a post

 

Rocket man

 

Could you elobarate on this process? I am extremely new to OS/Software deployment and frankly I am getting overwhelmed by it.

 

I will do the capture media in SCCM, still working on that.

 

My question is how would I get it to be able to deploy via PXE?

After the target machine is set to the baseline I prefer, Capture Media, burn ISO to disc, then what?

 

Sorry for the ignorant questions.

Share this post


Link to post
Share on other sites

Run the capture media CD on the baseline machine whilst logged in....(it cannot be on the domain)......Create a network share and share it out to your network access account.....once prompted to run the CD run it and enter in the UNC path to the share you are after creating ( this is where your image will be captured to)...directly below this enter in your network access account credentials in the form of domain\accountname.......password.........then give it a brief description on the next stage and proceed to sysprep.

 

hopefully it will be successful and capture your image to the share...you will be notified when the process is finished.

 

then create an operating system image out of this newly captured image via the software node ......operating systems node...im sure you are familiar with this???

Once the OS image is created...create a new task sequenec...choose create an exsisiting image ( the 1st choice and go through the steps)

 

Once the task sequence is created you can right click and edit it and add software packages...driver packages...command lines etc...... (do get familiar with this process)

Then you can deploy this to your collections....if the target machines have already got the client installed it will deploy even if the machines are in windows(it may take a while though, but you can force the process by openeing up the ConfMgr client in the control panel of the target machines and open up the actions tab and run machine policy...this forces the client to retrieve any policies...assignments targeted to it...by default the client is set to pole the site server every hour for new policies (this can be configured in the client settings)

 

 

If you are using PXE then again this only work if your target machines already have the client...if they dont it will not work (this is true and i hope others see this).....if your machines have no client but are still showing in your all devices collection then simply delete the entries from this collection out of the SCCM database and deploy the Task sequenec to the unknown Computer collection ( again i hope others read this as this is where alot of mistakes are made with PXE not working etc...even though it probably is working correctly, SCCM will not PXE boot a known computer)

 

there are scripts on the web you can get that will prompt the user to enter in a new computer name before the new OS is installed...i would advice you to source these and use 1 of them other wise SCCM will give the machines a strange name..

  • Like 1

Share this post


Link to post
Share on other sites

RocketMan,

 

Thanks for the help! I was able to resolve the issue. I used the ISO disc to capture the image and all is well now.

 

Also I tried the Build and Capture on a Dell E6500 with the same drivers and it worked perfectly. Apparently the Dell E6410 is the issue when trying to Capture automatically.

 

Resolved!!

Share this post


Link to post
Share on other sites

I'm having the same issue with my PXE boot: PXE-E53 "No boot filename received"

 

It suspect that I'm not getting any IP address from the server. From what I have read, this does not need to be configured in DHCP. Is this correct? Aside from that, where could I be going wrong? Is it possible a port issue on my server or router?

 

Thanks

Conor

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...