Exchange migration, best practices

[Greenbeast]

i guess the next task is to test ISA forwarding to OWA2010 instead

I've changed the ISA rule properties to look at my 2010 server instead of 2003 server but the traffic still heading straight to OWA2003

[Greenbeast]

Only internally though right, as you haven't exposed the 2010 namespace externally or moved it and used a legacyURL.

yes if i type https://exchange2010servername.domain.internal/owa i get OWA2010 and can log into the one mailbox

just tested a 2003 mailbox and it pushed my over to OWA2003

[Greenbeast]

ok i found this guide: ISA 2006 SP1 Configuration with Exchange 2010 - Exchange Team Blog - Site Home - TechNet Blogs

Followed the procedure but when i switch the rules over i lose connectivity to OWA, i get a 403 error for both /owa and /exchange

[sukh]

Some sort of authentication isn't setup correctly.
What exactly has changed?
Where does ISA point to now 2010 or 2003? If 2010, look at the IIS Logs and post relevant section so I can see.
Check logs on ISA too.
Run ExchRCA and lets see if that gives anymore info.

[Greenbeast]

ok attempting to simplify and make testing easier i've made two new publishing rules that are identical to the existing ones apart from they point to the new E2010 servername.

when i switch the rules i get 'IE cannot display the page' (if i browse directly to the internal server name it gives me OWA2010 correctly)

[sukh]

Do you get this error internally joined client or externally?
If internal, can you flushdns and test again, restart IE and test again?

[Greenbeast]

Internally, i'll keep it simple and deal with just internal stuff for now.

So just tested, switched the rule from OWA2003 to OWA2010, did flushdns and opened new IE window and i get 'page cannot be displayed'