Re: Wainig for latest service pack

See, Susan has her finger on that button. Perhaps pre-maturely (in this case), but - know that she is on a mission to educate certain folks about the impact this SP2 scenario has on small businesses.

--
Les Connor [SBS MVP]


"Les Connor [SBS MVP]" <les.connor@xxxxxxxxxxxx> wrote in message news:E7726767-4D79-44FA-AA16-573FE5E14FCE@xxxxxxxxxxxxxxxx
I'd expect CSS to contact you, that's SOP for support incidents - they want your feedback and I don't believe the case can be closed without it.

Also, it's SOP for the CSS rep to send you an email prior to connecting to your server. At the bottom of that email, or perhaps in some subsequent email, you'll have a link to the reps' supervisor.

That's the route to go, but if you don't get satisfaction in due course then do indicate so here - as some buttons can be pushed.

Be prepared for this, though:

While there are obviously issues with SP2, I'm not sure your experience with exchange is directly related - at least I haven't noticed similar issues bieng common here. It's possible that a pre-existing condition was exposed by SP2 and it's related service/system restart. I believe unless the condition was a *direct* result of SP2, in which case it should be reproduceable on many systems, you'll be expected to pay for the call.

It sounds like CSS did see you through to the end, which is what they're mandated to do, no matter how long it takes. The decision you took to bring in local support was yours to take, but doesn't change the CSS position. They'd continue to work with your hired support as the same case.

In the end, though - CSS wants you to be satisfied, so do persue it as you see fit.

--
Les Connor [SBS MVP]


"Lanwench [MVP - Exchange]" <lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:uZrXGbWcHHA.4984@xxxxxxxxxxxxxxxxxxxxxxx
John Z <JohnZ@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
I opened a thread 4 days ago in this forum about the serious probelm
we have after we load SP2 on our SBS2003 server. This is a really bad
experience. Our Excahnge server is down for 3 days. Called Microsoft
support on Sunday, they was not able to fix it, instead made things
even worse after the support person deleted a lot of registry in
order to manully reload Exchange server on our sbs box. Finally we
paid extra lots of $$ to hire a local support guy from a MS certified
partner to visit on site to fix the problem. That local support
person spent 14 hours onsite and talked with MS support on phone for
like more than 5 hours on Monday. Excahnge server finally worked.
The origianl issue is after I load sp2, the mail box store is
unmounted and can not be mounted again. I tried to remove sp2 but
still did not work.

Ugh....what a horror story. I'd be inclined to do a complete DR restore from the full backup I made before installing the SP. You have one, I hope?

Please be extra careful when you load new service pack from microsoft
even if you have carefully read the release note. This big lesson
destroys my trust on Microsoft totally.

Well, I don't install service packs until they've been out for a bit - and that's true for a basic Windows or Exchange server service pack, let alone anything for SBS. Never use automatic updates on a server, and don't try to stay on the bleeding edge. If you can, test stuff on a non-production machine (even a VM) before deploying it.


By the way, can anyone here tell me how I complian this and get my
money back from Microsoft? Microsoft charged me bussiness critical on
this support service. Thank you.

Call PSS and speak to a supervisor.



.

Quantcast