Prev: Remote Desktop Connection not working
Next: SBS 2008 RPC under wrong virtual directory in IIS
From: Susan Bradley on 7 Apr 2010 11:47
Leythos wrote:
> In article <e8Phxxl1KHA.5328(a)TK2MSFTNGP04.phx.gbl>, sbradcpa(a)pacbell.net
> says...
>
>> but to be clear to everyone SBS 2003 is not supported in HyperV .
>>
>>
>>
>
> That's why I'm not an MVP :-)
>
>
It has nothing to do with MVPdom it has to do with keeping clients on a
supported platform in case you need to call CSS.
From: Chucko on 7 Apr 2010 12:46
My advice to clients is to only upgrade when there is a compelling need or
reason to do so. In simpler terms, "if it's not broken, don't fix it".

We've been conditioned over the years to upgrade when new versions are
released by that is because it is in the financial best interests of the
software providers, not necessarily the users.

I'm perfectly happy to continue to use SBS 2003 for the majority of my
clients. It's solid, proven, stable, and meets their needs.

SBS 2008 does the same things, but not necessarily any better than SBS 2003
under normal circumstances.

If SBS 2003 currently meets your clients needs, what is their motivation for
upgrading?

"Boolean1" <Boolean1(a)discussions.microsoft.com> wrote in message
news:FD4076CF-F209-42B9-A0C2-D700A660045C(a)microsoft.com...
>I have a client on SBS2003 R2. They're okay with it, as it has been very
> stable environment for them. They would have upgraded to SBS2008 but
> decided
> not to because they see it as "an interim release" between SBS2008 R2 or
> SBS2010.
>
> Would you say that's a correct way of looking at this. I know the
> Exchange
> 2007 is a nice improvement with SBS2008. But they're actually okay with
> Exchange 2003 for now.
>
> They think they might want to wait for Exchange 2010 to be included before
> they consider upgrading. Not to rush them if they're happy, but I'm just
> curious to know when Exchange 2010 is slated to be part of the SBS family.
>
> Thanks,


From: Leythos on 7 Apr 2010 16:43
In article <OfcJlmm1KHA.5004(a)TK2MSFTNGP05.phx.gbl>, sbradcpa(a)pacbell.net
says...
>
> Leythos wrote:
> > In article <e8Phxxl1KHA.5328(a)TK2MSFTNGP04.phx.gbl>, sbradcpa(a)pacbell.net
> > says...
> >
> >> but to be clear to everyone SBS 2003 is not supported in HyperV .
> >>
> >>
> >>
> >
> > That's why I'm not an MVP :-)
> >
> >
> It has nothing to do with MVPdom it has to do with keeping clients on a
> supported platform in case you need to call CSS.

I know, I was kidding - I guess you didn't notice my :-) at the end of
the post.

--
You can't trust your best friends, your five senses, only the little
voice inside you that most civilians don't even hear -- Listen to that.
Trust yourself.
spam999free(a)rrohio.com (remove 999 for proper email address)
First  |  Prev  | 
Pages: 1 2 3
Prev: Remote Desktop Connection not working
Next: SBS 2008 RPC under wrong virtual directory in IIS