Skype for Business Profile Picture You can't insert a picture or profile picture option is greyed out: • Profile pictures require an Office365 mailbox to be assigned to users. Currently, mailboxes are not assigned to user because campus mail is Google not Office 365. Connecting with Regular Skype Users Connections (IMs, Calls, Video Calls, and friend requests, too) with regular Skype users may not work unless the regular Skype user is connecting with either the Skype for Windows desktop client or Skype for Mac.

Lync for Mac 2011 Video not Turned On • Click on the play button in the video area Garbled Video • Try maximizing the screen by selecting the Enter Full Screen button below the video window • Try pausing, and then resuming, the call (by clicking the pause and then resume buttons below the video window) Garbled Audio • Try pausing, and then resuming, the call (by clicking the pause and then resume buttons) iPad (iOS) Skype for Business app Certificate Error If you see the certficate error when signing into the Skype for Business iOS app: 'We can't verify the certificate from the server. Please contact your support team.'

HI Sir, I have downloaded the skype for busines from portal.office.c om - where i have access and I am working for company. Here my issue is while login to skype for business 2016. Here my issue is while login to skype for business 2016. Skype for Business/Lync Edge servers communicate with each other over Mutual Transport Layer Security (MTLS). When using MTLS connections the server originating a message and the server receiving it exchange certificates from mutually trusted Certificate Authorities.

You'll need to make your browser 'trust' this server. • Open this page on your iPad • D ownload this on your iPad • I nstall the profile at the prompt • T ap install again at the warning • Confirm install by tapping install a 3rd time.

• • • • • • This subreddit is meant for conversations about Skype for Business Server 2015, Skype for Business client, and legacy Lync/OCS implementations. If you need assistance with the consumer version of Skype, make sure to check out.

Rules: • All redditquette rules are enforced. • No direct sales posts allowed.

• Job postings are not allowed. Check out • Blogging Posts - Please be respectful when it comes to submitting multiple blogging posts. This is not a link dump and we encourage your involvement in the subreddit. My team has been experiencing this issue since Monday and nobody can figure it out.

Our office provides support for multiple companies, but we're all in the same office with laptops provided by our desktop support team. All other teams have working s4b programs except for my team (we'll call the company my team supports 'company X'), which consists of 5 people. Everything my team does is with credentials provided by company X which are identical to the credentials the actual employees get, but the work is done on a machine provided by my office (the company that provides the support). Here's what I know: • Skype does not work on any of my team's machines provided by our office when trying to sign in with company X's exchange credentials • I can sign in to s4b on my phone, home desktop, and Lync on my macbook just fine using my company X credentials, no issues • My work laptop still does not sign in using my company X credentials when I'm on my home network • When trying to sign in without using company X's VPN (how I usually sign on), I get 'You didn't get signed in. It might be your sign-in address or logon credentials, so try those again. If that doesn't work, contact your support team'. When using the VPN, I get 'there was a problem verifying the certificate from the server'.

• S4b stopped working on all of our machines on the same day, 6/13. • None of the actual employees of company X are having issues with s4b, just the support team in our office.

Any advice would be greatly appreciated. I've tried removing the SIP folders in appdata, removing crypto and credentials folders, removing all credentials out of the vault, reinstalling office, none of them worked. The only thing I can think of is that there's an expired certificate somewhere in the chain or my office pushed out some change through the domain that messed everything up, but that is a bit beyond my s4b/exchange troubleshooting knowledge.

As stated, it is hard to troubleshoot login issues without tearing thru client side logs. If all of this just stopped working on a specific day, then I'd go looking thru your change records of what was executed on that day. If you don't have those to view, I'd go into your client logs and start figuring out where it says you're failing the login.%userprofile% appdata local microsoft office 16.0 Lync Tracing and tear open the Lync-UccApi-0.UccApilog. As another suggestion, if you don't have the Lync/Skype debug tools installed on a server yet, go install it and find 'snooper.exe' and copy that locally to your laptop. Use snooper to open up the UccApilog and it will auto sort messages for you for easy viewing as opposed to 50mb+ of clear text in notepad++:P Hope this helps some. EDIT: it was the debug tools and not the resource kit that has snooper in it.

Beginning visual studio for mac: build cross-platform apps with xamarin and .net core. In here, make sure that you’ve selected the Target Runtime osx.10.12-x64 • Change the target location to another folder, so that we can distinguish between the Publish results for Windows and the results for macOS • Click Save • Now click Publish and that’s it! Publishing the applications to run on Windows Before we run the apps, we need to publish them, as you would do in production, to get a release build. • Do the same for the self-contained app Publishing for running on macOS If we want the framework-dependent app to run on macOS, we don’t have to do anything special, we can just use the publish results of the previous steps. However, if we want the self-contained app to run on anything other than Windows, we need to take additional steps: • In Visual Studio, right-click the project file of the self-contained app and click Edit Project to edit the project file • Now add a new Runtime Identifier to the file and save it, just as highlighted here: • Now right-click the project file again and click Publish • In the Publish overview, click the Settings link • This opens the Profile Settings popup that you see in the image below. For Windows, we can follow the same steps for both applications: • In Visual Studio, right-click the project file and click Publish, like in the image below • Then, you can pick a folder and click publish.