Archived from groups: microsoft.public.windowsxp.basics,microsoft.public.windowsxp.help_and_support (
More info?)
Michael,
Thanks for the response, and I agree that the current MVP program is
completely product-centric. However, I think you are missing the point of a
System Builder MVP program and what system builders are all about. In the US
alone, there are over 70k system builders (almost 200k worlwide) who have
special technical needs, training needs, pre-installation tools, and business
plans that go way beyond just talking about hardware. Also, the fact that
more computers are built world-wide by the small system builders than by the
big guys is another reason for the creation of a program such as this. We at
Microsoft need to do a better job of helping system builders survive and
compete with our products, and likewise we need to hear what they need from
us in future OS releases.
Microsoft is actually already very, very involved with system builders
(hince my job and my team <big grin>). While I also agree that some of the
discussion could be handled on 3rd party vendor sites, part of our
(Microsoft's) responsibility should be to help our partners (and end-users in
the ultimate sense) in any way we can. Heck, that is why we allow Windows
Update to provide updates to drivers in addition to hot fixes.
The whole idea of this thought is to help system builders be better at what
they do, and to have a group they can turn to for system builder issues.
Just my $.37 worth...
See ya,
Steve Winfield
National System Builder Tech Manager (aka BOB)
US Partner Group, Microsoft Corporation
"Michael Solomon (MS-MVP)" wrote:
> Just to add my 2 cents which might not be worth much, generally, the MS-MVP
> program is geared to help with specific MS Products. System Building
> doesn't actually fall into that category and the MS public newsgroups do
> include a Hardware newsgroup. I don't know that there are any "Hardware"
> specific MVPs but a number of MVPs who are versed in hardware issues do
> populate that group.
>
> We do occasionally get questions in these groups from system builders but
> generally, they are related to a specific product.
>
> System building issues don't fall under the purview of Microsoft. Hardware
> issues, drivers, updates compatibility are the responsibility of the
> manufacturer, something we preach in these groups as users sometimes get the
> idea that the OS will be patched to accommodate every individual problem or
> issue, something that is definitely not the case and decidedly wrong.
>
> I would think, if a system builder has some issue between the hardware and
> the OS, the public hardware group would be where he would post but an awful
> lot of those legitimately should go to the hardware manufacturer assuming
> the person with the issue can determine which piece of hardware is at fault.
>
> --
> Michael Solomon MS-MVP
> Windows Shell/User
> Backup is a PC User's Best Friend
> DTS-L.Org: http://www.dts-l.org/
>
> "Steve Winfield [MSFT]" <BOBTalk@microsoft.com> wrote in message
> news:9A0600EB-EB86-41F8-9EDD-919336BF5B3C@microsoft.com...
> > You bring up some very good points. I would imagine that the System
> > Builder
> > MVPs and System Builder newsgroup would focus more on issues for System
> > Builders only. If any end-user did post, then we would be good
> > net-citizens
> > and direct them politely and appropriately to the proper newsgroup or
> > resource. The main purpose is for System Builders to help System Builders
> > and to improve communication with Microsoft. This new approach would
> > address
> > all levels of System Builder questions, either from the peers or from
> > experts
> > at Microsoft.
> >
> > Regarding the idea of pointing end-users with issues to local resources,
> > there is actually a group working on this from the Microsoft Partner
> > Program
> > (so make sure you are registered at
> > www.microsoft.com/partner...hint-hint).
> >
> > Thanks for the great input.
> >
> > If you want to get involved in the idea, please send me an e-mail at
> > BOBTalk@microsoft.com.
> >
> > See ya,
> > Steve
> >
> > Regarding
> >
> > "D.Currie" wrote:
> >
> >> Seems to me that system builders and others who are dealing with
> >> repairing
> >> other people's computers are going to run into problems that don't apply
> >> to
> >> someone tweaking their own system. And we've also probably got an array
> >> of
> >> tools that an average user isn't going to have available. And when we
> >> have a
> >> problem, by the time we come to a group to ask a question, it's not going
> >> to
> >> be a simple matter of scanning for viruses.
> >>
> >> Just wondering though -- are you imagining that this is going to be open
> >> to
> >> the public, or is it going to be private? If it's a public group, one
> >> benefit might be some sort of referral system where people looking for
> >> repairs, computer, on-site service, technical support, or whatever, might
> >> get a link to a business in their area. The downside to making it public
> >> is
> >> that folks will be posting the simple questions and expecting
> >> professional
> >> answers, where the system builders would be looking to solve their own
> >> unique problems with help from peers.
> >>
> >>
> >> "Steve Winfield [MSFT]" <BOBTalk@microsoft.com> wrote in message
> >> news:7194496A-E27B-4764-B822-B890DB04A8A5@microsoft.com...
> >> > Why is it that the product groups get to have all of the fun? I see
> >> > MVPs
> >> > all
> >> > the time for XP and for Server and for IIS and for SQL, but where are
> >> > the
> >> > MVPs for System Builders? They tell me there cannot be an MVP group
> >> > for a
> >> > "Program", only for products because there would not be enough to offer
> >> > either side in the relationship.
> >> >
> >> > Dang it...I say that is not true. I can think of many ways in which a
> >> > n
> >> > MVP
> >> > program could be beneficial to both Microsoft and to the System
> >> > Builders
> >> > involved.
> >> >
> >> > Maybe we should just create a group called System Builder MVPs and
> >> > prove
> >> > that we are a "worthy" group...
> >> >
> >> > Before I give my ideas as to what would be involved in this
> >> > give-and-take
> >> > relationship, what are your thoughts? If you were an MVP, what would
> >> > you
> >> > expect to get from Microsoft and what should you be expected to do in
> >> > turn?
> >> >
> >> > (Note - There are no dumb ideas here, only dumb people...wait, that
> >> > doesn't
> >> > sound right...<big grin>)
> >> >
> >> > --
> >> > Steve Winfield
> >> > National SB Tech Manager (aka BOB)
> >> > US Partner Group, Microsoft
> >> >
> >> > ***E-mail: BOBTalk@microsoft.com***
> >> > *** Web: oem.microsoft.com/BOB***
> >>
> >>
> >>
>
>
>