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
Related
I have an Add-in I have written for Microsoft Outlook. The Add-in runs in a task pane. I have a button on the html in the page that opens a new window using Office.context.ui.displayDialogAsync. This button works fine in the web client, but when clicked in the full Outlook client, a window appears and disappears in a split second. This Add-in was developed outside VS so not sure how I can debug apart from in web client, which not does have the issue.
The domain is the same, and the domain is in the appDomain of the XML manifest. The URL is also https.
Does anyone have any ideas, have I missed something that says this isn't available in full client and only available in web client?
About Outlook version:
Version 2102 (Build 13801.21004 Click-to-Run)
Microsoft Office for Outlook 365 MSO (16.0.13801.21002) 64-bit
If I clock Office Updates, it tells me Office is up to date.
Update
I have another machine with Outlook installed, and I have discovered the dialog opens fine on the full outlook client. Looking at the version for that version of outlook (logged in to the same Office 365 account), the version shows as:
Version 2110 (Build 14527.20226 Click-to Run)
Microsoft Office for Outlook 365 MSO (Version 2110 Build 16.0.14527.20168) 64-bit
So it looks like maybe the earlier build had an issue in Outlook?
Would you like to share a screen recording in the machine where the API is not working?
Besides, you could also try a test add-in with this: Manifest.
It's an app command so you can click "Show Taskpane" first, and then click "launchDialogSameOrigin" button in the taskpane. You can observe whether the dialog is working correctly in this add-in.
Thanks.
This is in an Enterprise setup (had a lot of GPO set) running Exchange 2013 Server, with Outlook 2013 client.
I installed the add-in using OWA
Manage Add-ins > Add from file
The add-in appeared in and worked fine
When I open outlook 2013, I do not see the add-in appear, tried a lot of steps to debug.
As per this doc https://learn.microsoft.com/en-us/outlook/add-ins/troubleshoot-outlook-add-in-activation
Version no was ?Session.ExchangeMailboxServerVersion
15.0.1320.4000
Is the add-in disabled?
Enabled
Is the add-in manifest installed properly, and does Outlook have a cached copy?
%LocalAppData%\Microsoft\Office\15.0\WEF \<insert your guid>\<insert base 64 hash>\Manifests\<ManifestID>_<ManifestVersion>
The new added add-in files would get removed everytime the data is pulled from exchange servers. Only 3 default add-in files were available.
Checked Windows Logs in Eventviewer
The Exchange web service request GetAppManifests succeeded.
Got this message with event id 63
We also checked Fiddler and could see the call going to get the manifests but that would give the manifest of only 3 add-ins that come installed by default on Exchange Setup.
For the same account, the add-in works fine in a Virtual Environment, VDI setup. But doesn't appear on the desktop environment, if that helps.
To rule out the possibility of a wrong manifest file, we tried using the Outlook Command Demo Add-in. This also worked on Virtual Environment, VDI setup. But doesn't appear on the desktop environment.
Are there any other steps that can help us debug this? Any directory where logs are available for add-ins?
We have hit a roadblock due to this with no idea how to debug/get it working.
I am having a horrible time getting started at creating an add-in for Outlook. I want to use the new html/javascript/manifest approach. I have been able to create a manifest and application which works great with outlook.live.com. Where I am completely getting stuck is with desktop Outlook. How do I install/debug my add-in with desktop Outlook?
I cannot find anything in the UI which will let me add this style of add-in. Additionally the Microsoft documentation did not make things any clearer. Their docs seem to hint using this type of add-in is only possible if you are connecting to an Exchange server.
Any help would be greatly appreciated.
Yes the add-in will load on Outlook desktop only if your mailbox is Exchange. I am not sure the add-ins work with a personal Microsoft account (e.g hotmail.com, outlook.com) and Office desktop. Keep in mind that the support of mail add-ins for personal account is relatively new (officially announced in march 2016).
To develop your add-in I suggest you to use a organizational account (i.e. Office365 account). Support for organizational account has been released in 2013 and is a much more mature solution for you to get started. You can have a free dev account at dev.office.com.
Edit: October 2016 personal account are supported now by "Personal mailbox accounts" aka outlook.com accounts
Let us keep in mind that a mail add-in is not installed on a mail client (desktop, OWA) but on the mail account. When you "install" an add-in you only set a xml file on your mailbox that basically says "there is a web add-in out there called X and that is served at this url...". Then, if you install add-in X on your mailbox smaclell#mytestcompany.onmicrosoft.com, this add-in will load the add-in web iframes whether you are consulting your mailbox with Outlook Web Access (OWA) or Outlook Desktop.
To install the add-in for one user mailaccount, you have to use the Outlook Web Access. See this blog post. Note also that you can install the add-in for the whole organisation (Admin > Exchange Admin > Add-ins). Finally, Visual Studio is also able to push the manifest to your office 365 mailbox. To have this you need Office Development Tools.
For debugging in Outlook Desktop, I know two approaches.
Use the Office Developement Tools with visual studio
and select your sample add-in project as 'Starting project' and in properties select 'Office Desktop'.
Plain web development.
Personally, I do not use really much the Office Development Tools. I install manually my add-in with "https://localhost:XXXX" for url and I start the web project on IIS express to do the debugging. For stepping into the source code, I use the debugger of my browser (Chrome, Edge, IE etc.) when browsing in OWA. When I need to step into source code specifically on Desktop (For windows or for Mac) I use Vorlon.js see also this blog post.
My advice is also to test/debug frequently with IE 11 (still available in Win10!) and OWA. Indeed, the browser used internally by Office Desktop for the add-ins is IE.
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
I had to rebuild my Mac and installed Office for Mac 2016 (from an Office 365 subscription). I am not able to click on a link on a web page and edit the document with WebDAV (iTHit implementation not SharePoint). I was using Office for Mac 2011 before the rebuild and that was working...When I clicked on the link using Safari, the pop up for allowing the SharePoint browser plug-in did not display. Since the site I am connecting to uses basic authentication over a non-SSL connection, I used Terminal and ran the following command: defaults -currentHost write com.microsoft.registrationDB hkey_current_user\hkey_local_machine\software\microsoft\office\15.0\common\internet\basicauthlevel -int 2
I was not able to have the document open with Word.
I uninstalled Office for Mac 2016 and deleted and file that reference Microsoft..Then I installed Office for Mac 2011 and ran the command above with \14.0\ instead of \15.0\. I can edit documents with WebDAV.
What settings will allow the use of Office for Mac 2016?
I am having a similar problem and trying to open / edit office documents from the browser via WebDAV / Sharepoint plugin. This used to work with prior office versions, but not with Office 2016.
Apparently Microsoft dropped the WebDAV support for Office 2016 which would also affect the itHit library: http://answers.microsoft.com/en-us/mac/forum/macoffice2016-macword/using-office-for-mac-2016-to-edit-a-document-from/2aee8656-313a-4c97-8223-9a20373b9891
We have retested IT Hit WebDAV Ajax Library and Ajax File Browser with Office for Mac 2016.
Opening and saving MS Office documents from a web page works just fine. The Word, Excel and PowerPoint documents opened from server successfully, edited and saved back directly to server with no problem.
For testing we were using MS Office for Mac Version 15.22 (160506) with default install options and ajaxbrowser.com running Ajax File Browser v3.0.0.2465 (WebDAV Ajax Library v2.0.1735) as a testing server. The MS Office was installed on a clean Mac v10.11.3 that did not have MS Office 2011 installed previously, so there is no any remains of protocols installed by MS Office 2011. There is also no IT Hit Edit Document Opener installed on this machine.
The confusion around WebDAV being not supported is probably caused by a new MS Office "Save As..." dialog that shows the WebDAV location from which the document is opened but it does not allow browsing WebDAV folders. Even though, saving under new name in the same folder works well in "Save As" dialog.