Unable to Windows Update and WSUS brokenProblem with WSUS databaseWSUS appears to be functioning, however errors are reported in Application Log (DSS Authentication Web Service is not working)Using WSUS to update machines not on the domainMS WSUS 3 not detecting PCs in All ComputersWindows Server Update Services (WSUS) 3.0 SP2 not installing successfully on SBS 2003 SP2WSUS console : Unable to connect to server from wsus consoleSCCM SUP cannot connect with WSUS Server - WSUS Server version 3.0 SP2 or above is not installedWindows 10 can't reach WSUS with GPOCan't access WSUS console from local system; can access it from another host?WSUS stuck at 98%
Copy previous line to current line from text file
What is the solution to this metapuzzle from a university puzzling column?
How do LIGO and VIRGO know that a gravitational wave has its origin in a neutron star or a black hole?
Gerrymandering Puzzle - Rig the Election
Has a commercial or military jet bi-plane ever been manufactured?
What does this wavy downward arrow preceding a piano chord mean?
Will 700 more planes a day fly because of the Heathrow expansion?
Has the Hulk always been able to talk?
Why are UK Bank Holidays on Mondays?
Word meaning as function of the composition of its phonemes
Is there an official reason for not adding a post-credits scene?
How can I roleplay a follower-type character when I as a player have a leader-type personality?
How can I get a job without pushing my family's income into a higher tax bracket?
Pressure inside an infinite ocean?
US born but as a child of foreign diplomat
What does 'made on' mean here?
Decoupling cap routing on a 4 layer PCB
Do publishers care if submitted work has already been copyrighted?
Why do people keep telling me that I am a bad photographer?
How can I get people to remember my character's gender?
Out of scope work duties and resignation
How should I tell my manager I'm not paying for an optional after work event I'm not going to?
What to use instead of cling film to wrap pastry
IP addresses from public IP block in my LAN
Unable to Windows Update and WSUS broken
Problem with WSUS databaseWSUS appears to be functioning, however errors are reported in Application Log (DSS Authentication Web Service is not working)Using WSUS to update machines not on the domainMS WSUS 3 not detecting PCs in All ComputersWindows Server Update Services (WSUS) 3.0 SP2 not installing successfully on SBS 2003 SP2WSUS console : Unable to connect to server from wsus consoleSCCM SUP cannot connect with WSUS Server - WSUS Server version 3.0 SP2 or above is not installedWindows 10 can't reach WSUS with GPOCan't access WSUS console from local system; can access it from another host?WSUS stuck at 98%
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
for a while now, despite working faultlessly for over 3 years, both WSUS and Windows Update have stopped working on our single domain contoller running Windows Server 2008 (not R2).
The error we get when trying to run Windows Update is "80072efd" which of course we've Google'd and tends to point to a firewall issue. We're inclined to believe this isn't the problem, as there are a couple of standalone PC's on the network here that aren't part of the domain and as such don't use the DC as a source for updates which connect through to Windows Update just fine. As all connections are routed the same way this would suggest the firewall is not at fault, and also the age old saying of "nothing has been changed on the firewall" - which it hasn't to prompt this sudden stoppage on the DC and subsequent domain machines.
Also, whilst investigating, I've noticed the WSUS snap-in doesn't load anymore, just prompts for "Reset Server Node" which doesn't work. Further to this I've taken a look in IIS and can see the WSUS Administration "site" it stopped. I cannot restart it as it says another site is using that port, which from what I can tell within IIS is not the case. We only have 2 sites in IIS and one uses 80 and the other, WSUS Administration, uses 8530/1.
I've also tried removing and upping the limits on WsusPool in the Recyling tab as a technet post suggested this could be the cause, but even after restarting IIS - nothing. I presume this is all related to Windows Update not working either but can't be sure.
I have attached below the error from the WSUS snap-in:
The WSUS administration console was unable to connect to the WSUS Server via the remote API.
Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.
The WSUS administration console was unable to connect to the WSUS Server via the remote API.
Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.
System.Net.Sockets.SocketException -- No connection could be made because the target machine actively refused it 10.0.0.253:8530
Source
System
Stack Trace:
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)
** this exception was nested inside of the following exception **
System.Net.WebException -- Unable to connect to the remote server
Source
Microsoft.UpdateServices.Administration
Stack Trace:
at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)
at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
at Microsoft.UpdateServices.UI.AdminApiAccess.AdminApiTools.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.GetUpdateServer(PersistedServerSettings settings)
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServer()
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServerAndPopulateNode(Boolean connectingServerToConsole)
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.OnExpandFromLoad(SyncStatus status)
Server was rebooted last night to take care of SQL/IIS and the update service but to no avail.
Any pointers greatly appreciated. Much as I hate to say it, the server has been running since 2013 and WSUS and all domain PC's have been updating wonderfully until it seems one fateful day when, from what we can tell, no conscious changes were made at all.
windows-server-2008 iis sql wsus
asked Jul 13 '17 at 8:53
fRAiLtY-fRAiLtY-
2317
add a comment |
for a while now, despite working faultlessly for over 3 years, both WSUS and Windows Update have stopped working on our single domain contoller running Windows Server 2008 (not R2).
The error we get when trying to run Windows Update is "80072efd" which of course we've Google'd and tends to point to a firewall issue. We're inclined to believe this isn't the problem, as there are a couple of standalone PC's on the network here that aren't part of the domain and as such don't use the DC as a source for updates which connect through to Windows Update just fine. As all connections are routed the same way this would suggest the firewall is not at fault, and also the age old saying of "nothing has been changed on the firewall" - which it hasn't to prompt this sudden stoppage on the DC and subsequent domain machines.
Also, whilst investigating, I've noticed the WSUS snap-in doesn't load anymore, just prompts for "Reset Server Node" which doesn't work. Further to this I've taken a look in IIS and can see the WSUS Administration "site" it stopped. I cannot restart it as it says another site is using that port, which from what I can tell within IIS is not the case. We only have 2 sites in IIS and one uses 80 and the other, WSUS Administration, uses 8530/1.
I've also tried removing and upping the limits on WsusPool in the Recyling tab as a technet post suggested this could be the cause, but even after restarting IIS - nothing. I presume this is all related to Windows Update not working either but can't be sure.
I have attached below the error from the WSUS snap-in:
The WSUS administration console was unable to connect to the WSUS Server via the remote API.
Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.
The WSUS administration console was unable to connect to the WSUS Server via the remote API.
Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.
System.Net.Sockets.SocketException -- No connection could be made because the target machine actively refused it 10.0.0.253:8530
Source
System
Stack Trace:
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)
** this exception was nested inside of the following exception **
System.Net.WebException -- Unable to connect to the remote server
Source
Microsoft.UpdateServices.Administration
Stack Trace:
at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)
at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
at Microsoft.UpdateServices.UI.AdminApiAccess.AdminApiTools.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.GetUpdateServer(PersistedServerSettings settings)
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServer()
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServerAndPopulateNode(Boolean connectingServerToConsole)
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.OnExpandFromLoad(SyncStatus status)
Server was rebooted last night to take care of SQL/IIS and the update service but to no avail.
Any pointers greatly appreciated. Much as I hate to say it, the server has been running since 2013 and WSUS and all domain PC's have been updating wonderfully until it seems one fateful day when, from what we can tell, no conscious changes were made at all.
windows-server-2008 iis sql wsus
asked Jul 13 '17 at 8:53
fRAiLtY-fRAiLtY-
2317
WSUS isn't supported when running on a Domain Controller, and as such, my recommendation would be that you move it to another server.
– joeqwerty
Jul 13 '17 at 11:19
add a comment |
for a while now, despite working faultlessly for over 3 years, both WSUS and Windows Update have stopped working on our single domain contoller running Windows Server 2008 (not R2).
The error we get when trying to run Windows Update is "80072efd" which of course we've Google'd and tends to point to a firewall issue. We're inclined to believe this isn't the problem, as there are a couple of standalone PC's on the network here that aren't part of the domain and as such don't use the DC as a source for updates which connect through to Windows Update just fine. As all connections are routed the same way this would suggest the firewall is not at fault, and also the age old saying of "nothing has been changed on the firewall" - which it hasn't to prompt this sudden stoppage on the DC and subsequent domain machines.
Also, whilst investigating, I've noticed the WSUS snap-in doesn't load anymore, just prompts for "Reset Server Node" which doesn't work. Further to this I've taken a look in IIS and can see the WSUS Administration "site" it stopped. I cannot restart it as it says another site is using that port, which from what I can tell within IIS is not the case. We only have 2 sites in IIS and one uses 80 and the other, WSUS Administration, uses 8530/1.
I've also tried removing and upping the limits on WsusPool in the Recyling tab as a technet post suggested this could be the cause, but even after restarting IIS - nothing. I presume this is all related to Windows Update not working either but can't be sure.
I have attached below the error from the WSUS snap-in:
The WSUS administration console was unable to connect to the WSUS Server via the remote API.
Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.
The WSUS administration console was unable to connect to the WSUS Server via the remote API.
Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.
System.Net.Sockets.SocketException -- No connection could be made because the target machine actively refused it 10.0.0.253:8530
Source
System
Stack Trace:
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)
** this exception was nested inside of the following exception **
System.Net.WebException -- Unable to connect to the remote server
Source
Microsoft.UpdateServices.Administration
Stack Trace:
at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)
at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
at Microsoft.UpdateServices.UI.AdminApiAccess.AdminApiTools.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.GetUpdateServer(PersistedServerSettings settings)
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServer()
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServerAndPopulateNode(Boolean connectingServerToConsole)
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.OnExpandFromLoad(SyncStatus status)
Server was rebooted last night to take care of SQL/IIS and the update service but to no avail.
Any pointers greatly appreciated. Much as I hate to say it, the server has been running since 2013 and WSUS and all domain PC's have been updating wonderfully until it seems one fateful day when, from what we can tell, no conscious changes were made at all.
windows-server-2008 iis sql wsus
asked Jul 13 '17 at 8:53
fRAiLtY-fRAiLtY-
2317
for a while now, despite working faultlessly for over 3 years, both WSUS and Windows Update have stopped working on our single domain contoller running Windows Server 2008 (not R2).
The error we get when trying to run Windows Update is "80072efd" which of course we've Google'd and tends to point to a firewall issue. We're inclined to believe this isn't the problem, as there are a couple of standalone PC's on the network here that aren't part of the domain and as such don't use the DC as a source for updates which connect through to Windows Update just fine. As all connections are routed the same way this would suggest the firewall is not at fault, and also the age old saying of "nothing has been changed on the firewall" - which it hasn't to prompt this sudden stoppage on the DC and subsequent domain machines.
Also, whilst investigating, I've noticed the WSUS snap-in doesn't load anymore, just prompts for "Reset Server Node" which doesn't work. Further to this I've taken a look in IIS and can see the WSUS Administration "site" it stopped. I cannot restart it as it says another site is using that port, which from what I can tell within IIS is not the case. We only have 2 sites in IIS and one uses 80 and the other, WSUS Administration, uses 8530/1.
I've also tried removing and upping the limits on WsusPool in the Recyling tab as a technet post suggested this could be the cause, but even after restarting IIS - nothing. I presume this is all related to Windows Update not working either but can't be sure.
I have attached below the error from the WSUS snap-in:
The WSUS administration console was unable to connect to the WSUS Server via the remote API.
Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.
The WSUS administration console was unable to connect to the WSUS Server via the remote API.
Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.
System.Net.Sockets.SocketException -- No connection could be made because the target machine actively refused it 10.0.0.253:8530
Source
System
Stack Trace:
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)
** this exception was nested inside of the following exception **
System.Net.WebException -- Unable to connect to the remote server
Source
Microsoft.UpdateServices.Administration
Stack Trace:
at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)
at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
at Microsoft.UpdateServices.UI.AdminApiAccess.AdminApiTools.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.GetUpdateServer(PersistedServerSettings settings)
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServer()
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServerAndPopulateNode(Boolean connectingServerToConsole)
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.OnExpandFromLoad(SyncStatus status)
Server was rebooted last night to take care of SQL/IIS and the update service but to no avail.
Any pointers greatly appreciated. Much as I hate to say it, the server has been running since 2013 and WSUS and all domain PC's have been updating wonderfully until it seems one fateful day when, from what we can tell, no conscious changes were made at all.
windows-server-2008 iis sql wsus
windows-server-2008 iis sql wsus
asked Jul 13 '17 at 8:53
fRAiLtY-fRAiLtY-
2317
asked Jul 13 '17 at 8:53
fRAiLtY-fRAiLtY-
2317
asked Jul 13 '17 at 8:53
fRAiLtY-fRAiLtY-
2317
asked Jul 13 '17 at 8:53
fRAiLtY-fRAiLtY-
2317
asked Jul 13 '17 at 8:53
fRAiLtY-fRAiLtY-
2317
2317
WSUS isn't supported when running on a Domain Controller, and as such, my recommendation would be that you move it to another server.
– joeqwerty
Jul 13 '17 at 11:19
add a comment |
WSUS isn't supported when running on a Domain Controller, and as such, my recommendation would be that you move it to another server.
– joeqwerty
Jul 13 '17 at 11:19
WSUS isn't supported when running on a Domain Controller, and as such, my recommendation would be that you move it to another server.
– joeqwerty
Jul 13 '17 at 11:19
WSUS isn't supported when running on a Domain Controller, and as such, my recommendation would be that you move it to another server.
– joeqwerty
Jul 13 '17 at 11:19
add a comment |
2 Answers
2
active
oldest
votes
Well it's sorted now. I can't remember when setting it up if http and https protocols (8530 and 8531) were both in there, however I've removed 8531 as it wasn't attempting to use that port anyway and the IIS website now starts, the WSUS control panel starts and all machines are back receiving updates.
Hope this helps someone.
answered Jul 13 '17 at 15:29
fRAiLtY-fRAiLtY-
2317
add a comment |
I just had this exact same issue while trying to setup WSUS to use SSL.
In IIS Manager, Navigate to the WSUS Administration Site and select SSL Settings:
IIS Manager
Make sure that require SSL is not checked and Ignore Client Certificates, click on Apply
Configure SSL Settings
answered Sep 20 '18 at 20:04
DanDan
1
Is this a scenario to recreate the issue? Or to actually solve it?
– Pierre.Vriens
Sep 20 '18 at 20:07
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f861926%2funable-to-windows-update-and-wsus-broken%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Well it's sorted now. I can't remember when setting it up if http and https protocols (8530 and 8531) were both in there, however I've removed 8531 as it wasn't attempting to use that port anyway and the IIS website now starts, the WSUS control panel starts and all machines are back receiving updates.
Hope this helps someone.
answered Jul 13 '17 at 15:29
fRAiLtY-fRAiLtY-
2317
add a comment |
Well it's sorted now. I can't remember when setting it up if http and https protocols (8530 and 8531) were both in there, however I've removed 8531 as it wasn't attempting to use that port anyway and the IIS website now starts, the WSUS control panel starts and all machines are back receiving updates.
Hope this helps someone.
answered Jul 13 '17 at 15:29
fRAiLtY-fRAiLtY-
2317
add a comment |
Well it's sorted now. I can't remember when setting it up if http and https protocols (8530 and 8531) were both in there, however I've removed 8531 as it wasn't attempting to use that port anyway and the IIS website now starts, the WSUS control panel starts and all machines are back receiving updates.
Hope this helps someone.
answered Jul 13 '17 at 15:29
fRAiLtY-fRAiLtY-
2317
Well it's sorted now. I can't remember when setting it up if http and https protocols (8530 and 8531) were both in there, however I've removed 8531 as it wasn't attempting to use that port anyway and the IIS website now starts, the WSUS control panel starts and all machines are back receiving updates.
Hope this helps someone.
answered Jul 13 '17 at 15:29
fRAiLtY-fRAiLtY-
2317
answered Jul 13 '17 at 15:29
fRAiLtY-fRAiLtY-
2317
answered Jul 13 '17 at 15:29
fRAiLtY-fRAiLtY-
2317
answered Jul 13 '17 at 15:29
fRAiLtY-fRAiLtY-
2317
2317
add a comment |
add a comment |
I just had this exact same issue while trying to setup WSUS to use SSL.
In IIS Manager, Navigate to the WSUS Administration Site and select SSL Settings:
IIS Manager
Make sure that require SSL is not checked and Ignore Client Certificates, click on Apply
Configure SSL Settings
answered Sep 20 '18 at 20:04
DanDan
1
Is this a scenario to recreate the issue? Or to actually solve it?
– Pierre.Vriens
Sep 20 '18 at 20:07
add a comment |
I just had this exact same issue while trying to setup WSUS to use SSL.
In IIS Manager, Navigate to the WSUS Administration Site and select SSL Settings:
IIS Manager
Make sure that require SSL is not checked and Ignore Client Certificates, click on Apply
Configure SSL Settings
answered Sep 20 '18 at 20:04
DanDan
1
Is this a scenario to recreate the issue? Or to actually solve it?
– Pierre.Vriens
Sep 20 '18 at 20:07
add a comment |
I just had this exact same issue while trying to setup WSUS to use SSL.
In IIS Manager, Navigate to the WSUS Administration Site and select SSL Settings:
IIS Manager
Make sure that require SSL is not checked and Ignore Client Certificates, click on Apply
Configure SSL Settings
answered Sep 20 '18 at 20:04
DanDan
1
I just had this exact same issue while trying to setup WSUS to use SSL.
In IIS Manager, Navigate to the WSUS Administration Site and select SSL Settings:
IIS Manager
Make sure that require SSL is not checked and Ignore Client Certificates, click on Apply
Configure SSL Settings
answered Sep 20 '18 at 20:04
DanDan
1
answered Sep 20 '18 at 20:04
DanDan
1
answered Sep 20 '18 at 20:04
DanDan
1
answered Sep 20 '18 at 20:04
DanDan
1
1
Is this a scenario to recreate the issue? Or to actually solve it?
– Pierre.Vriens
Sep 20 '18 at 20:07
add a comment |
Is this a scenario to recreate the issue? Or to actually solve it?
– Pierre.Vriens
Sep 20 '18 at 20:07
Is this a scenario to recreate the issue? Or to actually solve it?
– Pierre.Vriens
Sep 20 '18 at 20:07
Is this a scenario to recreate the issue? Or to actually solve it?
– Pierre.Vriens
Sep 20 '18 at 20:07
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f861926%2funable-to-windows-update-and-wsus-broken%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
WSUS isn't supported when running on a Domain Controller, and as such, my recommendation would be that you move it to another server.
– joeqwerty
Jul 13 '17 at 11:19