Sheridan Posted June 15, 2017 Posted June 15, 2017 After setting up SUS on a 2016 server (I know, I'm a sucker for punishment!) I realised that it was still dhcp, so I set the lan card to a fixed IP. Oh Oh, bad idea, WSUS is now broken! It can't synchronize any more and after much searching around it seems a full uninstall and reinstall of wsus is required. You can really tell 2016 server is based on W10! So beware changing ip or lan card after wsus install, it breaks it!
Sheridan Posted June 15, 2017 Author Posted June 15, 2017 Actually - correction, once you do this WSUS is completely broken, even uninstalling it and reinstalling doesn't work. Only a reinstall of the server! Otherwise you will get stuck on the http error! Time to bin WSUS and just use home updating methods I think
woreilly Posted June 26, 2017 Posted June 26, 2017 After setting up SUS on a 2016 server (I know, I'm a sucker for punishment!) I realised that it was still dhcp, so I set the lan card to a fixed IP. Oh Oh, bad idea, WSUS is now broken! It can't synchronize any more and after much searching around it seems a full uninstall and reinstall of wsus is required. You can really tell 2016 server is based on W10! So beware changing ip or lan card after wsus install, it breaks it! Could you not have just changed the DHCP Lease to a reservation for your WSUS server? 1
pete Posted June 26, 2017 Posted June 26, 2017 Have you checked IIS hasn't bound to the old IP and you need to manually point it to the new one?
Sheridan Posted July 3, 2017 Author Posted July 3, 2017 Changing up back to what it was didn't fix the problem, it really screwed up Wsus! In the end I did a reinstall on the new IP address.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now