"PXE-T04: Access Violation Error Received from TFTP Server"

当利用WDS进行系统部署或使用系统中心配置管理器去跨子网通过PXE引导客户裸机,则可能会出现以下错误：

PXE-T04: Access Violation
PXE-E36: Error Received from TFTP Server
PXE-M-F Exiting PXE Rom

这可能发生在试图从虚拟机的PXE或物理机的引导,您可能还注意到在PXE服务点上的客户端你是从PXE引导服务器SMSPXE.log缺乏的条目，这表明客户端永远不会接触的PXE服务点。
这种情况可能发生在一个DHCP问题.
可能需要配置路由器的IP助手（BOOTP）,设置或配置适当的DHCP作用域选项。但如果设置的配置不当,这也可能发生.

(This can occur when trying to PXE Boot from a Virtual Machine or Physical Machine.  You may also notice a lack of entries in the SMSPXE.log on the PXE Service Point Server from the clients you are PXE booting, indicating that the client never contacts the PXE Service Point.

Cause:
This can occur do to an issue with DHCP.

Resolution:
You may need to configure IP Helper (BOOTP) settings on the router or configure the DHCP Scope Options as appropriate.  This can also occur if the settings are configured improperly.  
For example, looking at a network capture you might notice that the PXE Boot File path being passed to the client from the DHCP Offer packet is something like \smsboot\x86\name.com which indicates that the PXE Boot File Path is not getting passed correctly from the DHCP Scope Options on the DHCP server.  This can occur with some Linux DHCP server appliances unless the path is specified as such:
\\smsboot\\x86\\name.com 
Some DHCP servers require double backslashes for the Boot File Name Scope Option so if you configure it using standard UNC naming conventions (e.g. \\smsboot\x86\name.com) it can fail in this manner.)