New answers tagged outlook
Shane's solution is for Exchange 2016. I've used AD Photo Edit by Cjwdev. Pretty simplistic, gets the job done.
Have you tried using Code Two Active Directory? It upload images to Active Directory and resize photos. This way, you can easily add pictures to internal Outlook 2010 messages and display them in GAL (Global Address List) and contacts.
This is likely to be closed as it is more of a "software recommendation" question as it is currently written. You may be able to wordsmith your question better to avoid that, not sure. That said, there is no built in functionality within Exchange to do this, but you could look at programmatically doing what you want. A possible solution (logically) would ...
I'm not aware of any. You could probably get something together if you bring in Microsoft Flow or PowerApp. You could create a SharePoint list for tracking submissions, and wire up flow to take action when new items are added to the calendar, that checks against that SP list. Flow is still evolving, and I know it has a check for new items being added to ...
Microsoft provides the Inbox Repair Tool for correcting most problems with damaged Personal Folders .pst files. If you do not see the Inbox Repair Tool on the Start menu, under Programs | Accessories | System Tools, use Start | Find or Start | Search (depending on your operating system) to search your system for Scanpst.exe. https://support.microsoft.com/...
As per below Microsoft's KB article, installing certain updates can cause the issue. Follow the below steps taken from the site to disable (ignore) the "Require SSL" option under both Autodiscover (which Outlook client uses to connect to Exchange) and Virtual Directory pages under your Default Site on your Exchange 2010 server. Quoting from https://support....
You can go to File > Open to open the old .pst file and view the emails. You can also use the Import/Export option to import the messages into your new PST file if you would like.
The problem was that the outlook autodiscover records must point to the on-premises exchange server until the very last user is migrated from it. The on-premises exchange server is doing the autodiscover redirection, for mailboxes that are in the O365 Cloud. The confusion that happened is that O365 gives a warning that the DNS records are incorrect. That is ...
Check with your IT department and see if they are giving the users "Full Control" to the mailbox from the Exchange admin console. That is the permission that allows you to access the mailbox as if it was yours.
Top 50 recent answers are included