Professional Documents
Culture Documents
Lync Setup Guide
Lync Setup Guide
Lync 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.
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
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.
ONPREM.LOCAL REDMOND
WAC01 10.0.0.85
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.
WEBNET
NIC2
VIRTUAL SWITCHES
NIC2
INTERNAL
NIC1 NIC1
One External Virtual Switch attached to all VMs called INTERNAL and not used by the hosts.
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.
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.
Pod 1 Hosts
Pod 3 Hosts
Pod 2 Hosts
Pod 4 Hosts
Hardware Requirements: Dual Core Processor > 2.5 GHz Two GB of Memory HD Web Camera Headset with microphone Mouse and keyboard
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 DC01 LS2010 EX01 TMG01 EDGE01 SQL01 SQL02 SQL03 LSFE01 LSFE02 LSFE03 WAC01 LSPC01 RAS01 CLIENT01 CLIENT02 Total RAM (MB) 1024 2048 3072 1024 2048 1536 1536 1536 3072 3072 3072 1024 1536 512 1024 1024 28.5 GB Role Domain Controller, DNS, Certificate Authority Lync Server 2010 CU5, Standard Edition Exchange Server 2013 Threat Management Gateway 2010, Firewall Lync 2013 Edge Services SQL Server 2012 Back End for Redmond site SQL Server 2012 Mirror for Redmond site SQL Server 2012 Back End for Rome site Lync 2013 Front End for Redmond site Lync 2013 Front End for Redmond site Lync 2013 Front End for Rome site Office 2013 Office Web Apps Server Lync 2013 Group Chat Routing between Redmond and Rome sites Windows 8 Client, Office 2013, Lync 2013 Redmond Site Windows 8 Client, Office 2010, Lync 2010 Rome site
Microsoft Lync Ignite 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.
WEBNET
NIC2
VIRTUAL SWITCHES
NIC2
INTERNAL
NIC1 NIC1
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.
10
Microsoft Lync Ignite 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 4. Type the following command and press Enter: (Only for Windows Server 2012) Set-Service Name Audiosrv StartupType Automatic 5. Close Windows PowerShell and restart the computer if you installed the Desktop Experience.
6. Verify that C:\LabFiles\BaseVHD contains the following files: W2K8R2SP1Base.vhd WIN8Base.vhd WIN12EEBase.vhd
11
Microsoft Lync Ignite Setup Guide 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
12
13
Microsoft Lync Ignite Setup Guide 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.
14
Microsoft Lync Ignite 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 4. Type the following command and press Enter: (Only for Windows Server 2012) Set-Service Name Audiosrv StartupType Automatic 5. Close Windows PowerShell and restart the computer if you installed the Desktop Experience.
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
15
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
16
17
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.
18
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.
19