GAL Segmentation, Exchange Server 2010 and Address Book Policies

It is amazing that Microsoft looks at its customers like the Japanese goverment looks at their residents.  Give them only what you want them to hear and hide what is really going on.  In the case of Exchange, it is only fathomable that Microsoft would not include GAL separation capabilites that have been available in all modern Exchange deployments prior to 2010 because they want those types of clients moved to their cloud services.  No other reason would explain the unbridled complexity of doing this along with the loss of so much functionality.  This constitutres abuse by Microsoft towards their customer base.  It is inexcusable behavior but typical of an organization which has lost its way.  As an Exchange 2003 Enterprise user hosting e-mail for many small customers, the move to 2010 is basically impossible and apparently designed this way by Microsoft.  To even produce a new version of Exchange which does not support this (2010 pre SP1) is treachery and then to add it in SP1 with such cripling loss of functionality (no Public Folders, no GUI, no UM, etc.) is disgusting behavior.  Users should be keenly aware that Microsoft is deceiving you in order to hold on to their dwindling market share by forcing small Exchange hosters into cloud services enriching Microsoft while desimating revenues for the small hoster.  To me, it is unconscienable behavior.  I know I cannot be alone in my dissatisfaction with Microsoft on these important issues.