.

MCITP: Microsoft Lync Server 2010 Administrator

I passed the Lync 70-665 exam today so apart from the paperwork, I am now an MCITP:Microsoft Lync Server 2010 Administrator. 


I don't intend to break the NDA, so enough to say, prepare for a lot of reading.

As I studied, I created a guide to the various subject areas, available here and used Microsoft Lync Server 2010 Unleashed book.

Unofficial Study Guide for Exam 70-665: PRO: Microsoft Lync Server 2010, Administrator


This will be a living post as I seek out information covering the topics of the Lync Administrator exam, 70-665.


Latest update: 
  • Phone Usage Records
  • Bandwidth requirements
  • E911
  • Private Lines
  • CAC
  • Media Bypass
  • Plan for DR - Bare Metal Restore
  • Monitoring objective
  • Designing Sites and Pools

Skills Being Measured This exam measures your ability to accomplish the technical tasks listed below. The percentages indicate the relative weight of each major topic area on the exam.



Designing a Topology for Lync Server 2010 (25 percent)

Designing a Conferencing and Enterprise Voice Infrastructure (25 percent)

  • Design a dial plan.
  • Design for voice routing.
    • This objective may include but is not limited to: 
      • PSTN breakout points; 
      • PBX phones; 
      • trunk routing; media gateway; 
      • least cost/alternate routing
  • Define voice policies.
    • This objective may include but is not limited to: 
  • Define conference policies.
    • This objective may include but is not limited to: 
      • controlling usage; 
      • system capacity considerations
  • Design for Response Group Services (RGS).
    • This objective may include but is not limited to: 
      • workflow; contact objects; 
      • agents and queues; 
      • groups
  • Design for emergency services implementation.
    • This objective may include but is not limited to: 
      • Enhanced 911 (E911)
      • SIP trunk emergency service providers; 
      • location policies; 
      • Location Information Service (LIS) wiremap; 
      • analyze network mapping
  • Plan for devices.
    • This objective may include but is not limited to: 
      • considerations for different endpoint types, including analog devices, common area phones, and standalone devices; 
      • DNS and DHCP requirements
Planning for External Dependencies and Migration (24 percent)

    • This objective may include but is not limited to: 
    • This objective may include but is not limited to: 
      • public and private certificates; 
      • Subject Alternate Names (SANs)
  • Plan for Exchange Unified Messaging (UM).
    • This objective may include but is not limited to: 
      • specify requirements to integrate Exchange UM with Lync Server 2010; 
      • Exchange UM dependencies; 
      • design Exchange UM dial plans
  • Plan for migration.
    • This objective may include but is not limited to: 
      • configuration requirements; 
      • side-by-side migration; 
      • Edge migration; 
      • meeting considerations; 
      • client limitation considerations
Planning for High Availability and Business Continuity (26 percent)

  • Plan for high availability.
    • This objective may include but is not limited to: 
      • choosing Survivable Branch Appliance (SBA) vs. Standard vs. Enterprise in high availability; 
      • number of servers and pools required; 
      • server redundancy
  • Plan for load balancing.
    • This objective may include but is not limited to: 
      • DNS; 
      • Hardware Load Balancing (HLB)
  • Plan for disaster recovery.
    • This objective may include but is not limited to: 
  • Plan for system monitoring.
    • This objective may include but is not limited to: 
      • synthetic transactions
      • identifying components to monitor; 
      • monitoring technologies such as Microsoft System Center Operations Manager
  • Plan for site resiliency.
    • This objective may include but is not limited to: 
      • SBA; 
      • backup registrar

Lync Phone Usage Records


Lync uses Phone Usage Records to define calling privileges for Enterprise Voice users. Phone Usage Records are simply labels, which can be given descriptive names such as 'Local Calls' or 'Calls to Mobile' or 'International Calls'. One or more Phone Usage Records are then added to an Enterprise Voice Policy which can be applied to users. The Phone Usage Records are also associated with outbound call routes. This is the 'glue' that applies the call privileges or restrictions to a user. The collection of Phone Usage Records in the Voice Policy determines all the authorised routes allowed to a user. When a user places a call, Lync Server matches the dialed number with a route in the authorized route list. If a matching route is found, the call is made. If no matching route is found, the call is not made.

The graphic below shows a simple example. We have two Enterprise Voice users. Mr Big is the manager and is allowed to make calls to National, Mobile and International numbers. Joe Bloggs is not to be allowed to make international calls. We already have outbound routes to National, Mobile and International (the examples shows Irish numbering where all national calls begin with a single 0, mobiles begin with 08 and international calls begin with 00). We create two Enterprise Voice Policy records called Manager and Staff. We assign these to Mr Big and Joe as appropriate. The Manager policy has Phone Usage Records called 'National', 'Mobile' and 'International', while the Staff policy only has 'National' and 'Mobile' Phone Usage records.

When either user makes a 'National' call, the Phone Usage Record of the 'National' route is compared against the list of Phone Usage Records assigned to the user, through the Voice Policy. In this case, both users will have a match and the call is allowed. When Mr Big makes an International call, again the Phone Usage Record for the route appears in his list of Phone Usage assignments and the call proceeds. On the other hand when Joe attempts an International call, the usage record on the route ('International') does not appear on his list of Phone Usage Records and the call is barred.

Generally, Phone Usage Records are created for two reasons – to restrict calls because of cost (e.g. International calls) or to restrict calls to inappropriate numbers (e.g. premium content services). In the example shown, the user Joe either needs to make calls to mobile (cell) numbers or the call cost to these are the same as calls to National numbers and therefore there is no point in restricting the calls. However, premium calls are generally not appropriate for business calls and are therefore restricted. This is shown in the graphic by the fact that the 'Premium' phone usage record is not applied to any Voice Policy – neither user could make Premium calls.

More Lync Resource Kit chapters available

Resource Kit Book Chapters:

Microsoft Lync 2010 Adoption and Training Kit Released

Microsoft have released a Lync Adoption and Training kit.

The kit provides:
  • A workbook that provides step-by-step guidance for each phase of the rollout and adoption process
  • Adoption and training resources, such as primers, email templates, and templates for a custom Lync 2010 intranet site to help organizations successfully roll out Lync
  • Modular, reusable, rebrandable, and in most cases, customizable user education and training materials, including frequently asked questions, Quick Start guides, how-to videos, Work Smart guides, and training videos
  • Buzzworthy applications such as IM an Expert and learning tools such as the Lync How-to that you can use to generate user excitement and drive the adoption of Lync

Hardware virtualisation support for Exchange UM Announced

Microsoft have announced support for the Exchange 2010 SP1 Unified Messaging role on hardware virtualisation. The Technet blog article is here and the official Exchange 2010 system requirements are available here.

Specifically, the UM role has the following requirements -
  • Four virtual processors are required for the virtual machine. Memory should be sized using standard best practices guidance.
  • Four physical processor cores are available for use at all times by each Unified Messaging role virtual machine. This requirement means that no processor oversubscription can be in use. This requirement affects the ability of the Unified Messaging role virtual machine to utilize physical processor resources.

Lync Server Troubleshooting

When you are looking at a system that isn't working and have a customer waiting for an update it's good to have a plan. Stale Hansen has given his thoughts on how to go about troubleshooting a Lync issue