Re: WSUS Clients not Appearing in Admin Console

Target groups won't help if your clients can't register with WSUS which if
they could would already be showing up.

I believe the problem is with the client proxy configuration;

Checking Proxy Configuration
> Checking for winhttp local machine Proxy settings . . . PASS
> Winhttp local machine access type
> <Direct Connection>
> Winhttp local machine Proxy. . . . . . . . . . NONE
> Winhttp local machine ProxyBypass. . . . . . . NONE
> Checking User IE Proxy settings . . . . . . . . . . . . PASS
> User IE Proxy
> w2ksvr1:8080
> User IE ProxyByPass
> <local>
> User IE AutoConfig URL Proxy
> http://w2ksvr1:8080/array.dll?Get.Routing.Script
> User IE AutoDetect
> AutoDetect in use
>
> Checking Connection to WSUS/SUS Server
> WUServer = http://w2ksvr1:8530
> WUStatusServer = http://w2ksvr1:8530
> UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
>
> VerifyWUServerURL() failed with hr=0x80072ee5
>
> The URL is invalid

Cross posting to the WSUS group for help.

--
/kj
"Bill Glidden" <billyg1943@hotmail.com> wrote in message
news:u4rXRHpaGHA.4360@TK2MSFTNGP05.phx.gbl...
> How do I set up targeted groups, please.
>
> "Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]" <sbradcpa@pacbell.net>
> wrote in message news:O%23plxJoaGHA.996@TK2MSFTNGP04.phx.gbl...
>> Either untick "compression" on the IIS web site or use "targeted" groups
>> to get them to check in
>>
>> Bill Glidden wrote:
>>> Sorry, this was also posted in update_services by mistake!
>>>
>>> I have Googled and looked at threads here but still can't see why this
>>> new
>>> install of WSUS has a problem adding clients to the admin console. I
>>> have
>>> installed WSUS at three different sites and this is the first one to
>>> have
>>> this problem. The admin console is working fine and I have synchronised
>>> with
>>> Microsoft. The SBS 2003 SP1 Prem Edition is fully patched. ISA 2004
>>> SP2,
>>> SQL 2000 SP4, Exchange 2003 SP1. All client PCs are XP Pro SP2. I have
>>> followed:
>>> "Step-by-Step Guide to Getting Started with Microsoft Windows Server
>>> Update
>>> Services on Windows Small Business Server 2003
>>> Microsoft Corporation
>>> Published: December 2005 (Version 2)
>>> Author: Tim Elhajj"
>>> The install completed without errors. I have checked RSOP on
>>> workstations
>>> and can see the Group Policy has been applied. I can also connect to
>>> http://servername:8530/wsusadmin from the workstations. I get "HTTP
>>> Error
>>> 403 - Forbidden" if I try to connect to http://servername:8530 > I have
>>> checked and rechecked the settings for the Default Web
>>> Site\ClientWebService
>>> & Selfupdate. Both are set for anonymous access and all computers are
>>> granted access. What could possibly be wrong?
>>> Internet Explorer
>>>
>>>
>>>
>
>

Thanks, kj.

I'm so used to WSUS just working I am at a loss when it doesn't : -(

Cheers,
Bill

"kj" <kj@nowhere.com> wrote in message
news:%23wbBF4vaGHA.4544@TK2MSFTNGP02.phx.gbl...
> Target groups won't help if your clients can't register with WSUS which if
> they could would already be showing up.
>
> I believe the problem is with the client proxy configuration;
>
> Checking Proxy Configuration
>> Checking for winhttp local machine Proxy settings . . . PASS
>> Winhttp local machine access type
>> <Direct Connection>
>> Winhttp local machine Proxy. . . . . . . . . . NONE
>> Winhttp local machine ProxyBypass. . . . . . . NONE
>> Checking User IE Proxy settings . . . . . . . . . . . . PASS
>> User IE Proxy
>> w2ksvr1:8080
>> User IE ProxyByPass
>> <local>
>> User IE AutoConfig URL Proxy
>> http://w2ksvr1:8080/array.dll?Get.Routing.Script
>> User IE AutoDetect
>> AutoDetect in use
>>
>> Checking Connection to WSUS/SUS Server
>> WUServer = http://w2ksvr1:8530
>> WUStatusServer = http://w2ksvr1:8530
>> UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
>>
>> VerifyWUServerURL() failed with hr=0x80072ee5
>>
>> The URL is invalid
>
> Cross posting to the WSUS group for help.
>
> --
> /kj
> "Bill Glidden" <billyg1943@hotmail.com> wrote in message
> news:u4rXRHpaGHA.4360@TK2MSFTNGP05.phx.gbl...
>> How do I set up targeted groups, please.
>>
>> "Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]" <sbradcpa@pacbell.net>
>> wrote in message news:O%23plxJoaGHA.996@TK2MSFTNGP04.phx.gbl...
>>> Either untick "compression" on the IIS web site or use "targeted" groups
>>> to get them to check in
>>>
>>> Bill Glidden wrote:
>>>> Sorry, this was also posted in update_services by mistake!
>>>>
>>>> I have Googled and looked at threads here but still can't see why this
>>>> new
>>>> install of WSUS has a problem adding clients to the admin console. I
>>>> have
>>>> installed WSUS at three different sites and this is the first one to
>>>> have
>>>> this problem. The admin console is working fine and I have synchronised
>>>> with
>>>> Microsoft. The SBS 2003 SP1 Prem Edition is fully patched. ISA 2004
>>>> SP2,
>>>> SQL 2000 SP4, Exchange 2003 SP1. All client PCs are XP Pro SP2. I have
>>>> followed:
>>>> "Step-by-Step Guide to Getting Started with Microsoft Windows Server
>>>> Update
>>>> Services on Windows Small Business Server 2003
>>>> Microsoft Corporation
>>>> Published: December 2005 (Version 2)
>>>> Author: Tim Elhajj"
>>>> The install completed without errors. I have checked RSOP on
>>>> workstations
>>>> and can see the Group Policy has been applied. I can also connect to
>>>> http://servername:8530/wsusadmin from the workstations. I get "HTTP
>>>> Error
>>>> 403 - Forbidden" if I try to connect to http://servername:8530 > I have
>>>> checked and rechecked the settings for the Default Web
>>>> Site\ClientWebService
>>>> & Selfupdate. Both are set for anonymous access and all computers are
>>>> granted access. What could possibly be wrong?
>>>> Internet Explorer
>>>>
>>>>
>>>>
>>
>>
>
>

My Dear brother the problem is very simple . the computer on which you have
installed that computer must have a windowsxp or windows 2003 . you plz OFF
the firewall of winxp/2003 builtin than all computers will start appearing
in the admin Console.
And as well tell me if I dont want to OFF the firewall of WinXP/2003 than
which port I will open in the WinXP/2003 built-in Firewall.

"kj" wrote:

> Target groups won't help if your clients can't register with WSUS which if
> they could would already be showing up.
>
> I believe the problem is with the client proxy configuration;
>
> Checking Proxy Configuration
> > Checking for winhttp local machine Proxy settings . . . PASS
> > Winhttp local machine access type
> > <Direct Connection>
> > Winhttp local machine Proxy. . . . . . . . . . NONE
> > Winhttp local machine ProxyBypass. . . . . . . NONE
> > Checking User IE Proxy settings . . . . . . . . . . . . PASS
> > User IE Proxy
> > w2ksvr1:8080
> > User IE ProxyByPass
> > <local>
> > User IE AutoConfig URL Proxy
> > http://w2ksvr1:8080/array.dll?Get.Routing.Script
> > User IE AutoDetect
> > AutoDetect in use
> >
> > Checking Connection to WSUS/SUS Server
> > WUServer = http://w2ksvr1:8530
> > WUStatusServer = http://w2ksvr1:8530
> > UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
> >
> > VerifyWUServerURL() failed with hr=0x80072ee5
> >
> > The URL is invalid
>
> Cross posting to the WSUS group for help.
>
> --
> /kj
> "Bill Glidden" <billyg1943@hotmail.com> wrote in message
> news:u4rXRHpaGHA.4360@TK2MSFTNGP05.phx.gbl...
> > How do I set up targeted groups, please.
> >
> > "Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]" <sbradcpa@pacbell.net>
> > wrote in message news:O%23plxJoaGHA.996@TK2MSFTNGP04.phx.gbl...
> >> Either untick "compression" on the IIS web site or use "targeted" groups
> >> to get them to check in
> >>
> >> Bill Glidden wrote:
> >>> Sorry, this was also posted in update_services by mistake!
> >>>
> >>> I have Googled and looked at threads here but still can't see why this
> >>> new
> >>> install of WSUS has a problem adding clients to the admin console. I
> >>> have
> >>> installed WSUS at three different sites and this is the first one to
> >>> have
> >>> this problem. The admin console is working fine and I have synchronised
> >>> with
> >>> Microsoft. The SBS 2003 SP1 Prem Edition is fully patched. ISA 2004
> >>> SP2,
> >>> SQL 2000 SP4, Exchange 2003 SP1. All client PCs are XP Pro SP2. I have
> >>> followed:
> >>> "Step-by-Step Guide to Getting Started with Microsoft Windows Server
> >>> Update
> >>> Services on Windows Small Business Server 2003
> >>> Microsoft Corporation
> >>> Published: December 2005 (Version 2)
> >>> Author: Tim Elhajj"
> >>> The install completed without errors. I have checked RSOP on
> >>> workstations
> >>> and can see the Group Policy has been applied. I can also connect to
> >>> http://servername:8530/wsusadmin from the workstations. I get "HTTP
> >>> Error
> >>> 403 - Forbidden" if I try to connect to http://servername:8530 > I have
> >>> checked and rechecked the settings for the Default Web
> >>> Site\ClientWebService
> >>> & Selfupdate. Both are set for anonymous access and all computers are
> >>> granted access. What could possibly be wrong?
> >>> Internet Explorer
> >>>
> >>>
> >>>
> >
> >
>
>
>

Hi kj,

a short question by the way: What Tool/Command do you use, to get this very
helpful output? I search for a tool like that to test the functionality of
the wsus connection on target machines.

Maybe others have such tools too?

"kj" wrote:

> Target groups won't help if your clients can't register with WSUS which if
> they could would already be showing up.
>
> I believe the problem is with the client proxy configuration;
>
> Checking Proxy Configuration
> > Checking for winhttp local machine Proxy settings . . . PASS
> > Winhttp local machine access type
> > <Direct Connection>
> > Winhttp local machine Proxy. . . . . . . . . . NONE
> > Winhttp local machine ProxyBypass. . . . . . . NONE
> > Checking User IE Proxy settings . . . . . . . . . . . . PASS
> > User IE Proxy
> > w2ksvr1:8080
> > User IE ProxyByPass
> > <local>
> > User IE AutoConfig URL Proxy
> > http://w2ksvr1:8080/array.dll?Get.Routing.Script
> > User IE AutoDetect
> > AutoDetect in use
> >
> > Checking Connection to WSUS/SUS Server
> > WUServer = http://w2ksvr1:8530
> > WUStatusServer = http://w2ksvr1:8530
> > UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
> >
> > VerifyWUServerURL() failed with hr=0x80072ee5
> >
> > The URL is invalid
>
> Cross posting to the WSUS group for help.

rbin, you can use "WSUS Client Diagnostic Tool" found at
http://wsusinfo.onsitechsolutions.com/downloads.htm.

There you can also find the server diagnostics tool among other things
(like documentation)...

HTH,
Pablo


rbin wrote:
> Hi kj,
>
> a short question by the way: What Tool/Command do you use, to get this very
> helpful output? I search for a tool like that to test the functionality of
> the wsus connection on target machines.
>
> Maybe others have such tools too?
>

Thank you Pablo,

that was exactly what i'm looking for.

YTH, (Yes that helps ;-)
rbin

"Pablo Cardoso" wrote:

> rbin, you can use "WSUS Client Diagnostic Tool" found at
> http://wsusinfo.onsitechsolutions.com/downloads.htm.
>
> There you can also find the server diagnostics tool among other things
> (like documentation)...
>
> HTH,
> Pablo
>
>
> rbin wrote:
> > Hi kj,
> >
> > a short question by the way: What Tool/Command do you use, to get this very
> > helpful output? I search for a tool like that to test the functionality of
> > the wsus connection on target machines.
> >
> > Maybe others have such tools too?
> >
>

The more direct and up-to-date link for WSUS downloads is;

http://www.microsoft.com/windowsserv...s/default.mspx

--
/kj
"rbin" <rbin@news.postalias> wrote in message
news:3677A491-8218-4825-BD3B-451D93C5C8EB@microsoft.com...
> Thank you Pablo,
>
> that was exactly what i'm looking for.
>
> YTH, (Yes that helps ;-)
> rbin
>
> "Pablo Cardoso" wrote:
>
>> rbin, you can use "WSUS Client Diagnostic Tool" found at
>> http://wsusinfo.onsitechsolutions.com/downloads.htm.
>>
>> There you can also find the server diagnostics tool among other things
>> (like documentation)...
>>
>> HTH,
>> Pablo
>>
>>
>> rbin wrote:
>> > Hi kj,
>> >
>> > a short question by the way: What Tool/Command do you use, to get this
>> > very
>> > helpful output? I search for a tool like that to test the functionality
>> > of
>> > the wsus connection on target machines.
>> >
>> > Maybe others have such tools too?
>> >
>>

"kj" <kj@nowhere.com> wrote in message
news:Oe1xZiNgGHA.1320@TK2MSFTNGP04.phx.gbl...
> The more direct and up-to-date link for WSUS downloads is;
>
> http://www.microsoft.com/windowsserv...s/default.mspx
>


Thank you kj.

Yes, the preferable source for Microsoft content is a microsoft.com link,
such as the one provided above, or the one provided in my sig.

If you browse to my downloads page, you'll also find that I provide the
direct links to microsoft.com for all resources available from there, and
the home page of the site encourages users to obtain content directly from
microsoft.com, rather than my site.

Truth be told, the links on that page were put there primarily for my
convenience. I use them a lot, to reference the Deployment Guide and Getting
Started Guides.

--
Lawrence Garvin, M.S., MVP-Software Distribution
Everything you need for WSUS is at
http://technet2.microsoft.com/window...s/default.mspx
And, eveything else is at
http://wsusinfo.onsitechsolutions.com
....

"Lawrence Garvin (MVP)" <onsitech@news.postalias> wrote in message
news:eTUrUqQgGHA.4276@TK2MSFTNGP03.phx.gbl...
> "kj" <kj@nowhere.com> wrote in message
> news:Oe1xZiNgGHA.1320@TK2MSFTNGP04.phx.gbl...
>> The more direct and up-to-date link for WSUS downloads is;
>>
>> http://www.microsoft.com/windowsserv...s/default.mspx
>>
>
>
> Thank you kj.
>
> Yes, the preferable source for Microsoft content is a microsoft.com link,
> such as the one provided above, or the one provided in my sig.
>
> If you browse to my downloads page, you'll also find that I provide the
> direct links to microsoft.com for all resources available from there, and
> the home page of the site encourages users to obtain content directly from
> microsoft.com, rather than my site.
>
> Truth be told, the links on that page were put there primarily for my
> convenience. I use them a lot, to reference the Deployment Guide and
> Getting Started Guides.
>
> --
> Lawrence Garvin, M.S., MVP-Software Distribution
> Everything you need for WSUS is at
> http://technet2.microsoft.com/window...s/default.mspx
> And, eveything else is at
> http://wsusinfo.onsitechsolutions.com
> ...

I didn't realize that was your site Lawrence, or that WSUS SP1 was either
released or so close that the technet link references for Vista Beta 2
updates.


- Thanks.

/kj

"kj" <kj@nowhere.com> wrote in message
news:erus7IWgGHA.1792@TK2MSFTNGP03.phx.gbl...
> I didn't realize that was your site Lawrence, or that WSUS SP1 was either
> released or so close that the technet link references for Vista Beta 2
> updates.

WSUS SP1 has not yet been released. To my knowledge there is no publicly
announced release date for it, yet; however, Bobbie Harder has posted here
that 1H of this year was the target. That translates to "within the next 30
days" at this moment.

--
Lawrence Garvin, M.S., MVP-Software Distribution
Everything you need for WSUS is at
http://technet2.microsoft.com/window...s/default.mspx
And, eveything else is at
http://wsusinfo.onsitechsolutions.com
....

Thanks Lawrence. I'll keep an eye out for it.

Did they have a public beta for it?

Any substantial feature additions expected other than I guess necessities
for Vista?

--
/kj
"Lawrence Garvin (MVP)" <onsitech@news.postalias> wrote in message
news:O5CNmangGHA.1272@TK2MSFTNGP03.phx.gbl...
> "kj" <kj@nowhere.com> wrote in message
> news:erus7IWgGHA.1792@TK2MSFTNGP03.phx.gbl...
>> I didn't realize that was your site Lawrence, or that WSUS SP1 was either
>> released or so close that the technet link references for Vista Beta 2
>> updates.
>
> WSUS SP1 has not yet been released. To my knowledge there is no publicly
> announced release date for it, yet; however, Bobbie Harder has posted here
> that 1H of this year was the target. That translates to "within the next
> 30 days" at this moment.
>
> --
> Lawrence Garvin, M.S., MVP-Software Distribution
> Everything you need for WSUS is at
> http://technet2.microsoft.com/window...s/default.mspx
> And, eveything else is at
> http://wsusinfo.onsitechsolutions.com
> ...
>
>

"kj" <kj@nowhere.com> wrote in message
news:u%23M9%23fpgGHA.3860@TK2MSFTNGP02.phx.gbl...
> Thanks Lawrence. I'll keep an eye out for it.
>
> Did they have a public beta for it?
>
> Any substantial feature additions expected other than I guess necessities
> for Vista?


There has been no public beta of SP1 for WSUS v2.0.

Aside from providing support for Vista Beta 2 updates via the Microsoft
Update Beta site
(see
http://technet2.microsoft.com/window...s/default.mspx
for detailed instructions on how to configure your WSUS SP1 server to do
this, once SP1 is released),
there are no 'feature additions' coming in SP1.

--
Lawrence Garvin, M.S., MVP-Software Distribution
Everything you need for WSUS is at
http://technet2.microsoft.com/window...s/default.mspx
And, eveything else is at
http://wsusinfo.onsitechsolutions.com
....

"Lawrence Garvin (MVP)" <onsitech@news.postalias> wrote in message
news:u5hpv2rgGHA.2188@TK2MSFTNGP04.phx.gbl...
> "kj" <kj@nowhere.com> wrote in message
> news:u%23M9%23fpgGHA.3860@TK2MSFTNGP02.phx.gbl...
>> Thanks Lawrence. I'll keep an eye out for it.
>>
>> Did they have a public beta for it?
>>
>> Any substantial feature additions expected other than I guess necessities
>> for Vista?
>
>
> There has been no public beta of SP1 for WSUS v2.0.
>
> Aside from providing support for Vista Beta 2 updates via the Microsoft
> Update Beta site
> (see
> http://technet2.microsoft.com/window...s/default.mspx
> for detailed instructions on how to configure your WSUS SP1 server to do
> this, once SP1 is released),
> there are no 'feature additions' coming in SP1.
>
> --
> Lawrence Garvin, M.S., MVP-Software Distribution
> Everything you need for WSUS is at
> http://technet2.microsoft.com/window...s/default.mspx
> And, eveything else is at
> http://wsusinfo.onsitechsolutions.com
> ...

Thanks Lawrence.

/kj