Constant WSUS issues (Connection Errors)
-
We've got ~500 systems on 8GB of RAM with 2vCPUs.
-
I get the error posted in the OP every now and again from the WSUS console on my Win10 PC. A reset always reconnects it.
-
I have a VM with 2vCPU and 8 GB of RAM for WSUS and about 250 devices.
-
Holy crap... I don't understand why it keeps getting disconnected or why it's chugging along. Although, it's reconnected now and seems to be stable.
One other question for you guys: What do you do about other non-Microsoft updates, like Java and Adobe. Does WSUS cover any of that at all?
-
@dave247 said in Constant WSUS issues (Connection Errors):
Holy crap... I don't understand why it keeps getting disconnected or why it's chugging along. Although, it's reconnected now and seems to be stable.
One other question for you guys: What do you do about other non-Microsoft updates, like Java and Adobe. Does WSUS cover any of that at all?
I've used a combination of pdq inventory and pdq deploy for managing 3rd party updates
-
@irj said in Constant WSUS issues (Connection Errors):
@dave247 said in Constant WSUS issues (Connection Errors):
Holy crap... I don't understand why it keeps getting disconnected or why it's chugging along. Although, it's reconnected now and seems to be stable.
One other question for you guys: What do you do about other non-Microsoft updates, like Java and Adobe. Does WSUS cover any of that at all?
I've used a combination of pdq inventory and pdq deploy for managing 3rd party updates
We have DesktopCentral. I guess I will keep using that for 3rd party updates as well as some software deployment.
-
@dave247 said in Constant WSUS issues (Connection Errors):
Well crap... I'm back to having that connection error again. I only have about 8 computers added to WSUS and I've deselected a bunch of products and classifications I didn't really need. Should I consider increasing the private memory limit and queue lengths again?
I haven't had the connection error since I made those changes Tim_G suggested I make to the WSUS resource pool. It's worth mentioning that the server has been pretty slow since adding the WSUS role. I literally have nothing else running on this system and it's a dual six-core processors (@ 2.20 GHz) and 56.0 GB of memory. I thought this would be sufficient..
Maybe it's busy downloading every available update.
I made sure to set it to only download approved updates. That's saves so much space and bandwidth.
But yeah that's way overkill on server resources. I use similar to what others mentioned with over 600 managed devices.
I've been doing WSUS for years and don't have these issues. The only issue I had cleared up and never came back... the one I said earlier.
-
@tim_g said in Constant WSUS issues (Connection Errors):
@dave247 said in Constant WSUS issues (Connection Errors):
Well crap... I'm back to having that connection error again. I only have about 8 computers added to WSUS and I've deselected a bunch of products and classifications I didn't really need. Should I consider increasing the private memory limit and queue lengths again?
I haven't had the connection error since I made those changes Tim_G suggested I make to the WSUS resource pool. It's worth mentioning that the server has been pretty slow since adding the WSUS role. I literally have nothing else running on this system and it's a dual six-core processors (@ 2.20 GHz) and 56.0 GB of memory. I thought this would be sufficient..
Maybe it's busy downloading every available update.
I made sure to set it to only download approved updates. That's saves so much space and bandwidth.
But yeah that's way overkill on server resources. I use similar to what others mentioned with over 600 managed devices.
I've been doing WSUS for years and don't have these issues. The only issue I had cleared up and never came back... the one I said earlier.
ok I will look to set that option.. I'm sure I messed up somewhere in there..
-
@dave247 said in Constant WSUS issues (Connection Errors):
@tim_g said in Constant WSUS issues (Connection Errors):
@dave247 said in Constant WSUS issues (Connection Errors):
Well crap... I'm back to having that connection error again. I only have about 8 computers added to WSUS and I've deselected a bunch of products and classifications I didn't really need. Should I consider increasing the private memory limit and queue lengths again?
I haven't had the connection error since I made those changes Tim_G suggested I make to the WSUS resource pool. It's worth mentioning that the server has been pretty slow since adding the WSUS role. I literally have nothing else running on this system and it's a dual six-core processors (@ 2.20 GHz) and 56.0 GB of memory. I thought this would be sufficient..
Maybe it's busy downloading every available update.
I made sure to set it to only download approved updates. That's saves so much space and bandwidth.
But yeah that's way overkill on server resources. I use similar to what others mentioned with over 600 managed devices.
I've been doing WSUS for years and don't have these issues. The only issue I had cleared up and never came back... the one I said earlier.
ok I will look to set that option.. I'm sure I messed up somewhere in there..
Yeah, a server busy doing downloads/catalog updates, etc can definitely cause it to be sluggish. You also need to do weekly if not daily maintenance on WSUS (or use the scripts posted on SW) to keep WSUS tight.
-
@tim_g said in Constant WSUS issues (Connection Errors):
@dave247 said in Constant WSUS issues (Connection Errors):
Well crap... I'm back to having that connection error again. I only have about 8 computers added to WSUS and I've deselected a bunch of products and classifications I didn't really need. Should I consider increasing the private memory limit and queue lengths again?
I haven't had the connection error since I made those changes Tim_G suggested I make to the WSUS resource pool. It's worth mentioning that the server has been pretty slow since adding the WSUS role. I literally have nothing else running on this system and it's a dual six-core processors (@ 2.20 GHz) and 56.0 GB of memory. I thought this would be sufficient..
Maybe it's busy downloading every available update.
I made sure to set it to only download approved updates. That's saves so much space and bandwidth.
Ah, according to your guide (which I followed) you said to un-check that option:
-
@dave247 said in Constant WSUS issues (Connection Errors):
@tim_g said in Constant WSUS issues (Connection Errors):
@dave247 said in Constant WSUS issues (Connection Errors):
Well crap... I'm back to having that connection error again. I only have about 8 computers added to WSUS and I've deselected a bunch of products and classifications I didn't really need. Should I consider increasing the private memory limit and queue lengths again?
I haven't had the connection error since I made those changes Tim_G suggested I make to the WSUS resource pool. It's worth mentioning that the server has been pretty slow since adding the WSUS role. I literally have nothing else running on this system and it's a dual six-core processors (@ 2.20 GHz) and 56.0 GB of memory. I thought this would be sufficient..
Maybe it's busy downloading every available update.
I made sure to set it to only download approved updates. That's saves so much space and bandwidth.
Ah, according to your guide (which I followed) you said to un-check that option:
Yes, but if you want a feature, use it. I ended up checking it.
-
I still haven't been able to get WSUS to work. Such bullshit. Luckily I have my 3rd party tool that I can depend on...
-
@dave247 said in Constant WSUS issues (Connection Errors):
I still haven't been able to get WSUS to work. Such bullshit. Luckily I have my 3rd party tool that I can depend on...
So strange, never had this problem like this yet.
-
How about starting over from scratch.
Delete the GPOs you made
format the host you made (rebuild it as a Hyper-V or KVM then install a VM of 2016, etc)
create new GPOs, but limit it to a small testing scope
then expand. -
@dave247 said in Constant WSUS issues (Connection Errors):
I still haven't been able to get WSUS to work. Such bullshit. Luckily I have my 3rd party tool that I can depend on...
That's odd... it's always just worked whenever I've set it up.
What exactly isn't working?
-
@dashrender said in Constant WSUS issues (Connection Errors):
How about starting over from scratch.
Delete the GPOs you made
format the host you made (rebuild it as a Hyper-V or KVM then install a VM of 2016, etc)
create new GPOs, but limit it to a small testing scope
then expand.Yeah I've started over from scratch 3 different times and no dice. 3 completely different servers. And it's not like it's my firewall because wsus has actually downloaded updates and installed some.
-
@dave247 said in Constant WSUS issues (Connection Errors):
@dashrender said in Constant WSUS issues (Connection Errors):
How about starting over from scratch.
Delete the GPOs you made
format the host you made (rebuild it as a Hyper-V or KVM then install a VM of 2016, etc)
create new GPOs, but limit it to a small testing scope
then expand.Yeah I've started over from scratch 3 different times and no dice. 3 completely different servers. And it's not like it's my firewall because wsus has actually downloaded updates and installed some.
but did you start over with the GPOs?
-
Bringing up my dead post here...
I recently looked back into this with my Group Policy and I noticed that I had a GPO that had this setting enabled: "Computer Conf > Policies > Admin Temps > System/Internet Communication Management/Internet Communication settings > Turn off access to all Windows Update features" and this was set to Enabled. I am wondering if this perhaps played a part with my WSUS server's continual connection error...
Here is the descritpion, "If you enable this policy setting, all Windows Update features are removed. This includes blocking access to the Windows Update website at http://windowsupdate.microsoft.com, from the Windows Update hyperlink on the Start menu, and also on the Tools menu in Internet Explorer. Windows automatic updating is also disabled; you will neither be notified about nor will you receive critical updates from Windows Update. This policy setting also prevents Device Manager from automatically installing driver updates from the Windows Update website."
According to the description, it is removing access to the Windows Update site, but it doesn't say anything in there about a local WSUS server.. so I would think a local WSUS would still work even if this setting is enabled.
Anyway, I am removing this setting and will try WSUS out again. I temporarily gave up on the project as I had continual connection issues, despite following technet setup guides and attempting to install the role on 3 different servers in an attempt to get it working. All failed..
-
@dave247 said in Constant WSUS issues (Connection Errors):
Bringing up my dead post here...
I recently looked back into this with my Group Policy and I noticed that I had a GPO that had this setting enabled: "Computer Conf > Policies > Admin Temps > System/Internet Communication Management/Internet Communication settings > Turn off access to all Windows Update features" and this was set to Enabled. I am wondering if this perhaps played a part with my WSUS server's continual connection error...
Here is the descritpion, "If you enable this policy setting, all Windows Update features are removed. This includes blocking access to the Windows Update website at http://windowsupdate.microsoft.com, from the Windows Update hyperlink on the Start menu, and also on the Tools menu in Internet Explorer. Windows automatic updating is also disabled; you will neither be notified about nor will you receive critical updates from Windows Update. This policy setting also prevents Device Manager from automatically installing driver updates from the Windows Update website."
According to the description, it is removing access to the Windows Update site, but it doesn't say anything in there about a local WSUS server.. so I would think a local WSUS would still work even if this setting is enabled.
Anyway, I am removing this setting and will try WSUS out again. I temporarily gave up on the project as I had continual connection issues, despite following technet setup guides and attempting to install the role on 3 different servers in an attempt to get it working. All failed..
Hopefully that will be it.
-
@dbeato said in Constant WSUS issues (Connection Errors):
@dave247 said in Constant WSUS issues (Connection Errors):
Bringing up my dead post here...
I recently looked back into this with my Group Policy and I noticed that I had a GPO that had this setting enabled: "Computer Conf > Policies > Admin Temps > System/Internet Communication Management/Internet Communication settings > Turn off access to all Windows Update features" and this was set to Enabled. I am wondering if this perhaps played a part with my WSUS server's continual connection error...
Here is the descritpion, "If you enable this policy setting, all Windows Update features are removed. This includes blocking access to the Windows Update website at http://windowsupdate.microsoft.com, from the Windows Update hyperlink on the Start menu, and also on the Tools menu in Internet Explorer. Windows automatic updating is also disabled; you will neither be notified about nor will you receive critical updates from Windows Update. This policy setting also prevents Device Manager from automatically installing driver updates from the Windows Update website."
According to the description, it is removing access to the Windows Update site, but it doesn't say anything in there about a local WSUS server.. so I would think a local WSUS would still work even if this setting is enabled.
Anyway, I am removing this setting and will try WSUS out again. I temporarily gave up on the project as I had continual connection issues, despite following technet setup guides and attempting to install the role on 3 different servers in an attempt to get it working. All failed..
Hopefully that will be it.
Actually, now that I think about it (after several hours of posting this and over a month since the original post) I believe the WSUS server was in an OU which had that GPO applied, thus I assume it was unable to reach windowsupdate.microsoft.com. Seems obvious to me now after such an unacceptably long time. Good lord I should let go for incompetence.
