Hello,
We're having an issue with the WSUS server that we have in place running on Windows Server 2012 R2. All the other machines detected and few of the imaged machines detected but at least 4 in a row machines did not get detected. I'm not too sure what that could be, I see no error logs in the event viewer. The computers are not on the domain, we've used local group policy. Now with the sysprep the unique identifier is different on every PC, that shouldn't be a problem. I've done the the following to look and detect for new clients.
I'm wondering what could be the problem and what is some of the information that I can provide with to check further on this matter.
Another quick question,
I came across one post which I am curious is true in regards to the WSUS as I am new to it: "Updates -- real updates like cumulative updates -- should have no adverse effect
on Sysprep. The problem, like stated above, is that upgrades (e.g., from 10240 to 10586) will cause Sysprep to no longer work. If you want to maintain an updated image, you have to recreate your image every time a new build is released." (https://community.spiceworks.com/topic/1423559-windows-10-sysprep-update-confusion)
Is that true? if that's the case, there's really not much of a point of the WSUS Server. Would I still be able to update to a new build but then after that it wouldn't work?
Thanks!
