It appears I needed the ASP.NET service installed on the server before I did the setup.exe /disasterrestore installation. I added that and it worked. I restored the .edb, .stm, and log files to their proper locations and everything is as it was. I suppose I should know what services Exchange needs but it was not listed on Microsoft's instructions for "How to Move Exchange Server 2003 to New Hardware and Keep the Same Server Name". It was mentioned on instructions I found on the www.msexchange.org site. The only thing now is the store was dismounted this morning. I mounted it again and it is fine. I just have to figure out that glitch. Douglas Jensen Douglas.Jensen@xxxxxxxxxxxxx <mailto:Douglas.Jensen@xxxxxxxxxxxxx> Voice (952) 402-9821 Fax (952) 402-9815 Network Administrator Scott Carver Dakota CAP Agency, Inc. 712 Canterbury Road Shakopee, MN 55379 www.capagency.org <file:///C:/Documents%20and%20Settings/djensen.SCDCAP/Application%20Data /Microsoft/Signatures/www.capagency.org> ________________________________ From: exchangelist-bounce@xxxxxxxxxxxxx [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Jensen, Douglas Sent: Saturday, November 11, 2006 10:02 AM To: exchangelist@xxxxxxxxxxxxx Subject: [ExchangeList] Re: Move Exchange 2003 SP2 to new hardware I would rather keep the same name but even so, I have to install Exchange 2003 on the server and it is saying I can not do that because of known compatibility issues with that version of Windows. Which does not make any sense to me. I must be reading that error wrong somehow. Doug ________________________________ From: exchangelist-bounce@xxxxxxxxxxxxx [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Simon Butler Sent: Saturday, November 11, 2006 9:40 AM To: exchangelist@xxxxxxxxxxxxx Subject: [ExchangeList] Re: Move Exchange 2003 SP2 to new hardware Any reason you want to keep the same server name? It complicates things greatly and is best avoided. If you have new hardware do a standard swing migration migration. This will allow you to do the work with zero downtime and no loss of data. The most common reason that people want to retain the same computer name is because they don't want to visit every machine to change Outlook. That isn't a problem. As long as both the old and the new server are alive with Exchange installed when the clients login for the first time then they will redirect to the new server automatically with no interaction from the administrator or user required. You can even do the move without the users even noticing. Simon. ________________________________ From: exchangelist-bounce@xxxxxxxxxxxxx [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Jensen, Douglas Sent: 11 November 2006 15:14 To: exchangelist@xxxxxxxxxxxxx Subject: [ExchangeList] Move Exchange 2003 SP2 to new hardware I am trying to move exchange to new hardware and am following the instructions from TechNet "How to Move Exchange Server 2003 to New Hardware and Keep the Same Server Name". It seems pretty simple. Make backups of the Exchange Storage Groups. Take the existing Exchange server off line. Install Server 2003 and all the service packs on the new server and name the server the same as the previous Exchange server. Reset the Computer Account for the server in the domain. Join the Server to the domain. Install Exchange 2003 with /disasterrecovery switch. Install Exchange service packs with /disasterrecovery switch. Restore the exchange databases. Mount the store. The problem comes with the install of Exchange 2003. I get an error saying Exchange has known issues with that version of windows but I can Continue if I want. I am thinking it really will work because I have Exchange 2003 running on Server 2003. The install continues and says it finishes but it does not really install Exchange. I put the old server back on line and am trying to figure out what went wrong. Any ideas? I had Exchange 2003 SP2 running on Member Server 2003 SP1 in a Windows 2000 domain. Am I misreading the error? I was going to try installing Exchange 2003 on Server 2003 without the service pack to see if that would work. That does not really make sense though. Douglas Jensen Douglas.Jensen@xxxxxxxxxxxxx <mailto:Douglas.Jensen@xxxxxxxxxxxxx> Voice (952) 402-9821 Fax (952) 402-9815 Network Administrator Scott Carver Dakota CAP Agency, Inc. 712 Canterbury Road Shakopee, MN 55379 www.capagency.org <file:///C:/Documents%20and%20Settings/djensen.SCDCAP/Application%20Data /Microsoft/Signatures/www.capagency.org>