Exchange Server TechCenter > Exchange Server Forums > Deploy > Exchange 2007 CAS with 2003 BE question
Ask a questionAsk a question
 

QuestionExchange 2007 CAS with 2003 BE question

  • Wednesday, October 21, 2009 7:07 PMMorvac Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    When accessing my https://mailserver/exchange url, I login and the page will display garbage...it almost looks like it didn't finish loading. There isn't any errors on the screen.   Can't test /owa because I don't have mailbox role installed yet, although form/login display fine.    Accessing the /exchange on my 2003 server works perfectly.   Anyone know what gives?

    Ending goal is fully migrating 2003 to 2007, one piece at a time.  The 2003 server is a single server.

All Replies

  • Wednesday, October 21, 2009 8:05 PMJohan VeldhuisMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi,

    With garbage you mean that the images are incorrectly displayed ?

    Regards,

    Johan
    blog: www.johanveldhuis.nl
  • Thursday, October 22, 2009 12:30 PMMorvac Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Correct.  Clicking on any of the items that are displayed on the left pane dont do anything.  Clicking on items on the right side, I get an error at the bottom of IE.
    ----------------------
    Object expected
    Inbox/                   Line 53

    Code:0

    URI:https://mail07/exchange/administrator/Inbox/?Cmd=contents


    ---------------------

    No background color or actual images are displayed....just some text.  I wish I could post a screen shot.

    I've tried accessing the page from Internet Explorer 6, 7 & 8 - all with the same results on a Windows XP or Server 2003 box.

    If I don't proxy thru 2007 CAS and access it directly on the 2003 server Https://mail/exchange  it works perfectly.
  • Monday, October 26, 2009 8:28 AMAllen SongMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi,

    Please check the authentication on the CAS and the BE based on the below link:
    http://msexchangeteam.com/archive/2008/02/01/447989.aspx

    Thanks

    Allen
  • Friday, November 13, 2009 4:52 PMMorvac Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    These permissions are correct, however problem remains.

    Hopefully i'll provide some more info here below be refreshing this post.

    ==============================================
    I am still having an issue with folder redirection on Exchange 2003 using a Exchange 2007 CAS.  I would like to deploy
    exchange 2007 cas as a front end while still using exchange 2003 & 2007 backends during a transition to single 2007 mailbox/hub server.

    I've tried rebuilding my test labs completely three times now for prep of same in production - maybe I am simply missing it or the product can't do what I think
    it should be able to do.

    My problem is this:  When I get my lab completely built (1 domain controller server, 1 exchange 2003 server, 1 Xp client, 1 2007 CAS server)
    I try and login to the CAS server via https://cas/owa - this works and gives me the expected error of mailbox does not exist on
    this server, which it does not.  I only have CAS role installed.  When I try and access https://cas/exchange I login and it begins
    to partially load the outlook web access pages.  I can see some items on the left (calendar, contacts, etc) and along the top but
    thats about it.  It never finishes loading.  Is the CAS server supposed to use the Exchange 2003 OWA 'format' when displaying mail,
    contacts, etc from the Exchange 2003 server or will it simply show the exchange 2007 forms login page and 2007 OWA pages?

    Like I said i've rebuilt this lab 3 with the same result.  What is the normal view with Exchange 2007 OWA redirection to a Exchange 2003
    mailbox using https://cas/exchange??  I assume if the mailbox is on a 2007 server, it will use the 2007 OWA pages.
    How can i fix this so it works properly?  I need to be able to access both mailboxes on exchange 2003 during a migration.

    Server are fully patched using latest service packs for both exchange 200x and windows server 2003.

    This seems like it should be a simple fix, but frustrating is a better word.  i'm leaning on just putting all the roles on a single server and migrate over a weekend to get it over with with all the users out of the office.