My primary use case for this solution is for internal meetings and meetings with customers.
CEO at Shivaami Cloud Services Pvt. Ltd.
It is a user-friendly solution that enables us to manage international meetings with ease.
Pros and Cons
- "We chose Skype for Business after other colleagues suggested that we give it a try. It has served us well."
- "We really like the screen sharing tool. The user experience is smooth, and user-friendly."
- "I venture to say that 30% of the people using this solution at our company have had issues with stability, due to the volatility and crashes."
- "Sometimes the connection crashes, which is understandable if you are traveling. But, it would be nice if this could be stabilized somehow."
What is our primary use case?
What is most valuable?
I find the international dialing is the best feature.
What needs improvement?
Skype for Business needs to improve their support for Android cellphones. Sometimes the connection crashes, which is understandable if you are traveling. But, it would be nice if this could be stabilized somehow.
Additionally, I think there is a need to improve the chat-for-groups feature. It is not perfected yet.
For how long have I used the solution?
One to three years.
Buyer's Guide
Skype for Business
December 2024
Learn what your peers think about Skype for Business. Get advice and tips from experienced pros sharing their opinions. Updated: December 2024.
831,265 professionals have used our research since 2012.
What do I think about the stability of the solution?
I venture to say that 30% of the people using this solution at our company have had issues with stability, due to the volatility and crashes.
How are customer service and support?
I do not have experience with tech support.
Which solution did I use previously and why did I switch?
We used to use G Suite Hangout as a similar solution. But, prior to that, we were not using anything else in this domain. We chose Skype for Business after other colleagues suggested that we give it a try. It has served us well.
What's my experience with pricing, setup cost, and licensing?
It may be considered costly for certain markets, such as in India.
What other advice do I have?
We really like the screen sharing tool. The user experience is smooth, and user-friendly.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Automation Systems Developer at a tech consulting company with 1-10 employees
Easy video conferencing with a simple setup and capable of saving conversations
Pros and Cons
- "I like the fact that it opens up your video conferencing, and, in many cases, the audio at the same time."
- "The integration with Outlook could be improved."
What is our primary use case?
Recently, we all went remote, so we needed a way to implement virtual meetings on a large scale and we utilize Skype for Business for these purposes. It might have a lot to do with the response to COVID and getting more people connected for remote access.
What is most valuable?
The solution connects to meetings pretty well.
I like the fact that it opens up your video conferencing, and, in many cases, the audio at the same time.
It's very useful that the solution can save conversations.
What needs improvement?
The implementation could be improved.
In my case, I don't necessarily pick up audio, so I have to dial in. I have two connections. One is a visual and one is strictly for audio calls. Some other users aren't experiencing that issue. It's inconsistent and I'm not sure why. I also can't say with certainty that this is a Skype problem or if something else is causing the discrepancy.
There seems to be some sort of setting whereby it pretty much keeps instant messenger open all the time. I don't know what the settings are, or if this can be switched off. I believe there's an integration with that, where it assumes a certain status. I haven't had a chance to manually change it or to look into how to adjust it.
The integration with Outlook could be improved.
There could be more opportunities for setting up your current status.
The solution feels like it's pretty bare-bones. There could be some additional features added, perhaps on the statuses or something of that nature because as it stands now, it's pretty sparse. I have heard that they're going to be introducing some features pretty soon. I hope that's the case.
For how long have I used the solution?
I've personally used Skype itself for years. However, in terms of utilizing Skype for Business, I've only been using the solution for the last month, or, more accurately, about three weeks.
What do I think about the stability of the solution?
The solution seems to be pretty stable and is just as stable in the business version as the regular version. I haven't had any issues whatsoever with crashes or glitches. However, it does feel like it's pretty bare-bones.
What do I think about the scalability of the solution?
The solution is pretty scalable. You can use it across the company, and certainly within IT. Since everybody's working remotely now, with COVID-19, I think it scales quite well.
Even when you add people, it's still easy to manage many multiples people in a single meeting
I don't know how many people in our company are actually on it at this point. I imagine it's quite a few, however, I'm not sure of which departments that are using it, or if it's been deployed across the board.
How are customer service and technical support?
I've logged into technical support a few times on the Microsoft store. They used to actually go through edX at one point. They may have their own portal now. I've looked at it for various products such as SQL, Visual Source Code, etc. and not just for Skype, so I can navigate it pretty well. I've been helped there. They do have paths to different types of certifications and stuff. I have not gone through any of that myself, however.
How was the initial setup?
The initial setup is straightforward. It's not complex at all.
What other advice do I have?
We're just a customer.
I'd advise other organizations that the implementation is pretty smooth as far as installations go, so they shouldn't be afraid to give it a try. Using it is very straightforward, and it just sits on your desktop as an icon, so it's easy to access when you need it.
Overall, I'd rate the solution eight out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Skype for Business
December 2024
Learn what your peers think about Skype for Business. Get advice and tips from experienced pros sharing their opinions. Updated: December 2024.
831,265 professionals have used our research since 2012.
Computer Maintenance Technician at GTP Sistemas S.L at GTP Sistemas S.L
Although seemingly obvious, I would note that the call quality is excellent.
What is our primary use case?
- Firstly, it is an innovative and even more profitable way of communicating. Also, the product offers a very professional image, which is very useful to the organization. Thanks to the interface, quality, design and easy handling, it allows for establishing a better relationship.
- Secondly, in terms of conversations whether via voice or video call, Skype for Bussiness meets the necessary criteria and with respect to the costs, it is profitable, plus it can be used in various equipment and operating systems which is another advantage.
How has it helped my organization?
Skype for Business has improved the communication system in my organization. It is not just a mere implementation; it is something that will undoubtedly influence the productive system likewise, especially in a company where operations are relatively small.
Despite having few members, the use of this product strengthens the communication links and not only internally, it has also been used with some suppliers, partners, and friends, which has been a pleasant experience.
What is most valuable?
One of the most useful functions has been its use for calls. Although seeming obvious, it should be noted that the quality I would say is excellent, and the plans offered by the product are superb, also, the image represents the product strength of my organization and without a doubt, it is something innovative.
What needs improvement?
Specifically in the service area: Since my organization is in charge of repair and maintenance service of computer equipment, and also works internally in communication with members who bring about growth in the company, to include any functionality would be a service that transmits data stored in the cloud, in the form that can be saved, and also to send and receive useful files.
For how long have I used the solution?
One to three years.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Senior Voice and Network Manager
While it makes troubleshooting a little easier, our users have struggle with product adoption
Pros and Cons
- "We like the easy provisioning of Skype for Business Conferencing."
- "We like the tools our administrator can use to identify which calls had quality issues and why. This makes troubleshooting our user experience somewhat easier."
- "We would like to better customize our instructions within the Outlook plugin/invite, but we are unable to do so."
- "We overcame the audio quality issues by asking users to use the 'Call Me' feature with their desk phone."
What is our primary use case?
Skype for Business and PSTN Conferencing. Our users are using this add-on license to perform internal and external web and audio conferences for between two and 200 users.
What is most valuable?
We like the easy provisioning of Skype for Business Conferencing. Also, we like the tools our administrator can use to identify which calls had quality issues and why. This makes troubleshooting our user experience somewhat easier.
What needs improvement?
- We overcame the audio quality issues by asking users to use the 'Call Me' feature with their desk phone.
- We would like to better customize our instructions within the Outlook plugin/invite, but we are unable to do so.
- Our user base has struggled for adoption, as using Skype audio is not a very consistent experience due to the diverse networks that they are on (home office, corporate office, and branch office networks).
For how long have I used the solution?
Less than one year.
What was our ROI?
We have been able to save money by moving our conferencing solution to Skype for Business Conferencing.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Info Sec Consultant at Size 41 Digital
In one of two companies, I was introduced to it as, "problematic." Now, having used it for months, multiple times a day for video, voice and chat, I never had a problem with it.
Enterprise voice in the cloud
I've used Skype Business (name change from Lync) in two companies. In one of them I was introduced to it as, "problematic." Now, having used it for months, multiple times a day for video, voice and chat, I never had a problem with it.
Voice calls - great quality if it was with someone in the same building or half way across the globe. No fuzzing or dropping.
Video calls - same. Great quality. No big drain on the computer so I could do other things. Again, good quality for the same building or globally.
Chat - what to say here apart from, it worked. Chat is a nice feature if you want to keep a history of messages.
(source: Skype.com)
Meetings - we managed to get +10 people, all from various locations, on different systems, using varying bandwidths, some connecting via Skype/Skype for business/mobiles, landlines. Only 1 person had a problem and that was due to their AD FS set up. We had video, audio, and chat. We transferred files. Some of us switched to muted mics just to listen....
Some people have had sign on issues but I think that may be more to do with internal set up because my experience hasn't included this.
Security and features that I used/like:
Skype For Business traffic is encrypted using TLS
You get archiving of messages
P2P file transfers
IM and conferencing
HD 1080p available depending on plan
Ability to have a presenter for training or to chair meetings
You can record content
Meetings can be scheduled via Outlook
The thing I want from any app is this: it needs to deliver. For me, Skype Business did. Does it take a bit of work to integrate into systems? Well, I've yet to meet a bit of kit with more than three features that doesn't. Is it worth it? I believe so. Skype for business is convenient. It's one of those things that's there, you use it, you forget about it - we're all happy. (or, at least, I was)
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Senior Consultant at Unify Square
How Much do I Have to Spend to Bring Microsoft Lync to My Company?
Disclaimer: the new version of Lync Server 2013, Skype for Business (SfB) Server 2015, has been released a few weeks ago. Licensing model is the same you had for Lync Server, with companies paying only Front End servers (i.e. the ones hosting user accounts and the core services for your infrastructure). SfB contains some new features, including support for Back End availability based on AlwaysOn groups. I will write a dedicated post asap.
The costs related to Microsoft Lync are something that I have talked about more than once but this is the first time I try to summarize information in a single document. I will limit my reflections to on-premises organizations, because as I am writing, Lync Online has no serious support for Enterprise Voice (i.e. VOIP) and this makes the Cloud version of Lync less flexible (and somewhat less interesting) than the more traditional, corporate deployment.
Your House, Your Rules
A starting point for all cost-related considerations is to understand which kind of service we need. Lync Server 2013 supports solutions ranging from a single, all-in-one box (with a mandatory Office Web Apps server required to share PowerPoint presentations) to hundreds of servers geographically dispersed. Let us list some parameters.
1. Number of Users
The first parameter you have to establish is the number of users that will require Lync services. Lync 2013 Standard Edition (S.E.), the aforementioned single box, is tested to support up to 5,000 users. Obviously, before you reach the 4,999th Lync enabled account, it could be a good idea to add a second Front End (the server that delivers core services to the users) or consider a Lync Enterprise Edition (E.E.) solution (more details on the two editions of Lync Server 2013 are explained in the next paragraph)
2. Required Availability
Second parameter will be the required level of availability. If we deem service continuity as required for any of the Lync features (especially if we are going to use Lync as our VOIP system), it should be in a high availability deployment. Lync pools support a feature called Pool Pairing, if we have at least a couple of Lync 2013 S.E. Front End servers in our infrastructure.
It is not an H.A. solution, but adds resiliency to the solution and it grants some degree of survivability to the voice users. In a paired pool, using a series of scripts, we are also able to fail-over and fail-back Lync users, restoring full functionality for them. A highly available solution requires the E.E. of Lync Server 2013.
Although there is no difference in the cost of licenses between S.E and E.E., to use Enterprise Edition you must have at least pool of three Front Ends connected to a separate SQL Server database (whereas S.E. uses a collocated SQL Server express at no additional cost).
A dedicated SQL infrastructure would also require a continuity solution, like clustering or mirroring. A well-known rule of thumb is if we need to provide high availability, then we need to remove any potential Single Point of Failure in the design.
Small, remote offices might also require (at least) voice survivability. For such a scenario, we have a dedicated implementation of Lync Server 2013, the Survivable Branch Appliances (SBA); these are less expensive than a full-blown Lync front-end server.
Note: SQL licensing for Lync Server 2013 has been deep dived in a good post from fellow MVP Thomas Poett in his blog Lync Server 2013: Lync Backend SQL Server Licensing http://lyncuc.blogspot.it/2014/01/lync-server-2013-lync-backend-sql.html
Availability requirements have an impact also on point 3 and 5 of this list.
3. Additional Servers
Lync requires some additional servers that have no additional cost from the Lync server licensing point of view but that add costs to acquire the base Operating System, hardware and so on.
- At least a Lync 2013 Edge server and a reverse proxy are required to make our services available to users outside our corporate network
- The only Lync role that requires a Lync server license is the Front End. All other additional roles like Mediation, Director and the aforementioned Edge are not subject to additional Lync server licensing
- At least an Office Web Apps server is required (as I said before) if PowerPoint sharing is required
- If we have high-availability requirements, the aforementioned services should be redundant through an edge pool, a highly-available reverse proxy and an Office Web Apps farm
- Lync integrate with Exchange Unified Messaging (UM) for services like voice mail. Exchange will have its own requirements and costs, but we have to keep them in mind if we require UM-related services
- A Lync 2013 E.E. pool requires a dedicated load balancer to balance certain type of traffic from the pool. This may be provided in the form of a physical or virtual appliance. Remembering SPoF, load balancer should also require an additional standby device for resiliency.
Note: Every Lync, Office Web Apps, SQL database and reverse proxy (if you are going to use a solution based on Windows Server) will require a license for the Operating System. You could use virtualization rights (Licensing for Virtual Environments https://www.microsoft.com/licensing/about-licensing/virtualization.aspx ) to keep costs down, but this aspect is to be included in the list
4. Client Licenses
For the following point, I will quote my free e-book Microsoft Lync Server 2013: Basic Administration (http://gallery.technet.microsoft.com/office/Lync-Server-2013-Basic-0a86824d )
Lync requires a CAL (Client Access License) for each user or machine that logs on to the server. CALs are of three types and each one is entitled to the use of a part of the features. Access to premium functionality is determined by adoption of the Standard CAL and then you have to add supplemental CALS, an Enterprise CAL and, for some additional features, a third license called Plus CAL (you may think to Enterprise CAL and Plus CAL as supplemental to the Standard CAL).
- Standard CAL: offers IM (Instant Messaging) and Presence, as well as PC-PC audio and video communication
- Enterprise CAL: the user can use multi-party Lync meetings (including Gallery View, a feature allowing up to five active video streams to be displayed at once)
- Plus CAL: enables enterprise voice capabilities
5. Infrastructure costs
There are a couple of entries in the bill of materials not directly related to Lync, but that we have to consider anyway:
- If we are going to use Lync Server 2013 as our telephony infrastructure, we will require access to the public telephony system. There are a lot of offers and solutions from hundreds of providers worldwide, so an exact cost estimation is tough to outline here. Granting high availability will raise the costs here too, adding mandatory backup lines in case of a failure on our provider’s side
- Lync Server 2013 has a high level of security by default and requires digital certificates to function. While our internal infrastructure can work with a corporate Certification Authority (C.A.), if we plan to make our Lync services available to Internet users (and to federate them with external Unified Communication systems) we have to use commercial certificates from a well-known, third party C.A. The cost here is not something to underestimate, because digital certificates will have to be SAN with many alternative names inside. In addition, the more SIP domains we will manage with our Lync deployment, the more names we will need in the certificates, and certificate fees are likely to ramp-up further.
Summarizing
Now, as it is easy to understand from the previous list, there is no right answer to the starting question. I will try to focus a few points:
1.High Availability will raise the costs, as usual
2.Using Lync Enterprise Voice will add license and infrastructure costs (as well as making H.A. almost mandatory)
3.The number of users and their level of access to Lync’s features will impact budget both for the deployment sizing and for the needed client licenses
4.The bulk part of the expenditure items related to a Lync deployment are not related to Lync server licensing, but to the other voices we have seen
Alessio Giombini contributed to this review.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Senior Specialist Unified Communications at a comms service provider with 10,001+ employees
RDS, Conferencing, VoIP and IM are the most valuable features
What is most valuable?
RDS, Conferencing, VoIP and IM are the most valuable features.
The Remote Desktop Sharing (RDS): It allows the users to share the desktop during a collaboration session. This feature gained popularity with our users whilst assisting others or working on a document together.
Conferencing: The ability to host conference calls with multiple users and bring in mobile users or other participants on the click of a button proved superior. All the users, now, have conferencing space which is readily available on a moments notice. Scheduled meetings which are tightly integrated with Microsoft Outlook means the users spend less time organizing meetings; where the users needed to call the support team to book boardrooms or book conferencing resources, this is all now integrated with Outlook. Anyone can now do this easily without engaging with support desks or engaging conferencing of the support teams.
VoIP: The ability to call any user without incurring any charges. Since introducing Microsoft Lync, our users can now call other Lync users in other organizations. Our system is equipped with PSTN calling, which has allowed the users to make calls to PSTN from anywhere in the world. It has introduced flexibility in the way we work. We, now, have our users working on the road all the time and they can call/be called on their Skype number anytime-anywhere.
How has it helped my organization?
We have used Microsoft products and this product is tightly integrated in the Microsoft ecosystem. Everyone in the company uses some aspect of this product.
What needs improvement?
Conferencing and interoperability need to be improved.
The biggest challenge has been seen in terms of interoperability with the other vendors. Microsoft chose standards which are freely available to minimize their costs. This decision means other vendors cannot integrate with Skype because they are using licensed technologies. Conferences on Microsoft cannot be joined to conferences from other vendors; no collaboration across technologies. That means gateways that allow Skype to communicate with other conferencing systems are required. These gateways usually come with limitations on what you can/can't do during a conference. Adding gateways means spending more money without a guarantee that everything will work as intended. It, also, complicates the solution to provide all services.
Luckily, there are vendors who have risen to fill this gap, vendors such as Pexip and Acano. Fortunately or unfortunately, Acano was acquired by Cisco. These gateways allow Microsoft Skype to communicate with any conferencing systems without losing any functionality.
For how long have I used the solution?
I have used this solution for eight years.
What do I think about the stability of the solution?
It has been stable.
What do I think about the scalability of the solution?
Scalability is good so far. We just added more servers to meet our needs.
How is customer service and technical support?
I would rate the technical support an eight out of 10.
How was the initial setup?
The setup was straightforward.
What's my experience with pricing, setup cost, and licensing?
Business Enterprise Voice provides the most pain for pricing.
What other advice do I have?
QoS and ample bandwidth are a must. Virtualization can be a source of pain, i.e., if it is not implemented as per the requirements from Microsoft.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Senior Consultant at Unify Square
Lync 2013 High Availability
High availability is something that companies do not take for granted, they take it as given (especially when we talk about telephony). While Lync 2010 did a good work on this critical aspect there were still some weak points on the architecture when there was the need for a really continuous service. For example the mechanism behind the “backup registrar” implementation was really a limit and, for the Enterprise Front End deployments, the need for a clustered SQL server Back End was a restriction and did not match with the requirements related (also) to some kind of disaster recovery plan.
Front End Pairing and new rules on licensing
Lync 2013 makes a step forward, building on what was valid in the previous logics and using whole new solutions were they are necessary. The first huge improvement is related to the so called “Front End pairing”. I have created a presentation about this solution some time ago (http://bit.ly/XKCBzd) anyway what you need to know is that now your Standard Edition Front Ends (or your Enterprise Edition pools) can be tied and you are able to failover and failback users completely from one Front End to the other one with a simple Shell command. Some limits apply (pairing is supported only on similar Front Ends, so Enterprise Edition and Standard Edition mixes are not supported) but the result is really what you wish you had some years ago. The licensing has changed accordingly so that now there is no difference in the costs of a Standard or Enterprise edition of Lync. Obviously we are not talking about a “free lunch” because an Enterprise Edition deployment has a suggested minimum of three servers and you have to add the cost of at least one SQL server license to the amount. Talking about the Lync databases, we have another hot topic
Back End mirroring
The Lync Back End server (basically a SQL database hosting some of the Lync configurations and data) is really less important than it was in the past (and that’s why we are able to pair the Front Ends) but it is still mandatory for an Enterprise configuration of Lync. The high availability for Lync 2013 Back End supports:
- SQL database mirroring
- SQL database clustering (starting with the August 2013 update
Mirroring is interesting because it allows for geographically dispersed deployments and requiring no shared storage between the different SQL “nodes”.
There is no support fo SQL AlwaysOn, at the moment.
Pools
As I said, solutions used in Lync 2010 that were effective have been used also in Lync 2013. This is the case of the Lync roles “pools” that are still used to grant the availability of features such as Lync Edge, Mediation and Director (the last one being now more optional than ever). However something has changed also in Lync pools implementation. Monitoring and Archiving are no longer independent roles but are collocated with the Front Ends, so you do not need to create dedicated pools. Persistent Chat Server (a new role, interesting in scenarios where you need to create persistent “rooms” for users IM conversations) must be pooled too if you want to grant its continuous accessibility.
Mediation Server Supporting Multiple Trunk and Inter-Trunk Routing
This last topic is not strictly related to the high availability but the aforementioned features (multiple trunks and inter-trunk routing) add a series of possibilities when planning an Enterprise Voice solution and the additional elasticity can be turned in a resiliency instrument. For example multiple trunks can be defined between a Mediation Server and a voice gateway or multiple Mediation Servers can route calls to the same gateway. Applying the right voice routing policies you will be able to create a series of solutions to use existing connections to the PSTN network or SIP trunks for continuity. Inter-Trunk routing enables the interconnection of two or more IP-PBX systems and this could be used as a way to add voice resiliency too.
Drawing a conclusion
The new features and possibilities we have seen here have a deep impact on the design of a Lync solution and on the perception of Lync as an enterprise ready solution. With the right design (and investment) every piece of the deployment can be made highly available and affordable, with a logic that is no more bound to a single site but can include also branch offices, disaster recovery sites and Cloud features too (hybrid deployments are part of the game now). You can stay assured that people will look with a growing interest to Lync now that the aforementioned possibilities are no longer only in the wish list.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Download our free Skype for Business Report and get advice and tips from experienced pros
sharing their opinions.
Updated: December 2024
Product Categories
Virtual MeetingsPopular Comparisons
TeamViewer
3CX Live Chat
Cisco Meeting Server
GoToMeeting
Cisco TelePresence
BlueJeans Meetings
Buyer's Guide
Download our free Skype for Business Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
Hi Alin.
As you easily understand, I can not answer because the information I have are under a NDA.
However things move always so fast that you will not have to wait too much for an official answer on this topic from Microsoft :-)