Deployment and Migration Scenarios with Microsoft Lync Server 2010

Lync will be released in the end of the year

There is a public announcement the 17th of Nov.

Some whitepapers and guides could be presented that date but that is not confirmed.

Upgrade migration from LCS

If you want to upgrade a LCS environment to Lync, you need to first do an upgrade on server and client to OCS 2007 and then upgrade to Lync.

If you don´t need a migration you can just uninstall LCS and than do a new installation of Lync.

Support of OS

  • Only Windows 2008 R2 is supported on server with Lync.

Support for virtualization

  • Fully support virtual servers on all roles

Difference between Standard (SE) and Enterprise Edition (EE)

  • SE                5000 client concurrent users
  • EE                10000 concurrent users

Installation procedure

  1. Schema upgrade and domain upgrade
  2. Topology  setup
    1. Need SQL server. Standard Edition can use SQL express

                                                               i.      It is the holder of the topology XML

  1. Install Standard Edition or a Enterprise pool
  2. Mediation server if connection to PBX

PBX Interoperability

  • List on vendors on Microsoft.com
  • Contact the vendors and explain what you want to do

Bandwidth management= CAC

  • Group sites with subnets
  • Region based configuration
  • You may setup how much bandwidth it uses per feature
  • Rules can be setup between sites (links)
  • CAC is static and doesn´t learn how the network is.
  • Single central server (CAC)

Migrate mediation server

  • Lync server support för PBX
  • Lync client can use both ocs and Lync
  • Migrate users first than the mediation

Datacenter management

  • A new site in i each

—————————————————————————————

Enable Secure Access using Forefront UAG Service Pack 1

New in SP1

  • Simplified DA Deployment
  • One-time-Password support for DA (must have a dedicated CA. Could be a sub-ordinate CA in present CA infrastructure)
    • Integrated securID agent into DA scenario
    • 3rd party supports using nRadius (OATH compliant)
    • Comprehensive policy management
    • Integrated NAP
    • Use a dedicated CA
      • Best practice
      • Use present Root CA and have seperate subordinate CAs for NAP and OTP
  • Monitoring Direct Access out of the box
    • Integrated into UAG web Monitor
    • Integrated SCOM style
    • Storage is SQL based

 

ADFSv2 integration

Not able to use both ADFSv2 and ADFSv2 with UAG in the same environment.

So you need to remove present ADFS if you have before you install UAG with integrated ADFS

Deployment Multi Entry points

Included in release 2011 H1 (UAG SPI UP1)

——————————————————————————————-

Failover clustering and Hyper-V: Planning your Highly-Available virtualization environment

Host clustering

  • Cluster service runs inside physical host
  • Live migration
  • Quick migration

Guest clustering

  • Cluster runs inside a VM
  • Is application aware
  • Only iSCSI

Guest and host clustering can be at the same time. It is the optimal solution that offers the most flexibility and protection.

If you have question of the impact of virtualized SQL server on Hyper-V., the SQL team have published a Whitepaper of the result and impact. Read it!

This is all supported on Windows server 2008 R2

Powershell support

  • Improved Manageability
  • Hyper-V integration
  • Replaces cluster.exe as the CLI tool

You can use Powershell to create a entire cluster

Don´t do an image after you installed the cluster feature. It will not work. There are some dependencies of Mac address that is created when installing the feature.

Do the image before and script the installation of clustering feature.

Cluster share volumes

  • Live migration with CSV. No dismounted and remounting
  • ARP redirects client to new node (sends an arp to the router)

AD consideration

  • Nodes in the same domain
  • Need accessible writeable DC
  • DCs can be run on nodes, but use 2+ nodes
  • Don´t install DC on parent partition or no other features
  • Do not put all your DCs on clustered VMs
    • DC i needed for the cluster service

 Network considerations

Minimum of two networks:

  •     Internal and live migration
  •     Public and Guest Management

Use network prioritizing to configure your network

Best solution: 5 NIC

AntiAffinityClassNames

  • Enabled VM Distribution
  • Failover behavior on large clusters: KB299631

Root Memory reserve(d)

Difference between 2008 R2 RTM and 2008 R2 SP1

In Sp1 you don´t need to configure.

Dynamic memory SP1

Memory Priority Value is configurable per VM

Where to changes

Always use Failover Cluster manager or SCVMM when doing changes

Hyper-V Manager is not cluster aware

Storage Migrations

SCVMM enabled Quick Storage Migration. Not live migration. You will have some downtime.