Conference rooms are frequently reserved for ongoing recurring meetings as calendar placeholders. Unfortunately, these conference rooms remain booked when the likelihood of having the meeting is low. Sending email alerts 1-2 days prior to a scheduled meeting requiring the host to confirm the room booking would free up abandoned meeting rooms for other people. This is a similar approach that doctors and dentists use to... more »
I often find myself constantly playing email 'catch-up' and responding to my large email backlog long after normal work hours. As many of my email contacts are extremely high level business executives and/or highly dedicated senior technical professionals, these after-hours email communications often become an unnecessary late night wake-up call. Other than the current Draft email solution (which implies that additional... more »
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..
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?
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.
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.
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.
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.
Each email account configured in Outlook should have separate S/MIME configuration. Right now, if you configure Outlook with an S/MIME cert on one account, and set it auto encrypt, it applies those settings to all email accounts, even those you don't have an S/MIME cert for.
Right now, if you enable the client side auto archiving in Outlook, and have multiple accounts configured in Outlook, all messages from all accounts are archived into the same .pst file. This should not be the case.
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/
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.
At the moment Retention Policies are only triggered on their retention age. Enhancing it with additional regular expressions (like transport/mail rules) will help manage the mailbox. 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 »
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.
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.