Steps for Installing and Configuring System Center 2012 Virtual Machine Manager R2

1.     Right-click ADKSetup.exe, and then click Run as administrator.

2.     Click Install the Assessment and Deployment Kit to this computer, specify the location where you want to install the Windows ADK features, and then click Next.

3.     On the CEIP screen, click Next.

4.     Click Accept to accept the license agreement.

5.     On the feature selection screen, select Deployment Tools and Windows Preinstallation Environment (Windows PE). Click Install.

6.     Wait for the installation to complete, and then click Close.

1.     Insert the SQL Server installation media. From the root folder, double-click Setup.exe. To install from a network share, locate the root folder on the share, and then double-click Setup.exe.

2.     The Installation Wizard runs the SQL Server Installation Center. To create a new installation of SQL Server, click Installation in the left-hand navigation area, and then click New SQL Server stand-alone installation or add features to an existing installation.

3.     The System Configuration Checker runs a discovery operation. To continue, click OK. You can view the details on the screen by clicking Show Details, or as an HTML report by clicking View detailed report.

4.     On the Product Key page, select an option to indicate whether you are installing a free edition of SQL Server, or a production version of the product that has a PID key.

5.     To continue, click Next.

6.     On the License Terms page, review the license agreement, select the I accept the license terms check box, and then click Next. To help improve SQL Server, you can also enable the feature usage option and send reports to Microsoft.

7.     On the Product Updates page, the latest available SQL Server product updates are displayed. If you don't want to include the updates, clear the Include SQL Server product updates check box. If no product updates are discovered, SQL Server Setup does not display this page and auto advances to the Install Setup Files page.

8.     On the Install Setup files page, Setup provides the progress of downloading, extracting, and installing the Setup files. If an update for SQL Server Setup is found, and is specified to be included, that update will also be installed.

9.     On the Setup Support Rules page, click Next.

10.  On the Setup Role page, select SQL Server Feature Installation, and then click Next.

11.  On the Feature Selection page, under Instance Features, select Database Engine Services. Click Next to continue.

12.  On the Installation Rules page, Setup verifies the system state of your computer before Setup continues. Click Next to continue.

13.  On the Instance Configuration page, specify Default instance. Click Next to continue.

14.  Click Next on the Disk Space Requirements page.

15.  On the Server Configuration page, click Next.

16.  On the Server Configuration tab of the Database Engine Configuration page, click Add Current User to specify a SQL Server administrator, and then click Next.

17.  On the Error Reporting page, specify the information that you want to send to Microsoft that will help improve SQL Server. Click Next.

18.  The System Configuration Checker will run a set of rules to validate your computer configuration with the SQL Server features that you have specified. Click Next.

19.  The Ready to Install page shows a tree view of installation options that were specified during Setup. On this page, Setup indicates whether the Product Update feature is enabled or disabled and the final update version. To continue, click Install. SQL Server Setup will first install the required prerequisites for the selected features followed by the feature installation.

20.  During installation, the Installation Progress page provides status so that you can monitor installation progress as Setup continues.

21.  After installation, the Complete page provides a link to the summary log file for the installation and other important notes. To complete the SQL Server installation process, click Close.

1.     To start the Virtual Machine Manager Setup Wizard, on your installation media, right-click setup.exe, and then click Run as administrator.

Note

Before beginning the installation of VMM, close any open programs and ensure that there are no pending restarts on the computer. For example, if you have installed a server role by using Server Manager or have applied a security update, you may need to restart the computer and then log on to the computer with the same user account to finish the installation of the server role or the security update.

2.     On the main setup page, click Install.

3.     If you have not installed Microsoft .NET Framework, VMM will prompt you to install now.

4.     On the Select features to install page, select the VMM management server check box, and then click Next.

Note

The VMM console is automatically installed when you install a VMM management server.

5.     On the Product registration information page, provide the appropriate information, and then click Next.

6.     On the Please read this license agreement page, review the license agreement, select the I have read, understood, and agree with the terms of the license agreement check box, and then click Next.

7.     On the Join the Customer Experience Improvement Program (CEIP) page, select either option and then click Next.

8.     On the Microsoft Update page, select whether to deliver VMM updates automatically, and then click Next.

9.     On the Installation location page, use the default path or type a different installation path for the VMM program files, and then click Next.

10.  The computer on which you are installing the VMM management server will be checked to ensure that the appropriate hardware and software requirements are met. If a prerequisite is not met, a page will appear with information about which prerequisite has not been met and how to resolve the issue. If all prerequisites have been met, the Database configuration page appears.

11.  On the Database configuration page, do the following:

Specify WNVHOST2 as the server name.

Leave the Port box empty.

Select New database, and accept the default name VirtualManagerDB.

Click Next.

12.  On the Configure service account and distributed key management page, select Local System account. Click Next.

13.  On the Port configuration page, use the default port numbers, and then click Next.

Important

The ports that you assign during the installation of a VMM management server cannot be changed without uninstalling and reinstalling the VMM management server.

14.  On the Library configuration page, ensure that Create a new library share is selected, and then click Next.

Note

The default library share created by VMM is named MSSCVMMLibrary and the folder is located at %SYSTEMDRIVE%\ProgramData\Virtual Machine Manager Library Files. ProgramData is a hidden folder.

After the VMM management server is installed, you can add library shares and additional library servers by using the VMM console or by using the VMM command shell.

15.  On the Installation summary page, review your selections and then click Install to install the VMM management server.

16.  After you click Install, the Installing features page appears and installation progress is displayed. On the Setup completed successfully page, click Close to finish the installation.

17.  To open the VMM console, ensure that the Open the VMM console when this wizard closes check box is selected.

Note

If there is a problem with setup completing successfully, consult the log files in the %SYSTEMDRIVE%\ProgramData\VMMLogs folder. ProgramData is a hidden folder.

1.     From the desktop shortcut on WNVHOST2, click Virtual Machine Manager Console.

2.     Click Connect.

3.     Open the Fabric workspace.

4.     In the Fabric pane, expand Servers, and then select All Hosts.

5.     On the Home tab, in the Add group, click Add Resources, and then click Hyper-V Hosts and Clusters. The Add Resource Wizard starts.

6.     On the Resource location page, click Windows Server computers in a trusted Active Directory domain, and then click Next.

7.     On the Credentials page, next to Run As account, click Browse.

8.     In the Select a Run As Account dialog, click Create Run As Account. Next to name, type Adatum User1. Next to User name, type CORP\User1. Type the password for User1, and then confirm the password. Click OK.

9.     In the Select a Run As Account dialog, select Adatum User1, and then click OK.

10.  On the Credentials page, click Next.

11.  On the Discovery Scope page, click Specify Windows Server computers by names. In the Computer names box, enter WNVHOST1, WNVHOST2, and WNVHOST3. Type each server name on its own line in the entry window. Select the checkbox for Skip AD verification and then click Next.

12.  On the Target resources page, click Select all to select WNVHOST1.corp.adatum.com, WNVHOST2.corp.adatum.com, and WNVHOST3.corp.adatum.com, and then click Next. Click OK in the resultant dialog prompt.

13.  On the Host settings page, click Next.

14.  On the Summary page, confirm the settings, and then click Finish.

15.  The Jobs dialog box appears to show the job status. Make sure that the job has a status of Completed w/ Info, and then close the dialog box.

16.  To verify that the host servers were successfully added, in the Fabric pane, select All Hosts, and then in the Hosts pane, verify that the host status for each server is listed as OK.

1.     In the Fabric pane, expand Networking, and then click Logical Networks. Logical networks represent an abstraction of the underlying physical network infrastructure. By default, when you add a Hyper-V host to VMM management, VMM automatically creates logical networks that match the first DNS suffix label of the connection-specific DNS suffix on each host network adapter. Since we added connection-specific DNS suffixes to the host adapters, they are easily identified in this interface.

2.     In the Logical Networks detail pane, right-click the logical network named corp, and then click Properties.

3.     Change the Name value to Management. Click Network Site. Under Network sites, click Add.

4.     Under Host groups that can use this network site, select All Hosts.

5.     Under Associated VLANs and IP subnets, click Insert row. Type 192.168.0.0/24 under IP subnet. Click OK.

1.     In the Fabric pane, expand Networking, and then click Logical Networks.

2.     Right-click Management, and then click Create IP Pool.

3.     The Create Static IP Address Pool Wizard opens.

4.     On the Name page, enter Management IP Pool as the name. Click Next.

5.     In the Network Site page, verify that Use an existing network site is selected, and that Management_0 is selected with IP subnet 192.168.0.0/24.

6.     Click Next.

7.     On the IP address range page, change the Starting IP address to 192.168.0.100. Change Ending IP address to 192.168.0.200. Click Next.

8.     On the Gateway page, click Next.

9.     On the DNS page, click Next.

10.  On the WINS page, click Next.

11.  On the Summary page, click Finish.

1.     In the Logical Networks detail pane, right-click the logical network named isp, and then click Properties.

2.     Change the Name value to Internet. Next to Description, type External Networks.

3.     Click Network Site. Under Network sites, click Add.

4.     Under Host groups that can use this network site, select All Hosts.

5.     Under Associated VLANs and IP subnets, click Insert row. Type 131.107.0.0/24 under IP subnet. Click OK.

1.     Right-click Logical Networks, and then click Create Logical Network. The Create Logical Network wizard launches.

2.     Next to Name, type Back End (NetVirt). Next to Description, type Tenant Networks. Select the checkbox box Allow new VM networks created on this logical network to use network virtualization.

3.     Click Next. Under Network sites, click Add.

4.     Under Host groups that can use this network site, select All Hosts.

5.     Under Associated VLANs and IP subnets, click Insert row. Type 172.16.1.0/24 under IP subnet. Click Next.

6.     On the Summary page, click Finish.

1.     In the Fabric pane, expand Networking, and then click Logical Networks.

2.     Right-click Back End (NetVirt), and then click Create IP Pool.

3.     The Create Static IP Address Pool Wizard opens.

4.     On the Name page, enter NetVirt IP Pool as the name. Click Next.

5.     In the Network Site page, verify that Use an existing network site is selected, and that Back End (NetVirt)_0 is selected with IP subnet 172.16.1.0/24.

6.     Click Next.

7.     On the IP address range page, change the Starting IP address to 172.16.1.100. Change Ending IP address to 172.16.1.200. Click Next.

8.     On the Gateway page, click Next.

9.     On the DNS page, click Next.

10.  On the WINS page, click Next.

11.  On the Summary page, click Finish.

1.     Open the Fabric workspace.

2.     In the Fabric pane, expand Servers, and then select All Hosts.

3.     Right-click WNVHOST3 in the details pane, and then click Properties.

4.     Click Hardware, and then scroll to the Network Adapters section.

5.     Under the Internet network adapter, click Logical network connectivity. Select the Internet logical network and the 131.107.0.0/24 network subnet.

6.     Under the Hosternet network adapter, click Logical network connectivity. Select both the Back End (NetVirt) subnet on 172.16.1.0/24 and the Management subnet on 192.168.0.0/24.

7.     Click OK to close the WNVHOST3 Properties dialog.

8.     Right-click WNVHOST2, and then click Properties.

9.     Click Hardware, and then scroll to the Network Adapters section.

10.  Under the Hosternet network adapter, click Logical network connectivity. Select both the Back End (NetVirt) subnet on 172.16.1.0/24 and the Management subnet on 192.168.0.0/24.

11.  Click OK to close the WNVHOST2 Properties dialog.

12.  Right-click WNVHOST1, and then click Properties.

13.  Click Hardware, and then scroll to the Network Adapters section.

14.  Under the Hosternet network adapter, click Logical network connectivity. Select both the Back End (NetVirt) subnet on 172.16.1.0/24 and the Management subnet on 192.168.0.0/24.

15.  Click OK to close the WNVHOST1 Properties dialog.

1.     Open the VMs and Services workspace.

2.     Under VMs and Services, select VM Networks.

3.       Right-click the VM Network named corp, and then click Properties.

4.       On the Name page, change the name to Management, and then in the Logical network list, select Management. Click OK.

5.       Right-click the VM Network named isp, and then click Properties.

6.       On the Name page, change the name to Internet, and then in the Logical network list, select Internet. Click OK.

1.       In Virtual Machine Manager Console, on the Home tab, in the Window group, click PowerShell. A VMM PowerShell console launches.

2.     Type the following command and then press ENTER to configure the WNVHOST3 Hyper-V server as a dedicated gateway host in VMM.

set-scvmhost -VMHost wnvhost3.corp.adatum.com -IsDedicatedToWNVGateway $true

1.     In Virtual Machine Manager Console on WNVHOST2, open the Fabric workspace.

2.     In the Fabric pane, expand Networking, and then select Network Service.

3.     Right-click Network Service, and then click Add Network Service. The Add Network Service Wizard launches.

4.     In Name, type Gateway1, and then click Next.

5.     On the Manufacturer and Model page, select Microsoft as the Manufacturer and Microsoft Windows Server Gateway as the Model, and then click Next.

6.     On the Credentials page, click Browse. Select the Adatum User1 account, and then click OK. Click Next.

7.     On the Connection String page, type VMHost=wnvhost3.corp.adatum.com;RRASServer=GatewayVM1.corp.adatum.com and then click Next.

8.     On the Certificates page, click Next.

9.     On the Provider page, click Test.

10.  Verify that no failures are recorded, and then click Next.

11.  On the Host Group page, select All Hosts, and then click Next.

12.  On the Summary page, click Finish. Wait for the Jobs dialog to display the Add network service device status as Completed. Close the Jobs dialog.

13.   In the Fabric pane, select Network Service.

14.  Verify that Gateway1 is listed in the details pane. Right-click Gateway1, and then click Properties.

15.  Click Connectivity in the console tree.

16.  Select Enable front end connection. Next to Front end network adapter, select Internet. Next to Front end network site, select Internet_0.

17.  Select Enable back end connection. Next to Back end network adapter, select Back End. Next to Back end network site, select Back End (NetVirt)_0.

18.  Click OK to close the Gateway1 Properties dialog.

19.  Switch to the Jobs workspace and wait for the Add gateway connection for Network gateway job to complete.

1.       Open the VMs and Services workspace.

2.       In the VMs and Services pane, click VM Networks.

3.       On the Home tab, in the Create group, click Create VM Network.

4.       The Create VM Network Wizard opens.

5.       On the Name page, enter Contoso VM Network, and then in the Logical network list, select Back End (NetVirt). Click Next.

6.       On the Isolation page, select Isolate using Hyper-V network virtualization, and then click Next.

7.       On the VM Subnets page, click Add, enter Contoso VM Subnet as the name for the IP subnet and specify the subnet by using CIDR notation 10.0.1.0/24. Click Next.

8.       On the Connectivity page, select Connect to another network through a VPN tunnel, and select Connect directly to an additional logical network using Direct routing. Verify that Gateway1 is selected as the Gateway device, and then click Next.

9.       On the VPN Connections page, next to Subnet, type 10.254.254.0/29. Under Specify VPN connections, click Add.

10.   Next to Name, type Contoso VPN Connection.

11.   Next to Remote endpoint, type 131.107.0.2.

12.   Click Authentication. Select Authenticate using the following credentials, and then click Browse.

13.   In the Select a Run As account dialog, click Create Run As Account.

14.   In the Create Run As Account dialog, Next to Name, type Contoso User1 Account. Next to User name, type User1@corp.contoso.com, and then type and confirm the password for User1. Clear the checkbox for Validate domain credentials, and then click OK.

15.   In the Select a Run As account dialog, verify that Contoso User1 Account is selected, and click OK.

16.   Click Routes, and then click Add. Type 10.0.0.0/24, under Subnet, and then click Next.

17.   On the Summary page, click Finish.

18.   The Jobs dialog box appears to show the job status. Make sure that the job has a status of Completed, and then close the dialog box.

1.       In the VMs and Services pane, click VM Networks.

2.       On the Home tab, in the Create group, click Create VM Network.

3.       The Create VM Network Wizard opens.

4.       On the Name page, enter Fabrikam VM Network, and then in the Logical network list, select Back End (NetVirt). Click Next.

5.       On the Isolation page, select Isolate using Hyper-V network virtualization, and then click Next.

6.       On the VM Subnets page, click Add, enter Fabrikam VM Subnet as the name for the IP subnet and specify the subnet by using CIDR notation 10.0.1.0/24. Click Next.

7.       On the Connectivity page, select Connect to another network through a VPN tunnel, and select Connect directly to an additional logical network. Verify that Gateway1 is selected, and then click Next.

8.       On the VPN Connections page, next to Subnet, type 10.254.254.0/29. Under Specify VPN connections, click Add.

9.       Next to Name, type Fabrikam VPN Connection.

10.   Next to Remote endpoint, type 131.107.0.5.

11.   Click Authentication. Select Authenticate using the following credentials, and then click Browse.

12.   In the Select a Run As account dialog, click Create Run As Account.

13.   In the Create Run As Account dialog, Next to Name, type Fabrikam User1 Account. Next to User name, type User1@corp.fabrikam.com, and then type and confirm the password for User1. Clear the checkbox for Validate domain credentials, and then click OK.

14.   In the Select a Run As account dialog, verify that Fabrikam User1 Account is selected, and click OK.

15.   Click Routes, and then click Add. Type 10.0.0.0/24, and then click Next.

16.   On the Summary page, click Finish.

17.   The Jobs dialog box appears to show the job status. Make sure that the job has a status of Completed, and then close the dialog box.

18.  Verify that the VM networks Contoso VM Network and Fabrikam VM Network appear in the VM Networks and IP Pools pane.

1.       Open the VMs and Services workspace.

2.       On the Home tab, in the Show group, click VM Networks.

3.     Right-click Contoso VM Network, and then click Create IP Pool.

4.     The Create IP Pool Wizard opens.

5.     In Name, type Contoso IP Pool. Select Contoso VM Network and Contoso VM Subnet (10.0.1.0/24). Click Next.

6.     On the IP address range page, change Starting IP address to 10.0.1.100, change Ending IP address to 10.0.1.200, and then click Next.

7.     On the Gateway page, click Next.

8.     On the DNS page, next to DNS server address, click Insert. Type a DNS Server address of 10.0.0.1. Next to DNS suffix, click Insert. Type a DNS suffix of corp.contoso.com. Click Next.

9.     On the WINS server page, click Next.

10.  On the Summary page, click Finish.

11.   The Jobs dialog box appears to show the job status. Make sure that the job has a status of Completed, and then close the dialog box.

12.  Right-click Fabrikam VM Network, and then click Create IP Pool.

13.  The Create IP Pool Wizard opens.

14.  In Name, type Fabrikam IP Pool. Select Fabrikam VM Network and Fabrikam VM Subnet (10.0.1.0/24). Click Next.

15.  On the IP address range page, change Starting IP address to 10.0.1.100, change Ending IP address to 10.0.1.200, and then click Next.

16.  On the Gateway page, click Next.

17.  On the DNS page, next to DNS server address, click Insert. Type a DNS Server address of 10.0.0.1. Next to DNS suffix, click Insert. Type a DNS suffix of corp.fabrikam.com. Click Next.

18.  On the WINS server page, click Next.

19.  On the Summary page, click Finish.

20.   The Jobs dialog box appears to show the job status. Make sure that the job has a status of Completed, and then close the dialog box.

21.  Verify that the VM networks Contoso VM Network and Fabrikam VM Network appear in the VM Networks and IP Pools pane with associated IP pools of 10.0.1.0/24.

1.     On WNVHOST2, in the Dashboard console of Server Manager, click Add roles and features.

2.     Click Next four times to get to the Features selection screen.

3.     In the Select features dialog, select IP Address Management (IPAM) Server, click Add Features when prompted, and then click Next.

4.     On the Confirmation screen, select Restart the destination server automatically if required, and then click Install.

5.     Allow the installation to complete, and then click Close.

1.     On the Server Manager menu, click Tools and then click Windows PowerShell.

2.     Type the following command at the Windows PowerShell prompt, and then press ENTER.

Invoke-IpamGpoProvisioning -Domain corp.adatum.com -GpoPrefixName IPAMGPO -DelegatedGpoUser User1 -IpamServerFqdn wnvhost2.corp.adatum.com -Force

3.     In Server Manager on WNVHOST2, click IPAM in the console tree.

4.     Verify that you are connected to WNVHOST2.corp.adatum.com.

5.     Click Provision the IPAM server.

6.     In the Provision IPAM wizard, click Next.

7.     On the Configure database screen, leave Windows Internal Database selected, and click Next.

8.     On the Select provisioning method screen, select Group Policy Based, and next to GPO name prefix, type IPAMGPO. Click Next.

9.     On the Summary screen, click Apply.

10.  In the Completion dialog box, confirm that IPAM provisioning completed successfully, and then click Close.

11.  Under IPAM Server Tasks, click Configure server discovery.

12.  In the Configure Discovery Settings wizard, next to (root domain) corp.adatum.com, click Add.

13.  Click OK to apply the discovery scope.

14.  Under IPAM Server Tasks, click Start server discovery.

15.  Click Server Inventory in the console tree. When the discovery process completes, the console should show WNVHOST1 as a discovered server. Note that Manageability Status is displayed as Unspecified, and IPAM access status is Blocked. In order to apply the GPO setting configured previously, you must set manageability status for the server.

16.  Right-click the entry for WNVHOST1, and click Edit Server.

17.  In the Add or Edit Server dialog, change Manageability status to Managed. Click OK.

18.  The IPAM settings will be applied the next time group policy is applied to WNVHOST1. To speed up this process, you can switch to WNVHOST1 and run gpupdate or restart the server.

19.  After updating policy on WNVHOST1, right-click WNVHOST1 in the IPAM Server Inventory console, and then click Refresh Server Access Status.

20.  Once IPAM Access Status shows as Unblocked, right-click the WNVHOST1 entry and click Retrieve All Server Data.

1.     In Virtual Machine Manager Console on WNVHOST2, open the Fabric workspace.

2.     In the Fabric pane, expand Networking, and then select Network Service.

3.     Right-click Network Service, and then click Add Network Service. The Add Network Service Wizard launches.

4.     In Name, type IPAM, and then click Next.

5.     On the Manufacturer and Model page, select Microsoft as the Manufacturer and Microsoft Windows Server IP Address Management as the Model, and then click Next.

6.     On the Credentials page, click Browse. Select the Adatum User1 account, and then click OK.

7.     Click Next.

8.     On the Connection String page, type WNVHOST2.corp.adatum.com, and then click Next.

9.     On the Provider page, click Test. In the test results pane, verify that Connection API, Capability discovery API, and Retrieve system info API are shown as Implemented, and that no tests failed. Click Next.

10.  On the Host Group page, select All Hosts, and then click Next.

11.  On the Summary page, click Finish.

1.     In Server Manager on WNVHOST2, click IPAM in the console tree.

2.     In the IPAM console, click Virtualized IP Address Space.

3.     Examine the IP address ranges for the virtualized address space. These address ranges were automatically imported to the IPAM database from VMM.