Luke, FYI, the "Exchange Service Account" doesn't apply to Exchange 200x, services run under LocalSystem.
Sounds to me like you have one or more of the following problems: - Permissions for installation account - Accessing Operations Master or Schema Master role in AD - Exchange Server not in appropriate groups (Exchange Domain Servers and Exchange Enterprise Servers) Check out this article: http://support.microsoft.com/default.aspx?scid=kb;en-us;Q319944 You may have to do some background reading on FSMO (Flexible Single Master Operations) Roles in AD. Also, being able to log onto a server does not mean there is nothing wrong with the machine account in the domain. AD uses a specific "machine password" to communicate with machines in the domain. Although I can't say why doing the upgrade would have affected the machine account in this way. Sakti -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, 29 April 2004 11:57 AM To: Exchange Discussions Subject: Exchange 2003 Migration - The home stretch Hi all, we recently began an Exchange 5.5 to 2003 'migration' following much of the stories from Microsoft on how this is to be done. After some initial problems with the domain setup reported by the migration tools and ADC replication, we finally managed to get the Exchange 5.5 information ported to AD. After the MSX2k3 install was complete, we rebooted the server without moving any mailboxes, etc.. onto it and few of the services started. We changed them to start with the Exchange Service account on the domain but this did not help. We have since changed it all back to starting with LocalSystem, but the system attendand will not start, with an error along the lines of Event ID: 9157 Insufficient access to read exchange config objects in the AD Searching knowledgebase indicates that this is a problem with a missing machine account in the domain. But the machine account is still there and it can log onto the domain properly. Its machine account is also a member of the groups necessary for Exchange to operate. Running DCDiag /s: (as recommended by the article on 9157) produces an error about the domain owner being deleted (as seen below): Starting test: KnowsOfRoleHolders Warning: CN="NTDS Settings DEL:0823a07d-02b9-418f-b2e9-77ae43a23098",CN="OLDDC DEL:5cd640b3-b566-4030-8522-a7292249ed1c",CN=Servers, CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domain,DC=com is the Domain Owner, but is deleted. ......................... E2K3 failed test KnowsOfRoleHolders Could these issues be related to our exchange woes? (I realise the AD part is off topic, but we dont know if this is causing the problem for Exchange). Any advice on this issue is appreciated. Regards, Luke _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&; lang=english To unsubscribe send a blank email to %%email.unsub%% Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with. ********************************************************************** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ********************************************************************** _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english To unsubscribe send a blank email to [EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with.
