I use Hyper-V in my LAB and that's what all these virtual machines will be running on. In my lab, I have Windows Server 2012 Datacenter installed as the server OS on the host machine. All other virtual machines will be running Windows Server 2012 Standard edition, with the graphical user interface (GUI).
My hardware consists of the following:
§ Intel Xeon E5-2620
§ Asus P90X79 WS
§ 64 GB G.Skill Ripjaws Z Series
§ 2 x 256 GB / 1 x 512 GB Samsung 840 Pro Series SSD
§ 1 x 150 GB HDD, and 1 x 250 GB HDD
High Level Plan
Here is a high level of what we are going to complete in this initial part of the series.
1. Create the Lab Environment
2. Install the Operating System
3. Install Active Directory Domain Services
4. Install SQL Server
5. Install System Center App Controller
So now let’s start with the first part, system requirements and creating the lab environment.
System Requirements
Note: The following page on TechNet describes the requirements for deploying AppController.
Server
§ OS: Windows Server 2008 R2 or Windows Server 2012
§ CPU: Dual-Processor, Dual-Core, 2.8 GHz (x64) or greater
§ RAM: 1 gigabyte (GB) of RAM minimum, 4 GB or more recommended
§ HDD: 1 gigabyte (GB) of available hard disk space
§ Software:
o Microsoft SQL Server 2008 R2 or Microsoft SQL Server 2012:
§ Database Engine Service
§ SQL_Latin1_General_CP1_CI_AS collation
o Microsoft .NET Framework 4.0
o Web Server (IIS):
§ Static Content
§ Default Document
§ Directory Browsing
§ HTTP Errors
§ ASP.NET
§ .NET Extensibility
§ ISAPI Extensions
§ ISAPI Filters
§ HTTP Logging
§ Request Monitor
§ Tracing
§ Basic Authentication
§ Windows Authentication
§ Request Filtering
§ Static Content Compression
§ IIS Management Console
o VMM Console
Create the Lab Environment:
Hyper-V Configuration
As mentioned, my environment uses Hyper-V. So, we’re going to start by configuring Hyper-V for our needs, and creating the Virtual Machines (VMs) required for our lab.
The first thing we need to do is setup a Virtual Switch for the VMs to connect through.
Launch Server Manager, click on Tools, and select Hyper-V Manager.
When Hyper-V loads, it will have nothing in it. Even if we were to create a VM, it wouldn’t have a network connection to use.
So we’ll start with creating a Virtual Switch. As you can from my screenshot, I have 2 LAN ports on my host. One of them has a connection to my home network and the Internet.
In the Hyper-V Manager, click the Virtual Switch Manager from the Actions pane.
Now, click on the Create Virtual Switch button.
From here, you now need to configure the virtual switch that your VMs will use. Give it a name to clearly identify it (in my case I called it ‘External Network’), and choose the connection type. For more information about virtual networks, see the following TechNet article: http://technet.microsoft.com/en-us/library/cc816585(v=ws.10).aspx.
Here is an excerpt from the article:
External virtual networks. Use this type when you want to provide virtual machines with access to a physical network to communicate with externally located servers and clients. This type of virtual network also allows virtual machines on the same virtualization server to communicate with each other. This type of network may also be available for use by the management operating system, depending on how you configure the networking. (The management operating system runs the Hyper-V role.) For more information, see “A closer look at external virtual networks” later in this topic.
Internal virtual networks. Use this type when you want to allow communication between virtual machines on the same virtualization server and between virtual machines and the management operating system. This type of virtual network is commonly used to build a test environment in which you need to connect to the virtual machines from the management operating system. An internal virtual network is not bound to a physical network adapter. As a result, an internal virtual network is isolated from all external network traffic.
Private virtual networks. Use this type when you want to allow communication only between virtual machines on the same virtualization server. A private virtual network is not bound to a physical network adapter. A private virtual network is isolated from all external network traffic on the virtualization server, as well any network traffic between the management operating system and the external network. This type of network is useful when you need to create an isolated networking environment, such as an isolated test domain.
For our demonstration, we are going to use an External Network so that the VMs can communicate with the Host system. Make all the appropriate selections and so forth, and then press OK. You may encounter the following warning message. This is because we are remotely connecting to the Host machine using the same network connection that we are about to setup as a Virtual Switch (hence selecting the ‘Allow management operating system to share this network adapter’ checkbox). Press ‘Yes’ to the dialog.
Now that we have the virtual switch setup, we can start creating VMs for our lab.
Create the Virtual Machines
Let’s now create the VM’s we will need for the lab, specifically one for Active Directory, and another for App Controller (since we are install all roles within the same server).
In Hyper-V Manager, from the Actions pane, click on New and choose Virtual Machine.
On the New Virtual Machine wizard beginning screen, click read the information presented and then click Next.
Enter a name for the VM. Note that this is NOT the name the VM will have within the Operating System (unless you name it the same), but rather, used as an identifier in Hyper-V Manager. After you have entered a name, click Next.
Now assign the amount of memory you want your VM to have, and then press Next.
This is the screen where you connect your VM to the network that we created, then press Next.
This is the screen where you configure how large a hard drive the VM will have. Make the appropriate customizations and click Next.
For the Installation Options, choose if you will install an OS later, or if you want to use an ISO, then click Next.
On the Summary screen, review your selections and entries, and click Finish.
Once the VM is created, it will appear in the Hyper-V Manager.
If you want to configure further settings, like the number of CPUs and mounting an OS ISO, right click on the VM and choose Settings or click on Settings from the Actions pane.
Repeat these steps for each VM you need to create, in our case one for Active Directory and another for App Controller.
Here are the settings I have used for each of the VM’s:
Active Directory:
§ Virtual Machine Name: AD
§ Memory: 2048 MB
o NOTE: Active Directory doesn’t need 2 GB of RAM, it will run fine with 512 MB. I just increased the RAM so that the OS would install/respond faster during setup.
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.
Introduction:
I use Hyper-V in my LAB and that's what all these virtual machines will be running on. In my lab, I have Windows Server 2012 Datacenter installed as the server OS on the host machine. All other virtual machines will be running Windows Server 2012 Standard edition, with the graphical user interface (GUI).
My hardware consists of the following:
§ Intel Xeon E5-2620
§ Asus P90X79 WS
§ 64 GB G.Skill Ripjaws Z Series
§ 2 x 256 GB / 1 x 512 GB Samsung 840 Pro Series SSD
§ 1 x 150 GB HDD, and 1 x 250 GB HDD
High Level Plan
Here is a high level of what we are going to complete in this initial part of the series.
1. Create the Lab Environment
2. Install the Operating System
3. Install Active Directory Domain Services
4. Install SQL Server
5. Install System Center App Controller
So now let’s start with the first part, system requirements and creating the lab environment.
System Requirements
Note: The following page on TechNet describes the requirements for deploying AppController.
Server§ OS: Windows Server 2008 R2 or Windows Server 2012
§ CPU: Dual-Processor, Dual-Core, 2.8 GHz (x64) or greater
§ RAM: 1 gigabyte (GB) of RAM minimum, 4 GB or more recommended
§ HDD: 1 gigabyte (GB) of available hard disk space
§ Software:
o Microsoft SQL Server 2008 R2 or Microsoft SQL Server 2012:
§ Database Engine Service
§ SQL_Latin1_General_CP1_CI_AS collation
o Microsoft .NET Framework 4.0
o Web Server (IIS):
§ Static Content
§ Default Document
§ Directory Browsing
§ HTTP Errors
§ ASP.NET
§ .NET Extensibility
§ ISAPI Extensions
§ ISAPI Filters
§ HTTP Logging
§ Request Monitor
§ Tracing
§ Basic Authentication
§ Windows Authentication
§ Request Filtering
§ Static Content Compression
§ IIS Management Console
o VMM Console
Create the Lab Environment:
Hyper-V Configuration
As mentioned, my environment uses Hyper-V. So, we’re going to start by configuring Hyper-V for our needs, and creating the Virtual Machines (VMs) required for our lab.
The first thing we need to do is setup a Virtual Switch for the VMs to connect through.
Launch Server Manager, click on Tools, and select Hyper-V Manager.
When Hyper-V loads, it will have nothing in it. Even if we were to create a VM, it wouldn’t have a network connection to use.
So we’ll start with creating a Virtual Switch. As you can from my screenshot, I have 2 LAN ports on my host. One of them has a connection to my home network and the Internet.
In the Hyper-V Manager, click the Virtual Switch Manager from the Actions pane.
Now, click on the Create Virtual Switch button.
From here, you now need to configure the virtual switch that your VMs will use. Give it a name to clearly identify it (in my case I called it ‘External Network’), and choose the connection type. For more information about virtual networks, see the following TechNet article: http://technet.microsoft.com/en-us/library/cc816585(v=ws.10).aspx.
Here is an excerpt from the article:
For our demonstration, we are going to use an External Network so that the VMs can communicate with the Host system. Make all the appropriate selections and so forth, and then press OK. You may encounter the following warning message. This is because we are remotely connecting to the Host machine using the same network connection that we are about to setup as a Virtual Switch (hence selecting the ‘Allow management operating system to share this network adapter’ checkbox). Press ‘Yes’ to the dialog.
Now that we have the virtual switch setup, we can start creating VMs for our lab.
Create the Virtual Machines
Let’s now create the VM’s we will need for the lab, specifically one for Active Directory, and another for App Controller (since we are install all roles within the same server).
In Hyper-V Manager, from the Actions pane, click on New and choose Virtual Machine.
On the New Virtual Machine wizard beginning screen, click read the information presented and then click Next.
Enter a name for the VM. Note that this is NOT the name the VM will have within the Operating System (unless you name it the same), but rather, used as an identifier in Hyper-V Manager. After you have entered a name, click Next.
Now assign the amount of memory you want your VM to have, and then press Next.
This is the screen where you connect your VM to the network that we created, then press Next.
This is the screen where you configure how large a hard drive the VM will have. Make the appropriate customizations and click Next.
For the Installation Options, choose if you will install an OS later, or if you want to use an ISO, then click Next.
On the Summary screen, review your selections and entries, and click Finish.
Once the VM is created, it will appear in the Hyper-V Manager.
If you want to configure further settings, like the number of CPUs and mounting an OS ISO, right click on the VM and choose Settings or click on Settings from the Actions pane.
Repeat these steps for each VM you need to create, in our case one for Active Directory and another for App Controller.
Here are the settings I have used for each of the VM’s:
Active Directory:
§ Virtual Machine Name: AD
§ Memory: 2048 MB
o NOTE: Active Directory doesn’t need 2 GB of RAM, it will run fine with 512 MB. I just increased the RAM so that the OS would install/respond faster during setup.
§ CPUs: 2
§ OS: Windows Server 2012
SCAC:
§ Virtual Machine Name: SCAC
§ Memory: 4096 MB
§ CPUs: 2
§ OS: Windows Server 2012
Share this post
Link to post
Share on other sites