|
|
Hi Folks,
I am a newbie to WSUS and have just set up my first server. The server is
syncing well with MS Updates, however I can't get any computers recognised.
I have followed the Microsoft Step by Step Guide and waded through the
deployment and operations guides.
I created a test group in AD and then created and applied a group policy to
it for Windows update. I attached four pc's to the test group, but none of
the computers show up in the WSUS console.
When I run clientdiag.exe I get on 80072ee5 error message.
I have tried even using local group policies and just editing the registry
but all with same result.
I have tried setting up with port number i.e. http://wsusserver:80, and
without but everything I try fails. It is fast becoming sledge hammer time.
Can anyone help? I can provide screen shots if it will help.
Thanks
Steve
|
|
"Stephen Lewis" <StephenLewis[ at ]discussions.microsoft.com> wrote in message
news:E85CCB0A-AA8A-4856-8CED-899D0B5A7C8F[ at ]microsoft.com...
[Quoted Text] > Hi Folks,
>
> I am a newbie to WSUS and have just set up my first server. The server is
> syncing well with MS Updates, however I can't get any computers
> recognised.
>
> I have followed the Microsoft Step by Step Guide and waded through the
> deployment and operations guides.
>
> I created a test group in AD and then created and applied a group policy
> to
> it for Windows update. I attached four pc's to the test group, but none
> of
> the computers show up in the WSUS console.
>
> When I run clientdiag.exe I get on 80072ee5 error message.
I LIKE these ones! :-)
The 0x80072ee5 error is an Invalid URL error.
> Can anyone help? I can provide screen shots if it will help.
Fixing the URL should solve your problem. It should be of the form
http://servername where servername is the name of your WSUS Server.
If you installed WSUS to the alternate virtual server in IIS, then the URL
should be http://servername:8530
There is no need to append the :80 port number -- but even if you did,
that's not what is causing the '2ee5' Invalid URL error.
If you're unable to resolve the URL issue, then the output of the Client
Diagnostic Tool would be the best information at this point.
http://download.microsoft.com/download/9/7/6/976d1084-d2fd-45a1-8c27-a467c768d8ef/WSUS%20Client%20Diagnostic%20Tool.EXE
--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
|
|
"Lawrence Garvin (MVP)" wrote:
[Quoted Text] > "Stephen Lewis" <StephenLewis[ at ]discussions.microsoft.com> wrote in message > news:E85CCB0A-AA8A-4856-8CED-899D0B5A7C8F[ at ]microsoft.com... > > Hi Folks, > > > > I am a newbie to WSUS and have just set up my first server. The server is > > syncing well with MS Updates, however I can't get any computers > > recognised. > > > > I have followed the Microsoft Step by Step Guide and waded through the > > deployment and operations guides. > > > > I created a test group in AD and then created and applied a group policy > > to > > it for Windows update. I attached four pc's to the test group, but none > > of > > the computers show up in the WSUS console. > > > > When I run clientdiag.exe I get on 80072ee5 error message. > > I LIKE these ones! :-) > > The 0x80072ee5 error is an Invalid URL error. > > > Can anyone help? I can provide screen shots if it will help. > > Fixing the URL should solve your problem. It should be of the form > http://servername where servername is the name of your WSUS Server. > If you installed WSUS to the alternate virtual server in IIS, then the URL > should be http://servername:8530> There is no need to append the :80 port number -- but even if you did, > that's not what is causing the '2ee5' Invalid URL error. > > If you're unable to resolve the URL issue, then the output of the Client > Diagnostic Tool would be the best information at this point. > > http://download.microsoft.com/download/9/7/6/976d1084-d2fd-45a1-8c27-a467c768d8ef/WSUS%20Client%20Diagnostic%20Tool.EXE> > > -- > Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP > Principal/CTO, Onsite Technology Solutions, Houston, Texas > Microsoft MVP - Software Distribution (2005-2009) > > MS WSUS Website: http://www.microsoft.com/wsus> My Websites: http://www.onsitechsolutions.com;> http://wsusinfo.onsitechsolutions.com> My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin> >
Thanks for your previous reply.
I discovered a typo in the url. Once I fixed this the local policy allowed
connection, however when I removed local policy and applied domain GPO. I
get:
GetAUSettingsRegistry(true,pszUseWu,&dwUseWu) failed with hr=0x80070002
|
|
"Stephen Lewis" <StephenLewis[ at ]discussions.microsoft.com> wrote in message
news:6436DD72-C74D-4603-B680-1F0BF5DC6F08[ at ]microsoft.com...
[Quoted Text] > Thanks for your previous reply.
>
> I discovered a typo in the url. Once I fixed this the local policy
> allowed
> connection, however when I removed local policy and applied domain GPO. I
> get:
>
> GetAUSettingsRegistry(true,pszUseWu,&dwUseWu) failed with hr=0x80070002
Having this error in context would help tremendously.
Does this error occur on ALL systems, or only one?
--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
|
|
"Lawrence Garvin (MVP)" wrote:
[Quoted Text] > "Stephen Lewis" <StephenLewis[ at ]discussions.microsoft.com> wrote in message
> news:6436DD72-C74D-4603-B680-1F0BF5DC6F08[ at ]microsoft.com...
>
> > Thanks for your previous reply.
> >
> > I discovered a typo in the url. Once I fixed this the local policy
> > allowed
> > connection, however when I removed local policy and applied domain GPO. I
> > get:
> >
> > GetAUSettingsRegistry(true,pszUseWu,&dwUseWu) failed with hr=0x80070002
>
> Having this error in context would help tremendously.
>
> Does this error occur on ALL systems, or only one?
>
It occurs on all four test machines I am using to test the updates on.
|
|
|
|
"Stephen Lewis" <StephenLewis[ at ]discussions.microsoft.com> wrote in message
news:A8CB3BAB-DB85-4BAC-99D5-576C1B8CC1F5[ at ]microsoft.com...
[Quoted Text] >> > GetAUSettingsRegistry(true,pszUseWu,&dwUseWu) failed with hr=0x80070002
>> Having this error in context would help tremendously.
>>
>> Does this error occur on ALL systems, or only one?
> It occurs on all four test machines I am using to test the updates on.
Okay.. can I see the error message in context, then, please?
The entire output of the Client Detection Tool,
combined with the output of the WindowsUpdate.log containing this error
message,
from one of these four systems.
--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
|
|
"Lawrence Garvin (MVP)" wrote:
[Quoted Text] > "Stephen Lewis" <StephenLewis[ at ]discussions.microsoft.com> wrote in message > news:A8CB3BAB-DB85-4BAC-99D5-576C1B8CC1F5[ at ]microsoft.com... > > >> > GetAUSettingsRegistry(true,pszUseWu,&dwUseWu) failed with hr=0x80070002 > > > >> Having this error in context would help tremendously. > >> > >> Does this error occur on ALL systems, or only one? > > > > It occurs on all four test machines I am using to test the updates on. > > > Okay.. can I see the error message in context, then, please? > > The entire output of the Client Detection Tool, > combined with the output of the WindowsUpdate.log containing this error > message, > from one of these four systems. > > > > -- > Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP > Principal/CTO, Onsite Technology Solutions, Houston, Texas > Microsoft MVP - Software Distribution (2005-2009) > > MS WSUS Website: http://www.microsoft.com/wsus> My Websites: http://www.onsitechsolutions.com;> http://wsusinfo.onsitechsolutions.com> My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin> >
WSUS Client Diagnostics Tool
Checking Machine State
Checking for admin rights to run tool . . . . . . . . . PASS
Automatic Updates Service is running. . . . . . . . . . PASS
Background Intelligent Transfer Service is running. . . PASS
Wuaueng.dll version 7.2.6001.784. . . . . . . . . . . . PASS
This version is WSUS 2.0
Checking AU Settings
AU Option is 3 : Notify Prior to Install. . . . . . . . PASS
Option is from Policy settings
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. . . . . . . . . . . . . . . . . NONE
User IE ProxyByPass. . . . . . . . . . . . . . NONE
User IE AutoConfig URL Proxy . . . . . . . . . NONE
User IE AutoDetect
AutoDetect in use
Checking Connection to WSUS/SUS Server
WUStatusServer is not set through Policy
WUServer is not set through Policy
UseWuServer value is missing. . . . . . . . . . . . . . FAIL
GetAUSettingsRegistry(true,pszUseWu,&dwUseWu) failed with hr=0x80070002
The system cannot find the file specified.
Press Enter to Complete
|
|
"Winfried Sonntag [MVP]" wrote:
[Quoted Text]
Sorry Winfried, neither solution helped.
|
|
"Stephen Lewis" <StephenLewis[ at ]discussions.microsoft.com> wrote in message
news:1BA48C4A-9825-4E41-BF74-0AD01D356CFE[ at ]microsoft.com...
[Quoted Text] > "Lawrence Garvin (MVP)" wrote:
> >> > GetAUSettingsRegistry(true,pszUseWu,&dwUseWu) failed with
> >> > hr=0x80070002
>> Okay.. can I see the error message in context, then, please?
> WUStatusServer is not set through Policy
> WUServer is not set through Policy
> UseWuServer value is missing. . . . . . . . . . . . . . FAIL
See how much more useful =context= is to the process. :-)
The error message is irrelevant.. but reading the plain text of the output
of the CDT tells us exactly where the fault is.
Your Group Policy has not been applied, and the necessary configuration data
for the client is missing.
--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
|
|
|