So here is an interesting problem...
We have a WDS running on WS2008R2 but want to remove it as the MDT on this server is obsolete (was used for Windows 7) and we have a new MDT for Windows 10 on a newer WS2012R2 (yes, I will upgrade this one as well).
PXE boots is working like a charm with the current WDS but when I try to move this service by installing a new WS2019 (also tried this with WS2016) no matter what we do (part from IP-helpers that is - they are not I place now so why
would I really need them?) there is no f**king way the WDS responds to PXE...
The only thing I have to do in order to have the original one stop responding is stopping the service and then again start it when I want it to respond...
How do I get the new WS2019 WDS to respond instead?
Obviously it doesn't do any good in stopping the service on old server and start it on the new one. Yes, I've tried this even with latency in the test - meaning I have waited a full 24 hours before I attempted an PXE-boot towards the new one.
Obviously it doesn't do any good in stopping the service on old server and start it on the new one. Yes, I've tried this even with latency in the test - meaning I have waited a full 24 hours before I attempted an PXE-boot towards the new one.
Stupid ideas that have come during error processing are as follows:
Is there possibly an issue with domain level? We're still on 2008R2... UEFI PXE-booting is currently working in all of our network, so this is why we have not gotten our noses into IP-helpers.
I have probably missed out on something we have tried here, but this is the general idea and problem...
Anyone? Something?