Lync Server on AWS
Lync Server Quick Start

Step 3. Test Your Lync Server 2013 Deployment

Once your Lync stack is up and running, you can connect to your servers and test your deployment. In this section, we'll explain how to create and enable users for Lync, and test sign-in from the Lync client. Then we'll take a look at how to fail over from one Availability Zone to the other.

Connecting to Lync Servers

  1. Remote into the environment through one of the Remote Desktop Gateway (RD Gateway) instances. Use the StackAdmin@example.com user name and the password you set when you launched the stack

    You can retrieve the Elastic IP address (EIP) for each RD Gateway instance from the Amazon EC2 console. You can use the Remote Desktop Gateway Quick Start to fully configure your RD Gateway instances, or you can simply connect to the desktop of your RD Gateway instances, and then start a new RDP client to connect internally to your remaining servers.

  2. RDP to the FE1 server, which is the Lync Front End Server in the first Availability Zone. From the Start menu, launch the Lync Control Panel. The Lync Control Panel is a Microsoft Silverlight-based web application, and the Silverlight client is already installed on the Lync servers.

    
                            Launching the Lync Control Panel

    Figure 6: Launching the Lync Control Panel

  3. You'll be prompted to select the server to connect to. Choose fe1.example.com.

    
                            Selecting the Server URL

    Figure 7: Selecting the Server URL

Creating Test Users

Follow the instructions in the Microsoft documentation to create test users with domain user permissions in Active Directory. We recommend that you include most of the standard fields, such as first name, last name, user principal name, and email.

Enabling Users

  1. In the Lync Control Panel, choose Users from the left navigation bar, and then choose Enable users.

    
                            Navigating to User Administration in the Lync Control
                                Panel

    Figure 8: Navigating to User Administration in the Lync Control Panel

  2. In the New Lync Server User dialog box, choose Add.

  3. In the Select from Active Directory dialog box, choose Find. This will allow you to select a user to enable for Lync. You can use the accounts you created in Active Directory. Make sure that you use a non-administrative account.

    Make a note of the user principal name (UPN), as this will serve as the sign-in name for the user. Choose OK when you're done.

    
                            Finding a User to Lync-Enable

    Figure 9: Finding a User to Lync-Enable

  4. The New Lync Server User dialog box will be redisplayed. Assign the user to the fe1.example.com pool. Make sure that you choose Use the user principal name (UPN) for the SIP URI. Then choose Enable.

    
                            Enabling a User for Lync

    Figure 10: Enabling a User for Lync

Validating the Lync Sign-in

Now that you have a Lync-enabled user, you can install the Lync client and test the sign-in to the Lync Server.

  1. Install a Lync client. For this task, you can use one of the Remote Desktop Gateway instances as a client machine. For example, from the RDGW1 server, you can install Office Professional Plus 2013, which includes the Lync client, or you can install the free Lync Basic 2013 client. You can download the Lync Basic client from the Microsoft Download Center. There are no special instructions for installing the Lync Basic client; follow the instructions on the setup screen and accept all the default settings.

  2. Launch the Lync client you installed in the previous step. Use the UPN for the user as the sign-in name. If you used one of the pre-created test accounts, use p@ssword123 for the password. Once you've successfully signed in, you'll see a green presence indicator next to your name.

    
                            Signing into Lync with a Test Account

    Figure 11: Signing into Lync with a Test Account

Testing Pool Failover for Disaster Recovery

Since you are now signed in with an account homed on the fe1.example.com pool, you can simulate a failure of that pool and invoke a pool failover for disaster recovery.

  1. On the FE1 server, stop the Lync Server Front-End service. You can do this in the GUI, or by using Windows PowerShell with the following command:

    Stop-Service RtcSrv -Force
  2. Now you're ready to fail over to the second Availability Zone. Remote into the FE2 server, and fire up PowerShell. To fail over the Central Management Server, run:

    Invoke-CsManagementServerFailover -BackupSqlServerFqdn fe2.example.com -BackupSqlInstanceName rtc -Force

    When you're prompted for confirmation, type A, and then press Enter to continue.

    
                            Invoking Management Server Failover

    Figure 12: Invoking Management Server Failover

  3. Next, run the following PowerShell command to fail the FE1 pool over to FE2.

    Invoke-CsPoolFailOver -PoolFqdn fe1.example.com -DisasterMode -Force

    When prompted for confirmation, type A, and then press Enter to continue.

    
                            Invoking Pool Failover

    Figure 13: Invoking Pool Failover

  4. After a few moments, the Lync client should reconnect to the pool in the second Availability Zone. If nothing happens, close the client (make sure the lync.exe process is closed) and try signing back in.

  5. You can view the client configuration by pressing the Ctrl key, right-clicking the Lync icon in the notification area, and choosing Configuration Information. You should see that the connected Lync server is now fe2.example.com.

    
                            Viewing Lync Client Configuration Information

    Figure 14: Viewing Lync Client Configuration Information

  6. At this point, you can fail the pool back to FE1. To do so, start the RtcSrv service on FE1, and run the following command on the FE2 server:

    Invoke-CsPoolFailBack -PoolFqdn fe1.example.com -Force

    For more information, see Managing Lync Server 2013 disaster recovery, high availability, and Backup Service on Microsoft TechNet.