• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 490
  • Last Modified:

Added SBS2003 Server to SBS2000 Domain. Mail delivery no longer works on SBS2000 Exchange

I have added a SBS 2003 server to a SBS2000 domain - made it the operations master on everything. Now mailboxes on the SBS2000 Server cannot get mail delivered to them anymore!

Can they not co-exist? I dont have to make the new one a front-end server for this to work do I?

I've never had to install a SBS2003 on a 2000 domain before.

Moving maiboxes to the new SBS2003 server makes the mailbox work but the postmaster comes back with UNDELIVERABLE messages when trying to send emails to mailboxes still on the SBS2000 Server.

Help?!
0
kajbjo
Asked:
kajbjo
  • 14
  • 7
  • 3
  • +2
4 Solutions
 
tigermattCommented:

Theoretically Exchange should work, however SBS will NOT. There can only be a maximum of ONE SBS Server per Active Directory domain. This is because an SBS must be the holder of all Operations Roles, and since each of the 5 roles can only exist on one server at a time, it is impossible to have both SBS Servers running with the Operations Roles assigned.

You can definitely have additional Server 2003 / 2008 Standard Edition DCs, but no more than one SBS Server on any domain.

-tigermatt
0
 
kajbjoAuthor Commented:
Forgot about that.

So if I manage to transfer all the mailboxes over I should be ok?

Thanks,

Kaj
0
 
Yossarian-22Commented:
May I add that SBS also cannot run as a standalone server. It will automatically shut down if it does not have any AD installed onto it.

Also in SBS domains there may just be one DC. There is no way you can have a second DC online within the domain.

The situation you have created is okay if you want to migrate SBS 2000 to SBS 2003.
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
tigermattCommented:

If you are simply looking to migrate, then SBS will give you a 7 day grace period before it starts to shutdown and do strange things.

If you can migrate the mailboxes to the SBS 2003 server within this time, transfer the FSMO Operations Roles and then demote and remove the SBS 2000 server, you should be OK. It is being the holder of the FSMO roles which will cause the SBS to reboot (or not). Since the SBS 2003 is the FSMO role holder, it would be the SBS 2000 server which will restart on regular intervals.

-tigermatt
0
 
kajbjoAuthor Commented:
I do want to migrate to 2003. I only have the 2000 still there until everything is transferred over - I just hadnt transferred all the boxes because I wasnt sure the 2003 was 100% .. now I have to do it quick..!
0
 
Yossarian-22Commented:
Yes, you should migrate all functions and roles to the new SBS2003 server and remove the SBS2000 then.
For details see: http://download.microsoft.com/download/6/d/c/6dccf9b4-d915-4c95-b5af-100b89e02add/SBS_MigratingSBS2k.doc
0
 
tigermattCommented:

kajbjo,

Provided you migrate within 7 days (I believe is the time scale - I would not push it past this) and remove the SBS 2000 no more than 7 days after the SBS 2003 was introduced, then there will be no issues.

Be sure to have Exchange installed and working on the SBS 2003, and then Move the Mailboxes to the new server. Remember that you also need to move shares and EVERY other piece of data from the SBS 2000, as this server will need to be fully removed (i.e. physically demoted and unplugged) from the network in order to stop any licensing violation causing server restarts.

-Matt
0
 
kajbjoAuthor Commented:
Great. Now when I try to move a mailbox over to the 2003 server I get:

  The MAPI call failed. MAPI or an unspecified service provider. ID no: 80004005-0000-00000000

0
 
tigermattCommented:

Looks like that could be a sign of corrupted mailboxes: http://support.microsoft.com/kb/264119.

Try an ISINTEG /ATTACH and see if that fixes things, if not, check the further steps detailed in the article above.

-tigermatt
0
 
kajbjoAuthor Commented:
Ya I saw that article. However it's doing that to every mailbox I'm trying even very small insignificant boxes. I doubt that's the problem.. I'm thinking it's more like:

http://support.microsoft.com/kb/259357/
259357 Error 80004005-0000-00000000 when moving mailbox between Exchange Server 5.5 and Exchange 2000 Server

Considering I now have 2000 and 2003 on the same domain (like a moron. So tired need sleep!) and have tried to "replicate" the public folders over (lol I'm guessing that won't work? Since I can only have one DC/GC?) and now I can no longer move the mailboxes.. sigh..
0
 
kajbjoAuthor Commented:
nevermind that article totally isn't it either...
0
 
kajbjoAuthor Commented:
When I try to run the isinteg /attach I get:

D:\Program Files\Exchsrvr\bin>isinteg /attach
Microsoft Exchange Information Store Integrity Checker v6.5.7638.2
Copyright (c) 1986-2000 Microsoft Corp.    All rights reserved.
Usage:
 isinteg -s ServerName [-fix] [-verbose] [-l logfilename] -test testname[[, test
name]...]
    -s               ServerName
    -fix             check and fix (default - check only)
    -verbose         report verbosely
    -l filename      log file name (default - .\isinteg.pri/pub)
    -t refdblocation (default - the location of the store)
    -test testname,...
       folder message aclitem mailbox(pri only) delfld acllist
       rcvfld(pri only) timedev rowcounts attach morefld ooflist(pri only)
       global searchq dlvrto replstate(pub only)
       peruser artidx(pub only) search newsfeed(pub only) dumpsterprops
       Ref count tests: msgref msgsoftref attachref acllistref aclitemref
       newsfeedref(pub only) fldrcv(pri only) fldsub dumpsterref
       Groups tests: allfoldertests allacltests
 isinteg -dump [-l logfilename] (verbose dump of store data)

and looking at that it looks like /attach isn't even an option? What did I miss...?
0
 
buddholeCommented:
Try the mail move on the other server. Otherwise, you can always revert to pst migration using exmerge instead of tossing around with databases for days.
0
 
buddholeCommented:
Also try  to run ISINTEG with the -fix test -attach option. Mailbox limits on the new server can also cause this error.
0
 
kajbjoAuthor Commented:
Yup I was thinking of trying exmerge.. sadly it worked yesterday.. O.o
0
 
buddholeCommented:
Double check mailbox and store limits. Maybe you forgot a 0. Google results in lots of hit concerning store limits.
0
 
tigermattCommented:

And you have permissions to access the mailboxes of the users you are moving? If you don't Exchange cannot connect to them and move them.
0
 
kajbjoAuthor Commented:
I am using the domain administrator account. I have made that account member of all exchange groups available besides domain admins groups etc.,

All the limits are set to default - which seemingly are no limits.

0
 
tigermattCommented:

Actually, making the Administrator a member of all the groups you think might not grant you the necessary levels of access. This is because Administrators are, by default, denied access to other users' mailboxes.

See http://www.petri.co.il/grant_full_mailbox_rights_on_exchange_2000_2003.htm, and follow the second section for a specific mailbox store to grant the Administrator account full rights over the store.

-tigermatt
0
 
kajbjoAuthor Commented:
I created a brand new user. Added domain admin rights to the new user account. Then added that user with full control on the mailboxstore. I logged on the server with that user account and tried moving. Get the same MAPI error at the end of the move (it looks like it's moving the whole box then when finished it errors out with The information store could not be opened. The MAPI provider failed. MAPI 1.0 ID no: 8004011d-0289-00000000 )
0
 
tigermattCommented:

Hmm... That's annoying. The SBS 2000 domain was prepped for Exchange before the SBS 2003 was added and Exchange installed, wasn't it?

I.e. Running the Exchange Setup /forestprep and then Setup /Domainprep?

-tm
0
 
kajbjoAuthor Commented:
Yes sir. All that was done and worked.

Otherwise I doubt I would ever have been able to move any mailboxes to the new SBS2003 server.

Only major things I changed since that worked was IIS stuff trying to get a SSL certificate in place for my exchange active sync that I  need to get working on the new server. I should've moved all the boxes over.. I just wasn't sure it was ready for that yet O.o
0
 
kajbjoAuthor Commented:
Now I'm trying to manually copy over the MDBDATA from the old server to the new O.o

Cross your fingers!
0
 
kajbjoAuthor Commented:
Great.

I copied over the MDBDATA folder to the new server and had tons of issues to get anything to work. I had to do a few EXMERGE's too (after removing the deny properties) to get the ONE mailbox I had moved over successfully yesterday before all that stopped working.

It so happened that there was all of a sudden TWO Default Websites in my IIS Manager!!

I stopped the 2nd wierd version and at least got exchange and OWA back again :(

Now I still have to struggle with IMAP and Exchange Active Sync.. but that's a whole new case!
0
 
kajbjoAuthor Commented:
P.S. - you can have two SBS Server in the same domain for a week. Then they stop working (rebooting every 1.5 hours). But of course you can only have ONE domain controller so once you move the Operations Master tasks to the new server the old one basically doesn't work for much anymore..
0
 
suppsawsCommented:
Hello kajbjo,

I want o make one thing clear here .... You CANNOT have two SBS servers on one domain, but you CAN have additional DC's on an sbs network (backup domain controllers if you want to call it like that).
http://www.microsoft.com/windowsserver2003/sbs/evaluation/topmyths.mspx
also read this: http://sbs.editme.com/getstarted   >>  Running Multiple Servers in a Windows Small Business Server Environment  /  Add and Manage Additional Servers in a Windows Small Business Server Domain

Regards,

suppsaws
0
 
kajbjoAuthor Commented:
Well technically after you move all the operations masters tasks over to one.. you only have A server yes
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 14
  • 7
  • 3
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now