Bear with me as I'm going to attempt to give as much input as possible upfront.
We recently migrated AD from a 2000 server to 2003 SBS using ADMT v3 along with v2 of the following documentation.... Migrating from Small Business Server 2000 or Windows 2000 Server to Windows Small Business Server 2003...link below
http://download.microsoft.com/download/6/d/c/6dccf9b4-d915-4c95-b5af-100b89e02add/SBS_MigratingSBS2k.doc
Note: The 2000 server did not have exchange. We only migrated the AD computers and users.
Our goal is to now use the 2003 SBS machine as the client's exchage server but we've hit several snags that are preventing us from doing so......
After the migration....we were in the process of creating mail accounts and noticed that we had errors in the event log saying that the Microsoft Exchange System Attendant wasn't running. Also had some Sharepoint error logs.....don't have the old events but will give the most recent logs in just a bit.
In addition only the old 2000 server was showing up in the default administration group in Exchange System Manager.
Since there wasn't any mailboxes(no exchange on old 2000 server so no exchange migration) we decide to reinstall IIS and exchange using the following document from microsoft.....
http://support.microsoft.com/kb/320202
Now we are getting the following event logs...
Event Type: Error
Event Source: MSExchangeSA
Event Category: Monitoring
Event ID: 9098
Date: 6/17/2008
Time: 6:13:21 PM
User: N/A
Computer: LRRSVR
Description:
The MAD Monitoring thread was unable to read its configuration from the DS, error '0xc004038a'.
For more information, click
http://www.microsoft.com/contentredirect.asp.
--------------------------
----------
----------
----------
----------
----------
----------
------
Event Type: Error
Event Source: Windows SharePoint Services 2.0
Event Category: None
Event ID: 1000
Date: 6/17/2008
Time: 6:19:53 PM
User: N/A
Computer: LRRSVR
Description:
#50070: Unable to connect to the database STS_Config on LRRSVR\Sharepoint. Check the database connection information and make sure that the database server is running.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
--------------------------
----------
----------
----------
----------
----------
---
Also the old 2000 server is still showing up in the Default Administrative Group in Exchange System Manager along with the new 2003 SBS sever.
Our main concern right now is getting exchange up and running properly. If possible we'll tackle Sharepoint later...I've included the sharepoint events as they appear to be related to the AD migration as well.
Any help getting exchange going would be greatly apprectiated and if Sharepoint gets fixed that would be a plus......but the priority right now is Exchange.
I've also included a word document with a couple of screenshots.
Thanks in Advance
ExchangeScreenshots.doc
http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=6.5.0000.0&EvtID=9098&EvtSrc=MSExchangeSA&LCID=1033
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/2003_Server/Q_22471568.html