Badges [ 7 ] [-]
Memberships [ 1 ] [+]
Activity Stream [+]
Ideas Contributed [ 5 ] [+]
Allow third party clients that can use LDAP directories and clients such as Outlook 2011 to use CAS servers as a hardened SSL LDAP proxy.
This will ensure any client can have an interface to the GAL (Internal or External) which follows the rules of Address Book Policies.
End users can share a calendar with anyone from Exchange using iCal or HTML. Extend this feature to allow authenticated users (either via URL, or username/password) to edit calendars shared via iCal, updating the same underlying feature to use HTTPS rather than HTTP. This will allow end users to collaborate better with anyone, whatever the platform, or whatever client they are using. This will also mean that users of ...more »
There are many times when administrators have a reason to disable mail-related attributes on AD objects. How many of these admins have accidentally lost the LegacyExchangeDN? Thousands of admins do this, even in Exchange Online. Either leave the LegacyExchangeDN as-is after the AD account is first mail/mailbox-enabled, or store it in an alternative attribute when disabling mail-related attributes and when re-enabling ...more »
Users can manage Distribution groups, but can only add members who have an AD object.
For example : Add a second multi-value attribute (eg externalMembers) and a permissions mask to provide the ability for an administrator to allow certain DGs to have a secondary list of external SMTP addresses.
It's 2013 and we still have a reliance on the LegacyExchangeDN within the Outlook client.
Update all supported clients to only cache the SMTP address in the autocomplete/nickname cache and when stored as properties on items.