Thanks.
That's interesting, never tested that way, but I heard something about
installing R2 after SP2 will cause problems to "if needed" uninstall SP2, so
I would assume that installing R2 after SP2 is possible... However according
with your experience doesn't sound that way, anyway could you post the exact
message that you're getting?
--
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MCSE, MVP Directory Services
"VG" <v...@vmware.com> wrote in message
news:%23G7QE8u...@TK2MSFTNGP04.phx.gbl...
Should we hold off on SP2 until we do R2 ????
--
Paul Williams
Microsoft MVP - Windows Server - Directory Services
http://www.msresource.net | http://forums.msresource.net
--
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MCSE, MVP Directory Services
"Geoff" <nigeltu...@gmail.com> wrote in message
news:uuNh3uyo...@TK2MSFTNGP03.phx.gbl...
I already had an enterprise Windows 2003 SP1 CD - I just integrated it using
MS methods (as I have since Windows 2000 days). When I had a Windows 2003
SP2 afterwards, I installed ona new server then tried to run the R2 we
originally received. Are you saying there are "newer" version of R2
specifically for SP2? If so, this would be ridiculuous. I attached the
screenshot error in the threads.
--
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MCSE, MVP Directory Services
"VG" <v...@vmware.com> wrote in message
news:esoRjPGp...@TK2MSFTNGP03.phx.gbl...
>
> "Jorge Silva" <jorges...@hotmail.com> wrote in message
> news:0661D7F8-E999-45DE...@microsoft.com...
> The exact message..is attached.
>
>
"Jorge Silva" <jorges...@hotmail.com> wrote in message
news:0EB2E8F6-269E-49DE...@microsoft.com...
I am still at lost how it works for others and not me...why did I get it
versus "everyone."
Just to recap...I integrated by Windows 2003 SP1 CD with SP2 source - to
generate a Windows 2003 SP2 integrated CD Enterprise Edition. Tried to
apply R2 on top of SP2 integrated disk and error was produced due to Service
Pack level not matching...change the R2INTL.INF (in the R2 folder) per Jorge
Silva's suggestion and it no longer produced the error.
"Jorge Silva" <jorges...@hotmail.com> wrote in message
news:0EB2E8F6-269E-49DE...@microsoft.com...
--
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MCSE, MVP Directory Services
"VG" <v...@vmware.com> wrote in message
news:OyOdDLip...@TK2MSFTNGP02.phx.gbl...
"Jorge Silva" <jorges...@hotmail.com> wrote in message
news:A222AB0D-B752-4740...@microsoft.com...