PXE-E53 "No boot filename received"

[tmiller_hockey]

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.

[ericksoncl23]

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.

[Iroqouiz]

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.

[ImaNewb]

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.

[ImaNewb]

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)

[Rocket Man]

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?

[ImaNewb]

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.

[Rocket Man]

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.

[ImaNewb]

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?

[Rocket Man]

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