Can the appserver resolve the new target name ?
yup, all hostnames were resolvable, we even updated etc/hosts with all target IPs
This was the weird part, during provisioning the auto enrollment failed, but after we canceled the provision job and manually added the new VM to managed servers list, it enrolled w/o a problem.
1 of 1 people found this helpful
so the original behavior w/o the bmi files on the datastore root was that the target never registered and the job never finished ? i believe that's expected if the bmi files are not present. once the files were there, are things working ?
yes, the prov job never finished and the target never registered, the target just installed the agent and skipped to login screen, very quickly. After placing the bmi files back into pxestore, the provisioning finished normally and enrolled the target.