For Outlook 2010, 2013 it was possible to programmatically create Outlook profile and set up all necessary RPC_OVER_HTTP connection settings via MAPI like in this article: http://blogs.msdn.com/b/dvespa/archive/2013/05/21/how-to-mfcmapi-create-mapi-profile-exchange-2013.aspx.
However, looks like this approach is not working for Outlook 2016. Anybody knows is it ever possible to manually setup connection settings(or whatever else) for Outlook 2016 to create new profile?
The way MSEMS provider is configured in Outlook 2016 is different from the previous versions. From what I heard, it will be documented soon.
Documentation has just been posted by Dave Vespa: http://blogs.msdn.com/b/dvespa/archive/2015/10/29/how-to-configure-an-outlook-2016-profile-using-mfcmapi.aspx
Related
I am trying to create an Outlook add-in with the onSend function. I can see on the GitHub onSend Tutorial that onSend is only supported on Outlook web and 365. Has this been updated now (the readme is 2 years old)? I am trying to debug mine on Outlook desktop 2016 (using Visual Code + Edge extension) and the debugger never reaches the function I created and that is supposed to be reached during the onSend event.
If still not supported, can I still deploy this add-in via 365 (admin) and get it reflected on Outlook desktop 2016?
Thank you very much.
The On-Send feature is supported by the desktop editions of Outlook for Windows. Make sure you deal with the supported version of Windows, Exchange server, Outlook. Read more about that in the On-send feature for Outlook add-ins article.
OnSend is not supported in Outlook Desktop 2016.
I've submitted my outlook add-in 6 times now and every time the certification failed for a different reason. The last rejection reason I got was that my add-in didn't work on Office 2013 and Office 2016 (which they also refer to as O365 Perpetual).
I develop on a Mac and I have no idea how to go about debugging why my add-in is not working on those older Offices. Can't I just drop support for older Office suites? How could I test these environments?
I'm pretty close to quitting and just not publishing my outlook addin. I have never experienced a worse app review process.
If you want to be published on the Office Store, you need to support all the platforms for the minimum Outlook API Requirement Set in your manifest.
If you do not need to support Outlook 2013 or Outlook 2016, you can set your minimum API requirement set to 1.5, which will drop support for those versions (1.4 was the last version supported by those versions of Outlook). When you submit to the Office Store, please make a note that your minimum API set means that the add-in will not run in those Office clients.
Can we deploy outlook web-addins for O365 accounts using centralized deployment as described here ?
Three/Four months before, if I tried to install outlook add-in using this method, installation itself would fail. Now, I don't get any errors while installing, but the add-in does not appear in Outlook clients (Outlook 2016 in Windows and OWA in browsers).
Are centralized deployments supported for Outlook add-ins now? Also, are there any client side requirements? I found some related information here. But I am doubtful if it is up-to date.
Thanks for the query bala. Centralized deployment for Outlook add-ins is not supported as of now and will come very soon. There are no specific client requirements other than minimum requirements for add-ins.
Our company recently switched to Lync 2013 and I noticed that under "Settings/My Profile Picture" there is no longer an option to specify a profile image. In Lync 2013 you could at least set a picture with less than 30kb that is hosted on a webserver.
The funny thing is I can use my Lync 2013 server account with the old Lync 2010 client and then I'm still able to set a profile picture (tested & woks).
Seems as Microsoft just killed this feature in the client but not on the server (LOL!?!?).
I would like to write a tool to be able to set a picture without having to install the old Lync 2010 client. Any hints, solutions or something to read?
Update as of 12/11/2013
The latest Lync update (Lync Client CU3 (November Update)) has the option to set a photo added back to the GUI.
Link to the KB Article
Link to the Download
Article with explanations and screenshots can be found here: Lync Client CU3 (November Update) – Show a picture from a website!.
Original Answer
This question comes up more often. It's indeed just a user interface change between the Lync 2010 and 2013 clients, the option to set an image URL has been removed. Underwater this option is still available though, and you can publish a Photo URL to the server from a user endpoint, or from a powershell admin screen as posted in GodEater's answer.
I answered with a description on how to publish photos using a user endpoint (wheter from client SDK or UCMA) here: Display User Picture in Lync 2013
Someone's implemented this as a powershell script here (and I've tested that it works on our Lync 2013 infrastructure) :
http://gallery.technet.microsoft.com/office/Add-Personal-URL-Photo-in-df0136ea
Hi we recently installed an SBS 2011 server for one of our clients and we had some problems using software that creates messages using mapi on exchange 2010. After investigation we found out that the root cause of this problem is that STORE_HTML_OK is not set in the PR_STORE_SUPPORT_MASK.
The weird thing is we (the firm, one of my collegues) did the installation of the sbs 2011 server with exchange 2010 for the client where STORE_HTML_OK is not set, during my investigation of the problem we installed another sbs 2011 server for testing purposes and there STORE_HTML_OK is set whereas it wasn't in the previous installation.
I would like to know what could cause the STORE_HTML flag not to be set in PR_STORE_SUPPORT_MASK on exchange 2010, i also would like to know if we can still change this somehow by changing settings in exchange management console or shell ?
We would like our futurue sbs 2011 servers always to have the STORE_HTML to be set in the PR_STORE_SUPPORT_MASK and like to know what could have caused it not to be set.
Thanks in advance
Willems Davy
EDIT:
Our new sbs 2011 installation has the same problem, i was always testing the code from a client pc where outlook was installed and when outlook is install the mapi version of outlook is used so when running the code from a client with outlook 2007 or even outlook 2003 installed the issue is not there, When installing the mapi runtime (messaging api and datacolaboration objects ...) on SBS2011 the problem is the same (i tested 3 sbs 2011 installations now). The weird thing however is i use the same setup for installing the mapi runtime on a SBS 2008 server and there we don't see this problem, could this be a problem with the mapi runtime being somehow incompatible with sbs2011 / exchange 2010 ?
EDIT2:
we were wrong in our assumption that the STORE_HTML_OK flag was the cause of the program failing, after some more testing it seems this flags is only set when using the mapi dll from outlook, it's never set in our test when looking with MFC_MAPI at the PR_STORE_SUPPORT_MASK on the server when using the mapi runtime not even on SBS 2008.
However the problem with the software is related to the PR_BODY_HTML flag, on exchange 2007 (SBS 2008) servers using the mapi runtime we can change this property on exchange 2010 servers (SBS 2011) we can not and get an error when opening the PR_BODY_HTML propert using openproperty that says "the client operation has failed" this seems to be our main problem and the problem of the software we have.
so it's not related to the PR_STORE_SUPPORT_MASK, maybe i should ask a new question about it, since the problem is not the same as we initally thought?
I don't think this is a server setting. That bit is exposed by the store provider, which runs locally.
What version of MAPI did you install on the machine where your code runs? Is it an older version of Outlook?