I had to restore one of our HUB transport servers from hardware up. The restore worked great. But I am having issues with OWA, Outlook Anywhere, ActiveSync. Anything that is using the IIS instance.We are running Exchange 2007 SP1. The HUB transport servers MAIL01, MAIL02, MAIL03, and MAIL04 all sit behind a BIG IP load balancer. We are using SSL Offloading for the connections. Everything works if I connect directly to MAIL01 without giong through the BIG IP. But when I add MAIL01 to the pool, it does not work correctly.Here is my questions. In researching it, I have compaired the output of all 4 get-owavirtualdirectory commands. All the servers have the same FolderPathName on each of the virtual directories. BUT MAIL01 has a different one. The domain name is different. I am guessing that this may be part of the problem, or at least want to eliminate the difference.How can I change the FolderPathname from \\.\BackOfficeStorage\domain1\MBX to \\.\BackOfficeStorage\domain2\MBX on those virtual directories? I don't think you can do it using the set=owavirtauldirectory command.Any suggestions, or do you think I am going in the wrong direction. I have verified that all the IIS settings are identical on all 4 servers as well. This is the only difference I have been able to find.

Hi,Please post the detail error inforamtion when user try to access OWA.But when I add MAIL01 to the pool, it does not work correctlyI'd like to know what is the pool,how did you add it.With Big IP load balance,how does user to access OWA, just type http://domain.com/owaor other?Mapping IP address to port?Please try to re-configure Big IP load balancer.Regards,Xiu

Hi mike, a detailed error would be nice. P. S since you mentioned that you have restored everything, it would be a good idea to re-create all the virtual directories. check kb 941201 on how to perform this.Also, i'm wondering how you're getting errors for owa vdirs if you restored the HUB server. i guess you must have CAS role installed on it.ThanksSatishna

I solved the problem. It had to do with the Exchange Install. I removed the HUB and CAS roles from the server and then removed IIS. Re-installed IIS, and then re-installed the HUB and CAS roles. It worked after that.