I had to use a different port for my WSUS setup, so client machines have to point to http://WSUSservername:8530
Then ran GPUPDATE /FORCE on all client machines and now they're checking in. Roger Wright Network Administrator Evatone, Inc. 727.572.7076 x388 _____ From: KC Carter [mailto:[EMAIL PROTECTED] Sent: Friday, October 31, 2008 10:50 AM To: NT System Admin Issues Subject: WSUS 3.0 SP1 I installed WSUS 3.0 SP1 and created the GPO to point the client computers to the WSUS server yesterday morning. I only have 7 computers out of 171 showing up and my concern is the client side targeting URL that I am using is hosting another website that I was not aware of. When I installed IIS component of WSUS I used the default settings and that URL was already being used for an intranet site. My question is does it matter if that URL http://servername <http://servername/> is being used? Can I change the settings in IIS to something else or would it just be easier to reinstall and change it there? My GPO for my clients point to htt://servername and I checked the registry on a dozen computers and it's pointed correctly but not showing up in the WSUS console. Thanks, KC Carter System Administrator 302-734-1450 [EMAIL PROTECTED] ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
