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?
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.
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.
It would be great to have visible status of Exchange Services in EAC - especially when RPCClientAccess Service stopping unexpectedly.
When DAG database failover event occurs alert admins through E-mail notification to notify over this event to take action, we have script which checks the database distribution on the Exchange Servers and when it finds any discrepancy in the distribution triggers an Email with the details with which we come to know about the issue and start the investigation, It would be good if this is automated with a Option in EAC ...more »
My understanding is that the SMTP Queue viewer is only available in the Exchange toolkit on the Exchange 2013 mailbox server. Would prefer to have the Queue viewer available in the web-based EAC.
I doubt you'll find an organization that has intentionally chosen to force their users to go to "https://mail.company.com/owa"; nearly everyone wants the "simple URL" of "http://mail.company.com". Instead of publishing a lengthy process for simplifying the URL (http://technet.microsoft.com/en-us/library/aa998359(v=exchg.150).aspx) or having consultants simplify it their own way through one of the many other methods, ...more »
You can set the AutoMapping feature when adding individual users to Shared Mailboxes.
However, this facility is not available for Security Groups.
A lot of organisations tend to link Security Groups to Shared Mailboxes as part of their designs, which is frustrating when AutoMapping doesn't work.
Would be good to solve this MS.
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 »