With the great move to virtualization we would like to have nfs/smb support to store the database files, meaning that we can haves support to present VMDKs hosted on NFS/SMB to the OS and host databases on them, this will be great for small and large enterprises due to the simplicity of nas based deployments...
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..
DIR 2.0 has added more functionality especially when combined with single item retention except for the ability to restore users deleted folders. If a user deletes a folder with items in it, we can only restore the items and not the folders WITH the items in it. In 2013, New public folders have the ability but not normal mailboxes.
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.
Adding Set-MailboxSentItemsConfiguration / Get-MailboxSentItemsConfiguration for Exchange 2013, which is more elegant and manageable than setting (version-dependent) Outlook registry keys.
Allow a user to change their FROM address to any of the SMTP addresses on their mailbox or one they have Send As rights to.
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?
This was available with Lync 2010/OWA integration, but Lync 2013 integration requires manually editing the web.config in Exchange.
Add the Rollup & Cumulative update version to the Server Version name. Currently when you run Get-ExchangeServer | FT Name, AdminDisplayVersion it just shows the build number which we have to lookup or remember every build number. This would remove the need for extensive scripts that look at registry keys among other things.
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.
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).
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.
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).
It would be great to have visible status of Exchange Services in EAC - especially when RPCClientAccess Service stopping unexpectedly.
Mobile devices connecting to Exchange is the way of the future yet most of the time when we get new devices the old one stays in the list. I have a powershell script to clean these up, but it would be nice if this could be automated through Exchange.