Re: SBS2003 to 2008 migration on the same box (not upgrading)?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Now what would ever make you think such a thing?<G>

Honestly, I expect Jeff to have an excellent solution that will give you a fall back position. Something the MS method lacks. But there's not a whole lot he can do to improve the Exchange situation, except to protect us from a bad result. The limitations are inherent in the process and design that Exchange has foisted on us.

--
Charlie.
http://msmvps.com/blogs/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel

"SteveB" <newsgroup@xxxxxxxxxx> wrote in message news:%232WISeOHJHA.2408@xxxxxxxxxxxxxxxxxxxxxxx
Do you think Jeff might have a "better" way up his sleeve?

"Charlie Russel - MVP" <charlie@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:OqLNWROHJHA.2580@xxxxxxxxxxxxxxxxxxxxxxx
Yeah, no forklift. Sigh. What you have to do is bring both versions of Exchange up, and then move them, including all replicas, from one to the other. The process is S L O W. On a large SBS, with large mailboxes, I'm guessing we're talking days not hours. Even essentially new empty mailboxes were hours.

--
Charlie.
http://msmvps.com/blogs/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel

"SuperGumby [SBS MVP]" <not@xxxxxxxxxxx> wrote in message news:Oq14H2MHJHA.3736@xxxxxxxxxxxxxxxxxxxxxxx
yeah Jim, if moving from 2003 to 2008 via a tempDC I would also keep the tempDC at 2003, I see no reason to affect the originAD in order to accomodate a 2008 DC, the targetAD can be adjusted while at 2003 level, on the tempDC, to allow SBS 2008 to be incorporated, but at this time it would be disconnected from originAD and have references removed about originSBS.

SO, it seems you guys are telling me I can't 'forklift' a store from Exch03 to Exch08. BUMMER (if true), how do they handle 'inplace upgrade' of Exch? or is that also 'not supported'.
(not much Exch08fu in this grasshopper)

I don't really see much problem in using an RSG as an interim step. Creation, and subsequent removal, of an RSG is simple in Exch03, does Exch08 make it more difficult?

"Jim Behning SBS MVP" <jimbehning@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:o1afd49v63l3psm5vqc6cu5j1d79s99nuf@xxxxxxxxxx
You know better as I have not suffered this yet. Introducing the
recovery storage group might be more fun than one wants?

On Mon, 22 Sep 2008 06:47:12 -0700, "Charlie Russel - MVP"
<charlie@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

Well, no, you could use an SBS 2k3 tempdc. In fact, I'd prefer it. You'd
have to move the Exchange using a recovery group mount, but that should be
doable.


--
Charlie.
http://msmvps.com/blogs/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel

"Jim Behning SBS MVP" <jimbehning@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:4r6fd4hgnmp5c4rvtfdgl7t9ulnt3vt2kp@xxxxxxxxxx
And it requires a 64 bit, 4 gig ram minimum temporary machine. Granted
that box is only $600 if you do not happen to have a modern box that
will take 4 gigs of ram. Any new decent workstation should be 64 bit
and take some more ram and a new temporary hard drive.

On Sun, 21 Sep 2008 22:20:37 -0700, "Charlie Russel - MVP"
<charlie@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

You're going to have to have someplace to park the current domain and
exchange. A swing to a temporary box and then flatten your original and
install back on it would work, but it's a lot trickier here since you
can't
do a simple move of the Exchange files. You have to move the individual
mailboxes while you have both versions of Exchange up and running. And it
will be slow. Really slow.

--
Charlie.
http://msmvps.com/blogs/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel

"Milhouse Van Houten" <btvs@xxxxxxxxxxxxx> wrote in message
news:uJ$6CBGHJHA.3668@xxxxxxxxxxxxxxxxxxxxxxx
I've read through the 2008 migration installation CHM file, and that
sounds terrific if you have a new server available, but what about the
situation where you want to put 2008 on the same box as 2003? I'm not
speaking of an upgrade, which I know isn't supported because of the move
to 64-bits, but a separate clean installation of 2008 on another
partition
which could utilize some form of earlier export from 2003 (AD, settings,
etc) that could be imported into 2008? I realize this is far from
ideal,
but I was wondering if there was a means for doing it.

Let's assume in this case that the box meets specs (enough RAM, 64-bit
CPU).

Thanks
See what SBS support is working on
http://blogs.technet.com/sbs/default.aspx
Check your SBS with the SBS Best Practices Analyzer
http://blogs.technet.com/sbs/archive/tags/BPA/default.aspx
See what SBS support is working on
http://blogs.technet.com/sbs/default.aspx
Check your SBS with the SBS Best Practices Analyzer
http://blogs.technet.com/sbs/archive/tags/BPA/default.aspx






.

Relevant Pages

  • Re: SBS2003 to 2008 migration on the same box (not upgrading)?
    ... The process is S L O W. On a large SBS, ... mailboxes, I'm guessing we're talking days not hours. ... Move Mailbox wizard that you run from within the Exchange Management ... originAD and have references removed about originSBS. ...
    (microsoft.public.windows.server.sbs)
  • RE: Configuring exchange 2003 in SBS
    ... As I know, this is not related to per user mailbox, it refer to the mailbox ... store on the whole Exchange server. ... This newsgroup only focuses on SBS technical issues. ... What minimum requirement if I want this server for a fileserver? ...
    (microsoft.public.windows.server.sbs)
  • Re: So why SBS?
    ... Public folders will be in the next version.. ... If SBS isn't for you...that's fine. ... Mailenable is an example of a freeware or pay for extra's, mail server. ... It is infinitly simpler to configure than Exchange once installed. ...
    (microsoft.public.windows.server.sbs)
  • Re: So why SBS?
    ... Public folders will be in the next version.. ... The sad part of most of us is that we haven't even tried or practiced a backup/restore and we freak out over a 'single" SBS box when we haven't even tried to restore it from a harddrive. ... Exchange seems to mix its words and titles, the global/generic use of POP and SMTP for just about every Exchange function is dumb, MailEnable understands post office protocol and simple mail transfer protocol in a "meaningfull" way. ... The standard profiles in Server are quite effective assuming you add new users to the correct account in the first place and your note running more than 1 file server. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS2003 to 2008 migration on the same box (not upgrading)?
    ... What you have to do is bring both versions of Exchange up, and then move them, including all replicas, from one to the other. ... The process is S L O W. On a large SBS, with large mailboxes, I'm guessing we're talking days not hours. ... tempDC at 2003, I see no reason to affect the originAD in order to accomodate a 2008 DC, the targetAD can be adjusted while at 2003 level, on the tempDC, to allow SBS 2008 to be incorporated, but at this time it would be disconnected from originAD and have references removed about originSBS. ... it seems you guys are telling me I can't 'forklift' a store from ...
    (microsoft.public.windows.server.sbs)