- [Instructor] Hello and welcome back. In this short lecture we're going to install the Migration Hub Discovery Agent. To discover resources using an agent you first need to download the agent and install it on a server that is part of the server fleet you wish to discover and ideally migrate to AWS. So, first off, let's choose Download the Agent from the Migration Hub dashboard and then in the dropdown select either the Windows Agent or the Linux Agent, so those are the two platforms the agent will run on. Today we're going to install the Discovery Agent on a Windows machine. So, first to do this we need to download and install the Microsoft Visual C++ runtime for the x86 environment and then we can download the Windows Agent Installer. So, first off, let's install the x86 version of the library and that has a file name vc_redist.x86.exe. No point using the vc_redist.x64.exe version 'cause that won't work as I discovered when I did this. The C++ runtime will run regardless of the architecture of the machine that you're installing it on if you use the x86 version, not so if you use the x64 version. Okay, once we have the C++ library installed, we can download and install the MSI Installer for the agent code. So, first of all, we need to as the administrator open the command prompt on our Windows machine and navigate to the location where we saved the installation package once we've downloaded it. To install the agent we need to run it as a command line entry, so run msiexec.exe/i AWSDiscoveryAgentInstaller.msi which is the MSI package, space REGION equals us-west 2, space KEY_ID equals YOUR KEY ID, your AWS KEY ID space KEY_SECRET and add your secret key /q. Now, once that's installed, agents automatically download and apply updates as they become available and that may not be ideal for your environment. It's a great feature which I recommend leaving on but if you do want to disable it for any reason, i.e. to avoid downloading agents and applying updates automatically which could mess with some of your setup, for example, then include the AUTO_UPDATE equals false parameter when you run your installation. Now, remember, these agents need outbound access to send data back to the Migration Hub in the US West region. So, if outbound connections from your network are restricted by either the machine or by your firewall, you're going to need to update your firewall settings. Now, agents require access to a host in the Amazon AWS domain and they need that access on port 443. They don't need any inbound ports to be open, so it's outbound egress only and agents will also work with transparent web proxies. Now, as with any agent setup, there's usually a few things that go wrong. I certainly have struck a few rocks when I was setting this up. So, if you encounter problems while installing it or using the application Discovery Agent or especially on Windows, check your installation logs first. That's the definitely the one source of truth for what went wrong. So, the msiexec command can fail for example, the Windows Service Manager may be showing that the Discovery Service has not been created, so add a /L*V to turn on verbose installation logging and then if you're up and running, we can stop and start the server from the Server Manager. You can also look at operational logs on the Windows Server 2008 runtime. The agent log files can be found under C:\ProgramData\AWS\AWS Discovery\Logs and on Windows Server 2003 the agent logs can be found under C:\Documents and settings\All Users\Application Data \AWS\AWSDiscovery\Logs. So, log files are named to indicate whether generated by the main service, automatic upgrader or by the installer. Now, the configuration file for the agent is located in C:\ProgramData\AWS\AWSDiscovery\Config. All right, so after you've successfully installed the agent, return to the Data Collector's page on the Migration Hub console and choose the Refresh icon. From here you can select the agents which you wish to start by turning on the Select box and then choose Start Data Collection. If you want to install additional agents, then you can deploy new discovery agents from the Migration Hub dashboard. Okay, so that closes our installation of the agent lecture.