Showing posts with label PXE. Show all posts
Showing posts with label PXE. Show all posts

Wednesday, December 19, 2012

PXE-E53: No boot filename received

PXE-E53: No boot filename received

everythink ok.. when checked
- Both the Boot Images are sent to WDS

Found one red Event in the application Events with event ID 258

executed below command to resolve the issue..

wdsutil /initialize-server /REMINST:"E:\remoteinstall"

Saturday, March 24, 2012

PXE Client How will find the PXE Server

 

 

The process is roughly as below:

 

1. Client powers on
2. NIC initiates PXE process
3. NIC acquires DHCP address
4. NIC contacts PXE server (WDS)
5. PXE server delivers NBP to client
6. NIC TFTPs boot image (from WDS)

4 This can be couple of different ways. If the DHCP request returned options 66 and 67, then the NIC BIOS will directly use the information in these options to contact the PXE server.

If options 66 & 67 are not specified, then the NIC BIOS will send a broadcast request to find a PXE server.

If the PXE server is not on a local subnet, then something needs to forward the broadcast request to the PXE server: iphelpers (there are other possibilities but this is the primary solution to this).

Once the PXE server is contacted, it sends back the info to the client so the client can directly contact the PXE server.

Wednesday, January 25, 2012

PXE-T00: Unspecified file opening error detected

Found the error: While deploying 7 with the SCCM 2007 and MDT 2010.

sccm PXE-T00: Unspecified file opening error detected
PXE-E36:Error Received from TFTP server

 

image

Solution:This is not related to SCCM / WDS Issue.. it was with Symantec Ghost caused the issue, once the service was stopped the issue is resolved.

Thursday, October 20, 2011

Error information 0xC1030104


Add the following to your DHCP scope options:if you want to use DHCP Scope options
066 Boot Server Host Name - DNS name of PXE server
067 Bootfile Name - smsboot\x86\wdsnbp.com

For not to listen the DHCP on Ports (WDS Port & DHCP Ports are same so you must execute this registry change),...............

WDSUTIL /Set-Server /UseDHCPPorts:No /DHCPOption60:Yes

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSPXE

Set the registry value to:

UseDHCPPorts = 0

For the new configuration to take effect run the following command on the co-located DHCP and WDS server:

WDSUTIL /Set-Server /UseDHCPPorts:No /DHCPOption60:Yes
then i got below error 0xC1030104..........


When the error 0xC1030104 i encounter i executed below and resolved this error.

This error was appeared after i configured my SCCM PXE server not to USE DHCP ports

wdsutil /initialize-server /REMINST:"D:\remoteinstall"

even this was not resolved on few servers then i went for clean uninstall and install the PXE point.. then it worked