After installing IAG 2007 SP2 - Mobile Devices can no longer synchronize through IAG

After installing IAG 2007 SP2 - Mobile Devices can no longer synchronize through IAG

  • Comments 1
  • Likes

With the release of IAG 2007 SP2 (although this behavior can happen with any new update), we have been receiving some support calls about this subject and we want to bring some awareness about this behavior. Last year we published two posts about Active Sync configuration on IAG 2007:

 

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

 

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

 

When you use Part 1 of this article you will notice that step 9 advises to make a modification to the file \Whale-Com\e-Gap\von\InternalSite\ActiveSyncLogin.asp in order to enter the authentication repository. This works, but there is a caveat that wasn’t mentioned in the original post. The caveat is that changes made to IAG’s default ASP/INC/etc. files could be overwritten when software updates are applied to IAG. So the question now is: what should I do?

 

There are some others approaches to achieve this task and here are the options that you have:

 

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.

 

Method B) Create an ActiveSync specific repository that matches the domain name.

·         Pros: Works out of the box. There will be no need to edit or maintain custom files and it will be backed up with an IAG backup.

·         Cons: creates limitation in naming convention of repository.

 

Method C) Create a CustomUpdate ActiveSyncLogin.asp

·         How:

1.       Copy ActiveSyncLogin.asp from ..\Whale-Com\e-Gap\von\InternalSite to ..\Whale-Com\e-Gap\von\InternalSite\CustomUpdate

2.       Modify the version in the CustomUpdate directory

3.       Open the Advanced Configuration for the ActiveSync trunk

4.       Select the Authentication Tab

5.       Change the Login Page from ActiveSyncLogin.asp to /CustomUpdate/ActiveSyncLogin.asp

6.       Change the On-the-Fly Login Page from ActiveSyncLogin.asp to /CustomUpdate/ActiveSyncLogin.asp

·         Pros: Very advanced option that is not recommended unless major parts of ActiveSyncLogin.asp are to be re-written and designed to persist on software updates, will be backed up an the IAG backup

·         Cons: Updates to IAG that change ActiveSyncLogin.asp will not be applied to the custom file any changes to the default file will have to be monitored and merged into the custom file manually after every update.

 

 Now you just need to plan which option best fits with your needs and start deploying it.

 

Authors

Yuri Diogenes

Security Support Engineer – ISA/IAG Team

Microsoft – Texas

 

Dan Herzog

Security Support Engineer – IAG Team

Microsoft – Washington

 

Tech Reviewers

Ran Dolev

Security Consultant – IAG Team

Microsoft – Israel

 

Ophir Polotsky

Forefront Edge Supportability Program Manager

Microsoft – Israel

 

John Redding

Security Support Engineer – IAG Team

Microsoft - Washington

 

Comments
  • 203 Microsoft Team blogs searched, 88 blogs have new articles in the past 7 days. 199 new articles found

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment