Lonnus_Maximus
asked on
Migrating Exchange - OWA on new server before the first is decomisioned?
I am migrating my Exchange to a new server for a hardware upgrade. Both exist in AD now, I replicated the public folders, and I move my mailbox over to the new server. Outlook works fine, however when I try to use OWA I get page not found wether I use xxx.newserverip/exchange, or xxx.oldserver/exchange. Everyone I did not move yet of course can still access OWA the old way.
I am trying to figure out if my OWA is not working on the new server, or if, from what I read, you just actually cannot have OWA working on multiple severs unless you are running a Front End/Back End configuration, which I am not. In this case I was hoping it would just start working after I migrated everyone, removed the first server from the site, and made the new server the first server.
In IIS on the new server, I see the Exchange web site, all permission look just like the first server. I did not do anything to configure it, because as far as I could remember, OWA just works after the install and no configuration was needed. Is that where I am going wrong?
Thank for any help,
Lon
I am trying to figure out if my OWA is not working on the new server, or if, from what I read, you just actually cannot have OWA working on multiple severs unless you are running a Front End/Back End configuration, which I am not. In this case I was hoping it would just start working after I migrated everyone, removed the first server from the site, and made the new server the first server.
In IIS on the new server, I see the Exchange web site, all permission look just like the first server. I did not do anything to configure it, because as far as I could remember, OWA just works after the install and no configuration was needed. Is that where I am going wrong?
Thank for any help,
Lon
LeeDerbyshire
Because you are not in a FE/BE configuration, you need to go to the server that has your mailbox on - http://newserver/exchange . If you go to http://oldserver/exchange , it should redirect your browser to http://newserver/exchange . If you had FE/BE, the oldserver would act as a proxy. Can you access the Default Web Site at http://newserver ?
ASKER
If I just type in http://newserver I get the Lotus Notes Domino help screen, which I assume installed itself there when notes was installed.
http://oldserver/exchange give me the login screen, and then page not found after I log in. http://newserver/exchange does not even give me the login screen. I guess OWA is just not working probably, hence why the redirect is also not working. (Both servers are Win2K and Exchange 2000)
http://oldserver/exchange give me the login screen, and then page not found after I log in. http://newserver/exchange does not even give me the login screen. I guess OWA is just not working probably, hence why the redirect is also not working. (Both servers are Win2K and Exchange 2000)
If you open IIS Manager on the new server, and right-click the Exchange VDir, do you see a Browse option? What happens if you click it?
Also, did you have Domino/Notes installed on the old server? I've never seen this combination of Notes/Exchange before. Maybe someone else has specific experience of this?
ASKER
Weird... if I go to IIS on the new server and right-click browse on Exchange or Public I get page not found. If I go to IIS on the old server and do the same for Public, it comes up. If on the old server I try to browse Exchange IE comes up with http://newserver/exchange in the URL and says page not found... it is redirecting it from there even though I didn't change anything, and users can still use it.
No Notes on the old server. We are only using the Databse portion of it, not the Email part.
No Notes on the old server. We are only using the Databse portion of it, not the Email part.
Are any 'Automatic' start-up services not running in the services list?
Which version of Exchange is it, by the way? If it's 2003, try deleting the three Exchange VDirs (Exchange ExAdmin Exchweb) and recreate them with this:
http://support.microsoft.com/kb/883380
In Exchange 2000, they will be recreated if you stop/start the System Attendant. According to that article, anyway. I never actually tried that in E2000 .
ASKER
Well, now I see that under Exchange Manager, Servers, Newserver, Protocols, HTTP, Exchange Virtual Server has a red x by it. When I try to start it, I get this error in the event log.
Source: W3SVC
ID: 115
The service could not bind instance 1. The data is the error code.
A google search leads me to believe something else is on the same port, probably the Notes? From what I have also read, OWA does not work very well if you switch it to a different port.
Source: W3SVC
ID: 115
The service could not bind instance 1. The data is the error code.
A google search leads me to believe something else is on the same port, probably the Notes? From what I have also read, OWA does not work very well if you switch it to a different port.
ASKER
IIS on newserver also says Default Web Site (stopped). When I try to start it, I just get "Already in use"
OWA works fine if you switch the Default Web Site to another port. You just need to remember to put it in the URL http://newserver:81/exchange . If Notes has installed its own Website, then you'll need to use a host header or a different port number (probably easiest for testing purposes) on the DWS.
ASKER
Well I finally got most of it working this weekend.... Lotus was using port 80 and we switched it to port 81. Since I last spoke, I fixed some Active Directory errors, and fixing them broke the new mail server. (Could not start the System Attendant or the mount the stores) I fixed that by running DomainPrep and ForestPrep again as per a MS article. Web Access worked before that problem, but not now.
Point value increase for new work :)
If I am on the server itself, web access works. If I use a client computer, it pops up the logon screen, but the logon screen just comes back after I type the password. So it is seeing it but not acepting my login/password.
2nd, though I replicated the Public Folders and can see them in Outlook, unless the old server information store is started, when I click on them it says the folder can't be viewed because of netowork problems.
Point value increase for new work :)
If I am on the server itself, web access works. If I use a client computer, it pops up the logon screen, but the logon screen just comes back after I type the password. So it is seeing it but not acepting my login/password.
2nd, though I replicated the Public Folders and can see them in Outlook, unless the old server information store is started, when I click on them it says the folder can't be viewed because of netowork problems.
ASKER
hmm... actually OWA does work, but I have to type domainname\username now instead of just the username like I used to....
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.