- #MICROSOFT LYNC 2013 64 BIT UPDATE#
- #MICROSOFT LYNC 2013 64 BIT LICENSE#
- #MICROSOFT LYNC 2013 64 BIT DOWNLOAD#
#MICROSOFT LYNC 2013 64 BIT UPDATE#
Let’s look at the Basic Client in a line up against my current Office 2013 O365 Pro Plus client with my E3 subscription which entitles me to run the Office 2013 suite.Īs I was halfway through writing this blog, Microsoft released an update allowing some nice additional features for the Basic Client that puts it on par with the full client for conferencing/meeting experience.
![microsoft lync 2013 64 bit microsoft lync 2013 64 bit](http://blog.schertz.name/wp-content/uploads/2014/08/image.png)
#MICROSOFT LYNC 2013 64 BIT DOWNLOAD#
Free in the terms of it’s a public Microsoft Download “ Drive away no more to pay”. The answer is the Lync 2013 Basic Client which offers a lot of feature sets minus some enterprise voice goodies, oh and by the way it’s FREE! I repeat again….FREE.
#MICROSOFT LYNC 2013 64 BIT LICENSE#
“So how do I take advantage of these features without worrying about my Office Suite licensing? I don’t want to go back to my license rep and fight with them over how I get to 2013 from my current arrangement just to get Lync rolled out to my end users”. So in short, it will do less with only a single participant stream and in lesser quality on same hardware and OS (ouch). A Lync 2010 client alongside a Lync 2013 client with same hardware and OS would present a media stream to the user, while the Lync 2013 client could do the full Also the conference/meeting experience will be hampered for the individual with only smaller selection of meeting modalities on offer at the lesser resolution. Well that isn’t entirely true, the Lync Server 2013 AVMCU does control rate matching and upscaling of video streams in a much better way on server 2013, but without the updated client endpoints, a 2010 client with none optimized video codec will never get the optimal stream it deserves like a 720p/ resolution for P2P or Lync Meeting video even if the client/network permits. I think the general miss conception is that the server should provide all the grunt and the client should just be the shell to display the media stream. The new Lync client isn’t just white in colour and offer a minimalistic design, it also adds a lot of additional functionality that is key to the user experience with 2013 backend servers pulling the strings. Well in some context this statement is right, but with the wrong approach. So I’m just expecting my users to use IM/P and potentially ‘ some‘ video.
![microsoft lync 2013 64 bit microsoft lync 2013 64 bit](https://i.stack.imgur.com/5CeJz.jpg)
“I’m not an enterprise voice user and I don’t know the adoption of Lync Meetings yet. Standing up a Lync Server 2013 environment and then rolling out the Lync 2010 client just makes me feel sad for all the end users, as they look at their ‘ new‘ client which too many others around the world would look like the ‘ old‘ client that we were happy to uninstall a few years ago.
![microsoft lync 2013 64 bit microsoft lync 2013 64 bit](https://static.filehorse.com/screenshots/office-and-business-tools/microsoft-office-2013-screenshot-02.png)
Whether this is because of the analysis needed to roll out the suite or they still are in an agreement that only allows them to Office 2010. This can be a project in itself and one that IT Admins aren’t always prepared to look at. I’ve had conversations with customers lately whom are looking to use Lync Server 2013 and currently don’t want to move their desktop SOE to Office 2013 suite with Lync 2013 Client.