Migration from SBS to 2003 Enterprise Server - Exchange Disaster?



The company I've been working with has had a pair of servers running SBS for
several years. I am at a loss to understand how they got two SBS servers
running on the same domain in the first place, but when I came into the
picture that is how it was. One was the domain controller and file server
while the other was the exchange server.

A hard drive failed in the mail server and the system was physically
unrecoverable.

I immediately built a new server using the second SBS license creating a new
domain and hand recreating the user accounts...as an emergency way to get
their email back in service. This worked with little difficulty for 2 months
(minor inconveniences in terms of workstation configurations since connecting
to a second domain for email, and hand synchronizing password changes.)

Meanwhile I had them buy and built a new domain controller using Win 2003
Server Enterprise. I joined the new machine to the old domain as a secondary
DC, promoted to primary (transferrring the GC, etc.) and demoted the old
domain server to a standard server.

Next I had the damaged machine repaired and had the vendor install Win2003
Server Enterprise as a standard server. I transfered all the user files and
shares to the rebuilt machine and powered down the old demoted DC.

So far so good. Now I'm attempting to add the Exchange Server 2003
functionality to the NEW PDC. The intention is that I will retire the
temporary/emergency email server that I put together.

As it stands the primary domain user accounts have exchange settings
pointing to the long gone email server that failed (for example:
OLDFAILEDSERVER/First Storage Group/Mailbox Store (OLDFAILEDSERVER)). So I
attempted to migrate the matching accounts from the working SBS server in the
other domain...I ended up with a set of new accounts complete with the email
from the working server, and mailbox stores on the new server (for example:
NEWPDC/First Storage Group/Mailbox Store (NEWPDC)). From reading the
directions it seemed that it would be possible to map the migrating boxes to
existing user accounts, but THAT option was never presented by the utility.

I only have about a dozen email/user accounts, so after pulling my hair out
for days I decided to that I would simply create new accounts from scratch if
necessary. I attempted to create one new test account but when I go through
the new user dialog it forces me to use the 'olddeadserver' mailstore
location. Likewise the mailstore field on the A/D user edit screen is 'VIEW
ONLY'. I assume this is driven from some registry key / A/D value tucked
away somewhere, and that even if I searched it out there would be multiple
unhappy reprocutions from attempting to change it by hand.

In exasperation, I decided to attempt uninstalling Exchange (AGAIN, tried
this several times already and while it went through the motions without
errors, major pieces were left in tact.) NOW I can not uninstall as it tells
me there are active email accounts. I must be careful as the machine I'm
attempting to get the Exchange functionality working on is our live PDC.

I know I've left out lots of details along the way...for instance, I've
painstakingly stepped through measures at:
http://support.microsoft.com/?kbid=823159,
and at: http://support.microsoft.com/kb/837285/ (even though I wasn't yet
running windows firewall.)

Given my level of knowledge, my next step is to start from scratch with two
new servers and never let them see the old servers...this seems a bit
drastic. I'm hoping that the problem is imminently solvable by someone more
knowledable here...Please help.

--
Regards,

Alan
.



Relevant Pages

  • 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: Easy to use second 2000 Server for Exchange?
    ... Existing Exchange 2000 server - therefore have the CALs - so no new ones are ... Frank McCallister SBS MVP ...
    (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: Email for second domain
    ... The Microsoft Exchange MTA Stacks service is normally disabled on Exchange 2003 Servers on SBS 2003. ... You can safely ignore the MTA warning messages on the SBS 2003 server. ...
    (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)

Loading