Thanks for the information. I'll have to be a bit more careful in handling this patch for the SBS. It's getting close to a bad time of year for me to be applying updates that frak everything up.
On Thu, Jan 15, 2009 at 2:36 PM, David Florea <[email protected]> wrote: > Sure, as best I know – just uninstalling the patch did not work. So, on > the phone with PSS. Found RPC can be reenabled, sort of, if you go into > safe mode (otherwise you don't have permission to do a freaking thing) and > get to the registry, I think it was > HKLM/System/CurrentControlSet/Services/RPCss, and change 'ObjectName' from > NT Authority\NetworkService' to just 'LocalSystem'. It's not a 'recommended > practice', PSS explained, but it will grant you some control. > > > > The eventual fix was to first restore the System State from hopefully > recent backup – but that didn't completely resolve it. Then we ran a long > 'secedit' command line string, and the machine appeared to come back > properly. But – when it rebooted it gleefully told me it had reinstalled > the missing update and was going to reboot [shudder]. So I quickly > uninstalled the patch again before it rebooted, disabled the automatic > update svc, and rebooted – machine was then OK. I'll send you the secedit > string offline if you want it, but I highly recommend calling PSS if you end > up with an operational server with the problem. No charge. > > > > Good luck, > > > > David > > > > *From:* Jonathan Link [mailto:[email protected]] > *Sent:* Thursday, January 15, 2009 10:52 AM > *To:* NT System Admin Issues > *Subject:* Re: MS-patch 09-001 > > > > Can you detail the resolution to your problem? I have an SBS, and was > contemplating the upgrade this weekend. > > On Thu, Jan 15, 2009 at 1:07 PM, David Florea <[email protected]> wrote: > > I just resubbed after an absence, so I may have not seen prior traffic > about Tuesday's update: I had a horrible experience with patch KB958687 on > an SBS2003 server -- immediately after rebooting, RPC was inoperable, which > caused the NICs to fail, and most other dependent services to not start > (which was most of them). Took six hours with PSS to repair, but > fortunately the file structure was intact. So much for early adopting. PSS > indicated there were many of this problem, though it may be limited to SBS > servers, not sure, they were pretty close-mouthed about it. Just a word to > the wise. > > David > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > > > > > > > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
