How Find Contact Works
As I mentioned before, these tools to not
currently leverage ActiveSync. In my larger SmartPhone
deployments, I have created new Virtual Servers in IIS (on the
Front Ends) to support Active-Sync and NAT’ed these IPs and
Virtual servers from the outside using only port 443. Of course
Network Load Balancing is much better, but in some situations I
can’t use it.
What you have with this design is the
minimum footprint required to support ActiveSync synchronization
over the wire. Unfortunately, this configuration is so
locked-down; it will not allow the Find Contact features to
work! Here is why:
ActiveSync uses GETS, POSTS and OPENS to
synchronize against the /Microsoft-Server-ActiveSync application
that is loaded on the Exchange 2003 Servers:
POST,
/Microsoft-Server-ActiveSync, User=STEVEBRYANT&DeviceId=200687CAB5517E14783A6C62D31D4DC1&DeviceType=PocketPC&Cmd=GetItemEstimate&Log=V4TNASNC:0A0C0D0FS:0A0C0D0SP:1C7I5801S74670R0S0L0H0P
So my locked down configuration works just
peachy. Unfortunately, the Find Contact function must access the
/Public virtual directory since that is where Free/Busy
information is kept:
GET,
/public/, Cmd=freebusy&start=2006-04-18T00:00:00-04:00&end=2006-04-19T00:00:00-04:00&interval=30&u=SMTP:Jason%2eSherry%40theproexchange%2ecom&u=SMTP:Steve%2eA%2eBryant%40theproexchange%2ecom |
