Export (0) Print
Expand All

Preinstallation Tasks

Updated: September 1, 2011

Applies To: Active Directory Federation Services (AD FS) 2.0

The instructions in this guide do not walk you through the steps for how to create the four base VMs required for this lab. Therefore to proceed with this guide, you must first use the How to Set Up the AD FS 2.0 VM Lab Environment for Federated Collaboration (http://go.microsoft.com/fwlink/?LinkId=205539) guide to create the VMs necessary for this test lab environment.

Administrative credentials

To perform all the tasks in this guide, log on to the virtual server computer—and to each of the four VMs that you create on it—with the local Administrator account for each computer.

Once you have created your four base VMs using the instructions provided in the How to Set Up the AD FS 2.0 VM Lab Environment for Federated Collaboration (http://go.microsoft.com/fwlink/?LinkId=205539) guide, you will need to use the following procedures to create a virtual network in Hyper-V™ and import the VMs.

noteNote
You can import the VMs only on a Windows Server® 2008 R2 computer.

The following table specifies the recommended RAM allocation for each VM along with what is installed, and the appropriate VM names to use for best results when you import the four VMs that you created using the federated collaboration how to guide.

 

VM Name RAM Software installed IP configuration

CONTOSOSRV01

1.5 GB

Operating system: Windows Server 2008 R2 Enterprise

Roles: AD DS, AD CS, DNS, AD RMS

10.0.0.1/8
(AD DS, DNS, AD CS)

10.0.0.20/8
(AD FS 2.0)

10.0.0.30/8 (AD RMS)

FABRIKAMSRV01

1.5 GB

Operating system: Windows Server 2008 R2 Enterprise

Roles: AD DS, AD CS, DNS

10.0.0.101/8
(AD DS, DNS, AD CS)

10.0.0.120/8
(AD FS 2.0)

CONTOSOSRV02

1.5 GB

Operating system: Windows Server 2008 R2 Enterprise

Applications: Microsoft Office SharePoint Server 2007 SP1

10.0.0.2/8 (internal)

10.0.0.40/8 (external)

FABRIKAMSRV02

1.5 GB

Operating system: Windows Server 2008 R2 Enterprise

Applications: Microsoft Office Professional 2007

10.0.0.110/8

  1. On the host computer, open Hyper-V Manager.

    To open Hyper-V Manager, on the Start menu, point to Administrative Tools, and then click Hyper-V Manager.

  2. In Hyper-V Manager, on the Action menu, click Virtual Network Manager.

  3. In Virtual Network Manager, click Internal for the type of virtual network that you want to create, and then click Add.

  4. In New Virtual Network, for Name type Internal-Network, verify that for Type the Internal only option is selected, and then click OK.

    Note that the network name is case sensitive and should be entered exactly as provided above. All four VMs will need to use this network, which will be a "local only" interface. All four VM images should already be IP configured as described in the previous table.

  1. In Hyper-V Manager, on the Action menu, click Import Virtual Machine.

  2. In the Import Virtual Machine dialog box, click Browse.

  3. In the Select Folder dialog box, browse and locate the named folder for the VM that you want to import.

    For example, to import the CONTOSOSRV01 VM, navigate to c:\VM and select ContosoSrv01 folder and click Select Folder.

  4. For the Settings, keep Move or restore the virtual machine setting selected.

  5. Click Import to begin importing the VM.

  6. Repeat these steps for each VM until all VMs have been imported.

We recommend that you not start all four VMs at the same time. Instead, it’s preferable for performance reasons to start each VM by itself. When the VM is turned on and running, start another VM. Also, the order in which you start VMs by using Hyper-V Manager is important. For best results, start the four VMs one at a time in the following order: CONTOSOSVR01, FABRIKAMSRV01, CONTOSOSRV02, FABRIKAMSRV02.

If, after turning the VM on and logging in, you are prompted to restart the VM, choose to restart.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft