[There's a reason that Yoda is the unofficial mascot of SBS.  Size indeed matters not.] I'm not thrilled about that resolution. - THE OFFICIAL BLOG OF THE SBS DIVA
Mon, Apr 25 2011 23:23 bradley

I'm not thrilled about that resolution.

http://blogs.technet.com/b/joscon/archive/2011/04/25/update-on-torn-state-systems.aspx

I'm not thrilled about that resolution.

Especially since it appears to me that they didn't learn any lessons from this fiasco the last time  - http://news.softpedia.com/news/Vista-SP2-Perpetual-Black-Screens-of-Death-0xc0000034-121528.shtml

I also don't think that the product group really and truly understands the impact to the customers.  Many of those impacted either will be paying a consultant to clean up the mess or the consultant will be eating that cost.

Bottom line I'm not happy at all how that turned out.

Filed under:

# re: I'm not thrilled about that resolution.

Tuesday, April 26, 2011 1:00 PM by mjwelte

All I can say is "Wow". Total denial of responsibility. How do I, in good faith, go to my customers and explain to them that the product I service is what caused the mess and the solution to get them working is going to cost them at minimum $100 per machine? So I eat the time and support the customer or I bill the customer and make them angry. What a complete at total failure on Microsoft's part.

# re: I'm not thrilled about that resolution.

Tuesday, April 26, 2011 8:59 PM by Dean

"Total denial of responsibility"

Well, lets look at what happened here. People ran into a problem. They jumped on Google and implemented the first "solution" that came up. They didn't bother to actually call Microsoft and see what they may have to say about it. So now they are running with thier "solution" and later discover that it really wasn't a solution after all. This is Microsoft's fault ? Mmmmm not really. If they were told on the phone with Microsoft tech support to edit the pending.xml file then I would have to say that Microsoft gave them bad information and is totally to blame but to say that it's Microsofts fault that many people used bad judgment and got themselves into trouble is not at all fare. People have to take personal responsibilty for thier decisions.

Let the flaming begin.

# re: I'm not thrilled about that resolution.

Tuesday, April 26, 2011 10:48 PM by Dean

If you look at KB975484 the first step in the resolution is

1. Locate a second computer with access to the internet

Uh, OK why ? None of the rest of the steps have anything to do with the Internet. So is it like "Ha ! now that we made you do that we will get on with the real solution" ?

# re: I'm not thrilled about that resolution.

Wednesday, April 27, 2011 12:50 AM by bradley

And if someone in support also picked up on the pending hack and recommended it?  What then?

social.microsoft.com/.../9b8c894c-97aa-4334-be46-7c35a1b034f5

# re: I'm not thrilled about that resolution.

Wednesday, April 27, 2011 6:39 AM by Bill V

Googled solution or not... It shouldn't have happened in the first place. And that's Microsoft's fault... period.

# re: I'm not thrilled about that resolution.

Wednesday, April 27, 2011 9:14 AM by Dean

"And if someone in support also picked up on the pending hack and recommended it?"

That link does not work. I get "You are not authorized to perform this action."

But to answer your question. Personally I don't know if tech support via the web is the best thing. Maybe I'm old fashioned but for me if you are dealing with a NEW problem, and let me make that clear, I'm talking about a problem that does not have an official documented solution that you can Google, I think it is far better to get your answers over the phone. You will be dealing with someone who is focused ONLY on your problem and not multitasking doing this and that and only half thinking about what they are suggesting. Plus the person on phone support, as has been done many times for me in the past, can collaborate with other depts within Microsoft in real time to get a solution to the problem. Bottom line. You want a good answer to your problem ? Pick up the phone.

# re: I'm not thrilled about that resolution.

Wednesday, April 27, 2011 10:09 AM by bradley

The link works.  When it doesn't work for you you haven't signed up for access to the MS partner forums and if you are a partner you need to sign up for them.

And I will show you person after person say that the call back process now where you have to wait for a call back doesn't work.

# re: I'm not thrilled about that resolution.

Wednesday, April 27, 2011 12:30 PM by Dean

"And I will show you person after person say that the call back process now where you have to wait for a call back doesn't work."

You mean they really don't call you back ? If so that is really really bad and THAT is where the pressure on Microsoft should be. If they are thinking of ditching phone support in favor of web support to "save costs" people need to get on them NOW to nip that in the bud fast.

You will NEVER have the same quality of support on the Web as you would get on a phone call. Ever.

# re: I'm not thrilled about that resolution.

Wednesday, April 27, 2011 8:08 PM by Ben Krause

I have gotten fed up with MS tech support.   I feel like it's people just like me searching the knowledge base articles.  I can do that.  When I have a problem I want someone savier than me but normally it's someone just as knowledgable or less and it's irritating.  I wish I could get Mark Russonivich on the phone everytime I called, that guy would be able to solve my issue right away every time.

rant rant rant

# re: I'm not thrilled about that resolution.

Wednesday, April 27, 2011 8:11 PM by bradley

Betcha he couldn't either.

# re: I'm not thrilled about that resolution.

Thursday, April 28, 2011 2:39 AM by mjwelte

It is a total denial of responsibility. Placed a support call for MS and did not get a call back in a decent amount of time. Systems were down. Followed the knowledge base article and did not edit the pending.xml file. Did the recommended registry edit listed in the KB article. Systems are now in an unsupported state. I say that is a denial of responsibility as I followed the KB article and am now told in order to be in a supported state I need to do a total reinstall.