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..
Adding Set-MailboxSentItemsConfiguration / Get-MailboxSentItemsConfiguration for Exchange 2013, which is more elegant and manageable than setting (version-dependent) Outlook registry keys.
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.
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 »
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?
When generating certificate requests, you cannot directly use an internal CA such as with the Lync Deployment tool.
This isn't an issue for public certificates, but for internal certificates (for instance OAuth) this would make my life a bit more pleasant.
Title says it all. Exchange databases grows mainly because of the attachments witch causes challenges to backup and maintain operations. There has to be some kind of solution in the future that reduces database size and disk utilization.
It would be a killer feature that all the attachments could be stored to a deduplication database and original message could refer with link to the attachment.
Would be easier to apply retention policies to mailbox databases rather than individual user mailboxes. Easier to organize this way rather than having a bunch of nightly PowerShell scripts.
For instance: Mail to archive when retention age is 90 days, unless object has attachment the mail is moved to archive when retention age is 45 days.
(In my own mailbox, I move certain mails via a rule to a folder which has a specific retention... more »
Can we go back to preventing users from Creating Globally Visible Distribution Lists as a default? Yes, I know there are workarounds, but it would just be better if this never was allowed to begin with.
Currently neither native to Exchange so a third party MTA on-prem or in cloud is required. I've had some customers that required this, not having this native added additional cost.
More info: http://dkim.org/
Easier for end users to share calendars or provide public F/B. Can be done today but by default is off and require admin PS plus difficult end user config, simple end user share using URL and be done.
The combination of Exchange 2010 and Forefront protection for Exchange 2010 is/was offering a decent multi engines antivirus and antispam solution. Forefront integrates on Exchange/Edge features like recipient filtering or safelist aggregation. Messages can be scanned at Edge, at internal transport level (and at mailbox level)… It offers a better protection than what is possible with Exchange 2013.