Re: How much is to much? Why should my clients have to pay again?



estover wrote:
> I really think MS has gone a little too far with this. Eight of my
> clients have had a problem with this new fangled validation tool.
> The first 3 have a bill totaling just over 600 dollars. The other 5
> are on the calender for Monday, and if is the same amount of time as
> the other 3 there bills will total over 1,000.00 dollars. How many
> others are there spending the same amount or more? And from what I
> understand there is already a "hack", "workaround", or "fix" out
> there in the wild that is going to cause MS to redo the tool, to
> protect there investment. Well I want to know why MS thinks it is OK
> to screw the little guys out of money just to protect MS? I have one
> client that is going to look for a new tech because she doesn't think
> I know what I am doing. She could not get updates, and blamed it on
> me. Microsoft, hear me: MOST PEOPLE DO NOT READ THE NEWS ABOUT PC
> AND SOFTWARE!!!!!! When something goes wrong it is MY fault, not
> yours, MINE. You can keep playing around with this validation crap
> and help me to move people to Linux. I am in charge of keeping my
> clients up and running and feeling safe. Please start thinking like
> I have to and you will win in the end.

Shenan Stanley wrote:
> What are you talking about?
>
> I assume you mean you have had customers complaining they could not
> get the updates and wanted to know why.
> I don't know how you billed each one $200 (what did you do to fix the
> problem - I guess they were out of warranty?)
>
> None of my clients have had any issues.. large or small - with the
> validation tool. I'll admit seeing the problems discussed on these
> newsgroups - but not an overwhelming number discussed by any means - I
> definitely saw more discussion about SP2 than the "new validation
> procedures".
>
> How about presenting your solutions here instead of randomly (and
> incoherently without multiple readings) ranting about the money you
> are making (customers you are losing possibly) because they believe
> you are inept? You obviously have had problems you fixed for your
> customers - you could present these and who knows - maybe your
> solution is unique and may point to the crux of the problem more than
> "Please start thinking like I have to and you will win in the end."
> *grin*
>
> For or against the choice Microsoft made - I don't really care - I
> just know that complaining is only productive when presented with
> viable and non-emotional solutions and facts. I have no idea what
> you did to fix the problem, what errors your customers saw - why they
> saw them and if it was/wasn't anything you did/didn't do for your
> customers... You've only presented a number of customers that had
> some problem you blame the microsoft validation tool for and you
> charged them to fix it and at least one (of the number) blames you
> for their problem. Can you present more details? Because -
> certainly - you cannot be afraid that will lose you more customers
> since you believe they won't read this ever anyway..

Shenan Stanley wrote:
> BTW - this is one of the usual symptom/fixes:
>
> The Windows Genuine Advantage (WGA) validation check process
> does not complete when you try to validate your copy of Windows XP
> http://support.microsoft.com/kb/905226

estover wrote:
> You putz, who are you to question why I charged my customers for
> repairs. You have no clue as to the contract I have with them how,
> many PCs were affected, time of day work needed to be done. So
> unless you are going to offer a fix for someones problem, keep your
> pie hole shut. I cam on here to vent, not to ask you how to fix a
> problem. If you were to read my post you will see I did not one time
> ask for a fix to the problem. Am I sure didnt ask your opinion. As
> for your comment: "You've only
> presented a number of customers that had some problem you blame the
> microsoft validation tool for and you charged them to fix it "
>
> (I'm typing this real slow, so please read it s l o w l y so
> that you get it. Ummmmm the problem was the tool. If they didnt
> have to install it, there would have been a problem. Please tell me
> how this was not a problem with the tool.
> (Now I have asked a question, you may answer now.) Ahhh yes, I
> forgot your an MS guy. Nothing is ever wrong with an MS product.
> Silly me.
>
> I wonder how one goes about getting "MVP" after there name.........

I presented a reaction to your rant without resorting to name calling or
anything quite so roughhewn.

As for your first question - who am I? I am your customer.

As for your comment - yes - I have an idea why you charged your customers -
you said it was because of Microsoft.

As for "keeping my pie-hole shut" - did you expect no comment when you post
your drivel on internationally distributed newsgroups?

As for your venting - I did the same in kind.. If you expected those around
the world to deal with your venting (in a place frequented by those with
problems and those who help them - not Microsoft employees so much or
necessarily) - then it is quite simple to expect you deal with mine in the
same manner you expected yours to be dealt with.

As for asking for a fix to the problem - never said you did.. Doesn't
prevent one from offering one up or asking for more detail - after all -
that is what these newsgroups are for.

"Am I sure didnt ask your opinion." <- I would hope you are sure what you
did - but welcome to the public newsgroup arena anyway.

Roughhewn - again.

Was the validation tool the problem? As I said before - I do not know - I
only presented the thousands of cases I have seen where it was not. You
merely presented the eight (8) you claim were.

As for MS never being wrong.. Microsoft as a company - problems. Microsoft
products in general - problem.. As for me being a Microsoft guy - nope. I
am someone who uses and supports the product as one of many things I do and
of the many products I support. If Microsoft dropped out of the picture
tomorrow I would be no better or worse off.. Does not matter to me. You
say the product caused your problems - I present that it may have, it may
not have - but I have not personally seen it cause this problem yet and in
more cases than you presented it happening in.

As for the last question - Google or use the Microsoft search engine - I'm
sure you can find it.

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html


.



Relevant Pages

  • Re: How much is to much? Why should my clients have to pay again?
    ... > clients have had a problem with this new fangled validation tool. ... I assume you mean you have had customers complaining they could not get the ... I don't know how you billed each one $200 (what did you do to fix the ...
    (microsoft.public.windowsupdate)
  • Re: How much is to much? Why should my clients have to pay again?
    ... who are you to question why I charged my customers for repairs. ... offer a fix for someones problem, ... >> clients have had a problem with this new fangled validation tool. ... I am in charge of keeping my ...
    (microsoft.public.windowsupdate)
  • Re: When will MS03-032 get fixed?????
    ... This isn't an answer anybody can give, rob. ... The only answer you can get will be that "Microsoft is aware of the ... For the good of all its customers, Microsoft must speak with one voice with ... > when MS is going to fix the MS03-032 patch? ...
    (microsoft.public.security.virus)
  • RE: Conditional hyphens can cause Word 2007 SP1 Find & Replace to hang
    ... I Also Have seen this happen in multiple environments. ... Microsoft really needs ... to get a fix for this fast, my customers don't like it when I have to blame ...
    (microsoft.public.word.application.errors)
  • Slammer fix for RTM and SP1 installs
    ... You must call Product Support Services to obtain this fix. ... Microsoft has released a fix for the W32.Slammer worm, ... these fixes were also included in SQL Server 2000 Service Pack ... Microsoft strongly recommends customers immediately follow the ...
    (microsoft.public.security)

Loading