microsoft assessment & planning tool (map) and asr deployment … · 2020. 7. 14. · asr...

©2019 Tech Data Corp. All Rights Reserved. Confidential and Proprietary

Microsoft Assessment & Planning Tool (MAP) and ASR Deployment Planner

Installation Guideline

Microsoft Assessment & Planning Tool (MAP) and ASR Deployment Planner, v. 3.2

Confidential and Proprietary of 21

Contents

1 Introduction ........................................................................................................................................ 3

2 Microsoft Assessment & Planning Toolkit .............................................................................................. 3 2.1 Objective ................................................................................................................................................... 3 2.2 System Requirements ................................................................................................................................. 3 2.3 Instructions to Install the MAP Toolkit .......................................................................................................... 3

Preparing environment ............................................................................................................................... 6 Running MAP Toolkit .................................................................................................................................. 7 Collecting MAP Toolkit Output .................................................................................................................. 14

3 Azure Site Recovery Deployment Planner ........................................................................................... 15 3.1 Objective ..................................................................................................................................................15

ASR Deployment Planner for VMWare .........................................................................................................15 3.3 ASR Deployment Planner for Hyper-V ........................................................................................................ 18

Version 3.2

Date: 02/09/2019



1 Introduction

This document provides installation guide for the both MAP and ASR deployment planner tool. Unlike MAP tool, ASR deployment planner has different installation procedure for Hyper-V and VMware.

2 Microsoft Assessment & Planning Toolkit

2.1 Objective

The MAP Toolkit is used for multi-product assessment and planning. It assesses a network environment using agentless data collection technologies to gather inventory and performance information. Then provides assessment reports to aid organizations with their IT infrastructure planning.

The main areas of planning covered by MAP:

• Migration Planning • Consolidation/Virtualization • Private/Public Cloud Planning • Software Usage Tracking

The Microsoft Assessment and Planning (MAP) Toolkit is part of the Microsoft Solution Accelerators that provide tested guidance and automated tools to help plan, deploy, and manage new Microsoft technologies. They are all freely available and fully-supported by Microsoft.

2.2 System Requirements

• Windows 7 Service Pack 1, Windows 8, Windows 8.1, Windows 10, Windows Server 2008 R2 SP1, Windows Server 2012, Windows Server 2012 R2

• The MAP Toolkit requires a computer with the following minimum configuration: • 1.5 GHz dual core processor, 2.0 GB of memory, 1 GB free hard drive space (for database)

2.3 Instructions to Install the MAP Toolkit

• Download the tool from https://www.microsoft.com/en-in/download/details.aspx?id=7826 • Install the MAP Toolkit on a single computer that has access to the network on which you want to conduct

an inventory and assessment. The toolkit uses a SQL Server database to store and process the information that it collects from your environment. There are two options for your database installation:

Database Option When to use

Local DB • Most of the time. This is the default option, when the MAPS instance does not already exist

• Databases will be less than 10 GB

MAPS Instance • You have an existing MAP database that you want to preserve • Your database will grow more than 10GB • Multiple users need to connect to the MAPS database

• Save the MAPSetup.exe file in your computer • Run MAPSetup.exe as Administrator and complete the installation into your computer (Internet access is

not needed during installation of the MAP toolkit) • Follow below installation process to complete the setup



Once installation is finished, you can search for Microsoft Assessment and Planning Toolkit as shown below.

Preparing environment

Before you start collecting inventory data, you need to ensure that your environment is prepared to be inventoried. Follow below guide lines to prepare the environment

The MAP Toolkit uses collection protocols to communicate with computers in a network and collect information to use in the various assessments. The communication is subject to specific administration and security settings on the target computers and is based upon many things including the operating system, firewall and anti-virus settings as well as the information that you are trying to collect. In this phase, you will gather the user accounts and passwords needed to connect and successfully inventory your environment in advance of running the toolkit.

Disable IPS scanner

If your environment has IPS monitoring system/scanner enabled, you need to temporarily disable it while you run MAP tool otherwise the scanner/monitoring system may throw error or block MAP from collecting inventory data.

Ports and Protocols to be opened

IMPORTANT: Keep checking the MAP Blog and MAP Toolkit Content Index for updates and changes, especially after new versions of MAP are released.

In order for the MAP inventory to be successful, proper firewall configurations must be considered. The ports that need to be open depend on the collector technology being used. Each scenario on the “Inventory Scenarios” page of the inventory wizard uses different collector technologies and some collectors span multiple scenarios.

WMI – Port 135 (DCOM/RPC) for the initial connection, then a dynamically assigned port above 1024. This is a function of RPC/WMI and not MAP. Some firewalls, like Windows Firewall, allow you to specify exceptions for services, like WMI, rather than specific ports. Then the firewall takes care of opening the dynamically assigned ports for you. Some firewalls do not allow this and will require a range of ports to be opened. Consult your firewall’s documentation for more information.

SSH – Port 22. This is the default port MAP will use. In the inventory wizard, you can change the port that MAP uses if a non-default port is used in your environment.

VMware – Port 80 and/or 443. These are the default ports for HTTP and HTTPS respectively. In the inventory wizard, you can change the port that MAP uses if a non-default port is used in your environment. Some VMware environments use ports 8222 and/or 8333 for HTTP and HTTPS, but these are not listed by default in MAP.

PowerShell – 5985 and/or 5986. This is the default for PowerShell HTTP and HTTPS respectively. In the inventory wizard, you can change the port that MAP uses if a non-default port is used in your environment.



SQL Server – Port 1433 for default instances and port 1434 for the SQL Server Browser Service. For named instances, MAP queries the browser service and learns the port numbers assigned by SQL Server or that were manually set by the user. See this support article for more information on named instance port numbers.

Active Directory – In a domain that consists of Windows Server® 2003–based domain controllers, the default dynamic port range is 1025 through 5000. Windows Server 2008 R2 and Windows Server 2008, in compliance with Internet Assigned Numbers Authority (IANA) recommendations, increased the dynamic port range for connections. The new default start port is 49152, and the new default end port is 65535. Therefore, you must increase the remote procedure call (RPC) port range in your firewalls. If you have a mixed domain environment that includes a Windows Server 2008 R2 and Windows Server 2008 server and Windows Server 2003, allow traffic through ports 1025 through 5000 and 49152 through 65535. See this article for more information.

Oracle – 1521. This is the default port MAP will use. In the inventory wizard, you can change the port that MAP uses if a non-default port is used in your environment.

Running MAP Toolkit

After preparing the environment, you can start collecting inventory data. Follow the steps below to collect data. In this section you can find the steps for different scenarios such as on-premise environments with one Active Directory Domain or Multiple Active Directory Domains and Linux VMs with same user Name and Different passwords. Please refer to the respective section based on your environment.

• Create a database: click on File -> Create/Select Database

• Select create an inventory database

• Click on Perform an inventory.



To perform an inventory, you need to provide the below information based on your environment. The wizard defines multiple sections as: Inventory Scenarios, Discovery Methods, Active Directory Credentials, and Active Directory Options, All computers Credentials, Credentials Order and Summary.

Inventory Scenarios:

All on premise environments are different, so you need to make the right selection for your environment. For example, if you have Windows VMs and Linux VMs, Exchange Server and Active Directory Users etc. select respective checkboxes as shown in the screen below.

After selecting the respective checkboxes, click on “Next” to go to “Discovery Methods”.

Discovery Methods:

In this section you need to select the right discovery method that suits your environment. Different scenarios like customers that have a single active directory or multiple active directories may require a different selection. Select the options accordingly to what fits better to your environment.



For Single Active Directory choose as below:

Provide Active Directory Credentials:

On Active Directory Options, select option “Find all computers in all domains, containers, and organizational unit”. And click on “Next”.



To continue Jump on to “All Computer Credentials”

For Multiple Active Directories choose as below:

Besides the selections you made above, also select “Scan an IP address range” as shown in the below screen.

Then click on “Next” to move on to “Scan an IP Address Range” section. In this section, you need to enter the IP Address ranges of you want to collect inventory data.



Multiple Linux Machines with same user name with different passwords:

If customer environment has multiple Linux machines with same use name and different passwords, there is a limitation of MAP tool as it doesn’t allow multiple entries with the same user. You can use the following as a workaround of this situation:

• Create a new user account with root permissions on all the machines and use it using any suitable discovery method as, for instance, “Scan an IP address range” or “Import computer names from a file”

• Use the “Manually enter computer names and credentials” discovery method as shown in screenshot below

On the “Enter Computers Manually” screen, for each Linux machine, click “Create”, enter the machine name and check “Use specific credential” and provide the account details as shown in below screens.



Click “Add” and then “Save and New” to add additional machines.

Finally, you can see the list of computers you have added, as in the screen below, and proceed further with the remaining steps.

The steps below are common for all discovery methods.



All Computer Credentials:

Add credentials to be used to connect to the discovered machines based on the technology used.

Credentials Order:

Set the sequences of credentials to use for each discover technology.

Connection Properties:

Provide connection properties for each connection technology as, for instance, ports or encryption used.

Summary:

Review the summary screen and click Finish.



After clicking on finish button, MAP tool will start collecting data and it may take between 1 to 15 minutes depending on the environment size.

Finally, you will see the message that data collection got completed as shown in the below screen.

Collecting MAP Toolkit Output

After successfully collecting inventory data, follow the steps below to share MAP tool output with Tech Data for analysis and to produce Discovery Report.

• Open Microsoft Assessment & Planning Kit wizard • Click on File • Click on Manage Databases • Select Database File, in the Pop-up window • Click on Export • Save the File (Naming convention – “Customer Name MAP Output.bak”) • Zip the file and share it with Tech Data • Refer to below screenshot.



3 Azure Site Recovery Deployment Planner

3.1 Objective

The Site Recovery Deployment Planner is a command-line tool for both Hyper-V to Azure and VMware to Azure disaster recovery scenarios. You can remotely profile your VMware VMs by using this tool (with no production impact whatsoever) to understand the bandwidth and storage requirements for successful replication and test failover. You can run the tool without installing any Site Recovery components on-premises. To get accurate achieved throughput results, run the planner on a Windows Server that meets the minimum requirements of the Site Recovery configuration server that you eventually need to deploy as one of the first steps in production deployment.

The main areas of planning covered by ASR Deployment:

• Compatibility assessment • Network bandwidth need versus RPO assessment • Azure infrastructure requirements • On-premises infrastructure requirements • Estimated disaster recovery cost to Azure

The ASR Deployment planner Toolkit is part of the Microsoft Solution Accelerators that provide tested guidance and automated tools to help plan, deploy, and manage new Microsoft technologies. They are all freely available and fully-supported by Microsoft.

ASR Deployment Planner for VMWare

3.2.1 System Requirements

• Operating system: Windows Server 2016 or Windows Server 2012 R2 • Machine configuration: 8 vCPUs, 16 GB RAM, 300 GB HDD • Minimum 100 GB of free disk space (assuming 1,000 VMs with an average of three disks each, profiled for 30

days) • Microsoft .NET Framework 4.5



• Visual C++ Redistributable for Visual Studio 2012 • Administrator access on the server • VMware vSphere PowerCLI 6.0 R3 • VMware vCenter statistics level settings can be 1 or higher level • Allow vCenter port (default 443): Site Recovery Deployment Planner uses this port to connect to the vCenter

server/ESXi host

3.2.2 Installing ASR Deployment Planner

• Download the latest version of Site Recovery Deployment Planner. The tool is packaged in a .zip folder. • Copy the .zip folder to the Windows server from which you want to run the tool and the server should have

network access to connect to the vCenter server/vSphere ESXi host that holds the VMs to be profiled. • Extract the .zip folder. The folder contains multiple files and subfolders. The executable file is

ASRDeploymentPlanner.exe in the parent folder.

Example: Copy the .zip file to E:\ drive and extract it.

E:\ASR Deployment Planner-v2.3.zip

E:\ASR Deployment Planner-v2.3\ASRDeploymentPlanner.exe

3.2.3 Running ASR Deployment Planner

Create a list of VMs to profile

Follow below steps to create a list of VMs for profiling.

• Sign in to the VM that ASR deployment planner and VMware vSphere PowerCLI is installed in. • Create a folder to save the Profiling data. (Example: C:\VMprofilingvmware) • Open the VMware vSphere PowerCLI console. • Ensure that the execution policy is enabled for the script. If it is disabled, launch the VMware vSphere

PowerCLI console in administrator mode, and then enable it by running the following command:

Set-ExecutionPolicy –ExecutionPolicy AllSigned

• You may optionally need to run the following command if Connect-VIServer is not recognized as the name of cmdlet:

Add-PSSnapin VMWare.VimAutomation.Core

• To get all the names of VMs on a vCenter server/vSphere ESXi host run the below two commands:

Syntax: Connect-VIServer -Server <server name> -User <name> -Password <password>

Note: <Server name>: could be one of the following: vCenter Server or IP address / ESXi host or ESXi IP Address. If you have multiple ESXi hosts, you need to run the below two commands for every ESXi host. In below example –Server 172.21.2.110 is my ESXi IP.

Example: Connect-VIServer –Server 172.21.2.110 –User root –Password



Syntax: Get-VM | Select Name | Sort-Object -Property Name > <outputfile.txt>

Example: Get-VM | Select Name | Sort-Object -Property Name > C:\VMprofileVMWare\VMLIST-EXXi.txt

As result of the commands above, a file gets created with all the servers.

Start the Profiling

To start profiling you need to open VMware power CLI command window and navigate to the path where ASR deployment planner is installed.

Syntax:

.\ASRDeploymentPlanner.exe -Operation StartProfiling -Virtualization VMware -Directory “Directory Path” -Server <VcenterHostName/ESXi HostName/IP Address> -VMListFile “VMFile path” -NoOfMinutesToProfile 60 -User UserName

Example:



C:\ASRDeploymentPlanner-v2.3> .\ASRDeploymentPlanner.exe -Operation StartProfiling -Virtualization VMware -Directory “C:\VMprofilingVmware” –Server 172.21.2.110 -VMListFile “C:\VMprofilingVmware\VMList-ESXi01.txt” -NoOfMinutesToProfile 60 -User root

Share Profiling data with Tech Data

After the profiling gets completed, go to the Folder “C:\VMprofilingVMware” and check if you can see one .csv for each VM. ZIP the folder and share with Tech Data.

3.3 ASR Deployment Planner for Hyper-V

3.3.1 System Requirements

• Operating system: Windows Server 2016 or Windows Server 2012 R2 • Machine configuration: 8 vCPUs, 16 GB RAM, 300 GB HDD • Minimum 100 GB of free disk space. • Microsoft .NET Framework 4.5 • Visual C++ Redistributable for Visual Studio 2012 • Administrator access on the server • The VM from where you are running the Azure Site Recovery deployment planner tool must be added to

TrustedHosts list of all the Hyper-V servers. • All Hyper-V servers to be profiled must be added to TrustedHosts list of the client VM from where the tool is

being run. • The tool should be run from Administrative privileges from PowerShell or command-line console on the

client

3.3.2 Installing ASR Deployment Planner

• Download the latest version of Site Recovery Deployment Planner. The tool is packaged in a .zip folder. • Copy the .zip folder to the Windows server from which you want to run the tool. You can run the tool on a

Windows Server 2012 R2 or Windows Server 2016. • Extract the .zip folder. The folder contains multiple files and subfolders. The executable file is

ASRDeploymentPlanner.exe in the parent folder.

Example: Copy the .zip file to E:\ drive and extract it.

E:\ASR Deployment Planner-v2.3.zip

E:\ASR Deployment Planner-v2.3\ASRDeploymentPlanner.exe

3.3.3 Add Servers into Trusted Hosts List



• The VM from where the tool is to be deployed should have all the hosts to be profiled in its Trusted Hosts list. To add the client into Trusted hosts list run the following command in the VM where you installed ASR Deployment Plannerr from an elevated PowerShell

Syntax:

set-item wsman:\localhost\Client\TrustedHosts –value “Hyper-V host1, Hyper-V host2,IP Address” –Concatenate

Note: here, “Hyper-V hosts1” referrers to Host box server name, you can either provide IP address or Hyper-V host name. If you have multiple hostnames, please mention them by ‘,’ separated as shown in the above command.

Example:

set-item wsman:\localhost\Client\TrustedHosts –value “hyperVserver01”

-Concatenate

• Run the following commands in each Hyper-V Host. Each Hyper-V Host that needs to be profiled should

have:

1. The VM on which the tool is going to be run in its TrustedHosts list. Run the following command from an elevated PowerShell on the Hyper-V host.

Syntax:

set-item wsman:\localhost\Client\TrustedHosts -value '<ComputerName>[,<ComputerName>]' –Concatenate

Note:

Here, <ComputerName> is the name of the VM where Deployment planner tool is installed. You can either mention VM name or IP Address.

Repeat Step 2 on each Hyper-V host name

Example:

set-item wsman:\localhost\Client\TrustedHosts -value 'ASRDepServer01' –Concatenate



2. PowerShell remoting enabled

Syntax:

Enable-PSRemoting –Force

3.3.4 Get the Hyper-V VMs list

Create a file with all Hyper-V hosts / IP Address

The first step is to create a .txt file with all the Hyper-V host name or IP address or Hyper-V cluster name or IP address.

• Login into the VM where Deployment Planner tool is installed. • Navigate to any path you wish to save profiling data and create a .txt file to list all Hyper-V host names or IP

Address you wish to assess. “C:\ASRDPlanner\ProfileData” is the folder and HyperVhost.txt is the file.

Example: HyperVhost.txt contains the following servers:

Host_1

10.8.59.27

Cluster_1

Host_2

Get the VM list for profiling

To obtain a list of VMs running on each Hyper-V host, open an elevated PowerShell, navigate to the directory where Deployment Planner tool was installed, and run the below command.

Syntax:

.\ASRDeploymentPlanner.exe –Operation GetVMList –ServerListFile “text file location” –user “Admin account”

Example:

C:\ASR Deployment Planner_v2.3> .\ASRDeploymentPlanner.exe -Operation GetVMList -Directory "C:\ASRDPlanner\ProfiledData" -ServerListFile "C:\ASRDPlanner\ProfiledData\hypervhost.txt" -User hyperVserver01\azureadmin

After executing the command, it will ask you for Password. Please enter the correct password. A file gets created under the directory "C:\ASRDPlanner\ProfiledData" as shown below.



Profile the Hyper-V VMs

If you only want to profile a subset of machines, please edit the file that was created above. To start profiling the detected virtual machines execute the following:

Syntax:

.\ASRDeploymentPlanner.exe -Operation StartProfiling -Virtualization Hyper-V -Directory “Directory Path” -VMListFile “Path of the output VM list text file” -NoOfMinutesToProfile 60 –User “Admin Account”

Example:

C:\ASR Deployment Planner_v2.3> .\ASRDeploymentPlanner.exe -Operation StartProfiling -Virtualization Hyper-V -Directory "C:\ASRDPlanner\ProfiledData" -VMListFile "C:\ASRDPlanner\ProfiledData\vmlist.txt" -NoOfMinutesToProfile 60 -User hyperVserver01\Azureadmin

Share Profiling data with Tech Data

After the command gets executed successfully, you can go to the folder “C:\ASRDPlanner\ProfiledData” and verify if you get the files with the server names, zip the folder (ProfiledData) and share with Tech Data.

microsoft assessment & planning tool (map) and asr deployment … · 2020. 7. 14. · asr...

Documents