Kirk
Thu Mar 27 12:55:40 PDT 2008
This is a multi-part message in MIME format.
------=_NextPart_000_000C_01C89023.0168A730
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
I've been having all kinds of issues with my R2 keys.
Worked for a little while (about ten servers), then the "Invalid Key" =
problem started.
Still trying to get to the bottom of it. Not much success yet.
"Roberto R" <RobertoR@discussions.microsoft.com> wrote in message =
news:2F35AB7B-7432-4E2C-B079-516DFD924591@microsoft.com...
> Recently i have been upgrading all the servers to R2 with the =
exception of=20
> DCs. Upon upgrading one dc it prompted me to update the schema which i =
did=20
> with adprep /forestprep. After i ran the setup to install R2- it asks =
for=20
> product key to enter (so it can update the old standard to standard =
R2) after=20
> i enter my R2 key it comes back with invalid key. Very strange since =
this=20
> same product key works on all other standard servers equipped with =
Standard=20
> SP1 that i converted to R2. I did a little investigating to see if =
this only=20
> happened on that specific dc, so i try to upgrade another different dc =
to R2=20
> and after i enter the product key its says invalid. I verified with =
microsoft=20
> that the key is correct. Has anyone ever had this issue? any solution? =
thanks
------=_NextPart_000_000C_01C89023.0168A730
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.16608" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=3DVerdana size=3D2></FONT> </DIV>
<DIV><FONT face=3DVerdana size=3D2>I've been having all kinds of issues =
with my R2=20
keys.</FONT></DIV>
<DIV><FONT face=3DVerdana size=3D2>Worked for a little while (about ten =
servers),=20
then the "Invalid Key" problem started.</FONT></DIV>
<DIV><FONT face=3DVerdana size=3D2></FONT> </DIV>
<DIV><FONT face=3DVerdana size=3D2>Still trying to get to the bottom of =
it. =20
Not much success yet.</FONT></DIV>
<DIV><FONT face=3DVerdana size=3D2></FONT> </DIV>
<DIV><FONT face=3DVerdana size=3D2></FONT> </DIV>
<DIV> </DIV>
<DIV><FONT face=3DVerdana size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>"Roberto R" <</FONT><A=20
href=3D"mailto:RobertoR@discussions.microsoft.com"><FONT face=3DArial=20
size=3D2>RobertoR@discussions.microsoft.com</FONT></A><FONT face=3DArial =
size=3D2>>=20
wrote in message </FONT><A=20
href=3D"news:2F35AB7B-7432-4E2C-B079-516DFD924591@microsoft.com"><FONT =
face=3DArial=20
size=3D2>news:2F35AB7B-7432-4E2C-B079-516DFD924591@microsoft.com</FONT></=
A><FONT=20
face=3DArial size=3D2>...</FONT></DIV><FONT face=3DArial size=3D2>> =
Recently i have=20
been upgrading all the servers to R2 with the exception of <BR>> DCs. =
Upon=20
upgrading one dc it prompted me to update the schema which i did =
<BR>> with=20
adprep /forestprep. After i ran the setup to install R2- it asks for =
<BR>>=20
product key to enter (so it can update the old standard to standard R2) =
after=20
<BR>> i enter my R2 key it comes back with invalid key. Very strange =
since=20
this <BR>> same product key works on all other standard servers =
equipped with=20
Standard <BR>> SP1 that i converted to R2. I did a little =
investigating to=20
see if this only <BR>> happened on that specific dc, so i try to =
upgrade=20
another different dc to R2 <BR>> and after i enter the product key =
its says=20
invalid. I verified with microsoft <BR>> that the key is correct. Has =
anyone=20
ever had this issue? any solution? thanks</FONT></BODY></HTML>
------=_NextPart_000_000C_01C89023.0168A730--