Differences

This shows you the differences between two versions of the page.

--- virtualization:microsoft:hyper-v-create-virtual-machine [2013/03/30 16:21]
jcooper
+++ virtualization:microsoft:hyper-v-create-virtual-machine [2019/05/20 11:30] (current)
gcooper
@@ Line 1: / Line 1: @@
-**Manage Hyper-V Server remotely**
+====== Create a Hyper-V Virtual Machine ======
-Hint: If managing a server that is not joined to your domain connect to Hyper-V servers from a workstation using a login with admin username and password the same as server.
+See also **[[https://virtualarchitects.com/wiki/doku.php?do=search&id=start&q=hyper-v|more Hyper-V pages]]**
-On Windows 8 Pro or higher PC add the Hyper-V Manager feature in Programs and Features under Hyper-V, Hyper-V Management Tools.
+===== Manage Hyper-V Server Remotely =====
-**Make Hyper-V Server available for management**
+:!: If managing a server that is not joined to your domain, connect to Hyper-V servers from a workstation using a login with the same admin username and password as the server.
-Configure the Hyper-V Server for Remote Access
+:!: DNS must be in place so that the server and remote management PC can connect to each other via host name and IP address.  Do this with your current DNS system or using host files.
+On a Windows 8 Pro or higher PC, add the Hyper-V Manager feature in Programs and Features under **Hyper-V -> Hyper-V Management Tools**.
+==== Make Hyper-V Server Available for Remote Management ====
+=== Configure the Hyper-V Server for Remote Access ===
 http://technet.microsoft.com/en-us/library/ddb147c1-621c-4b89-9003-81c93ba050d7#BKMK_1_4
-If the Server Core server is not a member of a domain, establish alternate credentials to use to connect to the Server Core computer by typing the following command at a command prompt on the remote computer:
+On the Hyper-V server command menu:
-cmdkey /add:<ServerName> /user:<UserName> /pass:<password>
+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:
-ServerName is the name of the Server Core server
-UserName is the name of an administrator account
-To be prompted for a password, omit the /pass option.
-When prompted, type the password for the user name that is specified in the previous step
-If the firewall on the Server Core server is not already configured to allow MMC snap-ins to connect, follow the steps in "To configure Windows Firewall to allow MMC snap-in(s) to connect." Then return to this procedure.
-**Attach ISCSI Storage**
+<file>
+netsh advfirewall firewall set rule group="Windows Firewall Remote Management" new enable=yes
+</file>
-http://www.techrepublic.com/blog/datacenter/configure-the-iscsi-initiator-in-windows-server-core-or-hyper-v-server/3945
+:!: If you get the "Group cannot be specified with other identification conditions" error, delete the double quotes and replace on the console.  This error occurs if you copy and paste from the Technet website.
-On the Hyper-V server console command prmpt type iscsicpl.  If the ISCSI Initiator service is not running click yes to start and make automatic at start up.
+To allow only specific MMC snap-ins to connect run this PowerShell command:
-In the ISCSI Initiator type the "Target Name" of the ISCSI share and click connect.
+<file>
+Enable-NetFirewallRule -DisplayGroup "<rulegroup>"
+</file>
-It may take a reboot ofthe Hyper-V server to see the drive in Computer Management on your remote management PC.
+Where ''rulegroup'' is one of the values from the table below, depending on which snap-in you want to connect.
+^MMC Snap-In 	                         ^Rule Group                         ^
+|Event Viewer                            |Remote Event Log Management        |
+|Services                                |Remote Services Management         |
+|Shared Folders                          |File and Printer Sharing           |
+|Task Scheduler                          |Performance Logs and Alerts, File and Printer Sharing        |
+|Disk Management                         |Remote Volume Management           |
+|Windows Firewall with Advanced Security |Windows Firewall Remote Management |
+:!: All MMC Snap-ins work except for "Computer Manager" that is needed to manage disks.  For that to work, you can disable the firewall with ''netsh advfirewall set allprofiles state off'' at the console command line.  Enable with ''netsh advfirewall set allprofiles state on''.
+==== Attach iSCSI Storage ====
-**Create a Hyper-V Virtual Machine using Windows 8 Hyper-V Manager**
+=== Configure Network Interface for Storage Network ===
-http://technet.microsoft.com/en-us/library/ddb147c1-621c-4b89-9003-81c93ba050d7#BKMK_1_4
+http://www.techrepublic.com/blog/datacenter/configure-the-iscsi-initiator-in-windows-server-core-or-hyper-v-server/3945
-On the Windows 8 computer, start an MMC snap-in, such as Computer Management. (right click computer, manage)
+:!: If you have a separate NIC for Storage, perhaps 10GbE, you need to configure it separately.
-In the left pane, right-click the top of the tree and click Connect to another computer.
+On the Hyper-V server console, access the menu with ''sconfig.cmd'':
-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.
+  - 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
-On Windows 8 PC from Start just type hyper-v and choose Hyper-V Manager.
+On the Hyper-V server console command prompt, type ''iscsicpl.exe''.
-In the left pane right click on Hyper-V Manager and select "Connect to Server".
+:!: If the iSCSI Initiator service is not running click yes to start and make automatic at start up.
-Enter the Hostname or IP of server.
+In the iSCSI Initiator type the "Target Name" or IP address of the iSCSI share and click connect.
-Right click the Hyper-V server name and select New, Virtual machine.
+:!: Remember to use the storage network NIC IP of storage server if applicable.
+Once you have connected the iSCSI share, you may need to reboot both Hyper-V server and the management PC to see the volume in Computer Manager.
+If you have trouble initializing the disk do this at the Hyper-V server console.
+Type ''diskpart'' at the command line:
+<file>
+DISKPART> LIST DISK
+   Note the disk number of the ISCSI disk.
+DISKPART> SELECT DISK n
+DISKPART> ATTRIBUTES DISK CLEAR READONLY
+DISKPART> ONLINE DISK
+DISKPART> CONVERT GPT
+</file>
+:!: 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://technet.microsoft.com/en-us/library/ddb147c1-621c-4b89-9003-81c93ba050d7#BKMK_1_4
+  - 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 ''hyper-v'' and choose Hyper-V Manager.
+  - In the left pane right click on Hyper-V Manager and select "Connect to Server".
+  - Enter the Hostname or IP of server.
+  - Right click the Hyper-V server name and select New, Virtual machine.

Virtual Architects Support Wiki

User Tools

Site Tools

Differences

Page Tools