This was available with Lync 2010/OWA integration, but Lync 2013 integration requires manually editing the web.config in Exchange.
The ability to save signatures centrally (in the users mailbox) and not in the local profile. Saves a configuration step for users/admins and makes it possible for the user to use the exact same signatures in OWA, EAS, etc. etc..
An app like the OWA App for iPhone/iPad, but now for Android devices. No need for ActiveSync and all it's troubles that come with it (for instance: SD encryption sometimes formats the SD with loss of data) and no worries about a complete remote wipe (potentially wiping personal data).
An app like the OWA App for iPhone/iPad, but now for Windows Phone devices. No need for ActiveSync and no worries about a complete remote wipe (potentially wiping personal data).
It also allows for a more Premium experience on WP, compared to the native ActiveSync implementation.
Adding Set-MailboxSentItemsConfiguration / Get-MailboxSentItemsConfiguration for Exchange 2013, which is more elegant and manageable than setting (version-dependent) Outlook registry keys.
Pre-filled FROM: dropdown listbox in mail composition form (also OWA), using info from delegated / shared mailboxes a.o. (Send-As) to populate. More end-user friendly than typing in the 'from' address (once) or picking entry from GAL (when shown).
Just like the EMC (Exchange Management Console) in Exchange 2010. That had the ability to preview the Exchange Management Shell syntax or in other cases to review the used syntax after it was applied.
This ability is a great learning tool but also a valuable tool for documentation.
Exchange 2007/2010 supported the Connection Filtering Agent on the Hub Transport role. This agent is not available on the Exchange 2013 CAS and Mailbox roles.
This means we can't use real-time block lists on Exchange 2013 servers. Which is a shame because RBL's have proven to be a great measurement against spam.
PAL (http://pal.codeplex.com/) is the best tool to assist with Exchange performance issues. The tool helps with the creation of performance monitor counter logs and analyzing the logs against a threshold file. Unfortunately there's no threshold file for Exchange 2013 and the author of the 2010 versions doesn't respond to email. It would be great if the Exchange Team could support this, the tool is just as valuable as ...more »
Right now, when you disable someone from UM, it leaves the EUM addresses assigned to the user. It would be nice to see a prompt asking if you'd like those removed. Otherwise you have to manually remove them to make that extension available for another user.
Right now, there are something like 2900 UM system prompts. It's not supported to change them, and installing a CU overwrites them. It would be nice to have it supported to change them, along with a list of which prompts contain which message.
When a user leaves the organization and their mailbox and AD account are removed the delegate information get's stuck in the Outlook client and creates errors for the users until it is removed. Is there anyway to make this a function of AD or Exchange so that this removed when a user leaves?