Al
Wed May 14 09:10:55 PDT 2008
This is a multi-part message in MIME format.
------=_NextPart_000_0012_01C8B5AA.CC5724B0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
I had thought if you purchased Software Assurance on an OEM version =
within 90 days it converts it to retail, meaning it could be transferred =
(or something like that...)
Also, on a related note do you happen to know if the "Retail Upgrade" =
T75-00750 version (we upgraded from SBS 4.5) of SBS2003 is considered =
transferrable?
Thanks.
--=20
Allan Williams
"Cris Hanna [SBS-MVP]" <crisnospamhanna@cpunospamservices.net> wrote =
in message news:O2bHdedtIHA.4260@TK2MSFTNGP05.phx.gbl...
You are pretty much spot on
If you have a castastrophic hardware failure, you are somewhat =
screwed. You buy a new copy of SBS 2003
No, there is no option to "upgrade" OEM software to non-oem
Volume licensing or Full Retail copies are the only ones that can =
restore to new hardware
--=20
Cris Hanna [SBS-MVP]
-------------------------------------------------
Microsoft MVPs
Independent Experts (MVPs do not work for MS)
Real World Answers
---------------------------------------------------------
Please do not contact me directly regarding issues
"brianadkins" <brianadkins@discussions.microsoft.com> wrote in =
message news:8256B0D3-713A-4EE1-942C-6678E46B3B4D@microsoft.com...
So then this highlights the 4th question in my post:
4. Is there a way to upgrade our OEM SBS 2003 to a non-OEM version =
that
can be transfered via a disaster restore?=20
It sounds like if one actually purchases and use OEM SBS , you are =
giving up=20
the ability to every have a real disaster recovery plan in the =
future?
If this is not the case, then what might a disaster recovery plan =
look like=20
for OEM SBS 2003?
-Brian
"Cris Hanna [SBS-MVP]" wrote:
> The simple answer is, you as the end user, cannot re-install any =
OEM software (XP, SBS, Office, Windows Server Std, etc., etc.) on new =
hardware.
>=20
> There are certain circumstances under warranty situations where an =
OEM can do this but as the end user, OEM is tied to the hardware it was =
sold with...cannot be moved to new hardware.
>=20
>=20
>=20
> --=20
> Cris Hanna [SBS-MVP]
> -------------------------------------------------
> Microsoft MVPs
> Independent Experts (MVPs do not work for MS)
> Real World Answers
> ---------------------------------------------------------
> Please do not contact me directly regarding issues
>=20
> "brianadkins" <brianadkins@discussions.microsoft.com> wrote in =
message news:E0719D77-D542-4B02-B9FE-F2D2230CE4F8@microsoft.com...
> We are developing / testing our disaster recovery processes and =
are using=20
> Acronis True Image with the Universal Restore option. However, =
I'm pretty=20
> clueless about MS licensing...
>=20
> If our SBS 2003 domain controller dies ... we have an Acronis =
image that we=20
> can restore to a different piece of hardware using the Universal =
Restore=20
> option (bare-metal to different hardware).
>=20
> 1. How does MS licensing impact this scenario?=20
> 2. Will we be allowed to activate the OS on the new hardware =
platform=20
> since it is an OEM version?=20
> 3. Would this be any different if it were Windows Server 2003 =
instead of=20
> SBS ? (we have that scenario also)
> 4. Is there a way to upgrade our OEM SBS 2003 to a non-OEM =
version that=20
> can e transfered via a disaster restore?
>=20
> Finally, in order to even test out our disaster recovery plan, =
we would need=20
> to activate Windows Server on the new (different) hardware =
platform for a=20
> short period of time to validate that everything works.
>=20
> ...How are other companies working through this same disaster =
recovery=20
> scenario with MS licensing?
------=_NextPart_000_0012_01C8B5AA.CC5724B0
Content-Type: text/html;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8">
<META content=3D"MSHTML 6.00.6000.16640" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>I had thought if you purchased Software Assurance on =
an OEM=20
version within 90 days it converts it to retail, meaning it could be =
transferred=20
(or something like that...)</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>Also, on a related note do you happen to know if the =
"Retail=20
Upgrade" T75-00750 version (we upgraded from SBS 4.5) of SBS2003 is =
considered=20
transferrable?</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>Thanks.</FONT></DIV>
<DIV><FONT size=3D2></FONT><BR>-- <BR>Allan Williams</DIV>
<DIV> </DIV>
<DIV><BR> </DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Cris Hanna [SBS-MVP]" <<A=20
=
href=3D"mailto:crisnospamhanna@cpunospamservices.net">crisnospamhanna@cpu=
nospamservices.net</A>>=20
wrote in message <A=20
=
href=3D"news:O2bHdedtIHA.4260@TK2MSFTNGP05.phx.gbl">news:O2bHdedtIHA.4260=
@TK2MSFTNGP05.phx.gbl</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>You are pretty much spot =
on</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>If you have a castastrophic hardware =
failure, you=20
are somewhat screwed. You buy a new copy of SBS =
2003</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>No, there is no option to "upgrade" =
OEM software=20
to non-oem</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Volume licensing or Full Retail =
copies are the=20
only ones that can restore to new hardware</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><BR>-- <BR>Cris Hanna=20
=
[SBS-MVP]<BR>-------------------------------------------------<BR>Microso=
ft=20
MVPs<BR> Independent Experts (MVPs do not work for MS)<BR>Real =
World=20
=
Answers<BR>---------------------------------------------------------<BR>P=
lease=20
do not contact me directly regarding issues<BR></DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"brianadkins" <<A=20
=
href=3D"mailto:brianadkins@discussions.microsoft.com">brianadkins@discuss=
ions.microsoft.com</A>>=20
wrote in message <A=20
=
href=3D"news:8256B0D3-713A-4EE1-942C-6678E46B3B4D@microsoft.com">news:825=
6B0D3-713A-4EE1-942C-6678E46B3B4D@microsoft.com</A>...</DIV><BR>So=20
then this highlights the 4th question in my post:<BR> 4. Is =
there a way=20
to upgrade our OEM SBS 2003 to a non-OEM version that<BR>can be =
transfered=20
via a disaster restore? <BR><BR>It sounds like if one actually =
purchases and=20
use OEM SBS , you are giving up <BR>the ability to every have a real =
disaster recovery plan in the future?<BR><BR>If this is not the =
case, then=20
what might a disaster recovery plan look like <BR>for OEM SBS=20
2003?<BR><BR>-Brian<BR><BR>"Cris Hanna [SBS-MVP]" wrote:<BR><BR>> =
The=20
simple answer is, you as the end user, cannot re-install any OEM =
software=20
(XP, SBS, Office, Windows Server Std, etc., etc.) on new =
hardware.<BR>>=20
<BR>> There are certain circumstances under warranty situations =
where an=20
OEM can do this but as the end user, OEM is tied to the hardware it =
was sold=20
with...cannot be moved to new hardware.<BR>> <BR>> <BR>> =
<BR>>=20
-- <BR>> Cris Hanna [SBS-MVP]<BR>>=20
-------------------------------------------------<BR>> Microsoft=20
MVPs<BR>> Independent Experts (MVPs do not work for =
MS)<BR>>=20
Real World Answers<BR>>=20
---------------------------------------------------------<BR>> =
Please do=20
not contact me directly regarding issues<BR>> =
<BR>> =20
"brianadkins" <<A=20
=
href=3D"mailto:brianadkins@discussions.microsoft.com">brianadkins@discuss=
ions.microsoft.com</A>>=20
wrote in message <A=20
=
href=3D"news:E0719D77-D542-4B02-B9FE-F2D2230CE4F8@microsoft.com">news:E07=
19D77-D542-4B02-B9FE-F2D2230CE4F8@microsoft.com</A>...<BR>>  =
;=20
We are developing / testing our disaster recovery processes and are =
using=20
<BR>> Acronis True Image with the Universal Restore=20
option. However, I'm pretty <BR>> clueless =
about MS=20
licensing...<BR>> <BR>> If our SBS 2003 domain =
controller=20
dies ... we have an Acronis image that we <BR>> can =
restore=20
to a different piece of hardware using the Universal Restore=20
<BR>> option (bare-metal to different =
hardware).<BR>>=20
<BR>> 1. How does MS licensing =
impact this=20
scenario? <BR>> 2. Will we be =
allowed to=20
activate the OS on the new hardware platform <BR>> =
since it=20
is an OEM version? <BR>> 3. Would =
this be=20
any different if it were Windows Server 2003 instead of =
<BR>> =20
SBS ? (we have that scenario =
also)<BR>> 4.=20
Is there a way to upgrade our OEM SBS 2003 to a non-OEM version that =
<BR>> can e transfered via a disaster =
restore?<BR>>=20
<BR>> Finally, in order to even test out our disaster =
recovery plan, we would need <BR>> to activate =
Windows Server=20
on the new (different) hardware platform for a <BR>> =
short=20
period of time to validate that everything works.<BR>>=20
<BR>> ...How are other companies working through this =
same=20
disaster recovery <BR>> scenario with MS=20
licensing?</BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_0012_01C8B5AA.CC5724B0--