Your new "OS Imaging" module completely kills Windows Deployment Services (WDS)
Hello,
I have been using use Desktop Central on a Windows 2012 R2 server that is also using WSUS, MDT and especially WDS - for allowing my Windows 10 client machines to do OS upgrades and to allow new computers to use PXE boot to get the latest Windows 10 image for use.
I have not had to use WDS for several months as all machines are solid on Windows 1709. But with the new Spring Creator Update coming soon (V1803) - I wanted to begin preparations for deploying a new upgrade image using WDS.
When I logged into my server last night - I noticed a long string of errors messages (in Event Viewer) indicating that my WDS service could not be started. After several hours of investigation - it dawned on me that it's DesktopCentral and it's new OS Imaging module that most likely causing the issues.
I do remember "activating" this module several months ago when it first appeared but had no indication that it would interfere with the existing WDS service. Within the errors I am getting - it's seems that WDS needs Port 69 exclusively to start a UDP session (for PXE boot)
I have been using use Desktop Central on a Windows 2012 R2 server that is also using WSUS, MDT and especially WDS - for allowing my Windows 10 client machines to do OS upgrades and to allow new computers to use PXE boot to get the latest Windows 10 image for use.
I have not had to use WDS for several months as all machines are solid on Windows 1709. But with the new Spring Creator Update coming soon (V1803) - I wanted to begin preparations for deploying a new upgrade image using WDS.
When I logged into my server last night - I noticed a long string of errors messages (in Event Viewer) indicating that my WDS service could not be started. After several hours of investigation - it dawned on me that it's DesktopCentral and it's new OS Imaging module that most likely causing the issues.
I do remember "activating" this module several months ago when it first appeared but had no indication that it would interfere with the existing WDS service. Within the errors I am getting - it's seems that WDS needs Port 69 exclusively to start a UDP session (for PXE boot)
But after some analysis - it's looks like DesktopCentral (Java.exe) is stealing Port 69 now for it's own use. And I can only assume it's doing this to facilitate use of it's own OS Imaging/PXE functions.
While I am not married to using WDS (and am willing to remove it if necessary) - I need to know if DesktopCentrals OS Imaging module will allow me to take my existing OS images - ALL created using MDT - and deploy them per usual - instead of using WDS.
If this can be done - then I will remove WDS from the server and carry on with DesktopCentral and it's PXE boot functions.
Appreciate an update when you are able.
Cheers,
Bruce
While I am not married to using WDS (and am willing to remove it if necessary) - I need to know if DesktopCentrals OS Imaging module will allow me to take my existing OS images - ALL created using MDT - and deploy them per usual - instead of using WDS.
If this can be done - then I will remove WDS from the server and carry on with DesktopCentral and it's PXE boot functions.
Appreciate an update when you are able.
Cheers,
Bruce