Sorry, I use Google. Well I use my 2008 R2 DC's with Google as my forwarder.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Susan Bradley Sent: Thursday, November 20, 2014 11:47 AM To: Patch Management Mailing List; [email protected] Subject: [NTSysADM] Re: [patchmanagement] Windows 2003 WU Error: 0x80248015 after this months patchs About a month ago in the answers forum we had a RASH of folks having MU/WU errors where it wouldn't scan. If we flipped their DNS over to Google's DNS it would suddenly work just fine. It cleared up, but it felt like a root cause was something with MU not liking some DNS provider (openDNS maybe?) For all of you guys reporting this, what DNS provider are you using? What ISP are you using? It felt that the root cause before was Time Warner/OpenDNS. (yes we are now using 'feelings' regarding root cause when one has to rely on others for evidence and reports) ccin'g to the ntsysadmin list where there were reports there as well. Susan Bradley http://blogs.msmvps.com/bradley http://www.runasradio.com/default.aspx?showNum=390 On 11/20/2014 4:00 AM, Jason LaFrance wrote: > No I only saw it as I was going to scan and apply MS14-068. > > Jason > ________________________________________ > From: Susan Bradley [[email protected]] > Sent: Wednesday, November 19, 2014 1:46 PM > To: Patch Management Mailing List > Subject: Re: [patchmanagement] Windows 2003 WU Error: 0x80248015 after > this months patchs > > Are you seeing this after installing MS14-068 specifically? > > Susan Bradley > http://blogs.msmvps.com/bradley > http://www.runasradio.com/default.aspx?showNum=390 > > On 11/19/2014 10:03 AM, Jason LaFrance wrote: >> I am seeing this trying to update the couple of Win2K3 Vms we have >> via WU for the latest MS14-068. >> >> Doing some google in the past 24 hours seeing others with same issue. >> >> For me this happens only when Microsoft update is installed. If I >> shutdown service Automatic updates and BITS, rename >> C:\windows\softwaredistribution and then start again using Windows >> Update it works. If Microsoft Update is reinstall it fails again >> with 0x80248015. >> >> Windowsupdate.log shows: >> >> 2014-11-19 12:50:10:607 5356 4d4 Misc >> =========== Logging initialized (build: 7.6.7600.256, tz: -0500) >> =========== >> >> 2014-11-19 12:50:10:623 5356 4d4 Misc = >> Process: C:\Program Files\Internet Explorer\IEXPLORE.EXE >> >> 2014-11-19 12:50:10:623 5356 4d4 Misc = >> Module: C:\WINDOWS\system32\wuapi.dll >> >> 2014-11-19 12:50:10:607 5356 4d4 >> COMAPI ----------- COMAPI: >> IUpdateServiceManager::AddService ----------- >> >> 2014-11-19 12:50:10:623 5356 4d4 >> COMAPI - ServiceId = >> {7971f918-a847-4430-9279-4a52d1efe18d} >> >> 2014-11-19 12:50:10:623 5356 4d4 >> COMAPI - AuthorizationCabPath = >> C:\WINDOWS\SoftwareDistribution\AuthCabs\muauth.cab >> >> 2014-11-19 12:50:10:638 860 1604 Misc >> Validating signature for >> C:\WINDOWS\SoftwareDistribution\AuthCabs\Downloaded\7971f918-a847-4430-9279-4a52d1efe18d.auth.cab.temp\muauth.cab: >> >> 2014-11-19 12:50:10:670 860 1604 Misc >> Microsoft signed: Yes >> >> 2014-11-19 12:50:10:732 860 1604 Agent >> WARNING: WU client fails CClientCallRecorder::AddService2 with error >> 0x80248015 >> >> 2014-11-19 12:50:10:732 5356 4d4 >> COMAPI WARNING: ISusInternal::AddService failed, hr=80248015 >> >> 2014-11-19 12:50:10:732 5356 4d4 >> COMAPI - Exit code = 0x80248015 >> >> Jason LaFrance, GSEC, GCWN >> >> Network Engineer >> >> BioTek Instruments, INC. >> > > --- > PatchManagement.org is hosted by Shavlik > > The content on the email list is intended for assisting administrators. If > you would like to use any of this content in a blog or media publication, > please contact the owners of the list for approval. > > To unsubscribe send a blank email to > [email protected] > If you are unable to unsubscribe via this email address, please email > [email protected] > > --- > PatchManagement.org is hosted by Shavlik > > The content on the email list is intended for assisting administrators. If > you would like to use any of this content in a blog or media publication, > please contact the owners of the list for approval. > > To unsubscribe send a blank email to > [email protected] > If you are unable to unsubscribe via this email address, please email > [email protected] > >
