Exchange 2010 - IIS /public converted to Application... need to convert back to Virtual Directory
We're setting up Exchange 2010 and we have to create Public Folders... I know, I know, they suck. Anyway, our IIS guy saw the 'Default Web Site' and directories below it. While trying to troubleshoot our errors and why they wouldn't show up, he said that the folder had to be an Application to work. We converted the folder on both CAS servers in IIS to Applications. Now Microsoft says that they were suppose to be 'Virtual Directories' or folders all along.
How do we change this setting back? Can we revert the change? We just set this up and don't have a backup of the system state prior to the change.
How do we change this setting back? Can we revert the change? We just set this up and don't have a backup of the system state prior to the change.
ASKER
We have done what was mentioned above, but we still have a problem-- Users access public folders using the following: https://webmail.domain.com/public
They don't access them via the link within OWA. We need the same functionality as we had in 2003. We can actually access them from OWA (to be clear), but not using the /public URL.
We are getting the following error:
Server Error in '/' Application.
Runtime Error
I have also attached a screenshot.
They don't access them via the link within OWA. We need the same functionality as we had in 2003. We can actually access them from OWA (to be clear), but not using the /public URL.
We are getting the following error:
Server Error in '/' Application.
Runtime Error
I have also attached a screenshot.
Server Error in '/' Application.
Runtime Error
Why do the users need the /public URL? The Public VD is for backwards compatibility and is not needed if you have no exchange 2003 nor exchange 2000 servers as PFs can be accessed direct from /OWA
Does the 'Public Folders' button not work within OWA? Or when are you getting the error you posted? Do users get that error when accessing /public?
Sorry, but I didn't fully understand your comment above.
Does the 'Public Folders' button not work within OWA? Or when are you getting the error you posted? Do users get that error when accessing /public?
Sorry, but I didn't fully understand your comment above.
Check and ensure your OWA VD/App is not redirecting. Select OWA in IIS and then in the middle pane select the 'HTTP Redirect' option and make sure it is not redirecting anywhere. Do the same with the Public VD/App.
ASKER
As for your first comment, this is the way this organization has always accessed the public folders. While you can access them from OWA, I think that they would like to keep the structure as is to make the transition as smooth as possible. It's a small local government and any small change freaks people out.
That being said, I will look into the redirect panel in IIS today.
That being said, I will look into the redirect panel in IIS today.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Was redirection the issue?
ASKER
Yes... we had a strange redirect loop created from /owa to /public (Exchange 2010). It was causing chaos. But beyond that, we have to temporarily redirect to the legacy /public url to keep the same functionality (for now).
I hope we eventually turn off the public folders and go to another solution (we already use Sharepoint). People like to hold onto things for some reason.
I hope we eventually turn off the public folders and go to another solution (we already use Sharepoint). People like to hold onto things for some reason.
Thanks for the final update
http://blogs.technet.com/b/exchange/archive/2010/02/10/3409322.aspx