Thank you all for your comments.
However, a testbed system would not have helped this situation.
Suppose an administrator installed SP1 in April on a test station,
then ran it for 2 full months with no problem. Then, placed it
in production in June, runs fine for a full month, then BLAM
July 27th hits.
While it is important to emphasize the use of off-line tests,
that is not pertinent IN THE LEAST in this particular case.
In my case, the APC software had been installed by a previous
IT company, who presumably received the email from APC
indicating that a problem would occur - but not indicating
at all the severity of the problem. In fact, on APC's website
front page right now, their info states no worse impact than
that the APC software will not protect the server.
To date, THE ONLY place that I've found ANY documentation
of the full effects of this bug is on this group. If I were to place
blame (hoo boy, don't want to start another heated argument here)
I'd have to say that Microsoft is to blame for allowing a single service to
effectively bring down the entire server.
Chris
"Susan Bradley, CPA aka Ebitz - SBS Rocks" wrote:
> I don't they APC knew it was going to do this to be honest with you.
>
> Ergo...the bigger issue here.
>
> jnp213 wrote:
> > While all of the blame gets thrown around, I just wanted to thank the forum
> > users who made us aware of the issue and how to fix it.
> > And although I received email notification of the expiration, there was no
> > mention of it's full impact on the operating system, or how to resolve the
> > issue in the event that an upgrade was not performed before the expiration
> > date.
> > It merely states,
> > "Failure to upgrade will render PowerChute Business Edition inoperable."
> >
> > Lessons learned: 1. Read your email, and upgrade before the expiration date.
> > 2. Check forums before trying to blindly tackle the issue.
> >> Stay informed about: Windows 2003 SBS Hangs on "Applying computer Settings" 
FAQ
Profile
Private Messages
Log in
