WSUS - Server 2012 R2
-
@tim_g said in WSUS - Server 2012 R2:
@dustinb3403 said in WSUS - Server 2012 R2:
@tim_g said in WSUS - Server 2012 R2:
@dustinb3403 said in WSUS - Server 2012 R2:
@momurda said in WSUS - Server 2012 R2:
@dustinb3403 said in WSUS - Server 2012 R2:
When I just go to https://localhost I get a Http Error 404.0 - Not Found page.
Are you using https? If so, 8530 isnt the right port. 8531 is for https connections in wsus.
You should also just login to the server and restart the wsus services.I'm attempting to fix it as it's never worked (since my hire here) and finally I've got some time to dig into it.
Attempting to access either 8530 nor 8531 works.
If you didn't deploy it, and it's been f**ked since you've been there... just redeploy it on another VM or something if you have a license.
That is a part of the issue, I literally have no other options.
There's no other Windows server you can stick it on until you get it sorted out?
Nothing capable, even in the slightest.
-
@dustinb3403 said in WSUS - Server 2012 R2:
@tim_g said in WSUS - Server 2012 R2:
@dustinb3403 said in WSUS - Server 2012 R2:
@tim_g said in WSUS - Server 2012 R2:
@dustinb3403 said in WSUS - Server 2012 R2:
@momurda said in WSUS - Server 2012 R2:
@dustinb3403 said in WSUS - Server 2012 R2:
When I just go to https://localhost I get a Http Error 404.0 - Not Found page.
Are you using https? If so, 8530 isnt the right port. 8531 is for https connections in wsus.
You should also just login to the server and restart the wsus services.I'm attempting to fix it as it's never worked (since my hire here) and finally I've got some time to dig into it.
Attempting to access either 8530 nor 8531 works.
If you didn't deploy it, and it's been f**ked since you've been there... just redeploy it on another VM or something if you have a license.
That is a part of the issue, I literally have no other options.
There's no other Windows server you can stick it on until you get it sorted out?
Nothing capable, even in the slightest.
Looks like a non-starter then. Put your time somewhere else, or a WSUS alternative.
-
@tim_g said in WSUS - Server 2012 R2:
@dustinb3403 said in WSUS - Server 2012 R2:
@tim_g said in WSUS - Server 2012 R2:
@dustinb3403 said in WSUS - Server 2012 R2:
@tim_g said in WSUS - Server 2012 R2:
@dustinb3403 said in WSUS - Server 2012 R2:
@momurda said in WSUS - Server 2012 R2:
@dustinb3403 said in WSUS - Server 2012 R2:
When I just go to https://localhost I get a Http Error 404.0 - Not Found page.
Are you using https? If so, 8530 isnt the right port. 8531 is for https connections in wsus.
You should also just login to the server and restart the wsus services.I'm attempting to fix it as it's never worked (since my hire here) and finally I've got some time to dig into it.
Attempting to access either 8530 nor 8531 works.
If you didn't deploy it, and it's been f**ked since you've been there... just redeploy it on another VM or something if you have a license.
That is a part of the issue, I literally have no other options.
There's no other Windows server you can stick it on until you get it sorted out?
Nothing capable, even in the slightest.
Looks like a non-starter then. Put your time somewhere else, or a WSUS alternative.
You may just have to reboot the damn thing... or reinstall WSUS. If you just can't, then how are you doing server maintenance?
-
Enable the Hyper-V role, install another instance of Windows Server and setup WSUS there :smiling_face_with_halo:
-
@crustachio said in WSUS - Server 2012 R2:
Enable the Hyper-V role, install another instance of Windows Server and setup WSUS there :smiling_face_with_halo:
I might take you out back and beat you like a redheaded stepchild. . .
-
When did wsus stop working? before you started working there?
What does your iis mmc look like? wsus is just a website with a sql db.
-
@momurda As far as I know it hasn't worked since before I started.
-
@dustinb3403 Oh, that screen shows that wsus isnt installed correctly, if at all. That isnt what wsus should look like in iis.
That looks like someone installed wsus, then went into IIS and erased the website from IIS. -
@momurda said in WSUS - Server 2012 R2:
@dustinb3403 Oh, that screen shows that wsus isnt installed correctly, if at all. That isnt what wsus should look like in iis.
That looks like someone installed wsus, then went into IIS and erased the website from IIS.Any simple fix that you can think of? (reinstall the whole damn thing)
I know. . .
-
@dustinb3403 said in WSUS - Server 2012 R2:
@momurda As far as I know it hasn't worked since before I started.
Oh wow, yeah you are missing the WSUS website lol...
-
@dustinb3403 Remove then add the role again is all i know of. I cant remember if that requires a restart or not.
-
@momurda said in WSUS - Server 2012 R2:
@dustinb3403 Remove then add the role again is all i know of. I cant remember if that requires a restart or not.
I'm pretty certain it does, because I have to remove it (reboot to cleanup, stupid windows) and then install it.
-
@dustinb3403 said in WSUS - Server 2012 R2:
@momurda said in WSUS - Server 2012 R2:
@dustinb3403 Remove then add the role again is all i know of. I cant remember if that requires a restart or not.
I'm pretty certain it does, because I have to remove it (reboot to cleanup, stupid windows) and then install it.
You can still try it without rebooting. It doesn't force you to reboot. If you need to, reboot it when there are no users to be impacted. Or tell your boss the server is pending a reboot to get Windows Updates working for the company and that you need to schedule it.
-
I went back though my notes and I think this is the same thing Tim said, but don't have the time to check. Here are my screen shots:
-
Yea will have to reboot to complete it. . .
-
Use WSUS Offline for now
http://download.wsusoffline.net/A VM on a Windows 10 workstation might do go and then move it to a server if you wanted to test it. How many devices are we talking about here that will connect to WSUS?
-
I've had this happen on multiple occasions. The system was configured to use the internal windows database instead of sql, and there were too many records so the refreshes and etc. would take forever, or you'd get the reset server node issue. After I migrated the database to sql, the problem mostly went away. It still occurs on slow connections.
