Re: Migrate SBS2003 to new R2 installation
- From: "Al" <noreply@xxxxxxxxxxxxxxxx>
- Date: Sat, 28 Apr 2007 21:34:28 +0100
I'm in the same boat!! Half way there so far with 2 half days of work (and
I am not a techie!) - the main issues I have hit so far are that ISA Server
required a service pack to be applied before it would start!! (no mention
that I could find in the documentation) and with using exmerge to create the
pst files, need identical user mailbox names (obviously) and when importing
them I found that the sbs 2003 server's admin account did not have the
correct permissions to access mailboxes which took a couple of hours to find
from a google search & remedy. Fortunately my instal is for only 3/4 users
so I can see why the "experts" are keen to promote the "swing" pack for more
complicated sites. I have been running the new server with a test
workstation alongside (but on separate network switch/hub) pending the final
switch over & this certainly gives testing comfort!!
Good luck - it will be interesting to see how we get on with this, rather
than purchasing the "swing" kit.
"Cris Hanna [SBS-MVP]" <crisnospamhanna@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
wrote in message news:O5QbtMchHHA.4288@xxxxxxxxxxxxxxxxxxxxxxx
The swing migration is not painful at all other than the need for an
interim box for the swing but this can even be a workstation as its only
temporary.
And you will have more pain and upset from your customer over:
The new domain
Downtime
To name a couple
The Swing Migration is relatively invisible to your customer, since the
new server has the same server name, etc.
You can certainly do what your suggesting but you really have to question
if thats best for your customers.
--
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
"Bill Kuhn - MCSE" <bkuhn@xxxxxxxxxxxxx> wrote in message
news:CEEC6C6A-CE2E-4A56-A9D2-0D1808D33FE6@xxxxxxxxxxxxxxxx
We have a couple of SBS2003 Premium -> R2 upgrades that include new
server
hardware coming up.
From what I see, an actual migration looks fairly painful whether
Microsoft
whitepaper instructions are followed or a 'swing' migration is attempted.
In out cases, neither migration involves a lot of users (<15 users each).
It looks to me like our most straightforward process is likely to be
* copy existing exchange mail to PSTs for all users
* backup SQL databases (both customers use SQL for more than just
sharepoint)
* copy all customer data to USB drive
* install R2 on new hardware as a new domain
* recreate user accounts
* join workstations to new domain
* restore customer data and appropriate securities and shares
* restore SQL databases
* configure internet access/backups/SUS/etc
To me, this is a straightforward way to move the servers w/o relying on
quirky tools or worrying about really odd errors cropping up in the
middle
of migration.
Now to the question..
What I don't know how to do (if possible) is..
How can I migrate sharepoint (at least lists and calendar items) to the
new domain??
Bill Kuhn - MCSE
The Kuhn Group, Inc.
http://www.kuhngroup.com
.
- References:
- Migrate SBS2003 to new R2 installation
- From: Bill Kuhn - MCSE
- Re: Migrate SBS2003 to new R2 installation
- From: Cris Hanna [SBS-MVP]
- Migrate SBS2003 to new R2 installation
- Prev by Date: Re: Can't read memory!!!!!
- Next by Date: Re: SBS Backup
- Previous by thread: Re: Migrate SBS2003 to new R2 installation
- Next by thread: Re: POP3 and SMTP on the same account
- Index(es):
Relevant Pages
|
