RE: Remote Assistance problem

From: Kevin Witty (kdw_at_newsgroup.nospam)
Date: 05/04/05 

Date: Wed, 4 May 2005 13:37:04 -0700

Hi, Stefan -

I posted the question to the newsgroup you suggested on 4/30, and again
today. So far no answers. I may have to open a support incident.

I apologize for the tone of my message below. End of a long day with too
many MS things not working.

Kevin

""Stefan Schachner[MSFT]"" wrote:

>
> >>
> >>Thanks, YanHong. I wish that I, as a developer, had the ability (or the
> >>balls) to say to my client, "Gee, yes, that's a problem, but it's not my
> >>problem, it's MS's, or actually, it's not in this particular area, but in
> >>some other, which I don't have access to yet, so I really can't help you
> make
> >>my system work."
> >>
> >>Yup, that'd get me fired.
> >>
> >>Wish I could fire MS like that.
> >>
> >>I write this because it seems that MS has very recently started to get
> >>interested in gripes like mine, and I hope someone sees it. I've had
> major
> >>problems with printers on Terminal Services and Remote Assistance and
> other
> >>things recently, and they all affect my ability as a developer to deliver
> a
> >>good solution to my users. They expect me to have all the answers, and
> I'm
> >>not sure I can if MS doesn't.
> >>
> >>I write pretty complex systems, so I can understand part of MS's
> problems,
> >>but let me tell you, MS's cash flow is a whole lot bigger than mine is,
> and I
> >>wish they'd allocate some of it appropriately. I mean after 20 years
> they
> >>still can't write a decent word processor? No surprise if complicated
> stuff
> >>like Terminal Services breaks.
> >>
> >>Sorry to take this out on you, and nothing personal. but I'm about to
> give
> >>up and
> >>take up something like carpentry, where my Skil saw doesn't suddenly go
> off
> >>at a 90-degree angle. My tools should WORK! MS's DON'T.
> >>
> >>Kevin
> >>
> >>"Yan-Hong Huang[MSFT]" wrote:
> >>
> >>> Hello Kevin,
> >>>
> >>> Thanks very much for your feedback.
> >>>
> >>> I reviewed the email thread when Ray reported it to me. Based on my
> >>> understanding, this is a Remote Assistance related issue on windows.
> This
> >>> group is for security programing in platform SDK. Actually, all MSDN
> >>> managed newsgroups are supporting programming related issues. Windows
> OS
> >>> configuration/setup related issues are not covered in MSDN managed
> >>> newsgroup yet.
> >>>
> >>> For this issue, partner support private group is better for it. It is
> also
> >>> free to registered Microsoft partners. Please refer to the following
> link
> >>>
> https://partner.microsoft.com/US/technicalsupport/registeredsupport/40009639
> >>> It provides OS support, AD support, and other configuration support.
> >>>
> >>> Surely if you would like to use MSDN support on it, I think you can
> >>> consider using one of your free support incidents in MSDN package to
> >>> contact Microsoft and our support engineers will contact you directly
> on
> >>> it. If there is any unclear, please feel free to post here. Thanks very
> >>> much for your understanding.
> >>>
> >>> Best regards,
> >>> Yanhong Huang
> >>> Microsoft Community Support
> >>
> >>
> Hey Kevin,
> Please feel free to contact the MSDN Managed Newsgroup feedback alias
> (ngmsdnfb@microsoft.com)and some one will be more than happy to assist you..
>
> Yan-Hong and Rhett are not saying "Gee, yes, that's a problem, but it's not
> my problem" they are reiterating exactly what you said in your initial post
> "(I don't see a discussion group that this would naturally apply to. I
> hope
> Security is close enough.)" Unfortunately your question is not best suited
> for this newsgroup, the newsgroup best suited for this question is
> microsoft.public.windowsxp.work_remotely.. All Rhett was trying to do is
> assist you in locating the best resources to resolve your issue. Have you
> had a chance to post your question to that newsgroup yet? If you do not
> want to pursue that avenue then as Yan-Hong suggested we will be more than
> happy to open up a support call using one of your incidents.. If all of
> your incidents are used up then please contact us on the
> MsdnManagedNewsgroup Feedback alias and we will be more than happy to see
> what we can do to get you some assistance.
>
> I apologize for any inconvenience this delay may have caused you and if
> there is anything else I can do to assist you please let us know.
>
> Stefan Schachner
> MSDN Community Program Manager
> http://blogs.msdn.com/sschac
> This posting is provided “AS IS” with no warranties, and
> confers no rights.
>
>

Relevant Pages

  • Re: The Rules Of Conduct Just Went Out The Door
    ... >> This dustup is over FOUR incidents per month? ... >> Geez, people. ... > That is four incidents in the past month, only in this newsgroup and after ...
    (comp.databases.ms-access)
  • Re: The Rules Of Conduct Just Went Out The Door
    ... >>> I don't care about Steve's solicitations, ... That is four incidents in the past month, only in this newsgroup and after ...
    (comp.databases.ms-access)
  • Re: Revisions, track changes:
    ... I think I read somewhere that this may be causing a memory leak. ... worthwhile to open a support incident with Microsoft. ... This reply is posted in the Newsgroup; please post any follow question or reply ...
    (microsoft.public.word.vba.general)
  • Re: OEMStretchBltROP (i.e. DrvStretchBltROP)
    ... I wouldn't know what is going on without debugging it, ... what can be done in newsgroup. ... I would suggest you create a support incident, ... Microsoft DDK Support ...
    (microsoft.public.development.device.drivers)
  • RE: dialog database engine failure
    ... The only other thing I can suggest is to open a Support Incident with ... Microsoft support. ... If you're open to more extreme measures, you could try creating a new ... This reply is posted in the Newsgroup; please post any follow question or ...
    (microsoft.public.word.mailmerge.fields)
Quantcast