I am setting up a new WSUS server and using SSL certs. The server is Windows
2008 with IIS 7.0. The WSUS server is up and running and I can get computers
to check in, but I see in the log files some errors. I should state every
machine does this and the clientdiag tool states it passes all checks. I've
posted the key information from the logs. Its appears it checks in, finds
all patches, and usually reports the information in. But was it the pointer
going to microsoft for the cookie and the config chaged error? I some cases
the system will report in and others it doesnt. The microsoft patch that
matches these errors are for Windows 2003 sp1, this is windows 2008. I have
ran wuauclt.exe /resetauthorization /detectnow which will clear up the error
for a bit then it comes back and office 2003 sp1 issue does not apply as I
have declined the updates.

Thank you for any assistance

ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
https://pm2/ClientWebService/client.asmx

WARNING: Cached cookie has expired or new PID is available
Initializing simple targeting cookie, clientId =
a6cb26fb-ec8f-4256-815a-2e7cf7ca03e2, target group = , DNS name = ird-sectest

Server URL = https://pm2/SimpleAuthWebService/SimpleAuth.asmx

WARNING: GetCookie failure, error = 0x8024400D, soap client error = 7, soap
error code = 300, HTTP status code = 200

WARNING: SOAP Fault: 0x00012c

WARNING: faultstring:Fault occurred

WARNING: ErrorCode:ConfigChanged(2)

WARNING: Messagenull)

WARNING:
Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie"

WARNING: ID:cbb2bd0b-b64c-4fb9-b959-f5ab34a07f31

WARNING: Cached cookie has expired or new PID is available

Initializing simple targeting cookie, clientId =
a6cb26fb-ec8f-4256-815a-2e7cf7ca03e2, target group = , DNS name = ird-sectest

Server URL = https://kumc-pm2.kumc.edu/SimpleAuth...impleAuth.asmx

+++++++++ PT: Synchronizing extended update info +++++++++++

ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
https://pm2/ClientWebService/client.asmx

Found 0 updates and 48 categories in search; evaluated appl. rules of 500
out of 695 deployed entities

Windows Update Client successfully detected 0 updates.

Uploading 2 events using cached cookie, reporting URL =
https://pm2/ReportingWebService/Repo...ebService.asmx

Reporter successfully uploaded 2 events.

"Daniel V" <> wrote in message
news:E4B82B39-84BF-427C-ADA8-...
>I am setting up a new WSUS server and using SSL certs. The server is
>Windows
> 2008 with IIS 7.0. The WSUS server is up and running and I can get
> computers
> to check in, but I see in the log files some errors. I should state every
> machine does this and the clientdiag tool states it passes all checks.
> I've
> posted the key information from the logs. Its appears it checks in, finds
> all patches, and usually reports the information in. But was it the
> pointer
> going to microsoft for the cookie and the config chaged error? I some
> cases
> the system will report in and others it doesnt. The microsoft patch that
> matches these errors are for Windows 2003 sp1, this is windows 2008. I
> have
> ran wuauclt.exe /resetauthorization /detectnow which will clear up the
> error
> for a bit then it comes back and office 2003 sp1 issue does not apply as I
> have declined the updates.

Are these clients cloned from the same image?


--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

no they are not cloned and the susclientid's are unique. They all use to
connect to a different server, without ssl, with no problems. Just when
moving to the new one using ssl do I begin to see the error.

"Daniel V" <> wrote in message
news:7C81EB8E-25E0-4605-8E81-...

> Just when moving to the new one using ssl do I begin to see the error.

Okay... have you distributed the SSL certificate to all of the client
systems?



--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

Yes, the SSL cert is on all systems. The systems do check in and with a
wuauclt.exe /resetauthorization /detectnow the systems will usually clear up
the problem but only for awhile, then the error shows back up in the logs

"Daniel V" <> wrote in message
news:A0D342CE-E15D-47A9-B763-...
> Yes, the SSL cert is on all systems. The systems do check in and with a
> wuauclt.exe /resetauthorization /detectnow the systems will usually clear
> up
> the problem but only for awhile, then the error shows back up in the logs

Then let's look at an example of this in the logs..

both a successful detection, and the subsequent failure.



--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

I guess it is not really a problem for us after looking into it. Machines seem to actually be checking in. The error seems to occur when changing from one WSUS server to another. It might just have to do with the cookie currently on the system needing to be refreshed. The systems occasionaly throw up this message in the logs but does check for updates and report in.