none
ACTIVESYNC ISSUE USING IAG 2007 RRS feed

  • Question

  • Hello.

     

    I have an issue using the IAG 2007 for publishing Activesync (https). With the IAG out of the box Set for Activesync in combination with an Exchange 2003 Server (SP2) I always receive a login screen when a smartphone connects to the server. The login screen (user, password, domain) says that I have to correct my password for Exchange Server. I am sure that I enter the correct password but if I try again, the same login screen is shown. When checking the ISA Log, I can not see any traffic from the IAG to the Exchange Server or to the Domain Controller. OWA over IAG works fine - no problems with authentication.

     

    Has anyone information had such an issue with ISA or IAG?

     

    Greetz,

    XMI

    • Moved by Keith AlabasterModerator Tuesday, June 16, 2009 6:17 PM New Forum (From:Forefront Edge Security - Publishing)
    Thursday, January 17, 2008 9:54 PM

Answers

  • Hi XMI,

      I would recomend reviewing the problem and options described in this blog post http://blogs.technet.com/edgeaccessblog/archive/2009/01/15/after-installing-iag-2007-sp2-mobile-devices-can-no-longer-synchronize-through-iag.aspx for properly configuring ActiveSync.  Method A as described in that blog is the prefered method for defining the repository as it will persist on updates and be stored in the IAG backup.

     

    Method A) Add a custom “.inc” file in the CustomUpdate Folder

     

    · How:

    1. Create a file named [TrunkName](0|1)ActiveSyncLoginStart.inc in ..\Whale-Com\e-Gap\von\InternalSite\inc\CustomUpdate\

     

    2. Within this file add the following content:

     

    <% 'This file defines the repository that is used for ActiveSync for this trunk.

    repository = “[RepositoryName]”

    %>

     

    · Pros: easy to customize, flexible and update independent, will be backed up with an IAG backup.

     

    · Cons: in comparison to the other methods, this requires an .inc file to be created for each trunk that runs ActiveSync and the file name needs to match the trunk name.

     

    I would also recommend reviewing the blog posts about configuration and troubleshooting ActiveSync if after making the above change you still have problems with ActiveSync.

    http://blogs.technet.com/edgeaccessblog/archive/2008/07/24/publishing-microsoft-activesync-through-iag-2007-part-1-of-2.aspx and

    http://blogs.technet.com/edgeaccessblog/archive/2008/07/29/publishing-microsoft-activesync-through-iag-2007-part-2-of-2.aspx

     

    Regards,

    Dan

    Wednesday, June 17, 2009 2:07 AM
    Moderator

All replies

  • Hi.

     

    Is the repository="" line set properly?


    1) Browse to C:\Whale-Com\e-Gap\von\InternalSite
    2) Edit activesynclogin.asp
    3) Locate the line repository=""
    4) Modify that line to read repository="[NameOfTheRepositoryConfiguredForTheTrunk]"
    *note the name of the respository is case sensitive and must exactly match the name of the repository configured for that trunk
    5) Save the file.

    do a soft reset of the mobile device and try to re-sync the device should sync properly.

     

     

     

    Thursday, March 27, 2008 8:34 AM
  • Hi XMI,

      I would recomend reviewing the problem and options described in this blog post http://blogs.technet.com/edgeaccessblog/archive/2009/01/15/after-installing-iag-2007-sp2-mobile-devices-can-no-longer-synchronize-through-iag.aspx for properly configuring ActiveSync.  Method A as described in that blog is the prefered method for defining the repository as it will persist on updates and be stored in the IAG backup.

     

    Method A) Add a custom “.inc” file in the CustomUpdate Folder

     

    · How:

    1. Create a file named [TrunkName](0|1)ActiveSyncLoginStart.inc in ..\Whale-Com\e-Gap\von\InternalSite\inc\CustomUpdate\

     

    2. Within this file add the following content:

     

    <% 'This file defines the repository that is used for ActiveSync for this trunk.

    repository = “[RepositoryName]”

    %>

     

    · Pros: easy to customize, flexible and update independent, will be backed up with an IAG backup.

     

    · Cons: in comparison to the other methods, this requires an .inc file to be created for each trunk that runs ActiveSync and the file name needs to match the trunk name.

     

    I would also recommend reviewing the blog posts about configuration and troubleshooting ActiveSync if after making the above change you still have problems with ActiveSync.

    http://blogs.technet.com/edgeaccessblog/archive/2008/07/24/publishing-microsoft-activesync-through-iag-2007-part-1-of-2.aspx and

    http://blogs.technet.com/edgeaccessblog/archive/2008/07/29/publishing-microsoft-activesync-through-iag-2007-part-2-of-2.aspx

     

    Regards,

    Dan

    Wednesday, June 17, 2009 2:07 AM
    Moderator