1 of 1 people found this helpful
This is populated once connectivity via populate properties from the appserver to the agent is established.
I have seen this problem when the servers use DHCP. It seems that they are then not registered in DNS in time for the app server to be able to establish a connection to them for the update properties request using the hostname.
Try adding an update properties job (possibly with a short delay) as your first job in the post-provisioning batch job.
Both of these answers are fitting with what we're seeing in the environment. We've also recently made some changes to how DNS is delivered to the PXE server, so this is our primary focus area for fix now. Thank you both very much.