+ Post New Thread
Page 3 of 3 FirstFirst 123
Results 31 to 37 of 37
Enterprise Software Thread, Exchange migration, best practices in Technical; i guess the next task is to test ISA forwarding to OWA2010 instead I've changed the ISA rule properties to ...
  1. #31

    Join Date
    Feb 2007
    Location
    Kent
    Posts
    641
    Thank Post
    283
    Thanked 52 Times in 44 Posts
    Rep Power
    40
    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

  2. #32

    Join Date
    Feb 2007
    Location
    Kent
    Posts
    641
    Thank Post
    283
    Thanked 52 Times in 44 Posts
    Rep Power
    40
    Quote Originally Posted by sukh View Post
    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

  3. #33

    Join Date
    Feb 2007
    Location
    Kent
    Posts
    641
    Thank Post
    283
    Thanked 52 Times in 44 Posts
    Rep Power
    40
    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

  4. #34

    Join Date
    Dec 2008
    Location
    Essex
    Posts
    2,144
    Thank Post
    1
    Thanked 326 Times in 316 Posts
    Rep Power
    77
    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.

  5. #35

    Join Date
    Feb 2007
    Location
    Kent
    Posts
    641
    Thank Post
    283
    Thanked 52 Times in 44 Posts
    Rep Power
    40
    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)

  6. #36

    Join Date
    Dec 2008
    Location
    Essex
    Posts
    2,144
    Thank Post
    1
    Thanked 326 Times in 316 Posts
    Rep Power
    77
    Do you get this error internally joined client or externally?
    If internal, can you flushdns and test again, restart IE and test again?

  7. #37

    Join Date
    Feb 2007
    Location
    Kent
    Posts
    641
    Thank Post
    283
    Thanked 52 Times in 44 Posts
    Rep Power
    40
    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'
    Last edited by Greenbeast; 15th November 2012 at 10:41 AM.

SHARE:
+ Post New Thread
Page 3 of 3 FirstFirst 123

Similar Threads

  1. Replies: 8
    Last Post: 22nd June 2010, 11:12 AM
  2. Sophos EC and best practice
    By FatBoy in forum Windows
    Replies: 8
    Last Post: 17th November 2007, 09:37 AM
  3. DFS/FRS: best practice?
    By Oops_my_bad in forum Windows
    Replies: 3
    Last Post: 4th June 2007, 11:18 AM
  4. DHCP best practice and advice again
    By tosca925 in forum Windows
    Replies: 11
    Last Post: 23rd November 2006, 08:49 PM
  5. Implementing best practice ICT management and support
    By FITS in forum Courses and Training
    Replies: 16
    Last Post: 8th September 2005, 02:24 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •