does bis-f do anything during the preparation or personalization phase that might impact dhcp/dns settings or network adapters? specifically on server 2025, after sealing an image and creating a new catalog, these vm's are hit or miss when coming online and registering. we notice that there are no dns servers listed and the dhcp server is 255.255.255.255. reboot the servers (sometimes several times) and it might register. these vm's are hosted in azure
If we do not seal with bis-f, then we are not seeing this issue which is why we are wondering. We also do not see this on server 2019 when using bis-f. so there might be some compatibility thing?