I manage a small network with ~ 80 win PCs. Fog has been a real challenge and tremendous help (before and after it worked). However: I’m still learning.
So I came across a very weird behavious, and I’d like to have some inputs on this issue.
The schools network is basically devided in two big rooms. One (locally) very close to the physical fog server, connected with 100GBit, another - connected through an other single 1GBit / 100Mbit network switch - a bit further away.
I was able to successfully create multicast sessions in the second room, deploying a win 10 1909 image to 25 PCs, without any problems - until … Windows started to configure itself with several reboots. About 15 of he 25 machines got stuck with the message:
Windows setup could not configure to run on this computer’s hardware
The other 10 machines worked well. All the PCs have the same hardware (HP), and the testing of the imageing process worked well.
So I was desperate and tried to image some machines one by one: Unfortunately with the same result. After several hours of research for this kind of error message I decided to give up.
Well, one last try I was willing to make, to find the error. I took one machine to the other room and started the imaging process.
Guess what: It worked without any error. So the soultion was to move each single computer to the other room and do the imaging. Every single machine worked flawlessly.
So how crazy is that?
Any comments? I’d really like to hear your oppinions.
I’m sure it is a windows issue, but it may well be caused by the different network connection. So I don’t know where to put this question…
However: any ideas how to track this down and solve it? I’d like to do imaging without moving machines…