Lync Ignite Setup Guide

Microsoft® Lync® Ignite Lab Setup Guide

DISCLAIMER

© 2013 Microsoft Corporation. All rights reserved.

Microsoft®, Active Directory®, Hyper-V™, Internet Explorer®, Lync™, PowerShell®, Silverlight®, SQL Server®, Visual C++®,

Windows®, and Windows Server® are either registered trademarks or trademarks of Microsoft Corporation in the United

States and/or other countries.

The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

THE CONTENTS OF THIS PACKAGE ARE FOR INFORMATIONAL AND TRAINING PURPOSES ONLY AND ARE PROVIDED "AS IS" WITHOUT WARRANTY OF

ANY KIND, WHETHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A

PARTICULAR PURPOSE, AND NON-INFRINGEMENT.

No part of the text or software included in this training package may be reproduced or transmitted in any form or by any

means, electronic or mechanical, including photocopying, recording, or any information storage and retrieval system,

without permission from Microsoft. Because Microsoft must respond to changing market conditions, it should not be

interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information

presented after the date of publication. The names of actual companies and products mentioned herein may be the

trademarks of their respective owners.

To obtain authorization for uses other than those specified above, please visit the Microsoft Copyright Permissions Web

page at http://www.microsoft.com/about/legal/permissions

This content is proprietary and confidential, and is intended only for users described in the content provided in this

document. This content and information is provided to you under a Non-Disclosure Agreement and cannot be distributed.

Copying, disclosing all or any portion of the content and/or information included in this document is strictly prohibited.

http://www.microsoft.com/about/legal/permissions

Table of Contents Microsoft® Lync® Ignite Lab Setup Guide ...................................................................................................................... 1

Introducing Microsoft Hyper-V ..................................................................................................................................... 1

Setup Overview ............................................................................................................................................................... 2

Lab Environment and Configuration ..................................................................................................................... 2

Locally Hosted Environment Configuration ....................................................................................................... 8

Remotely Hosted Environment Configuration ................................................................................................ 13

Appendix A ..................................................................................................................................................................... 18

Microsoft Lync Ignite

©2013 Microsoft Confidential 1

Introducing Microsoft Hyper-V

IMPORTANT: This setup requires Windows Server 2012 Hyper-V.

This learning product is designed using Microsoft® Hyper-V™ running on Windows Server® 2012.

Hyper-V is a virtualization technology that allows a single computer to act as a host for one or more

virtual machines. The virtual machines use a set of virtual devices that might or might not map to

the physical hardware of the host computer.

The software that is installed onto the virtual machine is unmodified, full-version, retail software

that operates exactly as it does when it is installed onto physical hardware.

The following definitions will help you with the remainder of this document:

Hyper-V. Hyper-V is a server application that enables users to run a broad range of

operating systems (OS) simultaneously on a single physical server. Hyper-V is

included with some versions of Windows Server 2012. Hyper-V can be run only on a

64-bit version of Windows Server 2012 that is running on 64-bit hardware.

Host Computer. The physical computer onto which you install the operating system

and the Hyper-V server role.

Host Operating System. The operating system that is running on the physical

computer.

Virtual Machine. The computer that is running inside Hyper-V. In this document,

“Hyper-V” refers to the application running on the host, while “virtual machine” refers

to the guest operating system and any software that is running inside the Hyper-V

application.

Guest Operating System. The operating system that is running inside the virtual

machine.

NOTE: Pressing CTRL+ALT+DELETE while working with a virtual machine will

display the Windows Security dialog box for the host operating system. To close the

dialog box, press the ESC key. To access the Windows Security dialog box for a guest

operating system, press CTRL+ALT+END. Other than this difference, software on a

virtual machine behaves as it would behave on a physical computer.

You can configure virtual machines to communicate with the host computer, other virtual machines

on the same host computer, other host computers, virtual machines on other host computers, other

physical computers on the network, or any combination thereof.

Microsoft Lync Ignite Setup Guide


The setup instructions that you will follow as part of this classroom setup guide configure Hyper-V

and the Virtual Machines that run on the hosts. Changing any of the configuration settings may

render the labs for this learning product unusable.

Setup Overview

The host computers must be set up with a 64-bit version of Windows Server 2012 and must be

running on 64-bit hardware. For more information on the supported hardware for Hyper-V, go to

http://www.microsoft.com/hyper-v.

The virtual machines can either be hosted locally on the computers the attendees will be working

on, or remotely hosted on a server.

Lab Environment and Configuration

Lab Scenario

During this event, the attendees will be given a set of 16 virtual machines configured on Windows

Server 2012 Hyper-V virtual machine hosts. That will need to be hosted locally on the student work

computers, or on a remote host server that is connected to the student work computers on a

simulated classroom internet. All of the student work computers and host servers will need to be on

the same simulated classroom internet to facilitate the labs. They will all be given unique IP

addresses based on their pod numbers and in the 172.16.NN.0/16 subnet, where NN is the

student’s pod number.



Student Virtual Machine Environment

Student Environment

ONPREM.LOCAL – REDMOND

RAS0110.0.0.99 20.0.0.99

Lync 2013 Ignite Virtual Machines

ONPREM.LOCAL – ROME

Simulated Classroom Internet

EX01EXCHANGE 2013

10.0.0.20

DC01AD, DNS, CA

10.0.0.10

SQL01SQL SERVER

201210.0.0.30

SQL02SQL SERVER

201210.0.0.35

LSPC01Persistent

Chat10.0.0.65

LSFE01Lync 2013 FE

redpool10.0.0.50

LSFE02Lync 2013 FE

redpool10.0.0.60

LS2010Lync 2010 FE

10.0.0.80

WAC0110.0.0.85

172.16.NN.12

LSEDGE01Lync 2013 Edge

10.0.0.200

172.16.NN.11

TMG01TMG 2010

10.0.0.1

SQL03SQL SERVER

201220.0.0.30

LSFE03Lync 2013 FE

romepool20.0.0.50

CLIENT0220.0.0.150

Lync 2010 Client

CLIENT0110.0.0.150

Lync 2013 Client

LAPTOP2Lync 2013

172.16.NN.102

LAPTOP1Lync 2013

172.16.NN.101

The virtual machine set will consist of a domain called Onprem.Local that has Exchange 2013

installed; it will also include an already deployed Lync Server 2010 environment. It will not have

any users or mailboxes created. The students will perform Lab 0, which will create the users,

configure DNS, configure Lync, and Exchange, and make their pod unique.

Locally Hosted POD Configuration

This course can be presented in a POD configuration where the virtual machines are hosted locally

on two Windows Server 2012 Hyper-V host machines.



Networking Layout of Locally Hosted POD


HOST1Lync 2013

One External Virtual Switch attached to all VMs called INTERNAL and not used by the

hosts.

NIC1

HOST2Lync 2013

NIC2

One External Virtual Switch, called WebNet,

attached to only the External NICs of TMG01

and EDGE01 and the Local VM hosts.

NIC1

VIRTUAL SWITCHES

INTERNAL

NIC2

WEBNET

In this configuration, two host machines would be needed per POD, and the two students would

share performing the tasks in each of the labs on their local work computers. This requires both of

the host servers to have two network adapters.

Locally Hosted Pod Computer Hardware and Software Requirements

The pod computers needed for the Ignite locally hosted pod configuration are extensive and are

described in the following image.



Locally Hosted Pod ComputerHardware and Software Requirements

Hardware Requirements: Quad Core Processor > 2.5 GHz Sixteen GB of Memory minumum 250 GB HDD space HD Web Camera Headset with microphone Mouse and keyboard Two Network Adapters

Software Requirements: Microsoft Windows 2012 Windows Hyper-V Server Role Microsoft Lync 2013

All of the virtual machines will be hosted on these computers, plus the student client steps, thus

these hardware requirements are necessary for each host, to allow the labs to be performed.

Remotely Hosted Configuration

This course can be presented in a hosted configuration where the virtual machines are hosted at a

remote central location, such as a server room or server rack. Attendees would be asked to bring

their own laptop and they would connect to the lab environment through the hosting provider’s

interface to perform the labs. The users would need to have the appropriate rights to the laptop

brought to the class to be able to install the Lync clients, edit their local hosts file, and to import a

certificate to the Trusted Root Certification Authority store.



Classroom

Pod 1Virtual Machines





Remotely Hosted Networking Layout

Pod 4Hosts

LAPTOP1Lync 2013

172.16.4.101

LAPTOP2Lync 2013

172.16.4.102

Pod 3Hosts

LAPTOP1Lync 2013

172.16.3.101

LAPTOP2Lync 2013

172.16.3.102

Pod 2Hosts

LAPTOP1Lync 2013

172.16.2.101

LAPTOP2Lync 2013

172.16.2.102

Pod 1 Hosts

LAPTOP1Lync 2013

172.16.1.101

LAPTOP2Lync 2013

172.16.1.102

The preceding image shows the recommended setup.

Remotely Hosted Computer Hardware and Software Requirements

The pod computers needed for the remotely hosted configuration are minimal and are described in

the following image.



Remotely Hosted ComputerHardware and Software Requirements

Hardware Requirements: Dual Core Processor > 2.5 GHz Two GB of Memory HD Web Camera Headset with microphone Mouse and keyboard

Software Requirements: Microsoft Windows 7 or newer Microsoft Lync 2013

No virtual machines will be hosted on these computers, so an average to below average workstation

will suffice, and local administrator rights are needed.

The following table shows the map of all VMs required, whether hosted locally or on a server.

VM name RAM (MB)

Role

DC01 1024 Domain Controller, DNS, Certificate Authority LS2010 2048 Lync Server 2010 CU5, Standard Edition EX01 3072 Exchange Server 2013 TMG01 1024 Threat Management Gateway 2010, Firewall EDGE01 2048 Lync 2013 Edge Services SQL01 1536 SQL Server 2012 Back End for Redmond site SQL02 1536 SQL Server 2012 Mirror for Redmond site SQL03 1536 SQL Server 2012 Back End for Rome site LSFE01 3072 Lync 2013 Front End for Redmond site LSFE02 3072 Lync 2013 Front End for Redmond site LSFE03 3072 Lync 2013 Front End for Rome site WAC01 1024 Office 2013 Office Web Apps Server LSPC01 1536 Lync 2013 Group Chat RAS01 512 Routing between Redmond and Rome sites CLIENT01 1024 Windows 8 Client, Office 2013, Lync 2013 – Redmond Site CLIENT02 1024 Windows 8 Client, Office 2010, Lync 2010 – Rome site Total 28.5 GB



Locally Hosted Environment Configuration

This section describes how to set up the environment when the virtual machines are hosted on the

local host machines that the students will run throughout the course.

Rename the Host Computers

In this task, you will rename the student host computers to Laptop1 and Laptop2.

IMPORTANT: You can rename the computers with any name you like, but the lab documents refer

to Laptop1 and Laptop2.

1. On both student host computers, move the mouse pointer to the bottom left corner to

bring up the Start button.

2. Right-click Start, and then click System.

3. In the System console, under Computer name, domain and workgroup settings, click

Change settings.

4. On the System Properties page, on the Computer Name tab, click Change.

5. On the host on the left, in the Computer Name/Domain Changes window, in the

Computer name box, type Laptop1 and then click OK.

6. On the host on the right, in the Computer Name/Domain Changes window, in the

Computer name box, type Laptop2 and then click OK.

7. At the Computer Name/Domain Changes prompt, click OK.

8. On the System Properties page, click Close, and then click Restart Now.

Install the Hyper-V Server Role

In this task, you will install the Hyper-V server role on both Windows Server 2012 student work

computers.

IMPORTANT: If Hyper-V is installed already, you can skip this procedure.

1. On both student host computers, start Server Manager.

2. In Server Manager, in the Dashboard, click Add roles and features.

3. On the Before you begin page, click Next.

4. On the Select installation type page, verify Role-based or feature-based installation is

selected and then click Next.

5. On the Select destination server page, verify Select a server from the server pool is

selected and that the local server is highlighted in the Server Pool window, and then click

Next.



6. On the Select server roles page, select the Hyper-V check box.

7. At the Add Roles and Features Wizard prompt, click Add Features.

8. Back on the Select server roles page, click Next.

9. On the Select features page, click Next.

10. On the Hyper-V page, click Next.

11. On the Introduction to Hyper-V page, click Next.

12. On the Create Virtual Networks page, do not select any check boxes, and then click Next.

13. On the Virtual Machine Migration page, click Next.

14. On the Default Stores page, review the paths, and click Next.

15. On the Confirm Installation Selections page, click Install.

16. On the Installation Results page, click Close.

17. If prompted to restart the computer, click Yes. If not, restart the computer.

18. After the server restarts, logon using administrator credentials.

Create an External Virtual Switch

This section creates the necessary external virtual switch to allow all of the virtual machines to

communicate with each other between the two host servers. The name Internal is required so that

the virtual machines will import correctly, even though it is an external virtual switch. You will

create the WebNet virtual switch in Lab 0, which is the network adapter that is connected to the

Simulated Classroom Internet switch. If you have any existing virtual switches, it is recommended

that they be removed.



HOST1Lync 2013

One External Virtual Switch attached to all VMs called INTERNAL.

NIC1

HOST2Lync 2013

NIC2

NIC1

VIRTUAL SWITCHES

INTERNAL

NIC2

WEBNET

1. On both student host computers, in Hyper-V Manager, in the Actions pane, click Virtual

Switch Manager.

2. In Virtual Switch Manager, click External, and then click Create Virtual Switch.

3. On the Virtual Switch Properties page, in the Name box, type Internal

4. Under Connection type, in the External network drop-down list, select the network

adapter that is connected between the two virtual machine hosts.

5. Clear the Allow management operating system to share this network adapter check

box, and then click OK.

6. At the Applying Network Changes prompt, click Yes.

Disable the Windows Firewall and add Desktop Experience

In this task, you will disable the Windows Firewall for all network profiles. You will also add the

Desktop Experience and start the Windows Audio service if your hosts are Windows Server 2012.



1. On the virtual machine host server(s), start Windows PowerShell™ with Run As

Administrator.

2. At the elevated Windows PowerShell prompt, type the following command and press

Enter:

Get-NetFirewallProfile | Set-NetFirewallProfile -Enabled False

3. Type the following command and press Enter: (Only for Windows Server 2012)

Add-WindowsFeature Desktop-Experience


Set-Service –Name Audiosrv –StartupType Automatic

5. Close Windows PowerShell and restart the computer if you installed the Desktop

Experience.

Copy the Lync Ignite files

In this section, you will copy the Lync Ignite files to the virtual machine host server.

IMPORTANT: All paths shown are required for scripts to run correctly, and the VMs to import

successfully.

1. On both student host computers, start File Explorer.

2. In File Explorer, create a folder on the root of the C drive and call it LabFiles.

3. From the Lync Ignite files, copy over the BaseVHD and Scripts folders to the LabFiles

directory.

4. When this is done, you will have two directories in the LabFiles directory.

BaseVHD

Scripts

5. Verify that C:\LabFiles\Scripts contains the following files:

CreateSymLinks.cmd

CreateSymLinks-D_DRIVE.cmd

6. Verify that C:\LabFiles\BaseVHD contains the following files:

W2K8R2SP1Base.vhd

WIN8Base.vhd

WIN12EEBase.vhd

7. On both hosts, in C:\LabFiles, create a folder called VMs.



8. On Laptop1, copy over only these virtual machines:

CLIENT01

EX01

LSFE01

EDGE01

TMG01SQL01

SQL02

WAC01

9. On Laptop2, copy over only these virtual machines:

CLIENT02

DC01

LS2010

LSFE02

LSFE03

RAS01

SQL03

LSPC01

Create the necessary SymLinks

You will now run a script that will import the virtual machines. It will first create the necessary

SymLinks.

1. On both of the virtual machine hosts, start an elevated Command Prompt.

2. At the command prompt, type the following command and then press Enter:

CD “C:\LabFiles\Scripts”

3. At the command prompt, type the following command and then press Enter:

CreateSymLinks.cmd

NOTE: If you are using the D drive, instead of the C drive, type CreateSymLinks-D_Drive.cmd. If

you are using a drive other than C or D, you will need to edit the cmd files accordingly.

NOTE: You might see some warnings that the folder does not exist; this is expected since not all

virtual machines are on both laptops.



Import the Virtual Machines

You will now import the virtual machines.

1. On the virtual machine hosts, start Hyper-V Manager.

2. In Hyper-V Manager, in the Actions pane, click Import Virtual Machine.

3. On the Import Virtual Machine wizard, on the Before You Begin page, click Next.

4. On the Locate Folder page, click Browse.

5. On the Select Folder prompt, browse to C:\LabFiles\VMs.

6. Click the first Virtual Machine listed, and then click Select Folder.

7. Back on the Locate Folder page, click Next.

8. On the Select Virtual Machine page, verify CLIENT01 shows, and then click Next.

9. On the Chose Import Type page, leave the defaults, and click Next.

10. On the Completing Import Wizard page, click Finish.

11. Repeat steps 2 through 10 to import the rest of the virtual machines.

12. Once successfully imported, highlight all of the virtual machines, and then in the Actions

pane, click Snapshot. This will create a starting point snapshot.

Remotely Hosted Environment Configuration

This section describes how to configure the environment when the virtual machines are hosted on

servers in a remote location, such as servers in a server room.

Install the Hyper-V Server Role

In this task, you will install the Hyper-V server role on the Windows Server 2012 host server.

IMPORTANT: If Hyper-V is installed already, you can skip this procedure.

1. On the virtual machine host server, start Server Manager.

2. In Server Manager, in the Dashboard, click Add roles and features.

3. On the Before you begin page, click Next.

4. On the Select installation type page, verify Role-based or feature-based installation is

selected, and then click Next.



5. On the Select destination server page, verify Select a server from the server pool is

selected and that the local server is highlighted in the Server Pool window, and then click

Next.

6. On the Select server roles page, select the Hyper-V check box.

7. On the Add Roles and Features Wizard prompt, click Add Features.

8. Back on the Select server roles page, click Next.

9. On the Select features page, click Next.

10. On the Hyper-V page, click Next.

11. On the Introduction to Hyper-V page, click Next.

12. On the Create Virtual Networks page, do not check any check boxes, and then click Next.

13. On the Virtual Machine Migration page, click Next.

14. On the Default Stores page, review the paths, and click Next.

15. On the Confirm Installation Selections page, click Install.

16. On the Installation Progress page, click Close.

17. If prompted to restart the computer, click Yes. If not, restart the computer.

18. After the server restarts, log in using administrator credentials.

Create an Internal Virtual Switch

This section creates the necessary internal virtual switch to allow all of the virtual machines to

communicate with each other. The name Internal is required so the virtual machines will import

correctly. You will create the WebNet external virtual switch in Lab 0. If you have any existing

virtual switches, it is recommended that they be removed.

1. On the virtual machine host server, start Hyper-V Manager.

2. In Hyper-V Manager, in the Navigation pane, click the host server name.

3. In the Actions pane, click Virtual Switch Manager.

4. On the Virtual Switch Manager page, in the Create virtual switch box, click Internal, and

then click Create Virtual Switch.

5. In the Name box, type Internal and then click OK.

Disable the Windows Firewall and add Desktop Experience

In this task, you will disable the Windows Firewall for all network profiles and add the Desktop

Experience feature.



1. On the virtual machine host server(s), start Windows PowerShell, with Run As

Administrator.

2. At the elevated Windows PowerShell prompt, type the following command and press

Enter:

Get-NetFirewallProfile | Set-NetFirewallProfile -Enabled False


Add-WindowsFeature Desktop-Experience


Set-Service –Name Audiosrv –StartupType Automatic

5. Close Windows PowerShell and restart the computer if you installed the Desktop

Experience.

Copy the Lync Ignite files

In this section, you will copy the Lync Ignite files to the virtual machine host server.

IMPORTANT: All paths shown are required for scripts to run correctly and the VMs to

import successfully when installed to the C drive.

1. On the virtual machine host server, start File Explorer.

2. In File Explorer, create a folder on the root of the C drive and call it LabFiles.

3. Copy all of the Lync Ignite files to the LabFiles directory.

4. When done, you will have three folders in the LabFiles directory.

BaseVHD

Scripts

VMs

5. Verify that C:\LabFiles\Scripts contains the following files:

CreateSymLinks.cmd

CreateSymLinks-D_DRIVE.cmd

NOTE: If you are using the D drive, instead of the C drive, use the –D_Drive file instead

when instructed in later steps.

6. Verify that C:\LabFiles\BaseVHD contains the following files:

W2K8R2SP1Base.vhd

WIN8Base.vhd



WIN12EEBase.vhd

7. Verify that C:\LabFiles VMs contains the following directories:

CLIENT01

CLIENT02

DC01

EDGE01

EX01

LS2010

LSFE01

LSFE02

LSFE03

LSPC01

RAS01

SQL01

SQL02

SQL03

TMG01

WAC01

Create the necessary SymLinks

You will now run a script that will import the virtual machines. It will first create the necessary

SymLinks.

1. On the virtual machine host server, start an elevated Command Prompt.

2. At the command prompt, type the following command and then press ENTER:

CD “C:\LabFiles\Scripts”

3. At the command prompt, type the following command and then press ENTER:

CreateSymLinks.cmd

NOTE: If you are using the D drive, instead of the C drive, type CreateSymLinks-

D_Drive.cmd. If you are using a drive other than C or D, you will need to edit the cmd file

accordingly.



Import the Virtual Machines

You will now import the virtual machines.

1. On the virtual machine host server, start the Hyper-V Manager.

2. In Hyper-V Manager, in the Actions pane, click Import Virtual Machine.

3. On the Import Virtual Machine wizard, on the Before You Begin page, click Next.

4. On the Locate Folder page, click Browse.

5. On the Select Folder prompt, browse to C:\LabFiles\VMs.

6. Click CLIENT01, and then click Select Folder.

7. Back on the Locate Folder page, click Next.

8. On the Select Virtual Machine page, verify CLIENT01 shows and then click Next.

9. On the Chose Import Type page, leave the defaults, and click Next.

10. On the Completing Import Wizard page, click Finish.

11. Repeat steps 2 through 10 to import the rest of the virtual machines.

12. When finished, you will have the following virtual machines imported in Hyper-V

Manager:



13. Once successfully imported, highlight all of the virtual machines, and then in the Actions

pane, click Snapshot. This will create a starting point snapshot.

Appendix A

The virtual machines were developed using the English (United States) layout shown in the

following image.



If your physical keyboard does not match the above layout, you may need to refer to the above

layout for the character positions used to log on. For future logons and usage throughout the labs,

you may want to install your keyboard layout in the virtual machine.

Date post:	03-Jan-2016
Category:	Documents
Upload:	javedcg
View:	35 times
Download:	3 times

Lync Ignite Setup Guide

Documents