Re: Bug IIS 6 Anonymous Access

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Wade A. Hilmo [MS] (wadeh_at_microsoft.com)
Date: 01/17/05 

Date: Sun, 16 Jan 2005 21:15:43 -0800

Pardon my jumping in, but I want to make a few comments on some of the
technical and process topics here.

Regarding the issue of finding bugs in IIS, there are a few product group
members that read and respond to a number of newsgroups, including this one.
In most cases where one of use gets involved, we can help out with getting
IIS to work the way it is supposed to. This is good for the posters because
we can help resolve issues. It is good for the product group because it
gives is some feeling for how our product actually works in the field, and
how it doesn't work. We can use this information to improve the product in
the future.

Occasionally, someone will report an issue that turns out to be a genuine
bug in IIS. When this happens, we can offer workarounds and we can make
note of the problem. This is certainly not a guarantee that the product
will be fixed in a future version, but we do fix a lot of bugs (and make
changes to product design) based on discussions on this newsgroup.

If someone runs into a bug in IIS that they would like to see fixed, it is a
bit more complicated. For a number of reasons - which I won't go into
here - we need to get PSS to sponsor a hotfix release. This is why we refer
folks to PSS when they would like to see a hotfix. Note that this does not
mean that you have to explain your problem all over again to Microsoft.
When I refer someone to PSS for this purpose, I have them give my name to
the PSS engineer that handles the case - specifically so that they do not
have to start all over again at working the issue. (And once in a while,
I've even made the fix and I'm just waiting for the customer to get PSS to
kick off the process so that we can release it.)

Finally, to be clear, referring someone to PSS for a hotfix does not
guarantee that we will produce a hotfix. There are a number of factors that
need to be weighed on a case by case basis. For the purpose of my
statements below, I am using this bug as an example, and only looking at the
technical factors. If I understand correctly, my personal recommendation
would probably be to not issue a hotfix. The reason is that, once the
problem is identified on a machine, it is not difficult to resolve through
system configuration. This issue would be a very good candidate for a
Knowledge Base article (again, if I understand the technical issue fully.)
Also, as David's response suggests, I would certainly recommend that we fix
this in the next version of the product - but as you have surmised, this is
not a guarantee.

I hope that this answers some of the objective issues raised in this thread.

Thank you,
-Wade A. Hilmo,
-Microsoft

"Roland Hall" <nobody@nowhere> wrote in message
news:OWJwc08#EHA.2192@TK2MSFTNGP14.phx.gbl...
> "David Wang [Msft]" wrote in message
> news:Ox94pAw%23EHA.4072@TK2MSFTNGP10.phx.gbl...
> : I'm sorry if I offended you by being honest and frank and I apologize.
I
> am
> : an engineer and simply do not want to put on a marketing/sales cap and
> : mislead anyone by sugar coating the truth.
>
> All MSFT salespeople mislead their customers?
>
> : I acknowledged the customer's
> : bug, noted that I will make sure it will be fixed in a future release,
>
> Entering a bug report is a personal guarantee?
>
> : and
> : if you want a fix in the current release you have to engage PSS.
>
> Tell the story again to MSFT because once is not enough.
>
> : I thought I
> : was doing everyone a favor by being transparent with the process
affecting
> : the issue at hand (how to get a fix for IIS6)
>
> "How to get a fix for IIS" is guaranteed if PSS is contacted.
>
> : -- hopefully dispelling the
> : popular belief that Microsoft is arrogant and does not listen to
> : customers
>
> It's a popular belief that MSFT is arrogant and doesn't listen to their
> customers?
>
> : -- we listen a whole lot... but business does tend to drive those
> : decisions, and the net result is that Microsoft appears to not listen.
>
> Perhaps just listening is not enough?!
>
> : Please do not get me wrong -- I agree with your points. As someone who
> : tests software, I always want bugs to be fixed the right way, no matter
> when
> : they are found, and as fast as possible.
>
> That was not my point. My point was to be more compassionate with someone
> reporting a bug you have verified to be authentic.
>
> : I just happen to also see the
> : reality side of product servicing and wanted to share some additional
> : viewpoints.
>
> Implying reality is incomprehensionable on this end?
>
> : I realize that reality is harsh and that the truth can hurt, but
> : what doesn't kill you should make you stronger.
>
> That's great but we're not out at the bar trying to pick someone up at
> closing time.
>
> : The only safe response I can make to the remainder of your comments is
to
> : say that we are all making our best efforts to make the other party
happy,
> : within reason. If that is unreasonable to you, then as in life, you
> always
> : have a choice as to continue the relationship or not.
>
> So much for safe after including the final sentence. I'm a MSFT partner.
> Informing me I have the option of terminating my relationship with MSFT
> because I think your comments are arrogant and unprofessional leads me
only
> to reinforce my views. What I will terminate is this conversation and I
> doubt you and I will have any in the future.
>
> --
> Roland Hall
> /* This information is distributed in the hope that it will be useful, but
> without any warranty; without even the implied warranty of merchantability
> or fitness for a particular purpose. */
> Technet Script Center - http://www.microsoft.com/technet/scriptcenter/
> WSH 5.6 Documentation -
http://msdn.microsoft.com/downloads/list/webdev.asp
> MSDN Library - http://msdn.microsoft.com/library/default.asp
>
>
>

Relevant Pages

  • Re: Bug IIS 6 Anonymous Access
    ... of the initial response was frank but blunt and could use some tact -- it is ... If someone runs into a bug in IIS that they would like to see fixed, ... here - we need to get PSS to sponsor a hotfix release. ... :> Tell the story again to MSFT because once is not enough. ...
    (microsoft.public.inetserver.iis)
  • Re: Bug IIS 6 Anonymous Access
    ... If someone runs into a bug in IIS that they would like to see fixed, ... here - we need to get PSS to sponsor a hotfix release. ... :> Tell the story again to MSFT because once is not enough. ... :>: The only safe response I can make to the remainder of your comments is ...
    (microsoft.public.inetserver.iis)
  • Re: "There is not enough space on drive" error for SP3
    ... I've been told that this problem has been confirmed by PSS and the article ... This posting is provided "AS IS" with no warranties, ... >> guys should post this as a bug, ... >> Talha Rizvi ...
    (microsoft.public.sqlserver.security)
  • RE: CommandBarControl - keeping them tied to the menu item
    ... I understand that the bug won't be fixed for awhile. ... Why I suggest contact MS PSS is ... > request for a hotfix. ... > Microsoft Online Partner Support ...
    (microsoft.public.office.developer.com.add_ins)
  • Re: Security Update 8.00.0679
    ... Would it be possible for you to work with PSS to see if the problem can be ... We have rerun our tests on this build, and have not hit the problem. ... > I ran the Security Update that updated SQL to Build ... > It appears this bug is back. ...
    (microsoft.public.sqlserver.security)