Yes and I verified redirection was off. Free Busy Data is also affected. Whether they are users on 2010 trying to see other test mailboxes on 2010 or users on 2003.
From: Jean-Paul natola [mailto:jnat...@hotmail.com] Sent: Saturday, May 22, 2010 10:19 PM To: MS-Exchange Admin Issues Subject: RE: Need some 2010 help you dont need to dedicate a box for express if its small- is your 2010 single server setup? i have everything runnning on one box , granted i only have a few BB users Now I am working through a mailbox that I just moved, everything works but the OAB.. Soon as you click download it pops a 8004011d error message. Just started looking at that. Seems to be common for OAB errors. did you go to the web.config file and add /give the authenticated users read & execute permisssions? ________________________________ Subject: RE: Need some 2010 help Date: Sat, 22 May 2010 22:15:07 -0400 From: greg.swe...@actsconsulting.net To: exchangelist@lyris.sunbelt-software.com Thanks Jean-Paul, Bes Express, installing on a separate server. Going to use the transporter..hopefully..haven't read all the docs yet completely. Fortunately it's a small Bes implementation so it's a good practice ground if it doesn't work. I would love to hear any gotchas. We have been running the new Bes Express on a few clients under 2003 and 2007 for awhile so fortunately we are familiar with the new product. Now I am working through a mailbox that I just moved, everything works but the OAB.. Soon as you click download it pops a 8004011d error message. Just started looking at that. Seems to be common for OAB errors. Waiting on replication of public folders to complete then I will give it a look see. Greg From: Jean-Paul natola [mailto:jnat...@hotmail.com] Sent: Saturday, May 22, 2010 10:09 PM To: MS-Exchange Admin Issues Subject: RE: Need some 2010 help Glad it worked out, are you going with BES enterprise BES express? if its express let me know I have already deployed it and went through the headaches. enjoy your weekend ________________________________ Subject: RE: Need some 2010 help Date: Sat, 22 May 2010 21:35:20 -0400 From: greg.swe...@actsconsulting.net To: exchangelist@lyris.sunbelt-software.com Well..I am a bit ashamed to mention this, but for some reason it was stuck that Exchange 2010 was Proxying the connection, but in fact is basically doing a redirection. I changed my DNS for legacy to point to their 2nd IP that was pointed to their old server and shazaam.. Went to the old link, get the 2010 OWA and then straight to the 2003 page without having to relogin. When I inspected the web link it was coming up with I went into IIS on the 2010 server and discovered the folder structure didn't match and the file actually was not there...Went to the 2003 folder and saw it was there which is when I realized it was redirecting not proxying. So then I reread the docs on 2010 and how CAS handles it and its clear as day..Redirection instead of proxy. 2007 proxied it. Of course none of it worked right until I disabled kernel mode authentication. Thx Jean! Now to let it rest for a day make sure all is well and then onto BES.. Weekend at last!! From: greg.swe...@actsconsulting.net [mailto:greg.swe...@actsconsulting.net] Sent: Saturday, May 22, 2010 9:05 PM To: MS-Exchange Admin Issues Subject: RE: Need some 2010 help Jean Thank you!!!That command fixed one major problem. I am now able to access both internally and externally the main OWA page. >From inside I can access all resources without an issue. >From Outisde when I authenticate with a user account on the 2003 server I still get this 404 Page cannot be found. It has to be an authentication issue, but I cannot track it down. This is the link that the 2010 owa redirects me to and I cannot access. https://legacy.fqdn.com/exchweb/bin/auth/owaauth.dll Any ideas before I yank the CAS and reinstall, and if that doesn't work just flatten it and start over.. Thanks Greg From: greg.swe...@actsconsulting.net [mailto:greg.swe...@actsconsulting.net] Sent: Friday, May 21, 2010 8:35 AM To: MS-Exchange Admin Issues Subject: RE: Need some 2010 help You wouldn't happen to have an article with tose permissions written up. Not a whole lot out there and I don't have my test servers up. Found a few bits here and there. Heading over the water at noon, so it will be a weekend fix for me. Everything but OWA to the 2003 box is up. I restored from a backup the web.config file and I got /owa up and working and it actually redirects to legacy namespace internally, but from outside I get a 404 file not found. Cannot figure that out at all. The 2003 box works perfectly even if I do the legacy.fqdn.com/exchange Everyone suggests removing CAS and reinstalling it, but I don't think I am there yet. Greg From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Friday, May 21, 2010 6:56 AM To: MS-Exchange Admin Issues Subject: RE: Need some 2010 help 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 ________________________________ The New Busy think 9 to 5 is a cute idea. Combine multiple calendars with Hotmail. Get busy. ________________________________ The New Busy is not the too busy. Combine all your e-mail accounts with Hotmail. Get busy. <http://www.windowslive.com/campaign/thenewbusy?tile=multiaccount&ocid=P ID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_4>
