User Tools
virtualization:microsoft:hyper-v-create-virtual-machine
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
virtualization:microsoft:hyper-v-create-virtual-machine [2013/04/01 12:40] jcooper |
virtualization:microsoft:hyper-v-create-virtual-machine [2019/05/20 11:30] (current) gcooper |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | **Manage | + | ====== Create a Hyper-V |
| - | Hint: If managing a server that is not joined to your domain connect to Hyper-V | + | See also **[[https:// |
| - | Also: DNS must be in place so that the server and remote management PC can connect to each other via host name and IP address. | + | ===== Manage Hyper-V Server Remotely ===== |
| - | On Windows 8 Pro or higher PC add the Hyper-V | + | :!: If managing a server that is not joined to your domain, connect to Hyper-V |
| - | **Make Hyper-V Server available for management** | + | :!: DNS must be in place so that the server and remote |
| - | Configure | + | On a Windows 8 Pro or higher PC, add the Hyper-V |
| - | http:// | + | ==== Make Hyper-V Server Available for Remote Management ==== |
| - | To allow all MMC snap-ins to connect, run | + | === Configure the Hyper-V Server for Remote Access === |
| - | Enable-NetFirewallRule | + | http:// |
| - | To allow only specific MMC snap-ins to connect, run: | + | On the Hyper-V server command menu: |
| - | Enable-NetFirewallRule -DisplayGroup "< | + | Configure items 1, 2, 4, 7, 8 and 9. |
| - | Where: | + | To allow all MMC snap-ins to connect, at the command prompt on the Hyper-V server run: |
| - | Rulegroup is one of the values from the table below, depending on which snap-in you want to connect. | + | < |
| + | netsh advfirewall firewall set rule group=" | ||
| + | </ | ||
| + | :!: If you get the "Group cannot be specified with other identification conditions" | ||
| + | To allow only specific MMC snap-ins to connect run this PowerShell command: | ||
| - | **Attach ISCSI Storage** | + | < |
| + | Enable-NetFirewallRule -DisplayGroup "< | ||
| + | </ | ||
| - | http:// | + | Where '' |
| - | On the Hyper-V server console command prmpt type iscsicpl. | + | ^MMC Snap-In ^Rule Group ^ |
| + | |Event Viewer | ||
| + | |Services | ||
| + | |Shared Folders | ||
| + | |Task Scheduler | ||
| + | |Disk Management | ||
| + | |Windows Firewall with Advanced Security |Windows Firewall Remote Management | | ||
| - | In the ISCSI Initiator type the "Target Name" | + | :!: All MMC Snap-ins work except for "Computer Manager" |
| - | If you have trouble initializing the disk do this at the Hyper-V server console. | + | ==== Attach iSCSI Storage ==== |
| - | Type diskpart at the command line. | + | === Configure Network Interface for Storage Network === |
| - | Type list disk and note the disk number of the ISCSI disk. | + | |
| - | DISKPART> | + | |
| - | DISKPART> | + | |
| - | DISKPART> | + | |
| - | DISKPART> | + | |
| - | It may take a reboot ofthe Hyper-V server to see the drive in Computer Management on your remote management PC. | + | http:// |
| + | :!: If you have a separate NIC for Storage, perhaps 10GbE, you need to configure it separately. | ||
| + | On the Hyper-V server console, access the menu with '' | ||
| + | - Choose Network Settings | ||
| + | - Select the Index Number of the NIC to configure | ||
| + | - Choose (1) Set Network Adapter Address | ||
| + | - (S) Static | ||
| + | - Enter Static IP address | ||
| + | - Enter Subnet Mask | ||
| + | - Enter Gateway | ||
| + | - Choose (2) Set DNS Servers | ||
| + | - Enter primary and secondary servers | ||
| - | **Create a Hyper-V | + | On the Hyper-V |
| - | http:// | + | :!: If the iSCSI Initiator service is not running click yes to start and make automatic at start up. |
| - | On the Windows 8 computer, start an MMC snap-in, such as Computer Management. (right | + | In the iSCSI Initiator type the " |
| - | In the left pane, right-click the top of the tree and click Connect to another computer. | + | :!: Remember to use the storage network NIC IP of storage server if applicable. |
| - | Type the computer name of the server | + | Once you have connected |
| - | On Windows 8 PC from Start just type hyper-v and choose | + | If you have trouble initializing the disk do this at the Hyper-V |
| - | In the left pane right click on Hyper-V Manager and select " | + | Type '' |
| - | + | ||
| - | Enter the Hostname or IP of server. | + | |
| - | + | ||
| - | Right click the Hyper-V server name and select New, Virtual machine. | + | |
| + | < | ||
| + | DISKPART> | ||
| + | Note the disk number of the ISCSI disk. | ||
| + | DISKPART> | ||
| + | DISKPART> | ||
| + | DISKPART> | ||
| + | DISKPART> | ||
| + | </ | ||
| + | :!: It may take a reboot of the Hyper-V server to see the drive in Computer Management on your remote management PC. | ||
| + | ===== Create a Hyper-V Virtual Machine using Windows 8 Hyper-V Manager ===== | ||
| + | http:// | ||
| + | - On the Windows 8 computer, start an MMC snap-in, such as Computer Management. (right-click Computer -> Manage) | ||
| + | - In the left pane, right-click the top of the tree and click Connect to another computer. | ||
| + | - Type the computer name of the server that is in Server Core mode and click OK. You can now use the MMC snap-in to manage the Server Core server as you would any other computer running a Windows Server operating system. | ||
| + | - On Windows 8 PC from Start just type '' | ||
| + | - In the left pane right click on Hyper-V Manager and select " | ||
| + | - Enter the Hostname or IP of server. | ||
| + | - Right click the Hyper-V server name and select New, Virtual machine. | ||
virtualization/microsoft/hyper-v-create-virtual-machine.1364841645.txt.gz · Last modified: 2013/04/01 12:40 by jcooper
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
