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 »
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!
We host our Exchange and Lync community calls and send the invites out via DL’s. Generally this has been good and a major improvement over trying to maintain the list of invitees within the event itself. However, it’s far from perfect, people end up with old/stale invites, don’t get updates, get forward the invite so never receive updates etc. The solution, to my mind, is a calendar that people subscribe to – that way ...more »
When a cloud user logs into the on-premise OWA URL in a hybrid deployment, the user is prompted with the "Use the following link to open this mailbox..." prompt and a link to the Office 365 OWA interface. In the interest of providing the most seamless integration for hybrid organizations, it would be nice for the option exist to make this a silent redirection so both on-premise and cloud users can utilize the same URL. ...more »
The current method of migrating from legacy public folders to a public folder mailbox is painful. I appreciate all that has been written about the process, however, it simply does not work elegantly or efficiently enough to attempt the process. As it stands right now, PST export/import is the only method I will perform. Would love something more integrated.
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/
Similar to Recover Deleted Items and Quotas, SIR should be a property of the Mailbox DB. Hence it would be inherited by all mailboxes in the database and we no longer have to enable it per mailbox.
Currently (CU3), you only can create new groups which are immediately mail-enabled. But you cannot select groups to mail-enable them. You have to do this via shell.
Currently quarantine, block or allow, and approval for activesync devices is performed using the Set-ActiveSyncOrganizationSettings powershell cmdlet.
These features should be baked into Activesync Policies, allowing Exchange Administrators to prioritise block, quarantine and allow configurations based on the Activesync device policy a user mailbox has been set.
Exchange currently has the Scheduling Assistant in Outlook and OWA, but unless you have Exchange Federated partners in order to access each others organizations Free/Busy information, it's limited to internal users. This makes planning with external users more cumbersome. Basically something like Doodle.com, within Exchange but without the need for federation or extensive preparations. Inspired by a suggestion by Mike ...more »
There are many times when administrators have a reason to disable mail-related attributes on AD objects. How many of these admins have accidentally lost the LegacyExchangeDN? Thousands of admins do this, even in Exchange Online. Either leave the LegacyExchangeDN as-is after the AD account is first mail/mailbox-enabled, or store it in an alternative attribute when disabling mail-related attributes and when re-enabling ...more »
Realtime status and statistic reporting on Mailbox moves and PST import/export preferably in EAC.
Currently there is a very basic EAC alert and Mail report possible with PST im/ex, but it only reports completion or fails. You then have to use several cmdlets in the shell in order to find out what the cause was.
Basically more like the Staged/Cutover migration information in the Recipients>Migration pane in 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 »
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.
Using the support provided for DLP rules in 2013 we would like to use these same matching rules to applying a Retention and\or Archiving tag to messages based on their content.