I have exchange 2003 on server 2003 with the latest patches. I now want to use an old server that has server 2003 as well and install exchange 2003 and make it as a front end server. When i read a couple of articles on how to do it looked pretty simple and I actually already attempted once. I renmaed the machine exchangefs, the name was never used before. the real exchange is called exchange. Now when I installed exchange 2003 on the second server i click the front end server box and continued from there. Then I rebooted both exchange servers and when i got them back up my first exchange started to act up. The front end server as well. I couldnt get into OWA, I found a problem where the first exchange had an error saying it found a duplicated SPN name?? I looked at the front end it still had exchangefs as the name so it didn't change name. I don't know what I did wrong. I am basically about to uninstall exchange and start over again for the front end. But I want to know if someone else has seen the SPN error before or did I do something wrong? I followed this site: http://www.msexchange.org/tutorials/OWA_Exchange_Server_2003.html

I would start by removing Exchange from the frontend server, then wiping it and starting again. A renamed machine could have been through who knows what. It sounds like an AD issue rather than an Exchange issue and a fresh build of the machine will correct those issues. Install Windows 2003, SP2. Then add in the IIS components and patch it. Install Exchange 2003, then SP2, then run Microsoft Update to get the post SP2 updates. If the original machine went Exchange 2003 RTM, SP1, SP2, then you need to follow that same path. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources

I would start by removing Exchange from the frontend server, then wiping it and starting again. A renamed machine could have been through who knows what. It sounds like an AD issue rather than an Exchange issue and a fresh build of the machine will correct those issues. Install Windows 2003, SP2. Then add in the IIS components and patch it. Install Exchange 2003, then SP2, then run Microsoft Update to get the post SP2 updates. If the original machine went Exchange 2003 RTM, SP1, SP2, then you need to follow that same path. Simon. Simon Butler, Exchange MVP Blog | Exchange Resources Thank you Simon I was hoping I didn't have to do this but will do. I am going to rename it to something it never had before. Thanks

Its not the renaming that is the key - there is obviously some kind of link, so a clean build of Windows is the best option. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources

Its not the renaming that is the key - there is obviously some kind of link, so a clean build of Windows is the best option. Simon. Simon Butler, Exchange MVP Blog | Exchange Resources Thanks for the quick response but I am trying hard to think if I did do a clean wipe before I made it a front end. I am been playing with this server and I wiped it about 6 times already because I was trying to do some dr work on it. I will wipe it and see what happens but really thanks for the quick help.

I would start by removing Exchange from the frontend server, then wiping it and starting again. A renamed machine could have been through who knows what. It sounds like an AD issue rather than an Exchange issue and a fresh build of the machine will correct those issues. Install Windows 2003, SP2. Then add in the IIS components and patch it. Install Exchange 2003, then SP2, then run Microsoft Update to get the post SP2 updates. If the original machine went Exchange 2003 RTM, SP1, SP2, then you need to follow that same path. Simon. Simon Butler, Exchange MVP Blog | Exchange Resources I do have on more question, a lot of these forums and blogs show how to do implement the front end server but am I suppose to change something on the regular exchange server??? Thats something that doesn't show in the articles on how to do a front end server it just ends but I feel something needs to be done on the other server.

There is nothing to do on the backend server. Do ensure that the frontend is patched to the same level or higher than the backend. In some cases you have to reset the OWA virtual directories on the backend for full functionality. http://support.microsoft.com/default.aspx?kbid=883380 FE/BE is very straightforward and the most common issues with it are well known. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources

There is nothing to do on the backend server. Do ensure that the frontend is patched to the same level or higher than the backend. In some cases you have to reset the OWA virtual directories on the backend for full functionality. http://support.microsoft.com/default.aspx?kbid=883380 FE/BE is very straightforward and the most common issues with it are well known. Simon. Simon Butler, Exchange MVP Blog | Exchange Resources Thank you. I took your advise to reformat the server and start from scratch again and this time it finally worked so I guess before something got confused in Active Directory but I am thankful that I got it to work. Thanks