Exchange 2010 and accessing w/o https

yes but not really a best practice because i believe user names and passwords are exposed under HTTP and is really why it is best to have OWA under HTTPS.  May I ask why you would like to do that ?

because I need to terminate an SSL VPN Client connection to an ASA firweall, and right now all https/443 is being forwarded to the internal mail server, which I cannot do.

yep, that is exaclty where I am stuck right now.
I am hoping that I can specify a URL that the Cisco ASA will recognize, and then wont forward it to the internal server.
I wish I has another static/public ip that I could use.

I ran into that issue back in November when I bought my barracuda ssl vpn and I bought a block if IPS from my ISP and it was only 20 bucks.  call your ISP and get additional IP's.  you will get a new set of IP's they wont add to what you have unfortunately but it took 2 mins in the wizard to reconfigure the outside IP and extra couple of mins to create/modify an ACL's and NAT.  Much quicker and easier then dealing with exchange.

Welcome to the age where it is commonplace to have 64-bit computers and laptops...

Can't you just disable the requirement for https on Exchange 2010 for OWA?

why would you want to, thats to protect from all the packet sniffers out there peaking at your data as it crosses the information super highway. as far as im aware of 64 bit does not provide any protection in that avenue it just a bigger bus for data to travel on.  you could go through that process of disabling it but with the volume of data that in/out of the exchange server I wouldnt  want to have my systems compromised because a user names password is "password" and some hacker sniffed it out.

I fixed it by settign ssl vpn client to listen on a differnt port.