http://blogs.technet.com/b/exchange/archive/2005/12/09/415874.aspxWith Exchange 5.5 coming to the end of its support life cycle, lots of companies have been migrating quickly from Exchange 5.5 to Exchange 2000 or Exchange 2003. One major component that is affected by mixed mode site migrations/consolidation is the OABen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.technet.com/b/exchange/archive/2005/12/09/415874.aspx#415948Mon, 12 Dec 2005 20:51:27 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:415948dgoldmanAs to why it is so late, I can not answer that. I can tell you with all the work I have been doing, I work it and post it for everyone :)<div style="clear:both;"></div><img src="http://blogs.technet.com/aggbug.aspx?PostID=415948" width="1" height="1">http://blogs.technet.com/b/exchange/archive/2005/12/09/415874.aspx#415908Mon, 12 Dec 2005 02:44:22 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:415908MikwGood article, but: why is it available so late? Probably just few people really understood before installing Exchange 2003 what's going to happen with full OAB downloads and how much it's going to bug their networks! MS/MCS never pointed out Exchange 5.5 &lt;-&gt; 2003 sync as the source of permanent full OAB downloads. And workarounds are just ridiculous - &quot;install OAB only server&quot;. Guys, the main &quot;selling&quot; point for Exchange 2003 is consolidation and not istallation of additional servers in every single small office bugged by regular OAB regenerations! <br> <br>Hopefully we won't have such &quot;nice&quot; surprises with next versions of Exchange.<div style="clear:both;"></div><img src="http://blogs.technet.com/aggbug.aspx?PostID=415908" width="1" height="1">