Marina,
Not so much a typo as undisclosed thinking. Here's my backstory.
Most people who are running SBS 2003 (pre-R2) who then are deciding to run
SBS 2003 R2 are moving up from an OEM version of non-R2 to a retail/license
version of R2 (or -shudder- improperly using OEM media from a different
source). As such, my experience is that rerunning SBS Setup to get common
bits on all product is not only a license compliance thing, it's a disaster
recovery thing. You can get in trouble if you need to do a bare metal
recovery. Your installation sequence is to build a baseline of the server
media in hand in order to do an ASR full System State restore of the
installed version in the backup set. This can't happen (you say) without the
media in hand being the same as the media installed? It can if you are in
the middle of an upgrade or migration that crashes. You can have a situation
where the newer media is the media in hand and the backup refuses to install
over it with an "earlier version". (Think: You can't install Windows 2003 to
then restore Windows 2000 server on top, it's blocked. Now think in finer
resolution about the difference in schema version of Windows 2003 R2 and
Windows 2003...you get the same picture.)
I agree with you that you can run the setup disk and as long as SBS 2003 SP1
was previously installed the R2 bump should work just to give you SBS 2003
R2 features to play with. But I have run into cases where you couldn't
install the R2 without rerunning the entire set.
But with all that said, I am under the impression that one will not be able
to move to the final step he's cited to successfully run the SBS 003 R2
Transition Pack on this server unless one does the full SBS product update
to establish the baseline install using SBS 2003 R2, the Transition Pack
will say it can't run. Or worse, it will run as far as it can before it
dies.
Maybe I'm just trying to do the guys in 2nd Level SBS CSS a favor with a
better baseline for that "Transition Pack install failed, server down
support case" they will get. :-)
So I was leaning to the safe side (and shorter explanation) to suggest that
the CD set install probably would need to be installed in order to complete
the entire sequence he is asking about for the purpose he is stating.
- Jeff Middleton SBS-MVP
"Marina Roos [SBS-MVP]" <> wrote
in message news:%...
> Typo Jeff? R2 is just one CD that needs to be installed. You really don't
> need to reinstall all of the SBS cd's to get it to R2.
>
> --
> Regards,
>
> Marina Roos
> Microsoft SBS-MVP
> One of the Magical M&M's
> www.smallbizserver.net
> Take part in SBS forum:
> http://www.smallbizserver.net/Default.aspx?tabid=53
> "Jeff Middleton [SBS-MVP]" <> wrote in message
> news:...
>> John,
>>
>> You can in-place upgrade your existing server's installation of SBS 2003
>> with SBS 2003 R2 media. Generally this means a reload of the entire CD
>> set, not just the last CD.
>>
>> However, if you are preparing to move next to obtain and run the SBS R2
>> Transition Pack, this implies you are trying to exit from SBS product
>> feature/restrictions. That begs the question of "are you planning to
>> continue running your existing server configuration as is after the
>> Transition Pack or is all this just part of yet another step plan to go
>> to a new server with non-SBS features?"
>>
>> If you see the Transition Pack as ideal to your needs, you might first
>> confirm that you can actually even buy it still. Last I heard it had been
>> eliminated as a product option. You should also be aware that you do not
>> have assurance that your desirable SBS features (SBS Fax, RWW, SBS
>> Console, setup wizards, POP3 Connector, etc) are not assured to work and
>> will not be supported once you run the Transition Pack on your server.
>> You may find this also complicates any repair situations you have with
>> this server.
>>
>> If what you really want is the exact same server you have, on the
>> hardware you have, but without the SBS features and constraints, then I
>> suppose the R2 upgrade followed by Transition Pack may be your ticket.
>> But if you are actually trying to just move on to a new server without
>> SBS involved, all of this is mostly a waste of time and expense because
>> it's not necessary. You can accomplish the same thing using a Swing
>> Migration to simply move to the new server based operations without these
>> additional purchases.
>>
>> I would be happy to address any clarification you want to have on doing a
>> Swing Migration to address this project. You are welcome to post your
>> questions here or follow-up with me directly by email or through my
>> website at www.SBSmigration.com.
>>
>> Jeff Middleton SBS-MVP
>>
>>
>>
>> "JohnG" <> wrote in message
>> news:4b135e00$...
>>> Hi Guys,
>>>
>>> I inherrited a nework with SBS 2003. It has SP2 (Win & Exchange SP2)
>>> loaded but not the R2 component. SbS 2003 R2 has been purchased but not
>>> installed.
>>>
>>> We are looking at the R2 tranistion pack which I guess requires SBS R2
>>> installed.
>>>
>>> How do I load R2 component can just install R2 over SP2?
>>>
>>
>>
>
>
Similar Threads
Linear Mode
