deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-15 18:33:43 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

more content

Browse Source
This commit is contained in:
Greg Lindsay
2016-07-05 17:22:23 -07:00
parent 8585ce2f30
commit 309fc50437
1 changed files with 29 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

46
windows/deploy/windows-10-poc.md
View File

@ -52,56 +52,62 @@ Two computers are required to complete this guide:
<td BGCOLOR="#a0e4fa">**Computer 2**</td>
</tr>
<tr>
<td>Role</td>
<td BGCOLOR="#a0e4fa">Role</td>
<td>Hyper-V host</td>
<td>Client</td>
</tr>
<tr>
<td>Description</td>
<td>This computer will run Hyper-V, the Hyper-V management tools and the Hyper-V Windows PowerShell module.</td>
<td BGCOLOR="#a0e4fa">Description</td>
<td>This computer will run Hyper-V, the Hyper-V management tools, and the Hyper-V Windows PowerShell module.</td>
<td>This computer is a test system on your corporate network that will be converted to a VHD.</td>
</tr>
<tr>
<td>OS</td>
<td BGCOLOR="#a0e4fa">OS</td>
<td>Windows 8/8.1/10 or Windows Server 2012/2012 R2/2016</td>
<td>Windows 7 or a later*</td>
</tr>
<tr>
<td>RAM</td>
<td BGCOLOR="#a0e4fa">Architecture</td>
<td>64-bit</td>
<td>Any</td>
</tr>
<tr>
<td BGCOLOR="#a0e4fa">RAM</td>
<td>8 GB RAM (16 GB recommended)</td>
<td>Any</td>
</tr>
<tr>
<td>Disk</td>
<td BGCOLOR="#a0e4fa">Disk</td>
<td>50 GB available hard disk space (100 GB recommended)</td>
<td>Any</td>
</tr>
<tr>
<td>CPU</td>
<td BGCOLOR="#a0e4fa">CPU</td>
<td>SLAT-Capable CPU</td>
<td>Any</td>
</tr>
<tr>
<td>Network</td>
<td BGCOLOR="#a0e4fa">Network</td>
<td>Internet connection</td>
<td>Any</td>
</tr>
</table>
*This guide does not provide specific instructions for upgrading or downgrading the architecture of the client PC from 32-bit or 64-bit. An in-place upgrade can only be performed if the pre- and post-upgrade architecture is the same. To change the architecture of the client PC during the upgrade process, use the wipe and reload scenario procedures.
**Note**:
>Retaining applications and settings during the upgrade process requires that architecture (32 or 64-bit) is the same before and after the upgrade.
## Lab setup
The Hyper-V host computer is configured to host four VMs on a private, proof of concept network.
- Two VMs are running Windows Server 2012 R2 with required network services and tools installed.
- Two VMs are client systems with one VM intended to mirror a host on your corporate network, and one VM running Windows 10 to illustrate a hardware replacement scenario.
- Two VMs are client systems: One VM is intended to mirror a host on your corporate network; one VM is running Windows 10 to demonstrate the hardware replacement scenario.
Links are provided to download trial versions of Windows Server 2012 and all deployment tools necessary to complete the lab. See the following diagram:
![PoC](images/poc.png)
**Note**:
>If you have an existing Hyper-V host, you can use this host if desired and skip the Hyper-V installation section in this guide.
>If you have an existing Hyper-V host, you can use this host if desired and skip the Hyper-V installation section in this guide. If your Hyper-V host is running Windows Server 2008 R2, you must enable PowerShell functionality to complete the steps in this guide.
>The two Windows Server VMs can be combined into a single VM to conserve RAM and disk space if required. However, instructions in this guide assume two server systems are used.
@ -109,16 +115,20 @@ Links are provided to download trial versions of Windows Server 2012 and all dep
### In this section
[Install Hyper-V](#install-hyper-v)
[Download VHDs](#download-vhds)
[Configure Hyper-V](#configure-hyper-v)
[Configure VHDs](#configure-vhds)
[Install Hyper-V](#install-hyper-v)<BR>
[Download VHDs](#download-vhds)<BR>
[Configure Hyper-V](#configure-hyper-v)<BR>
[Configure VHDs](#configure-vhds)<BR>
[Verify the configuration](#verify-the-configuration)
### Install Hyper-V
Use one of the following procedures to install Hyper-V on the Hyper-V host computer:
Install Hyper-V on a computer running Windows 8/8.1 or Windows 10
[Install Hyper-V on a computer running Windows 8/8.1/10](#to-install-hyper-v-on-a-computer-running-windows-8-8-1-10)<BR>
[Install Hyper-V on a computer running Windows Server 2012/2012 R2/2016](#to-install-hyper-v-on-a-computer-running-windows-server-2012-2012-r2-2016)
####To install Hyper-V on a computer running Windows 8/8.1/10
Starting with Windows 8, the host computer’s microprocessor must support second level address translation (SLAT) to install Hyper-V. See [Hyper-V: List of SLAT-Capable CPUs for Hosts](http://social.technet.microsoft.com/wiki/contents/articles/1401.hyper-v-list-of-slat-capable-cpus-for-hosts.aspx) for more information.
@ -134,10 +144,12 @@ Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V –All
You can also install it via the Control Panel in Windows under Turn Windows features on or off, as shown here:
Important If you know that your processor supports SLAT, but you still get an error message that states Hyper-V cannot be installed, you might need to enable virtualization in the BIOS. The location of this setting will depend on the manufacturer and BIOS version. The following image shows an example of the required settings (under Security) in a Hewlett-Packard BIOS for an Intel processor:
**Important** If you know that your processor supports SLAT, but you still get an error message that states Hyper-V cannot be installed, you might need to enable virtualization in the BIOS. The location of this setting will depend on the manufacturer and BIOS version. The following image shows an example of the required settings (under Security) in a Hewlett-Packard BIOS for an Intel processor:
![security BIOS settings](images/sec-bios.png)
####To install Hyper-V on a computer running Windows Server 2012/2012 R2/2016
### Download VHDs
### Configure Hyper-V