Can't PXE boot a Surface Pro 3 after already successfully imaging it
hey guys. To try to eliminate a lot of the initial question that come up with this issue, I figure I will start with established info. Our SCCM environment is healthy, and all images, drivers and apps are distributed to all of our DP's. We can image
PC's and laptops with no issue at all. We use network PXE booting. Using a 64 bit boot image. Needed drivers are injected into the boot image. Firmware on the Surface was updated. Using the Surface NIC dongle. THis dongle was only used to image
this Surface Pro 3 tablet one time. There is no record of the MAC of the dongle in SCCM since I deleted the Surface out, to make it an unknown again.
So, with a lot of trial and error, I was finally able to get this tab to PXE boot, and then successfully image. Was testing out the new windows 8.1 image I had built.
Since it ewas successful I wanted to add all of our apps to the TS and test them out in imaging. Well, I can no longer get this thing to PXE boot. It shows trying to Start PXE over IPv4, then just skips to IPv6, then boots up into windows.
I have delted the secure keys form ther BIOS, then reloaded them. I have tried hte full shut down method (Holding Volume Up and Power for 15 seconds, then waiting for 10 seconds or longer, then trying to PXE boot. I am getting a valid connection fro
mthe dongle.
Nothinhg I try works. Its tries to PXE boot over IPv4, but never gets there. But I can PXE boot any of our PC's or Laptops,m so its just an issue with this damn Surface Pro 3.
ANy advice?
So I finally got our server guy to enable the logging and get that smspxe.log file to be accessible. So here is the info from the log, when I attempt to PXE boot the Surface. I see the last 2 lines where it ignores the request, I just don't know why its
ignoring it.
PXE::CNotifyTimer::TimerSignalFunc SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
PXE::CNotifyTimer::ProcessTimer SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
Potentially missed device 50:1A:C5:FE:D6:E9 SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
Cleared Old Devices: 1 / 1 SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
PXE::CBootImageManager::PerformMaintenenceTasks SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
PXE::CBootImageManager::PurgeOldImages SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
Purging old images: 0 SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
PXE::CNotifyTimer::Init SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
PXE::CNotifyTimer::CancelTimer SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
PXE::CNotifyTimer::RegisterTimeout SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
[172.028.000.223:67] Recv From:[172.028.011.002:67] Len:347 1ad0230 SMSPXE 4/14/2015 3:04:37 PM 5928 (0x1728)
============> Received from client: SMSPXE 4/14/2015 3:04:37 PM 5928 (0x1728)
DHCP message:
Operation: BootRequest (1)
Hardware Address type: 1
Hardware Address Length: 6
Hop Count: 1
Transaction ID: 24038353
Seconds Since Boot: 0
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: 172.028.011.002
Hardware Address: 50:1a:c5:fe:d6:e9:
Magic Cookie: 63538263
Options:
Type = 53 DHCP Message Type: 1=DHCPDiscover
Type = 57 Max DHCP Message Size: 05b8
Type = 55 Paramerter Request List: 0102030405060c0d0f111216171c28292a2b3233363a3b3c4243618081828384858687
Type = 97 UUID: 0068745ee6b94c0e21b76054522b6a7e02
Type = 94 UNDI: 010310
Type = 93 Client system Arch: 0007
Type = 60 ClassIdentifier: PXEClient:Arch:00007:UNDI:003016 SMSPXE 4/14/2015 3:04:37 PM 5928 (0x1728)
<============ SMSPXE 4/14/2015 3:04:37 PM 5928 (0x1728)
ProcessMessage: Context:0241DF40 dTime:0 SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
50:1A:C5:FE:D6:E9, E65E7468-4CB9-210E-B760-54522B6A7E02: DHCP Discover received. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
[172.028.000.223:67] Recv From:[172.028.011.003:67] Len:347 159d1f0 SMSPXE 4/14/2015 3:04:37 PM 5928 (0x1728)
============> Received from client: SMSPXE 4/14/2015 3:04:37 PM 5928 (0x1728)
DHCP message:
Operation: BootRequest (1)
Hardware Address type: 1
Hardware Address Length: 6
Hop Count: 1
Transaction ID: 24038353
Seconds Since Boot: 0
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: 172.028.011.003
Hardware Address: 50:1a:c5:fe:d6:e9:
Magic Cookie: 63538263
Options:
Type = 53 DHCP Message Type: 1=DHCPDiscover
Type = 57 Max DHCP Message Size: 05b8
Type = 55 Paramerter Request List: 0102030405060c0d0f111216171c28292a2b3233363a3b3c4243618081828384858687
Type = 97 UUID: 0068745ee6b94c0e21b76054522b6a7e02
Type = 94 UNDI: 010310
Type = 93 Client system Arch: 0007
Type = 60 ClassIdentifier: PXEClient:Arch:00007:UNDI:003016 SMSPXE 4/14/2015 3:04:37 PM 5928 (0x1728)
<============ SMSPXE 4/14/2015 3:04:37 PM 5928 (0x1728)
ProcessMessage: Context:0241DE50 dTime:0 SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
50:1A:C5:FE:D6:E9, E65E7468-4CB9-210E-B760-54522B6A7E02: DHCP Discover received. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Initialized CStringStream object with string: c7c22c7d-4f40-49f1-b7ed-871c18a07b05;2015-04-14T19:04:37Z. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Initialized CStringStream object with string: c7c22c7d-4f40-49f1-b7ed-871c18a07b05;2015-04-14T19:04:37Z. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Set enterpirse certificate in transport SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Set enterpirse certificate in transport SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Set media certificate in transport SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Set authenticator in transport SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
CLibSMSMessageWinHttpTransport::Send: URL: JAG-SCCM-01E.jonesapparel.com:443 GET /SMS_MP_AltAuth/.sms_aut?MPKEYINFORMATIONEX SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
In SSL, but with no client cert SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Set media certificate in transport SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Set authenticator in transport SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
CLibSMSMessageWinHttpTransport::Send: URL: JAG-SCCM-01E.jonesapparel.com:443 GET /SMS_MP_AltAuth/.sms_aut?MPKEYINFORMATIONEX SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
In SSL, but with no client cert SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Request was successful. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Request was successful. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Set authenticator in transport SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Set authenticator in transport SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Setting message signatures. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Setting the authenticator. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
CLibSMSMessageWinHttpTransport::Send: URL: JAG-SCCM-01E.jonesapparel.com:443 CCM_POST /ccm_system_AltAuth/request SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
In SSL, but with no client cert SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Setting message signatures. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Setting the authenticator. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
CLibSMSMessageWinHttpTransport::Send: URL: JAG-SCCM-01E.jonesapparel.com:443 CCM_POST /ccm_system_AltAuth/request SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
In SSL, but with no client cert SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Request was successful. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
::DecompressBuffer(65536) SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Decompression (zlib) succeeded: original size 148, uncompressed size 298. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
MP_LookupDevice succeeded: 0 1 0 1 0 SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
50:1A:C5:FE:D6:E9, E65E7468-4CB9-210E-B760-54522B6A7E02: device is not in the database. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Getting boot action for unknown machine: item key: 2046820352 SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Request was successful. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
::DecompressBuffer(65536) SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Decompression (zlib) succeeded: original size 148, uncompressed size 298. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
MP_LookupDevice succeeded: 0 1 0 1 0 SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
50:1A:C5:FE:D6:E9, E65E7468-4CB9-210E-B760-54522B6A7E02: device is not in the database. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Getting boot action for unknown machine: item key: 2046820352 SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Initialized CStringStream object with string: c7c22c7d-4f40-49f1-b7ed-871c18a07b05;2015-04-14T19:04:37Z. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Set enterpirse certificate in transport SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Initialized CStringStream object with string: c7c22c7d-4f40-49f1-b7ed-871c18a07b05;2015-04-14T19:04:37Z. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Set enterpirse certificate in transport SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Set media certificate in transport SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Set authenticator in transport SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
CLibSMSMessageWinHttpTransport::Send: URL: JAG-SCCM-01E.jonesapparel.com:443 GET /SMS_MP_AltAuth/.sms_aut?MPKEYINFORMATIONEX SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
In SSL, but with no client cert SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Set media certificate in transport SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Set authenticator in transport SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
CLibSMSMessageWinHttpTransport::Send: URL: JAG-SCCM-01E.jonesapparel.com:443 GET /SMS_MP_AltAuth/.sms_aut?MPKEYINFORMATIONEX SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
In SSL, but with no client cert SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Request was successful. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Request was successful. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Set authenticator in transport SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Set authenticator in transport SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Setting message signatures. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Setting the authenticator. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
CLibSMSMessageWinHttpTransport::Send: URL: JAG-SCCM-01E.jonesapparel.com:443 CCM_POST /ccm_system_AltAuth/request SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
In SSL, but with no client cert SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Setting message signatures. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Setting the authenticator. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
CLibSMSMessageWinHttpTransport::Send: URL: JAG-SCCM-01E.jonesapparel.com:443 CCM_POST /ccm_system_AltAuth/request SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
In SSL, but with no client cert SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Request was successful. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
::DecompressBuffer(65536) SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Decompression (zlib) succeeded: original size 409, uncompressed size 950. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName=""><Machine><ClientID>c70485df-9130-4b41-b61b-6c9e11b2f69a</ClientID><NetbiosName/></Machine></Identification><PXEBootAction
LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="10020125" OfferIDTime="4/2/2015 11:12:00 AM" PkgID="100000D0" PackageVersion="" PackagePath BootImageID="10000087" Mandatory="0"/></ClientIDReply>
SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Client Identity: c70485df-9130-4b41-b61b-6c9e11b2f69a SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
50:1A:C5:FE:D6:E9, E65E7468-4CB9-210E-B760-54522B6A7E02: SMSID=c70485df-9130-4b41-b61b-6c9e11b2f69a OfferID=10020125, PackageID=100000D0, PackageVersion=, BootImageID=10000087, PackagePath=http://JAG-SCCM-01E.jonesapparel.com/SMS_DP_SMSPKG$/10000087, Mandatory=0 SMSPXE 4/14/2015
3:04:37 PM 7484 (0x1D3C)
50:1A:C5:FE:D6:E9, E65E7468-4CB9-210E-B760-54522B6A7E02: found optional advertisement 10020125 SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
============> Reply to client (DHCPDISCOVER): SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
DHCP message:
Operation: BootReply (2)
Hardware Address type: 1
Hardware Address Length: 6
Hop Count: 0
Transaction ID: 24038353
Seconds Since Boot: 0
Client IP Address: 000.000.000.000
Your IP Address: 000.000.000.000
Server IP Address: 172.028.000.223
Relay Agent IP Address: 172.028.011.002
Hardware Address: 50:1a:c5:fe:d6:e9:
Magic Cookie: 63538263
Options:
Type = 53 DHCP Message Type: 2=DHCPOffer
Type = 54 Server idenitifier: 172.028.000.223
Type = 97 UUID: 0068745ee6b94c0e21b76054522b6a7e02
Type = 60 ClassIdentifier: PXEClient SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
<============ SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Request was successful. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
::DecompressBuffer(65536) SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Decompression (zlib) succeeded: original size 409, uncompressed size 950. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName=""><Machine><ClientID>c70485df-9130-4b41-b61b-6c9e11b2f69a</ClientID><NetbiosName/></Machine></Identification><PXEBootAction
LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="10020125" OfferIDTime="4/2/2015 11:12:00 AM" PkgID="100000D0" PackageVersion="" PackagePath="xx
BootImageID="10000087" Mandatory="0"/></ClientIDReply>
SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Client Identity: c70485df-9130-4b41-b61b-6c9e11b2f69a SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
50:1A:C5:FE:D6:E9, E65E7468-4CB9-210E-B760-54522B6A7E02: SMSID=c70485df-9130-4b41-b61b-6c9e11b2f69a OfferID=10020125, PackageID=100000D0, PackageVersion=, BootImageID=10000087, PackagePath=http://JAG-SCCM-01E.jonesapparel.com/SMS_DP_SMSPKG$/10000087, Mandatory=0 SMSPXE 4/14/2015
3:04:37 PM 7480 (0x1D38)
50:1A:C5:FE:D6:E9, E65E7468-4CB9-210E-B760-54522B6A7E02: found optional advertisement 10020125 SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
============> Reply to client (DHCPDISCOVER): SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
DHCP message:
Operation: BootReply (2)
Hardware Address type: 1
Hardware Address Length: 6
Hop Count: 0
Transaction ID: 24038353
Seconds Since Boot: 0
Client IP Address: 000.000.000.000
Your IP Address: 000.000.000.000
Server IP Address: 172.028.000.223
Relay Agent IP Address: 172.028.011.003
Hardware Address: 50:1a:c5:fe:d6:e9:
Magic Cookie: 63538263
Options:
Type = 53 DHCP Message Type: 2=DHCPOffer
Type = 54 Server idenitifier: 172.028.000.223
Type = 97 UUID: 0068745ee6b94c0e21b76054522b6a7e02
Type = 60 ClassIdentifier: PXEClient SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
<============ SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
[172.028.000.223:67] Recv From:[172.028.011.003:67] Len:359 1acbeb0 SMSPXE 4/14/2015 3:04:40 PM 5928 (0x1728)
[172.028.000.223:67] Recv From:[172.028.011.002:67] Len:359 15a41f0 SMSPXE 4/14/2015 3:04:40 PM 5972 (0x1754)
============> Received from client: SMSPXE 4/14/2015 3:04:40 PM 5928 (0x1728)
============> Received from client: SMSPXE 4/14/2015 3:04:40 PM 5972 (0x1754)
DHCP message:
Operation: BootRequest (1)
Hardware Address type: 1
Hardware Address Length: 6
Hop Count: 1
Transaction ID: 24038353
Seconds Since Boot: 0
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: 172.028.011.003
Hardware Address: 50:1a:c5:fe:d6:e9:
Magic Cookie: 63538263
Options:
Type = 53 DHCP Message Type: 3=DHCPRequest
Type = 54 Server idenitifier: 172.028.000.015
Type = 50 Requested IP: 172.028.011.052
Type = 57 Max DHCP Message Size: ff00
Type = 55 Paramerter Request List: 0102030405060c0d0f111216171c28292a2b3233363a3b3c4243618081828384858687
Type = 97 UUID: 0068745ee6b94c0e21b76054522b6a7e02
Type = 94 UNDI: 010310
Type = 93 Client system Arch: 0007
Type = 60 ClassIdentifier: PXEClient:Arch:00007:UNDI:003016 SMSPXE 4/14/2015 3:04:40 PM 5928 (0x1728)
DHCP message:
Operation: BootRequest (1)
Hardware Address type: 1
Hardware Address Length: 6
Hop Count: 1
Transaction ID: 24038353
Seconds Since Boot: 0
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: 172.028.011.002
Hardware Address: 50:1a:c5:fe:d6:e9:
Magic Cookie: 63538263
Options:
Type = 53 DHCP Message Type: 3=DHCPRequest
Type = 54 Server idenitifier: 172.028.000.015
Type = 50 Requested IP: 172.028.011.052
Type = 57 Max DHCP Message Size: ff00
Type = 55 Paramerter Request List: 0102030405060c0d0f111216171c28292a2b3233363a3b3c4243618081828384858687
Type = 97 UUID: 0068745ee6b94c0e21b76054522b6a7e02
Type = 94 UNDI: 010310
Type = 93 Client system Arch: 0007
Type = 60 ClassIdentifier: PXEClient:Arch:00007:UNDI:003016 SMSPXE 4/14/2015 3:04:40 PM 5972 (0x1754)
<============ SMSPXE 4/14/2015 3:04:40 PM 5928 (0x1728)
<============ SMSPXE 4/14/2015 3:04:40 PM 5972 (0x1754)
Ignoring req from [172.028.011.003:67] Dest Server:[172.028.000.015] SMSPXE 4/14/2015 3:04:40 PM 5928 (0x1728)
Ignoring req from [172.028.011.002:67] Dest Server:[172.028.000.015] SMSPXE 4/14/2015 3:04:40 PM 5972 (0x1754)
Similar Messages
-
Can't PXE boot Windows 8 models
We load the PCs with our own OS image as they come in. The process works off a PXE (network) boot image.
We recently started ording the same X230s, only with a Windows 8 license. Lenovo indicated that there should be no changes needed with our image.
However, we can not PXE boot these machines. We shut them down and bring them back up with an F12 on the bios splash screen and select PCI LAN.
We get a message saying >>Start PXE over IPv4
It hangs there a while, then tries IPv6, then goes back to the boot device ment.
We got a solid green and a flashing yellow light on the network connector. And we've PXE booted off of this connection many, many times
What are we missing?
Thank you.
Solved!
Go to Solution.Hey there DOTJKO,
I've seen over on another thread, that they were having the same issue. They were able to get the PXE Boot process to finally go by:
1) Go to BIOS
2) SECURITY tab --> Secure Boot --> set SECURE BOOT to [DISABLED]
3) Go to STARTUP tab --> UEFI/Legacy Boot --> set to [BOTH]
Hopefully this assists you in getting those X230s loaded up with your image. Good Luck, and keep us posted on your progress.
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution".! This will help the rest of the Community with similar issues identify the verified solution and benefit from it. -
PXE boot fails and reboots after loading PE
I have run into what I think is a unique issue and need some help determining the cause.
We are in the process of replacing and aging DP/PXE point (2003 R2 SP2) with a new server (2008 STD R2 SP1). What makes my pxe issue unique is that pxe works without issue on the existing 2003 DP/PXE server. But on the new 2008 server I run into
the following issue.
Environment: Config Manager 2007 R2, a single primary, multiple DP's and PXE points.
Issue: When I attempt to PXE boot a system, I am able to load PE, but shortly after the custom background screen is loaded, the system reboots. I've searched the internet quite a bit and found lots of potential causes including, bad/missing drivers,
certificate issues, rights issues, etc. None of these seem to be the cause.
My troubleshooting has determined that the client computers are unable to download the variables.dat file. I just don't know why.
We're using the same boot images on both servers.
I've tried using multiple computer models and VM's.
I've opened a command prompt as soon as our background image loads and have verified that the system is pulling a valid IP address. I am able to map a drive to the PXE server's REMINST share using our sccm net access account and manually copy the .var
file using xcopy to the appropriate directory on the local virtual drive. I've also attempted to manually run smstftp.exe by mimicking the command line from the smsts log file. I'll admit that I'm not sure I have the correct syntax for smstftp.
I've tried several variations and all but one result in a short pause and no file copied/created in the X:\sms\data folder. The one that does produce a result says that the file cannot be found. I checked for typos and made sure I used the name
of the newly created .var file.
I've also tried disabling anti-virus on the server, shutting off the windows firewall on the server, granting everyone read rights to the REMINST share.
Below is the smstslog file I've been using as a reference. Per corporate security policy, I have X'd out the IP address of the PXE server. The log file for the successful pxe boot from the 2003 server shows an exit code of 0 for smstftp.exe, a note
about successful download of the pxe var file and then it continues through the rest of the boot process.
-----SMSTS log file from a failed PXE boot on the new 2008 server -----
<![LOG[LOGGING: Finalize process ID set to 832]LOG]!><time="16:13:54.440+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836" file="tslogging.cpp:1489">
<![LOG[==============================[ TSBootShell.exe ]==============================]LOG]!><time="16:13:54.440+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836"
file="bootshell.cpp:963">
<![LOG[Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL']LOG]!><time="16:13:54.440+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836" file="util.cpp:869">
<![LOG[Debug shell is enabled]LOG]!><time="16:13:54.440+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836" file="bootshell.cpp:974">
<![LOG[Waiting for PNP initialization...]LOG]!><time="16:13:54.471+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:59">
<![LOG[Booted from network (PXE)]LOG]!><time="16:13:54.830+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="configpath.cpp:198">
<![LOG[Found config path X:\sms\data\]LOG]!><time="16:13:54.830+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:553">
<![LOG[Booting from removable media, not restoring bootloaders on hard drive]LOG]!><time="16:13:54.830+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:564">
<![LOG[Executing command line: wpeinit.exe -winpe]LOG]!><time="16:13:54.830+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:767">
<![LOG[Executing command line: X:\WINDOWS\system32\cmd.exe /k]LOG]!><time="16:13:57.014+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836" file="bootshell.cpp:767">
<![LOG[The command completed successfully.]LOG]!><time="16:13:57.014+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836" file="bootshell.cpp:850">
<![LOG[Successfully launched command shell.]LOG]!><time="16:13:57.014+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836" file="bootshell.cpp:430">
<![LOG[The command completed successfully.]LOG]!><time="16:14:41.458+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:850">
<![LOG[Starting DNS client service.]LOG]!><time="16:14:41.458+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:597">
<![LOG[Executing command line: X:\sms\bin\i386\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\]LOG]!><time="16:14:41.973+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880"
file="bootshell.cpp:767">
<![LOG[The command completed successfully.]LOG]!><time="16:14:41.973+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:850">
<![LOG[==============================[ TSMBootStrap.exe ]==============================]LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="1" thread="1932"
file="tsmbootstrap.cpp:1039">
<![LOG[Command line: X:\sms\bin\i386\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\]LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="0" thread="1932"
file="tsmbootstrap.cpp:1040">
<![LOG[Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL']LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="1" thread="1932" file="util.cpp:869">
<![LOG[Succeeded loading resource DLL 'X:\sms\bin\i386\TSRESNLC.DLL']LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="1" thread="1932" file="resourceutils.cpp:152">
<![LOG[Processor Is IA64: 0]LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="1" thread="1932" file="tsmbootstrap.cpp:1005">
<![LOG[PXE Boot with Root = X:\]LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="1" thread="1932" file="tsmbootstrap.cpp:921">
<![LOG[Executing from PXE in WinPE]LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="0" thread="1932" file="tsmbootstrap.cpp:936">
<![LOG[Loading TsPxe.dll from X:\sms\bin\i386\TsPxe.dll]LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="0" thread="1932" file="tsmbootstraputil.cpp:1319">
<![LOG[TsPxe.dll loaded]LOG]!><time="16:14:42.004+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932" file="tsmbootstraputil.cpp:1329">
<![LOG[Device has PXE booted]LOG]!><time="16:14:42.004+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932" file="tspxe.cpp:122">
<![LOG[Variable Path: \SMSTemp\2013.12.23.16.11.24.0002.{AB0FBE86-1F6C-47D7-919B-A44641035A2E}.boot.var]LOG]!><time="16:14:42.004+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932"
file="tspxe.cpp:134">
<![LOG[Variable Key Len: 61]LOG]!><time="16:14:42.004+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932" file="tspxe.cpp:141">
<![LOG[Succesfully added firewall rule for Tftp]LOG]!><time="16:14:42.004+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932" file="fwopen.cpp:123">
<![LOG[Executing: X:\sms\bin\i386\smstftp.exe -i XXX.XXX.XXX.XXX get \SMSTemp\2013.12.23.16.11.24.0002.{AB0FBE86-1F6C-47D7-919B-A44641035A2E}.boot.var X:\sms\data\variables.dat]LOG]!><time="16:14:42.004+000" date="12-23-2013"
component="TSPxe" context="" type="0" thread="1932" file="tspxe.cpp:177">
<![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="16:14:42.067+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932" file="commandline.cpp:229">
<![LOG[Set command line: "X:\sms\bin\i386\smstftp.exe" -i XXX.XXX.XXX.XXX get \SMSTemp\2013.12.23.16.11.24.0002.{AB0FBE86-1F6C-47D7-919B-A44641035A2E}.boot.var X:\sms\data\variables.dat]LOG]!><time="16:14:42.067+000" date="12-23-2013"
component="TSPxe" context="" type="0" thread="1932" file="commandline.cpp:707">
<![LOG[Executing command line: "X:\sms\bin\i386\smstftp.exe" -i XXX.XXX.XXX.XXX get \SMSTemp\2013.12.23.16.11.24.0002.{AB0FBE86-1F6C-47D7-919B-A44641035A2E}.boot.var X:\sms\data\variables.dat]LOG]!><time="16:14:42.067+000" date="12-23-2013"
component="TSPxe" context="" type="1" thread="1932" file="commandline.cpp:805">
<![LOG[Process completed with exit code 1]LOG]!><time="16:15:29.179+000" date="12-23-2013" component="TSPxe" context="" type="1" thread="1932" file="commandline.cpp:1102">
<![LOG[Succesfully removed firewall rule for Tftp]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932" file="fwopen.cpp:146">
<![LOG[uExitCode == 0, HRESULT=80004005 (e:\nts_sms_fre\sms\server\pxe\tspxe\tspxe.cpp,185)]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932"
file="tspxe.cpp:185">
<![LOG[Failed to download pxe variable file. Code(0x00000001)]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe" context="" type="3" thread="1932" file="tspxe.cpp:185">
<![LOG[PxeGetPxeData failed with 0x80004005]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe" context="" type="3" thread="1932" file="tsmbootstraputil.cpp:1419">
<![LOG[HRESULT_FROM_WIN32(dwError), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmbootstraputil.cpp,1420)]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe" context=""
type="0" thread="1932" file="tsmbootstraputil.cpp:1420">
<![LOG[TSMBootstrapUtil::PxeGetPxeData(&bPxeBooted, sVariablesFile, sPxePasswd), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2236)]LOG]!><time="16:15:29.194+000" date="12-23-2013"
component="TSPxe" context="" type="0" thread="1932" file="tsmediawizardcontrol.cpp:2236">
<![LOG[oTSMediaWizardControl.Run( sMediaRoot, true, true ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,937)]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe"
context="" type="0" thread="1932" file="tsmbootstrap.cpp:937">
<![LOG[Execute( eExecutionEnv, sConfigPath, sTSXMLFile, uBootCount, &uExitCode ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1106)]LOG]!><time="16:15:29.194+000" date="12-23-2013"
component="TSPxe" context="" type="0" thread="1932" file="tsmbootstrap.cpp:1106">
<![LOG[Exiting with return code 0x80004005]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe" context="" type="1" thread="1932" file="tsmbootstrap.cpp:1118">
<![LOG[Execution complete.]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:624">
<![LOG[Finalizing logging from process 832]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="tslogging.cpp:1736">
<![LOG[Finalizing logs to root of first available drive]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="tslogging.cpp:1578">
<![LOG[LOGGING: Setting log directory to "D:\SMSTSLog".]LOG]!><time="16:15:29.491+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="tslogging.cpp:1803">
This has been an extremely frustrating issue and any assistance would be greatly appreciated!Thanks for your quick response Jason! I didn't expect someone to reply so quickly or I would have checked back sooner.
I had found the two 'older' posts already, but had not seen the 'newer' one. Unfortunately that did not give me any new ideas. But your comment on checking for TFTP availability did. Here are things I have tried since my original
post...
I re-ran most of my tests in case I missed something. I only found one change. Even though I double-checked, I must have made a typo when I manually ran the smstftp.exe command, because when I ran it again I received a timeout message instead
of file not found.
I had a minor 'thinking outside of the box moment' and decided to PXE boot the new 2008 R2 server itself. This was successful and I interpreted the success as meaning that the hardware is ok. Thinking there may be a compatibility issue with
the hardware and the OS, I tried a few different NIC drivers, settings, registry keys, and even a completely different NIC. No luck on any of these.
I decided to build another Server on a VM tovalidate my build process and configuration. And of course clients in multiple locations were able to PXE boot off this VM. Too bad I can't use this in production.
After reading your response Jason, I began to focus on network. I moved the server to a few different locations so it was utilizing different switches. No luck. I noticed in the event viewer for WDS that the server was logging the
beginning of the boot.var file via TFTP. This of course was not very surprising. What was surprising is that the very next entry (informational) noted that the client 'COMPLETED' the download of the boot.var file via TFTP. I know that completed
does not mean successful, but it usually implies or is interpreted as successful. It should have logged a warning or error, or nothing at all because although the process completed, it was not successful. I re-verified that the file was not downloaded
to the client and the client log file still shows the same error noted in the logfile from my original post.
Finally, I installed sniffing software on the server and ran some captures while attempting to PXE boot. Even though I am not much of a network guy, I quickly discovered two things. First, I found the section where the client attempts to download
the boot.var file. Unfortunately I don't think the local security team will allow me to post the capture, so I'll do my best to describe what I found. It starts with a single entry where the client calls for the file via TFTP protocol. This
is followed by a series of alternating entries (all TFTP) where it looks like the server attempts to send a portion of the file, and the client sends an acknowledgement. The sending entries all have checksum errors. The checksum received on
all packets is 0x0000 and of course should be something else. There is also a shorter section below this with alternating entries where the server attempts to send ICMP packets and the client responds with TFTP acknowledgements.
The ICMP entries are all marked as Destination unreachable (Port Unreachable).
The second thing I noticed from the network capture is the a few 'Spanning Tree Protocol' entries. I my search for a solution, I remember reading several posts saying that Spanning Tree can cause this issue. When I asked, I was assured that
Spanning Tree was disabled in this environment. It made sense too, because the 2003 PXE server was functioning properly, and Spanning Tree should affect both 2003 and 2008 servers, right?
Either way I will bring my findings to the network team and see what they have to say.
Any additional thoughts or ideas??? -
Can't open Skype in Surface Pro Tablet
Skype works great on my desktop PC. But I have a problem with my Surface Pro Tablet. There is a Skype App and I can log on to my account.
The Problem:
There is a lot of stuff in the App that I don’t care about, but I don’t see where I can open the Skype page where my contacts are and make calls.As best as I can remember I quit trying to use the App, but went directly to Skype* and logged on to my account and then was able to see my regular Skype page. Hope that helps.
*Google: Type in "Skype my account" and log on. -
Can you PXE Boot WindowsToGo 8.1?
Is it possible to PXE boot WTG across the network? We have PC diagnostics software that exercises computer hardware we want to run on computers all over our network. We prefer to PXE Boot WTG and run this application (Passmark BurninTest). The version of
Passmark BurninTest we want to run supports WTG but we dont want to have USB sticks all over our production floor.
Thanks,
ToddIs it possible to PXE boot WTG across the network?
Hi Todd,
As we all know, a Windows To Go workstation is used when a user inserts the Windows To Go drive into a USB port and starts the host computer, it is based in the USB drive and we can consider that the workstation is stored in the USB.
While as I know, PXE boot obtains IP automatically via DHCP server when the target machine is booted, then the DHCP server provides information about the location of a TFTP server and boot image, target client contacts the TFTP server for
obtaining the boot image, then execute it. so the boot image is stored on the server, it's different from a Windows To go workstation, so I think it is impossible to PXE boot Windows To Go.
Regards
Yolanda Zhu
TechNet Community Support -
Can anyone explain why my surface pro 3 will not accurately use the brush tool in adobe illustrator?
My surface Pro 3 is amazing with photoshop but it cuts in and out using the brush tool in illustrator. Does anyone know of a fix?
Hi Dinar Fresco,
We have seen some issue with n-trig win tab drivers on surface pro 3. Here is a forum post with some solution https://forums.adobe.com/thread/1649008?q=surface%20pro
Sanjay. -
Dual Boot on Surface pro 3 (256GB I7) .. windows 8.1 & W10-Enterprise on VHD
Hi,
has anyone done this? it would assist me greatly in evaluating W10E... I know it would void the warranty, but I can always restore the original.
I am running W10E as VM at the moment but I would like to see how it performs natively ... but I need my W8.1 for work
many thanks
Sepp
Thanks SeppConfiguration for dual boot with VHD boot is the same as with any other UEFI system. Create a VHD, configure it with the GPT partitioning scheme, apply the install.wim from the Windows 10 Technical Preview installation media with DISM and set it to boot
with BCDBoot.
Applying the image is covered here.
Using BCDboot is covered here.
In regards to the warranty, the
Surface warranty FAQ states:
Technical support: Provides help and technical support on preinstalled software for the first 90 days after purchase.
Brandon
Windows Outreach Team- IT Pro
Windows for IT Pros on TechNet -
I can no longer boot up in osx after installing windows 7 with bootcamp
After installing windows 7 with boot camp I am no longer able to access my osx side, I do not receive an option when holding alt when turning on my MacBook
What options do you get? If you don't get any options then you may not be pressing and holding the option key long enough or you are pressing it too early or too late.
-
IOS App 8.1.5 Remote Desktop can't connect to Windows 7 Pro after upgrade. Error 0x00000507
Nothing has changed between my network, Windows 7 computer or my iPad besides the upgrade of the ios app software to 8.1.5. Did not used to have any issues connecting but now when I try to connect, I get the above error when logging in.
I have tried reinstalling the ios app with no success and also confirmed I can still remote desktop to the PC from another PC with the credentials I've always been using.
I've also tried explicitly including the domain when entering the username with no luck. Looked through my Windows 7 event logs and can't find any more information on what this error means.
Has anyone seen anything similar or have any ideas what I can do to troubleshoot? Thanks!Hi,
I have a same problem.
Although RD Client 8.1.4 worked great, now I cannot connect to Windows 7 Professional computer from my iPhone 5 (iOS 6.1.4) since the latest update.
Same as Twiggles, when I try to log in (just after entering username and password), the app gives me error code 0x507 "Disconnected from server".
Note that I connect to my PC over VPN using Cisco AnyConnect app.
After that, I've tried to connect to my PC in two different ways with same network settings as the above situation.
1. Use different remote app
I've tested free version of "PocketCloud" from Dell Wyse, and I CAN connect to my PC.
2. Use different version of iOS
I've tested the latest RD Client 8.1.5 on my another iPhone (5s) with iOS 8.1, and I CAN connect to my PC.
Therefore, I assume our 0x507 is not setting related, but probably some sort of iOS version dependent problem arise from the latest update.
Even though I tried PocketCloud, I believe RD Client is the BEST app for remote desktop for iOS.
I strongly hope this problem will be solved!
Thanks. -
Can I dual boot a macbook pro running Mavericks with Snow Leopard?
I just got a Macbook Pro with quad core i7 with osx 10.9.5 but need to run software that will not run on a system higher that 10.6.8. How can I partition the drive so that I can install these?
There have been discussions in ASC about using a virtualization software to then
run an older 'server version' of Snow Leopard on a partition within a newer Mac...
You can still buy the Server version of Snow Leopard from Apple. Not sure which
virtualization software or utility you'd need to set it up, though; or if you'd also need
to use BootCamp to set-aside a partition as well.
My antiques don't have a feel that sort of thing...
Good luck & happy computing! -
Can't find files on MacBook Pro after airdrop
When I use Airdrop on my iPhone I can hear the file go to my Macbook Pro but can't find it with finder.
Thanks. They were in the download folder, but the name was changed to a number and characters. That is why finder could not find my file.
-
Newbie at using LR. I tried my hand a first of images. I firgured out how to export to JPG but then found that in my LR I no longer had PSD file and all my editing Histroy was gone. I could see the JPG files.
Is there a way to print out (to JPG) incremental changes but still continue to work on the images?
Thnxanpbaba wrote:
...I exported to JPG in my Hard disk. Unitl this point I could see all the edits I made in History and the actual photo showed as a PSD file. After doing the export, when I look at the history it is empty. and the file now shows as a JPG. This means that I cannot build on the previous edits.
Because you're new to Lightroom you might not have noticed that the selected image changed when you exported. But more than that, the selected image source in the catalog changed. In the Library module, I'm sure that when you were editing your PSD file, the folder it was in was selected. But after you do an export, that changes so that it says Previous Export shows in the Catalog panel on the left, and the only contents of the Previous Export is the one JPG, so that's all you can see right now. But if you were to go back and re-select the folder on the left with the PSD in it, you'd see your PSD again. And when you select the PSD, all the edits will be there.
So nothing is lost, it's just that you're now looking at a view that contains only the exported file.
If you exported the JPG to the same folder as the original, you can choose Library > Go to Folder in Library and you'll be back there with both the original and the JPG listed. There are other ways to get back to the preview source like the left Back arrow at the top of the Filmstrip if you have that open. -
Can't edit/see Address Book entries after adding contact image
I added a photo to one of the contacts in Address Book and then all the card info for all contacts disappeared. I still see the names in the "name" list, but I cannot add a new one, edit any of them or do anything. I added the photo from iPhoto and then it seemed to die. Any tips on how to remedy, or at least wipe clean and start over? I thankfully only had three contacts in there (new computer) but I suppose I won't attempt to add any photos in the future. I just need to restart the application somehow and I don't know how to do that. Mac help menu didn't seem to address this at all.
Thanks for any help.
Mac Book Pro Mac OS X (10.4.8)Any chance your BlackBerry connected to an external BES, through your employer?
Or is your device on a personal BIS account?
1. If any post helps you please click the below the post(s) that helped you.
2. Please resolve your thread by marking the post "Solution?" which solved it for you!
3. Install free BlackBerry Protect today for backups of contacts and data.
4. Guide to Unlocking your BlackBerry & Unlock Codes
Join our BBM Channels (Beta)
BlackBerry Support Forums Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code -
Troubleshooting PXE boot issue
SCCM R2 not able to PXE boot from Surface pro. I am new to environment. How can I tell if PXE broadcasts are making it to device and to sccm ? I recieve the following output in CMTRACE in SMSPXE.log .. Am I doing something completely wrong ?
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16781189" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID=""
LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
Mjsmspxe.log will display the MAC address if the broadcast reached the server.
You have to use Wireshark or Netmon if you want to find out if the response reaches the client.
Torsten Meringer | http://www.mssccmfaq.de -
Problems PXE booting Gen 2 Virtual Machines after Upgrading to Windows Server 2012 R2
My Current Setup:
I have two virtual machines set up with Hyper V on my Windows Server 2012 Server.
VM1: Configured to boot from an ISO file and runs Clonezilla server.
VM2: Configured to PXE boot using a legacy network adapter, and with a passthrough 250Gb hard disk.
These two VMs are connected to an external Virtual Switch, which allows physical machines to PXE boot to the Clonezilla server.
For the past few months I have been using this setup for two purposes:
1. To clone physical machines to the Clonezilla virtual server (as a backup).
2. To restore those image to the second VM if I find that need to get access to the files on the original image..
This has worked perfectly, except for the fact that the speed of the legacy network adapter on the second VM (which is required to PXE boot) is very slow. But I know this is because of the limitations in how the legacy adapter works...
Now my problem:
I found out that Gen 2 VMs allow you to PXE boot without having use a legacy network adapter, allowing me to image back to the VM faster. So I upgraded the Server to Server 2012 R2 . I then created the same two virtual machines on the R2 server. I can still
PXE boot the Gen 1 VM to the Clonezilla Server but I cannot get the Gen 2 VMs to PXE boot properly. They get an IP address from the Clonezilla Server but then just stop with the following screen. (note: I have disabled the Secure Boot).
Are Gen 2 VMs unable to pull down images from anything other than a WDS Server?Hi J,
>>Unfortunately WDS is not a solution for us as it is dependent on the PC being part of a domain
If you would like to make the client not join to the domain, please check the box before “Do not join the client to a domain after an installation.” In addition, make sure not to set the client to the domain in the unattend file and do not prestage
the computer in AD. "
It is quoted from following thread :
https://social.technet.microsoft.com/Forums/windowsserver/en-US/1026c3a9-0a10-4a58-a48f-5391659a96c8/wds-set-unattend-file-for-workgroup?forum=winserversetup
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.
Maybe you are looking for
-
For 3 days I've had little to no Internet Access on my Samsumg Galaxy S4 in Bon Air Virginia (23235)
What's going on in the 23235 area code? No data connection for 3 days.
-
My ipod classic has a white screen
my ipod classic has a white screen
-
Why are the Apple mods deleting and locking threads?
I would like an answer as to why the mods are deleting and locking threads that have to do with the error that pervasive in the iPod 1.1 upgrade. It seems that Apple will not acknowledge it but some of us are trying to find an answer and Apple locks
-
Adobephotoshop CS5.1 installation problem.
Hello all, Good day!! I am trying to install adobe photoshop CS 5.1 but am failing. After being installed for 98% it shows error and says that it could not install all the component such as: PS.And the error log is as fol: Exit Code: 6 --------------
-
IMac screen pixelated and unreadable at startup...what's going on?
This morning when I started my computer for the day, I noticed that the wallpaper was very pixelated, almost like a transparent Photoshop layer. When I moved the cursor all I saw was a pixelated box and I was unable to interact with any folders/icon