<div>
Great little article - wish I would have found that one a while back. Anyway I actually ended up just disabling HTTPS in 2010 to get me through. Once the mailboxes are migrated I'll re-enable it and finish my migration to 2010 before making it available on the Internet. If anyone is interested here's the steps I took to disable HTTPS to allow the Unity Connection tool to connect:<br />
<br />
under owa properties in exchange 2010<br />
- change https to http<br />
- changed from forms authentication to basic<br />
- Default Website in IIS removed require SSL check mark
</div>


<div>
<div class="content wysiwyg-content">
We're about to upgrade from our existing version of Unity (4.2) to Unity Connection (8.x I believe). We are currently in the middle of an Exchange swing migration from 2003 to 2010 - I stopped because I realized that Unity 4.2 is not compatible with 2010. So now in order for the voicemail migration to work I need to have both Exchange servers either running HTTP or HTTPS. <br />
<br />
My preference is obviously to make 2003 HTTPS instead of making 2010 HTTP - however this is just temporary until I move all the mailboxes over (maybe a week possibly 2) so I don't really want to go through the trouble of getting a certificate - whats the easiest way to get 2003 to respond to HTTPS requests? <br />
<br />
This is a time sensitive issue - thanks in advance.
</div>
</div>


We're about to upgrade from our existing version of Unity (4.2) to Unity Connection (8.x I believe). We are currently in the middle of an Exchange swing migration from 2003 to 2010 - I stopped because I realized that Unity 4.2 is not compatible with 2010. So now in order for the voicemail migration to work I need to have both Exchange servers either running HTTP or HTTPS. 

My preference is obviously to make 2003 HTTPS instead of making 2010 HTTP - however this is just temporary until I move all the mailboxes over (maybe a week possibly 2) so I don't really want to go through the trouble of getting a certificate - whats the easiest way to get 2003 to respond to HTTPS requests? 

This is a time sensitive issue - thanks in advance.

Exchange 20xx change from HTTP to HTTPS or vice versa

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.