Lab 00: Configuring the Microsoft Lync Ignite Environment Cloud Hosted Version

Lab 00: Configuring the Microsoft Lync Ignite Environment Cloud Hosted Version

DISCLAIMER 2013 Microsoft Corporation. All rights reserved. Microsoft, Active Directory, Forefront, Hyper-V, Internet Explorer, Lync, Windows, Windows PowerShell, 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 Lab: Configuring the Microsoft Lync Environment... 1 Exercise 1: Connect to the Virtual Machines... 4 Exercise 2: Reconnecting for Troubleshooting and Reset... 10

Microsoft Lync Ignite Lab: Configuring the Microsoft Lync Environment For the cloud-hosted version of these labs, there is little setup configuration for you to perform. You will need to connect to the lab environment using the hollaunchpad application and then determine the public IP address assigned to one of the virtual machines. After determining this address, you will exit the hollaunchpad application and then connect to the lab environment using Remote Desktop Protocol. Estimated time to complete: 10 minutes What You Will Learn After completing the exercises, you will be able to: Determine the public IP address assigned to DC01. Describe how to retain or discard your lab session. Record information that may be required in a support request. Scenario Only one POD number is used in this version of the labs: 123. Because the lab manuals are used for different versions of these labs, you may see references to replaceable values NNN, where NNN represents your POD number. For example, you may be prompted to create DNS records that have the format meetnnn, sipnnn, and so on. In these cases you would enter sip123 and meet123. The child domain for the lab environment is onprem123.lyncignite.biz. If you have any questions about this, please consult a proctor or your instructor. The following diagram illustrates a big-picture view of a Microsoft Lync 2013 Ignite virtual machine deployment supporting the labs. The first of the following diagrams illustrates a view of the pod scenario. The second diagram depicts the connection used by the virtual machines to the simulated public Internet used in the lab on the 172.16.0.0/16 network. 1

Lab 00: Configuring the Microsoft Lync Ignite Environment TMG01 Lync Ignite Virtual Machine Set Figure 1: Pod scenario view Internal Network TMG01 Simulated Classroom Public Network CLASSROOM SIMULATED INTERNET Internal Network EDGE01 Figure 2: Virtual machine connection to the public internet 2

Microsoft Lync Ignite Figure 3: Classroom connection to hosted virtual lab environment All client tasks will be performed on the virtual machines. You will connect to the hosted environment by using either the hollaunchpad application or an RDP session. Tips Only one person at a time can connect to the lab environment using the hollaunchpad application. While it is possible for two people at a time to be connected to a virtual machine by using RDP, this might cause confusion and lead to mistakes. It is recommended that only one person at a time be connected to a virtual machine. It might be easier for one person to connect to the virtual machines at a time, while the other opens the lab documents. You can then swap duties periodically. Every password for every user is Password1, except for the following: o Administrator and Administrator2 use the password Lync!gnit3 (used for accessing the virtual environment). o EDGE01\Administrator uses the password Lync!gnit3 (only used for accessing the EDGE01 virtual machine). o TMG01\Administrator uses password Lync!gnit3 (only used for accessing the TMG01 virtual machine). o CLIENT03\LabAdmin uses the password Password1 (only used for accessing the CLIENT03 virtual machine). 3

Lab 00: Configuring the Microsoft Lync Ignite Environment Exercise 1: Connect to the Virtual Machines IMPORTANT: This exercise should be completed by only one member of each POD. This person will start the POD VMs, acquire and record the public IP addresses, and prepare the POD for RDP connectivity. Scenario Only one person at a time can connect to the lab environment by using the hollaunchpad application. If you are the only person performing the lab, you can continue to use the hollaunchpad exclusively for access to the lab environment. If you have a lab partner and are working in pairs, one or both of you will need to connect to the lab environment by using an RDP connection. Some labs will allow you to perform tasks on two separate machines at the same time. When you can perform tasks in parallel, the lab manual will clearly indicate this. For example, in Lab 01 - Deploying Microsoft Lync Server 2013, Exercise 4, Task 2, Start the Lync Server Deployment Wizard and install the Local Configuration Store, the lab manual clearly indicates that the task can be performed on both LFSE01 and LFSE02 at the same time. In this case, it might be desirable for both lab partners to connect to the environment at the same, one person connecting to LFSE01 and the other connecting to LFSE02 to perform the tasks. Depending on the situation, you have the choice to connect to the lab environment either through the hollaunchpad application or an RDP connection; however, in some cases, as discussed below, performing some lab steps is possible only through the hollaunchpad Limitations of double-hop RDP connections to the lab environment If any labs require you to use voice to test your implementation, for example, Lab 03 - Configuring Coexistence and Interoperability with Microsoft Lync Server 2013, you will need to use the hollaunchpad application to connect to the lab environment. When you use an RDP connection to connect to DC01 and then establish an RDP connection from DC01 to another lab virtual machine, such as CLIENT01, you are establishing a double-hop RDP connection. It is not possible to perform RDP recording redirection over more than one RDP hop, although RDP audio redirection will work over double hops. The hollaunchpad leverages technology that makes it possible to perform recording redirection (the use of a microphone) to the lab virtual machines. RDP connection limits Only two RDP administrative connections at a time are allowed to the servers in the lab environment. If you are logged on to a VM in the hollaunchpad, this will consume one RDP connection. If you and your partner both want to connect to the same machine at the same time, ensure that one of you uses the hollaunchpad and the other uses RDP. 4

Microsoft Lync Ignite Tasks 1. Log on to your designated lab portal. You will need to get the URL for your lab launch portal from your instructor. Your instructor will also provide each POD with a unique set of credentials for accessing the portal. If the POD is being managed by two students, only one student should perform this step. a. On your laptop, open Internet Explorer. b. Navigate to the URL for your lab launch portal, select HynesITe, Inc. and then authenticate using your provided credentials. c. Click the link to start the Lync Ignite lab environment. A sample portal page and launch URL is provided below. d. Wait for the hollaunchpad to start and your lab virtual machines to connect. This process will take between 2 and 5 minutes depending on system load. During this time all 17 VMs are provisioned and started. Ensure you wait for the process to fully start, even if appears hung, or to be slow. When completed, the active VM screen will look similar to the screenshot below. 5

Lab 00: Configuring the Microsoft Lync Ignite Environment Lync Ignite VMs contain many software packages and are resource intensive. VMs may appear sluggish at first, but this will quickly improve as the VMs are left running and software and processes settle down. This provides you with Hyper-V Console-level access to each virtual machine. To navigate to a different virtual machine, click the VM name in the Navigation Pane on the right side. 2. Determine your Public IP addresses and DNS names. The DC01 server has a public interface that will acquire an IP address from one of two public DHCP scopes. Both scopes are fully routable on the Internet. a. In hollaunchpad, click DC01. b. On the desktop, double-click the Enable-WebNet shortcut. c. On the desktop, double-click Lync-Ignite-What-is-My-IP.exe. d. In the Lync Ignite DNS Configuration dialog box, record the displayed public IP address. This is the IP address you and your partner (if you have one) will use to connect to the lab environment. e. Close the dialog box, and log off DC01. Note that if you do not log off DC01, only one person will be able to connect over an RDP connection. 6

Microsoft Lync Ignite 3. Determine the VM Host and Session ID for your lab instance. In the rare event that you have a support request that requires access to the Hyper-V host where your lab instance is running, you or your instructor will need to provide the VM host and session ID for the lab instance in the support request. In this task, you will note and record this information in case you need to provide it. a. On the lower-right hand side of the hollaunchpad, locate and record the VM host ID and session ID. A sample screen shot is provided to show you what this information looks like. 4. Exit the hollaunchpad application and retain your session. When you exit the hollaunchpad application, you have the option to discard or retain your session. IMPORTANT: If you discard your session, you will lose all work in the labs you have done to date, so please ensure that you retain your current session. a. In the upper-hand corner of the hollaunchpad application, click Exit Lab Environment. b. When prompted, click Retain Current Session, as shown below. c. The hollaunchpad will close, but your VMs will remain running. You can now use RDP in addition to the hollaunchpad to perform lab steps. 5. Start a Remote Desktop Connection to your POD. In this task you will configure your RDP client to connect to DC01 running in your lab instance. 7

Lab 00: Configuring the Microsoft Lync Ignite Environment a. On your laptop, click Start, and then click Run. b. In the Run window, in the Open box, type mstsc.exe and then click OK. c. In the Remote Desktop Connection window, in the Computer box, type the public IP address of the DC01 virtual machine that you determined earlier, and then click Options. d. Click the Display tab. e. Under Display configuration, slide the bar to your desired resolution. f. Verify that the color depth is set to High Color (16 bit), and then click the Local Resources tab. g. Under Remote audio, click Settings. h. On the Remote Desktop Connection page, under Remote audio playback, verify that Play on this computer is selected. i. Under Remote audio recording, select Record from this computer, and then click OK. j. Click the Experience tab. k. In the Choose your connection speed to optimize performance drop-down list, select Modem (56 Kbps), and then click Connect. This is to help maximize the Internet connection at this event. l. In the Remote Desktop Connection dialog box asking if you trust this remote connection, click Connect. m. On Laptop1, at the Windows Security prompt, log on as Onprem\Administrator with a password of Lync!gnit3 8

Microsoft Lync Ignite n. On Laptop2, at the Windows Security prompt, log on as Onprem\Administrator2 with a password of Lync!gnit3 o. Leave the Remember my credentials check box clear, and then click OK. p. At the Remote Desktop Connection prompt, select the Don t ask me again for connections to this computer check box and then click Yes. Both of you should now be connected to the DC01 of your virtual machine set. 6. Start Remote Desktop Connections to your POD VMs from DC01. a. On the remote desktop connection to DC01, on the desktop, double-click the Ignite RDP Connections shortcut. This will open a folder that contains a preset of RDP connection objects to your set of Ignite VMs. When a lab step requires a step on any of the VMs, you would double-click the corresponding RDP connection object. For steps on LFSE01, you would perform the steps by double-clicking on LFSE01 connection object and then logging on to the RDP session with the appropriate credentials. 9

Lab 00: Configuring the Microsoft Lync Ignite Environment Exercise 2: Reconnecting to Perform Lab Activities, Troubleshooting, and Reset You can leverage the hollaunchpad for lab session control for performing lab activities, resetting, and troubleshooting. Use the steps in this exercise in the following scenarios. You need to perform lab steps that require the use of recording redirection; that is, you need to be able to redirect the microphone on your physical machine to the virtual machine in the lab environment. You have lost network connectivity to one or more virtual machines. You are unable to RDP to one or more virtual machines. You need to reset your virtual machines to a clean state. You need to determine the VM host and session ID to request support to resolve items 2 and 3 above. 1. Reconnect to an existing the lab environment a. Launch your lab using the same steps presented in Exercise 1. b. When your lab is launching, click Yes, to resume your current session. IMPORTANT: Clicking No will discard all your VMs, provide you with a new session, deleting all your work to date. 2. Troubleshoot RDP or networking issues in one or more VMs. a. Reconnect to your existing lab environment. b. Using the console sections, perform standard network troubleshooting to resolve your issue. 3. Reset environment to a clean state. a. Reconnect to your existing lab environment. b. When your lab is launching, click No to delete your existing session and start a new session. 10