True, I have seen what you've just described as well. OTOH, when I've had a reboot after patching where all the services didn't come up properly, but did after a second reboot, the cause has not been the patch, but typically the reboot request. Other remote reboot requests have tended to cause similar issues for that machine.
* * *ASB* *http://about.me/Andrew.S.Baker* *Harnessing the Advantages of Technology for the SMB market… * On Mon, Aug 22, 2011 at 1:43 PM, Michael B. Smith <[email protected]>wrote: > Actually, I’ve seen this before.**** > > ** ** > > If there was a pending change prior to patches being installed, sometimes > MS-Installer won’t actually do all the patch updates until another reboot. > **** > > ** ** > > Therefore, I tend to do as Webster said – reboot first, then apply patches, > then reboot again.**** > > ** ** > > Regards,**** > > ** ** > > Michael B. Smith**** > > Consultant and Exchange MVP**** > > http://TheEssentialExchange.com**** > > ** ** > > *From:* Andrew S. Baker [mailto:[email protected]] > *Sent:* Monday, August 22, 2011 1:41 PM > > *To:* NT System Admin Issues > *Subject:* Re: MS Patch fallout - resolved**** > > ** ** > > How can it be the "patching" if a subsequent reboot is fine? > > Were any patches removed? > > Isn't it more likely that something happened during the earlier reboot > (which was associated with the patching) that impacted the functionality? > > How many systems were previously rebooted at the same time? > > Thx > > **** > > *ASB***** > > *http://about.me/Andrew.S.Baker***** > > *Harnessing the Advantages of Technology for the SMB market…***** > > > > **** > > On Mon, Aug 22, 2011 at 1:02 PM, David Lum <[email protected]> wrote:**** > > I blame the patching. I rebooted this server again and everything came back > to life…**** > > **** > > Dave**** > > **** > > *From:* David Lum [mailto:[email protected]] > *Sent:* Monday, August 22, 2011 9:24 AM > *To:* NT System Admin Issues > *Subject:* RE: MS Patch fallout**** > > **** > > Here’s one.**** > > **** > > I have a web server that before we patched it that worked fine. We patched > and now from the machine itself the url works (http://webaddress)**** > > But from a client machine the IP works (http://ipofwebserver), but > http://webaddress no worky, and neither does http://FQDNofwebaddress.**** > > **** > > Sicne the address works from the machine itself I know the site is OK.**** > > From a client, pinging webaddress returns the correct IP, pinging FQDN also > returns the correct IP, so name resolution is OK.**** > > **** > > It feels like an IIS/IP security issue, where it cares what IP you’re > coming from to allow access. I know I’ve seen this before and have fixed it, > but the fix eludes me at the moment..**** > > **** > > Dave**** > > **** > > *From:* Don Kuhlman [mailto:[email protected]] > *Sent:* Monday, August 22, 2011 9:12 AM > *To:* NT System Admin Issues > *Subject:* Re: MS Patch fallout**** > > **** > > After some more investigation - it seems as though there was a software > installation on one of the servers with issues that required a reboot before > the patches were applied. Our DR server is fine - which didn't get the > application installed on it but did get it's patches. So we're going to > recover and restore the prod server with the issues and go from there.**** > > **** > > Thanks for the insights folks...**** > > **** > > **** > > *From:* Christopher Bodnar <[email protected]> > *To:* NT System Admin Issues <[email protected]> > *Sent:* Monday, August 22, 2011 9:47 AM > *Subject:* Re: MS Patch fallout**** > > Can't say I've seen that here. How much of your environment is affected? > Every patch cycle I see a few servers that need an extra reboot to clear > this type of issue, but it's never been widespread. > > > > > Chris Bodnar, MCSE, MCITP > Technical Support III > Distributed Systems Service Delivery - Intel Services > Guardian Life Insurance Company of America > Email: [email protected] > Phone: 610-807-6459 > Fax: 610-807-6003 > > > > From: Don Kuhlman <[email protected]> > To: "NT System Admin Issues" <[email protected] > > > Date: 08/22/2011 09:32 AM > Subject: MS Patch fallout **** > > > > > Hi folks. Has anyone seen any issues with the Microsoft August patches > affecting RDP access on Windows 2003 servers or terminal servers? > Getting issues after patching yesterday with some 2003 servers won't allow > RDP access now. > Thanks > Don K **** > > ** ** > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
