Bridgehead VM moved to a new host now has problems
Hello everyone. I have a problem that needs some guidance. As I have inherited this Exchange environment I'm having some issues sorting out details and specifics about the setup but let me explain as best as I can. We have 2 VMware environments, a free version of ESXi 3.5 and a vSphere 4 environment with all the bells and whistles. I am in the process of moving systems from one host to another. I talked with our resident Exchange expert about our hub/bridgehead server. It was scheduled to be moved Sunday afternoon. The plan is a simple one of just powering down the VM and then starting it back up again on the new vSphere 4 system (all hosts have shared storage). I was told there would be no gotcha's or issues. So Sunday afternoon, I migrated the server and tested our OWA and it worked fine or so I thought. I tested the OWA access and it sort of works but not the way it did last week. We have SSL enabled and an RSA front end. The https website fails with a page not displayed and the unsecure site does not prompt me for the RSA token. The server sees and communicates with the RSA server just fine (ran sdtest). We also have some devices using the ActiveSync portion and they have not updated since Sunday either. So and I looking for a certificate issue or some sort of reset since the hardware changed? Or should I just dig through the settings step by step until I find something? Any help is appreciated. Bridgehead server - Windows 2003 Standard with SP2 Exchange - Exchange 2003 Peace ---Todd
August 10th, 2010 4:50pm

Hi You can start by going to this site and do a test and post the result in here https://www.testexchangeconnectivity.com/ Jonas Andersson MCTS: Microsoft Exchange Server 2007/2010 | MCITP: EMA 2007/2010 | MCSE/MCSA Blog: http://www.testlabs.se/blog
Free Windows Admin Tool Kit Click here and download it now
August 10th, 2010 5:19pm

Hi Todd, I would like to confirm if the only HTTPS protocol cannot work when accessing OWA, you are able access OWA by using HTTP? You can try to request a new certificate from your Local CA for the exchange server and see if the issue persists.
August 12th, 2010 10:46am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics