rver to be installed (this was discussed in the previous recipe). Additionally, you will need a Run As account created in VMM that has the following permissions on the IPAM server: IPAM ASM Administrators: This is a local group that exists on all IPAM servers and provides permissions for IP address space management (ASM) Remote Management Users: This is a built-in group that provides access to WMI resources through management protocols, such as WS-Management through the Windows Remote Management service In this case, a new user called SVC_VMMlpam was created in the ad. demo com domain and manually added to the two groups above on the IPAM server. This account was added to VMM as a new Run As account called VMM-IPAM. How to do it.. The following diagram shows you the high-level steps involved in this recipe: Overview of Recipe: Prerequisites (not covered by this recipe): Actions: Adding the new IPAM server to VMM 1. In the VMM Console, navigate to Fabric I Networking I Network Service. Right-click on Network Service and click on Add Network Service. 2. Enter a name for this connection; in this case, it is DEMO-IPAM01. Click on Next. Chapter 4 3. On the Manufacturer and Model page, select Microsoft as Manufacturer and Microsoft Windows Server IP Address Management as Model, as shown in the following screenshot. Click on Next. Specify manufacturer and model of network service Manufacturer: Microsoft Model: Microsoft Windows Server IP Address Management Configuration provider: Microsoft IP Address Management Provider If you are adding a gateway, after you complete this wizard, right-click the listing for the gateway, click Properties, and fill in the connectivity properties for the gateway. 4. Select the Run As account you created earlier; in this case, VMM-IPAM. Click on Next. Enter the FQDN of the IPAM server; in this case, DEMO - IPAM01 ad. demo com. Click on Next. Ensure the Configuration provider field is set to Microsoft IP Address Management Provider and click on Test. If the test comes back successful, click 