

- MICROSOFT LYNC FOR MAC FORUM INSTALL
- MICROSOFT LYNC FOR MAC FORUM PC
- MICROSOFT LYNC FOR MAC FORUM PLUS
The SOC Briefing for May 20th - Updates Here we Come! Security.I do notice that when I change the server settings back to Automatic, that the Connect using TLS doesn't go back to TCP. I have tried with adding the servers :443 like recommended on the MS page, but this doesn't help either. Network team have made sure that all FW and port settings are OK, and there is nothing here that is blocking the use. Still having the same issue on my MacBook ONLY when on the corporate network. Deleted what I could find of the folders described above. Anyone else have problems with this on Mac side? He's done all the same steps to my account that he did to his. Our SysAdmin has a Lync server running and he's able to login to Lync on his PC. Here is a collection of some pages that cover them.I'm the first Mac on our company's network and I'm trying to use Microsoft Lync, but when I try to login it says that "Sign In failed because the services is not available or you may not be connected to the Internet". There are tons of functional additions/improvements for the Mac clients that should remove most of the barriers previous clients had. Hearing what other folks are thinking about it is really useful! Wasn't sure if this could apply to the OP as well.Īnything that keeps the thread going and is informative is good IMO.

My apologies to the OP if this appears to be a threadjack.

Is there more parity between the two platforms with the release of Lync? I believe last time I looked the Mac clients couldn't start meetings (I have to double check that). Our main goal is peer to peer video conferencing and also being able to start a meeting and desktop share.
MICROSOFT LYNC FOR MAC FORUM PC
Our shop is really interested in OCS/Lync but our environment is a mix of PC and Mac and last time we looked the Mac client lacked alot of the features that the PC client has. Personally, I love it because I only have to interrupt my workflow in a very modest fashion to listen to a voice mail via my Outlook client.Īnd with Exchange 2010 UM we transcribe the beginning of every voicemail to text so you don't even have to listen to it if you don't want to.
MICROSOFT LYNC FOR MAC FORUM PLUS
Plus they may be some cultural issues from folks who will freak out if you take the phone away. I don't really see the point of the desk phone for most folks either, but we provide services for people that we don't provide IT services for. We were seeing the potential for voicemail/email convergence as a big cost saver too - particularly if there is litigation where discovery of voicemail becomes a relevant. I'm sure that we spend a fortune as well. I'll have to look at the audioconferencing implications. I'm a solid volunteer for getting rid of my desk phone. We will then rollout additional features as we can. We're primarily going with Lync because, operationally, it will save us a huge amount of money once the users begin adopting it for audioconferencing, as opposed to using a third party (which we spend a loooot of money on). As you state, we are sharepoint heavy, and have a pretty significant MS stack. We will be keeping our Avaya PBX for the near term, but Lync has a lot of compelling features. We've already done most of the architectural work. We have a small OCS foorprint (PoC more than anything). Thoughts anyone? What kind of icebergs should I be looking for? Are the infrastructure advantages worth the hell of dealing with Outlook or even OCS plugins? I really don't want the desktop team besieging my office with pitchforks and torches! my spider-sense activates because there is this dizzying array of products, licenses and add-ons that seem to do anything and everything. Soft-phone functionality seems more robust. The infrastructure seems more robust and enterprise-y. On the Cisco side, it seems like they have a strong client that doesn't integrate deeply into the client application stack. Also, many of the fancy features require fancy client licensing as well. On the flip side, it seems like soft-phone functionality is weak unless you are going to use OCS/Lync as your PBX. It seems to me that the Microsoft client is stronger if you're a SharePoint (esp SharePoint 2010) shop, and see a value in pulling communications into the Office suite and SharePoint.
MICROSOFT LYNC FOR MAC FORUM INSTALL
The level of marketing nonsense surrounding these technologies is absolutely amazing, and it is difficult to separate fantasy (like the CUCIMOC Cisco client that you install inside the Microsoft IM client) from reality. the idea is to start rolling out Exchange 2010 and VoIP (with Cisco Call Manager for call contrl) together and link the system to our existing room based videoconferencing system. We're in the process of planning to deploy unified communications technology. Does anyone out there have experience with either of these products in a large enterprise or multi-tenant environment?
