Your best bet is to copy permissions and settings from a known-good installation.
When you said you "did redirection at the root", what do you mean by that? For the future - you should take a look at metabase backups/restores... Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: greg.swe...@actsconsulting.net [mailto:greg.swe...@actsconsulting.net] Sent: Friday, May 21, 2010 5:58 AM To: MS-Exchange Admin Issues Subject: RE: Need some 2010 help Also, when I authenticate from outside to the /OWA site, it gives me the 404 file not found and this url. https://legacy.domain.com/exchweb/bin/auth/owaauth.dll From: greg.swe...@actsconsulting.net [mailto:greg.swe...@actsconsulting.net] Sent: Friday, May 21, 2010 5:01 AM To: MS-Exchange Admin Issues Subject: Need some 2010 help Gurus.. Did my first live 2003 to 2010 integration . everything went perfectly, until I got the bright idea to try and make redirection happen automatically...Then everything broke. Tried to change it back and no love. Got ActiveSync, Outlook anywhere and OWA to work but it will only redirect to the 2003 Mailboxes using the legacy namespace INTERNALLY. If I do it from outside I get a 404 file not found error. Prior to the redirection, I could access from /owa or /exchange and I got to the 2010 OWA and a login to a 2003 mb redirected me perfectly to the legacy namespace and all was well. After I tried the redirection at the default website..it all broke. Undid the redirections on the sub sites and rebooted IIS and those came back up but not OWA. Coming from Single Exchange 2003 Server. Forms, etc.. all is good. Single Exchange 2010 with CAS, transport, and MB roles. Activesync, Outlook anywhere all work. OWA works if I connect to a mailbox on the 2010 server and I goto the fqdn with /owa If I try /exchange...WHICH DID WORK.. I now get this. Runtime Error Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine. Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off". <!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="Off"/> </system.web> </configuration> Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL. <!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/> </system.web> </configuration> I have spent all night redoing my steps. Looking up articles. Any ideas?? Thx Greg
