GopherRob Posted March 25, 2010 Report post Posted March 25, 2010 We recently installed a fresh SCCM 2007 site on our existing WSUS 3.0 SP1 server. To get SCCM to properly exist with WSUS, we also did a fresh install of WSUS 3.0 SP1 and cancelled at the config screen as instructed. We don't want to disable the windows firewall or open a broad range of ports to install the new SCCM client, so we are having issues pushing the client. This caused me to look at deploying it through the SUP, but ever since performing the fresh install of WSUS on the SCCM server, client machines (with the old SMS 2003 client) are not commuticating with the WSUS portion of SCCM. On client machines I am seeing the following error messages in the Windowsupdate.log file. 2010-03-25 12:08:07:307 1164 780 PT WARNING: Cached cookie has expired or new PID is available2010-03-25 12:08:07:307 1164 780 PT Initializing simple targeting cookie, clientId = 62cb241f-4ebb-4022-adb4-dae37fe97b7be, target group = , DNS name = testbox.domain.com 2010-03-25 12:08:07:307 1164 780 PT Server URL = http://WsusServerName/SimpleAuthWebService/SimpleAuth.asmx 2010-03-25 12:08:07:323 1164 780 PT WARNING: GetAuthorizationCookie failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404 2010-03-25 12:08:07:323 1164 780 PT WARNING: Failed to initialize Simple Targeting Cookie: 0x80244019 2010-03-25 12:08:07:323 1164 780 PT WARNING: PopulateAuthCookies failed: 0x80244019 2010-03-25 12:08:07:323 1164 780 PT WARNING: RefreshCookie failed: 0x80244019 2010-03-25 12:08:07:323 1164 780 PT WARNING: RefreshPTState failed: 0x80244019 2010-03-25 12:08:07:323 1164 780 PT WARNING: PTError: 0x80244019 2010-03-25 12:08:07:323 1164 780 Report WARNING: Reporter failed to upload events with hr = 80244019. I have changed our GPO for WSUS from http://WSUSServerName to http://WSUSServerName:8530 since port 8530 is what the SUP is configured to use, where our old WSUS was using 80. Despite forcing a group policy update and running wuauclt.exe /detectnow, this error persists. Any ideas and input would be appreciated, as we need to get the new sccm client out on the domain ASAP. Thanks! Quote Share this post Link to post Share on other sites More sharing options...