Re: Activated 2003SBS asking to be activated again?

From: Kevin Weilbacher [SBS-MVP] (kweilbacMVP_at_gte.net)
Date: 07/18/04 

Date: Sun, 18 Jul 2004 10:00:04 -0400

I'm sorry if some people appear to be beating up on you. Certainly, that is
not my intent.

If what this person did is proprietary information, I would not expect that
to be posted it here. But without hearing from this Microsoft person and
getting his/her input, how would we know?

As such, there has already been a post from another user with almost the
identical problem you had. It would be great for us to respond with
something like: "Yes, that has occurred with others and the possible
solution is (a) download this hotfix from Microsoft, or (b) call PSS, or (c)
rerun some utility, or (d) make the follwoing change to a registry, or (e)
whatever the correct answer is....

This is a community forum trying to help one another.

If I would "beat you up" on anything, it would only be the fact that you
seem to be resisting even contacting the person that helped you and letting
him/her know. If this person does not want to post directly to this
newsgroup, they could certainly contact any of the SBS MVP's by email or IM
for a private discussion. All MVPs have signed the appropriate
non-disclosure agreements with Microsoft, and know where to draw the line as
far as what can or cannot be shared with the public. 

-- 
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"
"Phydeux" <phydeux@phydeux.com> wrote in message
news:%23661p8JbEHA.2340@TK2MSFTNGP09.phx.gbl...
>     No, what I said (or at least intended to imply) was that he wouldn't
> even share with me what the cause or fix were.  He asked for admin access,
I
> gave it to him, ten minutes later he calls and says he's done.  I found no
> obvious traces of what he did, and he couldn't divulge the details.  So
its
> not a matter of whether or not I wanted to post the details here or not.
I
> simply don't HAVE the details.  He never told me what the problem was,
only
> that it was fixed.  I was happy enough with that.  And I simply let folks
> here know it had been solved.  I didn't expect anyone to get indignant
about
> it.  Geez!
>
>     As to my point about not wanting him to post it in public, that's only
> common sense.  If you were MS, would YOU want people posting proprietary
> information in a public forum?  IBM has backdoor codes for its servers
that
> their technicians can't even write down.  They have to call in on a
landline
> phone without a cordless handset and have the code given to them as they
> type it with no one in the room.  All this to maintain security of their
> proprietary secrets.  Its no wonder the guy didn't leave any ostensible
> traces for me to look at or tell me what was wrong.
>
>
> "root" <postmaster@buchanangc.com> wrote in message
> news:%23hYr7OEbEHA.1644@tk2msftngp13.phx.gbl...
> >
> > "Phydeux" <phydeux@phydeux.com> wrote in message
> > news:%23c7Qz0DbEHA.3684@TK2MSFTNGP09.phx.gbl...
> > > I'm not saying ignorance is bliss.  I'm saying that it would be
> > > irresponsible to put such information out into public view.
> >
> > That's utter CRAP.
> >
> > What you were asked to do is describe any known problem that may have
been
> > discovered!  What was the nature of the fix in general?  If the MS guy
> used
> > a proprietary technique to fix it and preferred not to describe that in
> > detail then NO ONE here would have complained.  Instead what you did was
> > INSULT us all by saying I'm telling you folks NOTHING!
> >
> > >  But that
> > > presupposes that I even knew what he did,
> >
> > We don't necessarily want to know wht he did.  WE want to know the issue
> he
> > fixed.  We want you to find him and ask him THAT!
> >
> > > but he kept me from seeing it as
> > > well.  So all I know is he went into the server by remote, ten minutes
> > later
> > > it was working fine.  What he did I'll never know, I'm just grateful
he
> > was
> > > able to correct it without having to rebuild the entire server.
> >
> > Find him again and ask him for the sake of all SBS2003 users.
> >
> > > "root" <postmaster@buchanangc.com> wrote in message
> > > news:%23ykv0I6aEHA.2812@TK2MSFTNGP11.phx.gbl...
> > > >
> > > > "Phydeux" <phydeux@phydeux.com> wrote in message
> > > > news:eOiLxa4aEHA.2516@TK2MSFTNGP10.phx.gbl...
> > > > >     He wouldn't even tell ME what it was he did, that's why he
> needed
> > to
> > > > > remote in himself.  And to be honest, I don't think we'd want him
to
> > > post
> > > > > what he did and how he did it in public.  Many could misuse such
> > > > information
> > > > > to bypass the Windows Activation system.  I'm happy just knowing
he
> > was
> > > > able
> > > > > to correct the issue.
> > > >
> > > > That kind of a response doesn't buy you much here.  Ignorance is
bliss
> > for
> > > > SBS2003 professionals is an insult!
> > > >
> > > >
> > > > > "Kevin Weilbacher [SBS-MVP]" <kweilbacMVP@gte.net> wrote in
message
> > > > > news:uUFqPgzaEHA.644@tk2msftngp13.phx.gbl...
> > > > > > It would be nice if you could get back to the person who helped
> you
> > > and
> > > > > say
> > > > > > that the folks here at the Microsoft SBS newsgroup would like to
> > know
> > > > (a)
> > > > > > what caused the problem, and (v)how this was fixed for future
> > > reference.
> > > > > Or
> > > > > > ask him/her to come to the NG themselves and post an
explanation.
> > > > > >
> > > > > > -- 
> > > > > > Kevin Weilbacher [SBS-MVP]
> > > > > > "The days pass by so quickly now, the nights are seldom long"
> > > > > >
> > > > > >
> > > > > > "Phydeux" <phydeux@phydeux.com> wrote in message
> > > > > > news:%23QAoIPxaEHA.3944@tk2msftngp13.phx.gbl...
> > > > > > >     I have no idea what it was, he said he could fix it if I
> gave
> > > him
> > > > > > > temporary admin access and the IP.  He logged in, did about 5
> > > minutes
> > > > > > worth
> > > > > > > of work, and logged out.  Whatever he did left no visible
> traces.
> > > But
> > > > > > then
> > > > > > > again, he works at MS so I'm sure he's privvy to a few things
> > we're
> > > > not.
> > > > > > > Either way, its fixed.
> > > > > > >
> > > > > > >
> > > > > > > "root" <postmaster@buchanangc.com> wrote in message
> > > > > > > news:%23w4E$lfaEHA.712@TK2MSFTNGP11.phx.gbl...
> > > > > > > >
> > > > > > > > "Phydeux" <phydeux@phydeux.com> wrote in message
> > > > > > > > news:%23M7W1cfaEHA.2840@TK2MSFTNGP11.phx.gbl...
> > > > > > > > >     Well, my client has a close friend who is pretty high
up
> > in
> > > > the
> > > > > > > > echelons
> > > > > > > > > at Redmond, and asked him to get involved.  He worked some
> > kind
> > > of
> > > > > > > magic,
> > > > > > > > > and corrected the issue remotely.  So now its resolved.
And
> > > with
> > > > > only
> > > > > > 3
> > > > > > > > > days left before the windows would have slammed shut on
the
> > > > server.
> > > > > > > > *PHEW!*
> > > > > > > > > I wonder if his friend could get me a job with MS?
> HMmmm....
> > > :)
> > > > > > > >
> > > > > > > > So did you ever find out what was happening?  What the fix
> was?
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

Relevant Pages

  • Re: Activated 2003SBS asking to be activated again?
    ... even share with me what the cause or fix were. ... obvious traces of what he did, and he couldn't divulge the details. ... >> I'm not saying ignorance is bliss. ... >> able to correct it without having to rebuild the entire server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Your customers and their access to the server?
    ... craig carrigan typed: ... not saying that you are wrong. ... their server, it's their data, and they can fire me at any time - I will ... happy to come in and fix it after. ...
    (microsoft.public.windows.server.sbs)
  • File upload broken in default site.
    ... a way to fix it. ... I keep getting the error message ... saying "Cannot run the FrontPage Server Extensions on this ... associated guff on the server. ...
    (microsoft.public.frontpage.client)
  • Re: Exchange System Manager, Error ID: c0072afc
    ... > You are saying that you had this problem before installing Outlook on the ... And decided to fix it by installing Outlook? ...
    (microsoft.public.exchange.admin)
  • Re: E-mail
    ... Select the mail account you want to fix. ... check the server, and the username to make sure they are correct. ... choose Use Secure Connection SSL encryption ... Under Authentication type choose password. ...
    (Fedora)