talksr Posted February 4, 2016 Posted February 4, 2016 Hi there, I set up WSUS a while back, but I am noticing that I have a total of 32 computers (which is wrong, we have around 80), and all of them are showing as "The computer has not reported status yet" None of them have a firewall enabled and they all pick up the following policy... Our FRDC is \\stm-sr-001. \\stm-sr-002 is a domain member server 2008r2 used for Sophos EC, BE 2015 and WSUS. A little confused as to what the issue could be here?
sted Posted February 4, 2016 Posted February 4, 2016 try using ip rather than name. also check that the d:\wsus (or whereever it is) has correct permissions iirc users(local not domain) read network service\system full control
3s-gtech Posted February 4, 2016 Posted February 4, 2016 (edited) I always found that it liked having the port specified, though it should be running on port 80 on 2008 R2 it may be worth prompting the client in the GPO. http://servername:80. Server 2012 onwards use 8530. Edited February 4, 2016 by 3s-gtech
talksr Posted February 4, 2016 Author Posted February 4, 2016 try using ip rather than name. also check that the d:\wsus (or whereever it is) has correct permissions iirc users(local not domain) read network service\system full control Ok, thanks very much will give it a go. Do you think I should just put IP. If I browse to IP, I get the following folders (not sure if I should include the IP and folder in the path on Group Policy)... Data SophosUpdate SUMInstallSet Update Manager UpdateServicesPackages WsusContent WSUSTemp
sted Posted February 4, 2016 Posted February 4, 2016 gpo shoukd be something like set the Intranet update server for detecting updates http://10.10.10.10:8530 set the Intranet statistics server http://10.10.10.10:8530 1
3s-gtech Posted February 4, 2016 Posted February 4, 2016 If your DNS is working well it should make no difference, but it won't do any harm unless you have some complex IIS configuration in place (which I doubt). 1
sted Posted February 4, 2016 Posted February 4, 2016 If your DNS is working well it should make no difference, but it won't do any harm unless you have some complex IIS configuration in place (which I doubt). ive had it if you use a pac file just be a bit odd about name ip seemed to solve it with minimal changes 1
talksr Posted February 4, 2016 Author Posted February 4, 2016 Ok, thanks everyone, I have changed them both to: http://10.75.44.11:8530 Is there an easy way I can check if it is now working? DNS should be fine, any way of checking it's ok?
talksr Posted February 4, 2016 Author Posted February 4, 2016 At the moment, I am getting the following Windows Update error on my clients when I attempt to run an Manual Windows Update by clicking on Check for Updates: Fault bucket , type 0 Event Name: WindowsUpdateFailure3 Response: Not available Cab Id: 0 Problem signature: P1: 7.6.7601.19077 P2: 80244010 P3: 00000000-0000-0000-0000-000000000000 P4: Scan P5: 0 P6: 1 P7: 0 P8: AutomaticUpdates P9: {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} P10: 0 Attached files: These files may be available here: Analysis symbol: Rechecking for solution: 0 Report Id: 192d1edf-cb2d-11e5-93e0-e0946709f26e Report Status: 0
3s-gtech Posted February 4, 2016 Posted February 4, 2016 Port 8530 should only be used on Server 2012 an on. Your Server 2008 R2 server should be accessed on 80 unless you configured it to be elsewhere when you set it up. 1
talksr Posted February 4, 2016 Author Posted February 4, 2016 Port 8530 should only be used on Server 2012 an on. Your Server 2008 R2 server should be accessed on 80 unless you configured it to be elsewhere when you set it up. Sorry, my mistake, it is a 2012 server, but I posted in the wrong section of the forum.
3s-gtech Posted February 4, 2016 Posted February 4, 2016 https://blogs.technet.microsoft.com/sus/2008/09/18/wsus-clients-fail-with-warning-syncserverupdatesinternal-failed-0x80244010/ You may have a massive backlog of updates, so you need to keep checking over and over. Have a read.
talksr Posted February 4, 2016 Author Posted February 4, 2016 https://blogs.technet.microsoft.com/sus/2008/09/18/wsus-clients-fail-with-warning-syncserverupdatesinternal-failed-0x80244010/ You may have a massive backlog of updates, so you need to keep checking over and over. Have a read. Ok I have set the automatic update checking frequency, but I notice that on the system I am on now (Win 7) it has been doing updates between 11/6/15 to 17/12/15 Almost all updates have failed since 15/10/2015, which would have been about the time WSUS was installed.
3s-gtech Posted February 4, 2016 Posted February 4, 2016 That would fit, as your port setting was wrong before. 1
talksr Posted February 4, 2016 Author Posted February 4, 2016 That would fit, as your port setting was wrong before. Ok. I have tried clicking check for updates, many, many times, but just keep getting the same error. What can I do next?
3s-gtech Posted February 4, 2016 Posted February 4, 2016 Do you have many updates approved in WSUS? Or do you just have it set to auto-approve?
talksr Posted February 4, 2016 Author Posted February 4, 2016 Do you have many updates approved in WSUS? Or do you just have it set to auto-approve? All have been approved
newpersn Posted February 4, 2016 Posted February 4, 2016 All have been approved Wont they be started to be download to the Server? Ours take a few hours before they get pushed to computers.
talksr Posted February 4, 2016 Author Posted February 4, 2016 Wont they be started to be download to the Server? Ours take a few hours before they get pushed to computers. When I checked today, there was just one. There are thousands and thousands of ones I approved months ago, so no don't think it is to do with download times.
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