Why aren't my clients populating in WSUS Computer Groups
I recently set up WSUS 3.0 in my Domain. I have the following websites required and recommended steps and none of my computers are populating into the group created and pointed to within the GPO's. They dont populate anywhere. When I try to access my WSUS server by going to http://servername OR http://servername:8530 niether work, the only difference is the 8530 site says it requires you to log in to view the web site. What am I missing here?
http://blog.augustoalvarez.com.ar/2008/12/12/wsus-30-deployment-and-first-configurations-part-i/
http://blogs.microsoft.co.il/blogs/yanivf/archive/2007/09/23/install-wsus-3-0-step-by-step.aspx
Thanks for your help and support!
http://blog.augustoalvarez.com.ar/2008/12/12/wsus-30-deployment-and-first-configurations-part-i/
http://blogs.microsoft.co.il/blogs/yanivf/archive/2007/09/23/install-wsus-3-0-step-by-step.aspx
Thanks for your help and support!
dj_relentless
What other IIS sites do you have configured on the WSUS server?
ASKER
An Onsite Manager website for our monitoring software. They are a client of ours that we monitor all events on their domain. We cant move it to another server for lack of equipment reasons so they have to be on the same server and have not had any problems in the past combining the two. Thoughts?
So on the wsus server. What port is the wsus site running on? (check the site properties)
Also what URL did you type in for the wsus update group policy you created?
Also what URL did you type in for the wsus update group policy you created?
ASKER
You should definately be using http://servername:8530
Download the diag tool and we'll start looking at it from the clients pov.
http://download.microsoft.com/download/9/7/6/976d1084-d2fd-45a1-8c27-a467c768d8ef/WSUS%20Client%20Diagnostic%20Tool.EXE
Download the diag tool and we'll start looking at it from the clients pov.
http://download.microsoft.com/download/9/7/6/976d1084-d2fd-45a1-8c27-a467c768d8ef/WSUS%20Client%20Diagnostic%20Tool.EXE
check and see that windows firewall on the server is not blocking you. open up port 8530 to test if it is not already excluded.
I have had the same problem in the past. I had to double check the permissions on the web services directories and IIS. I thought I had done everything correctly, but after going through these documents again, I was able to resolve the issues.
Web Services Permissions: http://technet.microsoft.com/en-us/library/cc708487(WS.10).aspx
IIS Settings: http://technet.microsoft.com/en-us/library/cc708487(WS.10).aspx
Web Services Permissions: http://technet.microsoft.com/en-us/library/cc708487(WS.10).aspx
IIS Settings: http://technet.microsoft.com/en-us/library/cc708487(WS.10).aspx
"I have tried both http://servername and http://servername:8530"
Wsus 3.0 doesnt use the web browser anymore, you need to go to Start>>>Administrative tools>>>Microsoft Windows Server Update Services. Or you could create an MMC.
Wsus 3.0 doesnt use the web browser anymore, you need to go to Start>>>Administrative tools>>>Microsoft Windows Server Update Services. Or you could create an MMC.
ASKER
baddevildog82 - those are the same links....
dstewartjr - I was told if I could not access it from the website url at the client pc then it wouldnt work. I have been using the link in admin tools.
dstewartjr - I was told if I could not access it from the website url at the client pc then it wouldnt work. I have been using the link in admin tools.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Verify your client settings with clientdiag
http://download.microsoft.com/download/9/7/6/976d1084-d2fd-45a1-8c27-a467c768d8ef/WSUS%20Client%20Diagnostic%20Tool.EXE
http://download.microsoft.com/download/9/7/6/976d1084-d2fd-45a1-8c27-a467c768d8ef/WSUS%20Client%20Diagnostic%20Tool.EXE