Technical Requirements Litware identifies the following technical requirements

Technical requirements litware identifies the

This preview shows page 72 - 75 out of 105 pages.

Technical Requirements Litware identifies the following technical requirements for the planned migration: Users must be able to use all Lync Server features if a single server fails. Users must be able to connect to the Lync Server infrastructure if a single central site fails. Members of a group named Temp_Contractors must be prevented from using Microsoft Lync 2013 when they connect remotely. Only users in the human resources department must be able to access and discover a persistent chat room named HRConfidential. Security Requirements Litware plans to deploy remote access. Some users work remotely from their customers' offices, which have firewall restrictions. All of the remote users must be able to connect to the Lync Server infrastructure by using TCP port 443.
Image of page 72
73 Question: 1 DRAG DROP You are planning the Lync Server 2013 migration. You need to identify which management tools must be used to achieve the following migration tasks during the coexistence period: Move users from Lync Server 2010 to Lync Server 2013. Add a server that has Lync Server 2013 deployed to the topology. Remove a server that has Lync Server 2010 deployed from the topology. Which tools should you identify? To answer, drag the appropriate management tools to the correct migration task in the answer area. Each tool may be used once, more than once, or not at all. Additionally, you may need to drag the split bar between panes or scroll to view content. Answer: Explanation: 1) Lync Server 2013 Topology Builder 2) Microsoft Lync Server 2013 Control Panel 3) Microsoft Lync Server 2013 Control Panel Note: / You can move a single user or groups of users to your new Microsoft Lync Server 2013 deployment using the following two methods: Lync Server Control Panel and Lync Server Management Shell. / The deployment of Lync Server 2013 requires using Topology Builder to define your topology and the components you want to deploy, preparing your environment for deployment of the Lync Server 2013 components, publishing your topology design on the first Front End Server, and then installing and configuring Lync Server 2013 software for the components for your deployment. To remove a Front End Server from a pool 1. Open the Lync Server 2013 Front End Server, open Topology Builder. 2. Navigate to the Lync Server 2010 node.
Image of page 73
74 3. Expand Enterprise Edition Front End pools, expand the Front End pool with the Front End Server that you want to remove, right-click the Front End Server that you want to remove, and then click Delete. Reference: Migration from Lync Server 2010 to Lync Server 2013 Question: 2 DRAG DROP You are evaluating the deployment of the Persistent Chat feature. You need to recommend which tasks must be performed to create HRConfidential. Which three actions should you recommend? To answer, move the three appropriate actions from the list of actions to the answer area and arrange them in the correct order.
Image of page 74
Image of page 75

You've reached the end of your free preview.

Want to read all 105 pages?

  • Spring '16
  • Windows Server 2003, Windows PowerShell

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture