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.
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 »
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.
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 »
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.
In Exchange 2013, EAC (Exchange Admin Center), when you click on Edit, it opens a small window. It should open a larger window. For example, Recipients > Mailboxes > then click "Edit" on one mailbox. The window that opens is only about half the screen size. Why such a small screen ? I usually need to increase it anyway. And also why show -- More Options-- at the bottom of the Edit screen when there are only... more »
It would be great to have Exchange lookup free/busy for a remote hybrid organiation's cloud users using their native email address and (if possible) without having the need for a separate organization relationship.
It would be great to have a way to centrally manage the CMDlet Extention Agents instead of per server.
Aditionally preserving them through a CU upgrade would be equally appreciated!
In Exchange 2013, there are many options available when running a search cmdlet in PowerShell in particular to target those results to a Discovery Mailbox of your choice (i.e. New-MailboxSearch -TargetMailbox), but this option does not exist in the Exchange Admin Center. Allowing these options in the EAC will be helpful for non Exchange Admins, such as Compliance Officers to perform their daily tasks.
Exchange Online Protection offers some great compliance functionality in the cloud such as real-time DLP policy and rule matching. Adding these reporting features would be a great addition to the On-Premises product and helpful for validating localized transport of email containing PCI or PII data.
EAC logging only logs commands when the EAC logging window is open and it is not enabled on by default.
Message Recall almost never works and the recall and replace works ok. Anything to improve these features would be welcomed by end users.
In previous versions of Exchange using an MMC, opening the Receive Connector properties would give you a sorted list of the IP address(es) that were allowed to relay through a connector. Exchange 2013 haphazardly lists them in some random order. It's not even order the entries were created. Please sort the list. Another tag-along to that idea is to make that listbox typeable, so it'll bring you to the section of... more »