We need to integrate with a partner that runs Lync Server 2013, including the August 2016 cumulative update.
I would like to use UCWA version 2.0, which is well documented here: https://ucwa.skype.com/documentation/whats-new-ucwa
So far I couldn't find any release notes or documentation that confirms that Lync Server 2013 supports UCWA 2.0, and if it does - which updates are required.
Considering the following:
In general Lync Server 2013 CU1 and above used UCWA 1.0.* (Lync 2013 RTM didn´t have UCWA) while Skype for business Server 2015 used UCWA 2.0.*
In coexistence mode (Lync 2010 and Skype for Business 2015) you must point the Autodiscover CNAME (Lyncdiscover. and LyncDiscoverinternal.) to a Skype for Business Server 2015 pool in order support custom UCWA 2.0 application development (as written here). But that's for Lync 2010 which do not have any UCWA on its frontend server as written here.
A Lync 2013 mobile client used also the UCWA (as mentioned here or here) and is compatible with Skype for Business.
The UCWA 1.0 Code samples, Get started, What is this API?, Core features and Reference URLs here all points now to the UCWA 2.0 links.
lead to the point that this should work.
Related
I've tried to get the projects from the TFS on-premise version using below API,
http://tfs2013.ilinktrichy.com:8080/tfs/{organization}/_apis/projects?api-version=1.0
Used the basic authentication and enabled the basic authentication in IIS as well. Still am getting 401 unauthorized issue.
Do i need to do any other changes on IIS?
This is an easy answer, but you're not going to like it.
TFS 2013 did not have REST APIs. They were introduced in TFS 2015.
You can use the old SOAP .NET client for automating tasks against TFS 2013, or (better yet) you can upgrade to a modern version.
update
What I said is not entirely accurate: some of the APIs were present in 2013, but they were not officially introduced until 2015 and are thus largely undocumented and totally unsupported.
First post here. Facing a problem where on Windows 10 an Oracle Identity Access Management (IAM) Windows Native Authentication (WNA) protocol fallback to a form-based logon page always fails whenever the Microsoft Online Services Sign-In Assistant (SIA) is installed. Whenever we remove the SIA, the WNA fallback to a form-based logon page always succeeds. This error is reproducible 100% of the time. We have not tested on Windows 8 or Windows 7. I've researched it, and there is not much out there to read about the SIA; it does not look to be configurable on the client end. Really want to avoid changing up code on the IAM WNA side.
Anyone out there seen this before? This is a large enterprise network, using all Windows 10 computers, which has both Oracle IAM running for some applications as well as Microsoft Windows 2008 R2 Active Directory, to which all the Windows 10 computers are joined. We are also standardized with Office 2016 with all back-end servers supporting Office apps such as Outlook, Lync, etc. in the cloud (Office 365).
Please let me know if I need to show the Oracle IAM/WNA SSO fallback code.
The Microsoft Online Services Sign-In Assistant is not configurable. But, if all your computers are running Office 2016 you do not need it anyway and it can be safely uninstalled, which as you said will make the fallback to form-based logon page work. If you were running Office 2013 you would need it however. Office 2016 apps such as Outlook and Lync can go direct with ADFS whereas previous versions could not do this. I don't have a URL reference for you, this is based on my experience.
I am planning to develop an communication apps based on Lync SDK. I understood that in order to run my application, i have to install lync client in the computer. This is where the following question arises
Is it possible to develop advanced features (that is available when installing Lync advanced) by using Lync SDK with Lync basic as client?
What is the difference between Lync basic and Lync advanced when using Lync SDK?
Should i install Lync Advanced to use the advanced features using Lync SDK?
It would be helpful if someone could tell me the difference?
Regards,
Raja
There is pretty much no difference between the Lync Basic Client and the Lync Client when using the Lync Client SDK.
I've only found one very small difference that hit me, Lync Basic doesn't support the "PIN to Gallery" feature. If you call the "PIN to Gallery" API, it will throw and the API doesn't tell you it's not supported.
The only other limitation of Lync Basic I've hit is that you can't configure any forwards. But this is more of a client configuration rather than API access limitation.
Everything else I've done with the Lync Client SDK has worked fine between the Lync Basic and the Full Lync Clients.
I'm looking at whether we can migrate our old on-premises TFS 2010 server to Visual Studio Team Services. We all have MSDN subscriptions so it looks promising. But we have an app we wrote to keep our SQL scripts in version control. The app uses the old Microsoft.TeamFoundation.Client & Microsoft.TeamFoundation.VersionControl.Client object model approach. I'm lost in the Marketing-focused pages about VS Team Services and all I can find is talk of a REST API. Would we really have to re-write this part of the app or am I just missing something?
(I know we could do the source control bit from Visual Studio but the app has other functionality I haven't seen elsewhere.)
Can anyone advise me, please?
The TFS 2010 API works just fine with Team Services, so your app should just work.
You can currently use the 2010, 2012, 2013, and 2015 TFS client API's for TFS against Team Services. Team Services is just TFS on the internet...
Is there any way to send files using the Microsoft Communicator API/SDK?
No, sending files is not supported by the Automation API.
If upgrading to Lync Server 2010 is an option, the Lync SDK supports file transfers