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.
You have Inside and Outside Organization and you can even enable that only (outside) contacts receive an OOF reply. I would like a little bit more control over that, for instance by by white or blacklisting (external) contacts, so that they will or will not receive an OOF reply. Also the ability sending an OOF reply for external addresses only when you do not have them as a contact. It's reasonable to assume that contacts ...more »
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 »
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.