Copyright © 2019 - PrajwalDesai.Com All Rights Reserved.
Today one of the engineer reported a PXE error while imaging the laptops. The error was SCCM OSD error PXE-T04 Access violation. The engineer mentioned that OSD was working fine previously. However there were no changes done to distribution nor the DHCP server configuration. Note that this remote site has got multiple VLAN’s. There are few VLAN’s where the OSD is restricted. In other words OSD won’t work in such VLAN’s. As this issue occurred in a remote site, I had to simulate or test this in a virtual setup. Creating a new Hyper-V VM in remote site and PXE booting it showed the following error.
PXE-T04: Access Violation
PXE-E36: Error Received from TFTP Server
How to fix SCCM OSD Error PXE-T04 Access Violation
My first assumption was this issue could be related to DHCP server configuration. Therefore I checked the DHCP scope, options 66, 67 and all these were fine. I also ensured that Windows Deployment service was up and running. If you browse for error PXE-T04, most of the forum threads and posts tell you that it’s due to incorrect DHCP configuration. The solution suggested is to configure IP helper (BOOTP) settings on the routers or configure DHCP scope options. However in my case the DHCP configuration was very much correct. The network team told me that there were no changes done at all. I tested the OSD in multiple VLAN’s and the error was same in all the tests.
I had to login back to the remote distribution point server and see if I could get any clue over there. Finally I decided to uncheck the PXE and multicast from remote DP properties. Rebooted the distribution point server. Enabled PXE and multicast back on DP. After few minutes I tried PXE boot and to my luck the OSD started working fine. So a small trick fixed my issue. If something else worked for you, feel free to post it in comments.