Showing posts with label Lync Server 2010. Show all posts
Showing posts with label Lync Server 2010. Show all posts

Tuesday, December 13, 2011

Microsoft Begins Shipping the Lync Mobile Client

For those of us in the Lync world, the release of a Lync client for mobile phones has been long awaited. Although Microsoft released Lync 2010 to the market over a year ago, there has been no mobile client up till now. The lack of a mobile client has been a point some Microsoft competitors have been quick to jump on. But starting earlier this week, the client is slowly rolling out on 5 key platforms (Windows phone, iPhone, iPad, Android and Nokia Symbian).  Thus far, Microsoft has only released Lync for the Windows Phone – the others are shown as ‘coming soon’ on the Mobile Clients for Microsoft Lync web page.

Microsoft cites 4 key features of the new Lync mobile client:

  • Join conferences with a single touch - no access code or pin number is required.
  • Stay connected, while controlling your availability – you can see who's available at a glance and connect over IM, email or a call. You can also set your own status and notification settings so you can stay in touch while protecting your "off-work" time.
  • Communicate with others using a single, consistent identity. The Call-via-work feature allows outbound calls using your Enterprise Voice number, making it easier for others to recognize calls from the Lync mobile client.
  • Connect with confidence through channel encryption, transport layer security (TLS) support, and perimeter/internal network protection that help safeguard your communications.

To the dismay of some, there is no VOIP client – all phone calls to/from the device have to be made over the cellular network, but Call from work and One Number reach do make that a little less expensive.  It appears that the Call via Work feature will not be shipped with Android.

Like so many things Microsoft, the client is not something you can just load from the relevant store and have it work – you do need some work on your Lync implementation and need to install the latest cumulative updates (CU4 in particular) to get the necessary services up and running that support the motile client.

These requirements are spelt out in yet another TechNet article: http://technet.microsoft.com/en-us/library/hh690988.aspx. You will need to do some work against your DNS servers to ensure automatic discovery and sign-in works properly. Although this is pretty straightforward, it is work that needs to be planned for and carried out. If you are an Office 365 user and Microsoft is managing your DNS, the work appears to be already done. I host DNS externally to Office 365 but it took me just a few minutes to adjust my DNS settings as needed. You also have to install and configure the mobility service (in CU4), and update your voice policy to support use of the mobile client.

One important gotcha that might be easy to overlook: You need to include certain (new and additional) SAN entries on your key servers. In particular you need to adjust SAN entries on the certificates in your Director pool, your Front End Pool and the reverse proxy. If you use public certificates for any of these systems, you may have to buy an updated certificate for the RP system. 

In closing, it’s worth noting that the mobile client does NOT provide 100% of the features of the Lync desktop client.  You can see a good comparison of the various clients at: http://technet.microsoft.com/en-us/library/hh691004.aspx. Some features that are NOT provided by the mobile client (as documented in TechNet) include:

  • Caching multiple users account information on the same device
  • Modify Contacts List
  • Tag contacts for status change alerts
  • Control privacy relationships
  • Log IM conversations in Exchange/Outlook
  • Use dial-in audio conferencing
  • Transfer a call
  • Call a response group
  • Support E911
  • Client side IM archiving and client side recording

I can’t wait to get my hands on the client and to use it against my Office 365 account (tfl@reskit.onmicrosoft.com). From all I’ve heard from those who have the client – it does what it says it does and thus far appears stable and resilient. I look forward to using the client - As an iPhone user, I will have to patient. After all – I’ve been waiting 14 months or so for this client a few more days wait is not the end of the world! It will make a nice Christmas present!

Wednesday, May 25, 2011

Lync Resource Kit Server Administration Chapter Published by Microsoft

I just got email that Microsoft has published another Lync Resource Kit chapter or your edification. This chapter, Server Administration, was written by Indranil Dutta and Jens Trier Rasmussen. I was, with others, one of the technical reviewers. You can either download just this chapter, or download all 8 of the published chapter from here.

There are three key aspects to this chapter. First, the chapter covers Lync’s Central Management Store, including the data stored in the CMS, how replication of CMS occurs, and how to manage the CMS. The second section looks at the Lync Server Control Panel and how it works. The final section talks about Role Based Access Control and how to create custom RBAC scopes.

IN looking at it, one thing kind of missing is  Management using PowerShell – perhaps an introduction to PowerShell’s object model inside Lync. RBAC is based on PowerShell, so using RBAC and creating custom roles is covered. With over 600 cmdlets, I would have preferred some more details in the Server Administration chapter. Call me fussy!

The writing in the chapter is good, and it’s illustrated by some excellent diagrams. This chapter is 24 pages long – and well worth a read if you are architecting or implementing Lync Server.

Monday, May 16, 2011

Lync Server 2010 Resource Kit

One of the neat aspects of the Lync Server 2010 Resource is that it’s being published online, chapter by chapter as each chapter is finished. I suspect there will eventually be a physical book, in the meantime, Lync admins can get the deep technical and management info direct from the web.

Today, the latest chapter, Troubleshooting Lync, was released. To get this and the other released chapters, navigate to http://www.microsoft.com/downloads/en/details.aspx?FamilyID=8c64a1e1-f0b3-479c-a265-e480875c61d8&displaylang=en and download from there. You can download each of the 7 chapters published so one by one, or get a 12MB ZIP file with all the chapters.

If you are using Lync, or considering it, these downloads are mandatory reading.

Monday, February 14, 2011

Lync PowerShell Blog–A Challenge For You!

The folks behind the Lync Server 2010 PowerShell blog have another fun wheeze on: The PowerShell Challenge. The idea of this contest is simple: each week, the Blog team present 4 things and you need to figure out which is The Odd One Out (or as they put it, One Of These Things Is Not Like The Others).  You can read up on the rules here.

The PowerShell challenge has been going for a few weeks, and there are still 4 folks with perfect scores (naturally, I am one of those). But you can still join in the fun and compete in this week’s contest. Who knows, the top runners might have a bad week and you could end up winning the competition. But it’s not whether you win or lose – I am finding this contest very useful in helping me to get better familiar with the Cmdlets.

To see a summary of the past challenges (and answers), plus this weeks’ challenge, see: http://blogs.technet.com/b/csps/p/otherschallengearchive.aspx.

 

Saturday, December 11, 2010

Lync Server and PowerShell–a new forum

Over at Www.PowerShell.Com, there’s a new forum: PowerShell for Microsoft Lync Server. This is a forum where you can ask any and all your questions around using PowerShell and Lync Server 2010. As you may know, Lync Server 2010 follows in the foot steps of Exchange and other MS server applications in offering a complete PowerShell Admin experience.

For those of you who are getting into Lync, your basic administration can be done from the Lync Server Control Panel (a sliver light application that replaced the MMC console used in Office Communications Server and earlier versions of what we now call Lync. But for heavy duty admin, PowerShell, and the 543 cmdlets in the Lync Module are going to be your focus. I teach Lync in the UK and know that many of the admins I’ve taught thus far are going to struggle with PowerShell as many of them have little or no PowerShell background (with too many still living in the land where administration must mean doing it at the GUI).

So if you are getting into Lync, and are having trouble doing a specific thing – come on down. If you are a seasoned OCS admin, and a bit unsure on PowerShell – definitely come on over and ask your questions.

Tuesday, November 23, 2010

Microsoft Releases Lync Documentation

Continuing the tradition started with OCS, the Microsoft UC team have released a mountain of documentation for Lync 2010. As with OCS, there’s both a set of detailed documents, and a .CHM (complied HTML Help file) with all the documents in one place. Even better, you can get the detailed documents as downloadable .DOC files and as web documents you can read on line. A nice job!
To get to the detailed documents, you can go to this page in TechNet: http://technet.microsoft.com/en-us/library/gg398616.aspx. The .CHM file is at: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=9720c3f1-ddd4-426b-b98a-f1205561ce00&displaylang=en.
The UC team is to be congratulated for producing such comprehensive and accessible information. If only ALL software teams were so good!

Sunday, September 26, 2010

Lync Server 2010 and Virtualisation

With the Lync Server 2010 RC available, the details of what it will take to run Lync in production are emerging. One really nice change from OCS 2007 is that Lync is now fully supported when virtualised. With OCS 2007, only some roles were supported, although anecdotal evidence suggested OCS would work OK virtualised – the issue was more with the client.

This means that all major workloads, including presence, IM, conferencing and Enterprise Voice can be run in a virtual environment. This includes Standard and Enterprise editions. There are some restrictions on virtualisation platforms though, only VMware and Hyper-V are supported. For both virtualisation platforms, only Serve 2008 R2 is supported. And for Hyper-V, you must also run the host as Server 2008 R2.  Microsoft will support virtualisations using SE to support up to around 2000 users and Enterprise Edition pools supporting up to 40k users. Edge servers can also be virtualised.

For Hype-V at least, the hosting requirements will significant: 8 Core 2.27Ghz processors with 16GB+ of ram and fast disks (particularly for your back end SQL servers). With virtualisation, your overall consolidation ratio is around 3:1 A suitably speced out host machine will support around 4 Front End servers, or 4 A/V Conferencing Servers for a user base of up to 40k users. For full functionality, you’d also want at least Directors (2 Director roles can be co-located on a single Hyper-V host) and two Edge servers (also co-located on a single VM host). You can also co-locate your Monitoring and Archiving server roles.

You can also virtualise your SQL Server back end database, but in a large Enterprise environment, you may just want to keep your back end cluster as a pair of real servers. You can of course, co-locate two SQL Server VMs on a single host to serve as your fail over back end cluster. Although this only provides resilience in the case the guest OS or applications go down!

The total level of consolidation in such a scenairo would be from around 19 servers, down to around 6 or 7 large hosts machines. You’d then need to consider your Mediation Server requirements! To some degree, the number of mediation servers required will be based on your requirements (how many PSTN ingress/egress locations do you have and what sort of gateways are  you using). With Lync 2010’s Media Bypass facilities (and suitable PSTN gateways!) you could co-locate up to around 4 Mediation Servers on a single host. My guess, although I do not have the means to test it) is that you could probably support more Mediation Servers on a given host, depending on the Gateway architecture