Jump to content


Search the Community

Showing results for tags 'Hyper-V'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
    • Windows 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Official Forum Supporters
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • SMS 2003
    • Configuration Manager 2007
    • Configuration Manager 2012
    • System Center Configuration Manager (Current Branch)
    • Packaging
    • scripting
    • Endpoint Protection
  • Windows Client
    • how do I ?
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Vista
    • Windows XP
    • windows screenshots
  • Windows Server
    • Windows Server General
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Hyper V
    • Exchange
    • IIS/apache/web server
    • System Center Data Protection Manager
    • System Center Service Manager
    • System Center App Controller
    • System Center Virtual Machine Manager
    • System Center Orchestrator
    • Lync
    • Application Virtualization
    • Sharepoint
    • WSUS

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests

  1. In our last post we installed the Operating System on our VM's. Now, we will install Active Directory. Install Active Directory Domain Services Now that we have the VMs created, and the OS installed on both, we need to first install/setup Active Directory (AD). When you log into a new installation of Server 2012, Server Manager will auto launch. From Server Manager, click on Manage, and choose ‘Add Roles and Features’. On the Add Roles and Features Wizard, read the information on the Before You Begin dialog, and then click Next. On the Installation Type screen, select ‘Role-based on feature-based installation’ and then click Next. On the ‘Server Selection’ screen, since we are installed Active Directory on this local system, ensure that it is selected, and click Next. Side note: Windows Server 2012 has a new feature that allows you to remotely install Roles and Features on other systems. On the Server Roles screen, select ‘Active Directory Domain Services’. When you select ‘Active Directory Domain Services’, immediately you will be presented with the following dialog. Click Add Features. On the Features screen, accept what has already been selected by default, and click Next. On the AD DS screen, read the information presented, and click Next. On the Confirmation screen, check the ‘Restart the destination server automatically if required’ checkbox, and then click Install. Note: You are not required to check the ‘restart’ checkbox, however, you’re going to have to restart the system anyways after the installation, so you might as well let the system do it for you. Note: When you check off the ‘Restart the destination server automatically if required’ checkbox, you will immediately be prompted with the following dialog. Click Yes. On the Results screen, click Close. After the system restarts, and Server Manager launches, you will have to promote the server as a domain controller. This is because Active Directory has been installed, but that process does not automatically promote the server. Click on the ‘Promote this server to a domain controller’ link. On the Deployment Configuration screen, select ‘Add a new forest’ since this is the first domain controller in our lab. Then enter a root domain name, and click Next. In my example I am using “SC.LAB” for System Center Lab (since I will be installing all other System Center products in my lab eventually). For the Domain Controller Options, select the appropriate Forest functional level, and Domain functional level. This is more applicable if you already have an existing domain and are adding a new domain controller. But since this is the first domain controller in our new domain, then we’ll use the highest level, that of Windows Server 2012. Also, don’t forget to create the Directory Service Restore Mode password. Then press Next. On the DNS Options screen, you can ignore this warning message and click Next. On the Additional Options screen, click Next. On the Paths screen, normally you would change the location for the database, log files, and SYSVOL, but since we are just in a lab environment, we’ll leave it at the defaults and click Next. On the Review Options scree, review what you have entered/selected, and click Next. The Prerequisites Check screen will check and confirm that everything passes before promoting the system as a domain controller. You will notice in my screenshot, that I have 1 warning because I didn’t set a static IP for the server yet. After installation completes, the system will automatically restart. You will then be presented with the login screen. Something to note here, that because we were originally logged in with a local account, the first time you want to log on using a domain account you will have to type the domain\username; in my example SC\Administrator. When you login, you will then see in the Server Manager, that AD DS is now listed, along with DNS. Now all that you need to do is assign a static IP to your domain controller. To do this, in Server Manager, select Local Server from the panel on the left. From there, click on the Ethernet link labelled ‘IPv4 address assigned by DHCP, IPv6 enabled’. This will cause the Networks Connections explorer to open. From here, right click on the Ethernet network that is displayed. This is in fact the network connection that we configured when we first created the VM. On the Ethernet Properties dialog, select ‘Internet Protocol Version 4 (TCP/IPv4)’ and click the Properties button. Within the Internet Protocol Version 4 (TCP/IPv4) Properties dialog, enter a static IP, gateway, and DNS that is applicable to your network. Once all the items have been entered, click OK. You will also have to click Close on the Ethernet Properties dialog as well. Congratulations, you now have a domain setup in your lab environment. Add Systems to Your Domain Now that you have your domain setup, you need to add your other VM (the one that we will use for Orchestrator) to the domain before being able to install Orchestrator. Log into the system you want to add to the domain. To do this in Server 2012, launch Server Manager, and click on Local Server. Then click on the computer name. This will launch the System Properties dialog. From this dialog, click the Change button. From this dialog, select the Domain option for ‘Member of’, and enter the domain name you want to join and press OK. After pressing OK, you are immediately presented with a Windows Security dialog, in which you need to enter the credentials of an account that has Domain Admin rights. Enter the credentials and click OK. Once the system is successfully joined to the domain, you will receive the following Welcome message. Press OK. After you press OK to the Welcome message, you will receive a second prompt, indicating that you need to restart the system for the changes to take effect. You will be back on the System Properties dialog. Press Close. When you press Close, you will receive yet another prompt about restarting the system. You can choose to Restart Now or Restart Later, but you won’t be able to install Orchestrator without the VM being added to the domain. After the system restarts, you will then be presented with the login screen. Something to note here, that because we were originally logged in with a local account, the first time you want to log on using a domain account you will have to type the domain\username; in my example SC\Administrator. Now we have our Active Directory server setup and ready, and the VM we will be installing Orchestrator on is joined to the domain. Now we can move onto installing SQL Server.
  2. In our last post, we initially setup the VM's required for our lab. Now we'll focus on the OS. Install the Operating System Now that we have created the VMs for our lab, we can install the Operating System (OS). Start by connecting to one of the VMs, either by double clicking on the VM in Hyper-V Manager, right click the VM and choose Connect, or click on Connect from the Action pane/menu. When you have the VM connection up, and an ISO mounted, power the VM on. On the Windows Setup screen, select the Language, Time/Currency Format, and Keyboard Method appropriate, and click Next. All you have to do now is click Install Now. Next you have to choose the Operating System and version you want to install. In our lab example, I will choose Windows Server 2012 Standard (Server with a GUI). Make your selection and then click Next. You will have to accept the license terms, and then click Next. For the Installation Type, since we don’t already have an OS installed, we will choose the ‘Custom: Install Windows only (advanced)’ option. Now select the hard drive that you want to install the OS to. Since we only created one hard drive when setting up the VM, we only have one to choose from. Select it, and click Next. Now all you have to do is wait for the installation to finish. Once the installation is complete, you will be prompted to enter a password for the local administrator account. This is different from a domain-based local administrator account. Enter a password and click Finish. After some final quick configuration, you will then be presented with the login screen. Now repeat these steps for the other VMs in the lab. NOTE: After you install an OS, you will need to rename the computer within the OS. To do this in Server 2012, launch Server Manager, and click on Local Server. Then click on the computer name. This will launch the System Properties dialog. From this dialog, click the Change button. From this dialog, enter the name you want to call the computer. In my lab, I called the Active Directory computer “AD”, and the Orchestrator computer “SCORCH”. Press OK after entering the name. You will encounter the following prompt. Click OK. Then click Close on the System Properties dialog. You can choose to either Restart Now or Restart Later, but the name change will not take effect until you do so. In the next part of our guide, we will install Active Directory Domain Services, so stay tuned.
  3. SCORCH 2012 SP1 in a LAB – Installation (Part A – Create The Lab Environment) 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 High Level Plan Here is a high level of what we are going to complete in this initial part of the series. Create the Lab Environment Install the Operating System Install Active Directory Domain Services Install SQL Server Install System Center Orchestrator 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 Orchestator. Management Server OS: Windows Server 2008 R2 or Windows Server 2012 CPU: Dual-core Intel microprocessor, 2.1 gigahertz (GHz) or better RAM: 1 gigabyte (GB) of RAM minimum, 2 GB or more recommended HDD: 200 megabyte (MB) of available hard disk space Software:Microsoft SQL Server 2008 R2 or Microsoft SQL Server 2012:Database Engine Service SQL_Latin1_General_CP1_CI_AS collation Microsoft .NET Framework 3.5 Service Pack 1 Runbook Server OS: Windows Server 2008 R2 or Windows Server 2012 CPU: Dual-core Intel microprocessor, 2.1 gigahertz (GHz) or better RAM: 1 gigabyte (GB) of RAM minimum, 2 GB or more recommended HDD: 200 megabyte (MB) of available hard disk space Software:A functional Orchestrator management server and database Orchestrator Web Service OS: Windows Server 2008 R2 or Windows Server 2012 CPU: Dual-core Intel microprocessor, 2.1 gigahertz (GHz) or better RAM: 1 gigabyte (GB) of RAM minimum, 2 GB or more recommended HDD: 200 megabyte (MB) of available hard disk space Software:A functional Orchestrator management server and database Internet Information Services (IIS) 7.0 Microsoft .NET Framework 3.5 Service Pack 1 Microsoft .NET Framework 4.5 (which further requires HTTP Activation) WCF HTTP Activation Runbook Designer OS: Windows Server 2008 R2, Windows Server 2012, or Windows 7 (32-bit or 64-bit) CPU: Dual-core Intel microprocessor, 2.1 gigahertz (GHz) or better RAM: 1 gigabyte (GB) of RAM minimum, 2 GB or more recommended HDD: 200 megabyte (MB) of available hard disk space Software:A functional Orchestrator management server and database Microsoft .NET Framework 3.5 Service Pack 1 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 Orchestrator (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 Orchestrator. Here are the settings I have used for each of the VM’s: Active Directory: Virtual Machine Name: AD Memory: 2048 MBNOTE: 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 SCORCH: Virtual Machine Name: SCORCH Memory: 4096 MBNOTE: You may need to increase the amount of RAM this VM has, depending on performance. CPUs: 2 OS: Windows Server 2012
  4. In our last post, we initially setup the VM's required for our lab. Now we'll focus on the OS. Install the Operating System Now that we have created the VMs for our lab, we can install the Operating System (OS). Start by connecting to one of the VMs, either by double clicking on the VM in Hyper-V Manager, right click the VM and choose Connect, or click on Connect from the Action pane/menu. When you have the VM connection up, and an ISO mounted, power the VM on. On the Windows Setup screen, select the Language, Time/Currency Format, and Keyboard Method appropriate, and click Next. All you have to do now is click Install Now. Next you have to choose the Operating System and version you want to install. In our lab example, I will choose Windows Server 2012 Standard (Server with a GUI). Make your selection and then click Next. You will have to accept the license terms, and then click Next. For the Installation Type, since we don’t already have an OS installed, we will choose the ‘Custom: Install Windows only (advanced)’ option. Now select the hard drive that you want to install the OS to. Since we only created one hard drive when setting up the VM, we only have one to choose from. Select it, and click Next. Now all you have to do is wait for the installation to finish. Once the installation is complete, you will be prompted to enter a password for the local administrator account. This is different from a domain-based local administrator account. Enter a password and click Finish. After some final quick configuration, you will then be presented with the login screen. Now repeat these steps for the other VMs in the lab. NOTE: After you install an OS, you will need to rename the computer within the OS. To do this in Server 2012, launch Server Manager, and click on Local Server. Then click on the computer name. This will launch the System Properties dialog. From this dialog, click the Change button. From this dialog, enter the name you want to call the computer. In my lab, I called the Active Directory computer “AD”, and the Operations Manager computer “SCOM”. Press OK after entering the name. You will encounter the following prompt. Click OK. Then click Close on the System Properties dialog. You can choose to either Restart Now or Restart Later, but the name change will not take effect until you do so. In the next part of our guide, we will install Active Directory Domain Services, so stay tuned.
  5. Hi Folks, Although i'm a member here since 2009 I don't think I've ever posted anything here before. Well I'm going to change that now. I recently came across an issue (kinda) with Windows 2012 running Hyper-V and DNS. As I was running this in a test situation I only connected one network card on the system and this card was also setup as the Virtual Switch in Hyper-V. Its seems (although I haven't actually verified this) that if DNS is listening on the same network card the Simple and Recursive Tests on the Monitoring tab will fail Constantly. However, this doesn't stop DNS actually performing its duties. It still resolves all addresses and performs all other duties without fail. You just won't be able to get the Monitoring tests to Pass. To get around this you need to configure DNS to listen on a seperate network card to the one you specified as a Virtual Switch in Hyper-V and your laughing. I understand that this would be best practice anyway but as it was a lab situation I didn't bother and it tormented me for ages. Thought it was an interesting find that needed sharing. Cheers, Laoistom
  6. Hi, I’ve reviewed your Hyper-V threads and I haven’t scene anything talking about an Exchange setup in Hyper-V. My question is would such a thing be possible? I'm running Microsoft Server 2008 R2 SP2, and would be installing Exchange 2007. (out of box SP?)
×
×
  • Create New...

Important Information

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.