*>>I don't send sensitive information on any of my email accounts I hate to do banking by the web too. I am old and cranky, go figure.*
But you access them from your machines where you might be doing sensitive things. *ASB **http://XeeMe.com/AndrewBaker* <http://xeeme.com/AndrewBaker>* **Providing Virtual CIO Services (IT Operations & Information Security) for the SMB market…*** On Wed, Sep 11, 2013 at 10:46 PM, Jon Harris <jk.har...@live.com> wrote: > I don't send sensitive information on any of my email accounts I hate > to do banking by the web too. I am old and cranky, go figure. > > Jon > > ------------------------------ > From: damien.solo...@harrison.edu > > To: ntsysadm@lists.myitforum.com > Subject: RE: [NTSysADM] Windows Update Issues? > Date: Thu, 12 Sep 2013 01:32:53 +0000 > > > He says from a Microsoft cloud based email account. :-) > > > damien.solodow > > > > -------- Original message -------- > From: Jon Harris <jk.har...@live.com> > Date: 09/11/2013 9:07 PM (GMT-05:00) > To: ntsysadm@lists.myitforum.com > Subject: RE: [NTSysADM] Windows Update Issues? > > > Yeah at the cost of my privacy. Thanks but no thanks. > > Jon > > ------------------------------ > From: rodtr...@myitforum.com > To: ntsysadm@lists.myitforum.com > Subject: Re: [NTSysADM] Windows Update Issues? > Date: Thu, 12 Sep 2013 00:41:26 +0000 > > Per Microsoft, things will be perfect after you migrate to the Microsoft > Cloud. > > Sent from Lenovo Tablet 2 > > *From:* Jon Harris > *Sent:* Wednesday, September 11, 2013 8:23 PM > *To:* ntsysadm@lists.myitforum.com > > For a while a couple of years ago they had the process down pretty good > but I guess they are having issues keeping so many different versions of > stuff they can't keep all the balls in the air without dropping a bunch. > Maybe after they retire XP things will get better? > > Jon > > ------------------------------ > From: rodtr...@myitforum.com > To: ntsysadm@lists.myitforum.com > Subject: Re: [NTSysADM] Windows Update Issues? > Date: Thu, 12 Sep 2013 00:17:38 +0000 > > Funny thing is that I had a great chat with the VP of CSS a few weeks > back. She outlined the new processes they have put in place to fix the > quality issues due to the accelerated release schedule. It sounded logical. > Evidently they are just not using them. > > Sent from Lenovo Tablet 2 > > *From:* Michael B. Smith > *Sent:* Wednesday, September 11, 2013 8:12 PM > *To:* ntsysadm@lists.myitforum.com > > > +1 > > > > It’s appalling how bad the process has become. > > > > *From:* listsad...@lists.myitforum.com [mailto: > listsad...@lists.myitforum.com] *On Behalf Of *rodtr...@myitforum.com > *Sent:* Wednesday, September 11, 2013 7:38 PM > *To:* ntsysadm@lists.myitforum.com > *Subject:* Re: [NTSysADM] Windows Update Issues? > > > > This is not an adventure at all, but a monthly assault on IT Pros. > > > > Sent from Lenovo Tablet 2 > > > > *From:* Ziots, Edward > *Sent:* Wednesday, September 11, 2013 7:23 PM > *To:* ntsysadm@lists.myitforum.com > > > > Yep I got this straight from Susan Bradley SBS queen, off the Microsoft > Internal Discussions list, so the info is solid. Gotta love patching :_) > always an adventure J > > > > Z > > > > Edward E. Ziots, CISSP, CISA, Security +, Network + > > Security Engineer > > Lifespan Organization > > ezi...@lifespan.org > > Work:401-255-2497 > > > > > > This electronic message and any attachments may be privileged and > confidential and protected from disclosure. If you are reading this > message, but are not the intended recipient, nor an employee or agent > responsible for delivering this message to the intended recipient, you are > hereby notified that you are strictly prohibited from copying, printing, > forwarding or otherwise disseminating this communication. If you have > received this communication in error, please immediately notify the sender > by replying to the message. Then, delete the message from your computer. > Thank you. > > *[image: Description: Description: Lifespan]* > > > > > > *From:* listsad...@lists.myitforum.com [ > mailto:listsad...@lists.myitforum.com <listsad...@lists.myitforum.com>] *On > Behalf Of *Rod Trent > *Sent:* Wednesday, September 11, 2013 4:33 PM > *To:* ntsysadm@lists.myitforum.com > *Subject:* RE: [NTSysADM] Windows Update Issues? > > > > A security update with its own known issues list??? > > > > > > *From:* listsad...@lists.myitforum.com [ > mailto:listsad...@lists.myitforum.com <listsad...@lists.myitforum.com>] *On > Behalf Of *Ziots, Edward > *Sent:* Wednesday, September 11, 2013 3:55 PM > *To:* ntsysadm@lists.myitforum.com > *Subject:* RE: [NTSysADM] Windows Update Issues? > > > > Yeah Susan put this out on Windows 7 SP1. > > > > Follow the trail of the KBs...... > > > > Last month's kernel update of MS13-063 > > https://support.microsoft.com/kb/2859537 > > > > is replaced by this month's Service Control manager update and in THIS one > it lists the reasons for those BSOD's 6B errors: > > > > > > http://technet.microsoft.com/en-us/security/bulletin/ms13-077 > > > > > > Lists "known issues" > > None > > > > Yet in https://support.microsoft.com/kb/2872339 > > > > Clearly there are known issues.... > > > > > > > > Known issues with this security update > > > > After you install this security update, you may experience any of the > following issues: > > > > * You may receive a STOP 0x6B error message when you restart a > > computer that is running an x86-based version of Windows 7 SP1. This > > problem may occur if the following registry entry is missing: > > > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-ntdll_31bf3856ad364e35_none_b79ff9b5a57efc44 > > > > The missing registry entry could be caused by corruption in the > > registry or elsewhere in the system. > > * You may receive a STOP 0x6B error message when you restart a > > computer that is running an x64-based version of Windows 7 SP1. This > > problem may occur if either of the following registry entries is > > missing: > > > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-ntdll_31bf3856ad364e35_none_13be95395ddc6d7a > > > > > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\wow64_microsoft-windows-ntdll_31bf3856ad364e35_none_1e133f8b923d2f75 > > The missing registry entry could be caused by corruption in the > > registry or elsewhere in the system. > > * You may receive a STOP 0x6B error message when you restart a > > computer after you perform a specific System Restore operation. For > > example, the issue might occur in the following scenario: > > 1. You install this security update. During the installation, a > > restore point is automatically created. > > 2. You perform a System Restore operation to restore the system to > > the restore point that was created by this security update. > > 3. The computer is restarted. Notice that the system is now in an > > unprotected state because the security update was removed. > > 4. You try to undo the System Restore operation. > > 5. The computer is restarted, and then you receive the STOP 0x6B > > error message. > > > > To resolve these issues, you can use the Startup Repair recovery tool. > > For more information, go to the following Microsoft webpage: > > > http://windows.microsoft.com/en-ca/windows7/startup-repair-frequently-asked-questions > > > > ( > http://windows.microsoft.com/en-ca/windows7/startup-repair-frequently-asked-questions) > > > > > > > *Note* Not all STOP 0x6B errors are caused by the issues that are > described in this article. > > On 9/10/2013 11:03 PM, Susan Bradley wrote: > > > > > > Edward E. Ziots, CISSP, CISA, Security +, Network + > > Security Engineer > > Lifespan Organization > > ezi...@lifespan.org > > Work:401-255-2497 > > > > > > This electronic message and any attachments may be privileged and > confidential and protected from disclosure. If you are reading this > message, but are not the intended recipient, nor an employee or agent > responsible for delivering this message to the intended recipient, you are > hereby notified that you are strictly prohibited from copying, printing, > forwarding or otherwise disseminating this communication. If you have > received this communication in error, please immediately notify the sender > by replying to the message. Then, delete the message from your computer. > Thank you. > > *[image: Description: Description: Lifespan]* > > > > > > *From:* listsad...@lists.myitforum..com <listsad...@lists.myitforum.com> [ > mailto:listsad...@lists.myitforum.com <listsad...@lists.myitforum.com>] *On > Behalf Of *kz2...@googlemail.com > *Sent:* Wednesday, September 11, 2013 3:44 PM > *To:* ntsysadm@lists.myitforum.com > *Subject:* Re: [NTSysADM] Windows Update Issues? > > > > There's some talk of issues on the patch management list..... > > > "We’re seeing the same behavior for KB2760588, KB2760583, and KB2760411 in > our labs. We’re deferring until Microsoft issues revised updates. The > updates do install but are detected on the client-side as failed and > request for reinstallation." > > > > Sound like your issue? > > Sent from my Blackberry, which may be an antique but delivers email > RELIABLY > ------------------------------ > > *From: *"Sam Cayze" <sca...@gmail.com> > > *Sender: *listsad...@lists.myitforum.com > > *Date: *Wed, 11 Sep 2013 14:39:25 -0500 > > *To: *<ntsysadm@lists.myitforum.com> > > *ReplyTo: *ntsysadm@lists.myitforum.com > > *Subject: *[NTSysADM] Windows Update Issues? > > > > Have about 5 people from my company call in and say they have had to > install the windows updates today , repeatedly. Over and over. They don’t > fail, but they keep. > > > > Noticing it on my test machine too. Haven’t seen any negative reports > about this week’s updates… so just thought I’d ask. Haven’t delved into > it yet. > > > > Pushed them out via WSUS. Clients are XP. >
<<image001.jpg>>
