Virtual Architects Support Wiki

User Tools

Site Tools

You are here: start » virtualization » microsoft » hyper-v-create-virtual-machine
Trace:
virtualization:microsoft:hyper-v-create-virtual-machine

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
virtualization:microsoft:hyper-v-create-virtual-machine [2013/04/04 17:42]
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 +See also **[[https://virtualarchitects.com/wiki/doku.php?do=search&id=start&q=hyper-v|more Hyper-V pages]]**
-   a workstation using a login with admin username and password the same as server.+
  
-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.  Do this with your current DNS system or using host files.+===== Manage Hyper-V Server Remotely =====
  
-On Windows 8 Pro or higher PC add the Hyper-V Manager feature in Programs and Features under Hyper-V, Hyper-V Management Tools.+:!: 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.
  
-**Make Hyper-V Server available for remote management**+:!: 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.
  
-Configure the Hyper-V Server for Remote Access +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**.
  
-On the Hyper-V server command menu:+==== Make Hyper-V Server Available for Remote Management ====
  
-Configure #1,2,4,7,8 and 9.+=== Configure the Hyper-V Server for Remote Access ===
  
 http://technet.microsoft.com/en-us/library/ddb147c1-621c-4b89-9003-81c93ba050d7#BKMK_1_4 http://technet.microsoft.com/en-us/library/ddb147c1-621c-4b89-9003-81c93ba050d7#BKMK_1_4
  
-To allow all MMC snap-ins to connect, at the command prompt on the Hyper-V server run+On the Hyper-V server command menu:
  
 +Configure items 1, 2, 4, 7, 8 and 9.
 +
 +To allow all MMC snap-ins to connect, at the command prompt on the Hyper-V server run:
 +
 +<file>
 netsh advfirewall firewall set rule group="Windows Firewall Remote Management" new enable=yes netsh advfirewall firewall set rule group="Windows Firewall Remote Management" new enable=yes
 +</file>
  
-   Note: If you get the "Group cannot be specified with other identification conditions" error +:!: 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.
-   delete the double quotes and replace on the console.  This error occurs if you copy and past from +
-   the Technet website.+
  
 To allow only specific MMC snap-ins to connect run this PowerShell command: To allow only specific MMC snap-ins to connect run this PowerShell command:
  
 +<file>
 Enable-NetFirewallRule -DisplayGroup "<rulegroup>" Enable-NetFirewallRule -DisplayGroup "<rulegroup>"
 +</file>
  
-Where:+Where ''rulegroup'' is one of the values from the table below, depending on which snap-in you want to connect.
  
-Rulegroup is one of the values from the table below, depending on which snap-in you want to connect. +^MMC Snap-In                           ^Rule Group                         ^
- +
-^MMC snap-in                           ^Rule group                         ^+
 |Event Viewer                            |Remote Event Log Management        | |Event Viewer                            |Remote Event Log Management        |
 |Services                                |Remote Services Management         | |Services                                |Remote Services Management         |
Line 42: Line 45:
 |Windows Firewall with Advanced Security |Windows Firewall Remote Management | |Windows Firewall with Advanced Security |Windows Firewall Remote Management |
  
-   Note: All MMC Snap-ins work except for "Computer Manager" that is needed to manage disks.  For that to work +:!: 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''.
-   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**+==== Attach iSCSI Storage ====
  
-*Configure Network Interface for Storage Network*+=== Configure Network Interface for Storage Network ===
  
-If you have a seperate NIC for Storage (10GB?) you need to configure seperately.+http://www.techrepublic.com/blog/datacenter/configure-the-iscsi-initiator-in-windows-server-core-or-hyper-v-server/3945
  
-On the Hyper-V server console sconfig.cmd choose 8) Network settings +:!: If you have a separate NIC for Storage, perhaps 10GbE, you need to configure it separately.
-Select the Index# of the NIC to configure +
-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 the Hyper-V server console, access the menu with ''sconfig.cmd'':
  
-http://www.techrepublic.com/blog/datacenter/configure-the-iscsi-initiator-in-windows-server-core-or-hyper-v-server/3945+  - 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 the Hyper-V server console command prompt, type ''iscsicpl.exe''. 
 + 
 +:!: If the iSCSI Initiator service is not running click yes to start and make automatic at start up.
  
-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.+In the iSCSI Initiator type the "Target Name" or IP address of the iSCSI share and click connect.  
  
-In the ISCSI Initiator type the "Target Name" or IP address of the ISCSI share and click connect.  Remember to use the storage network NIC IP of storage server if applicable.+:!: 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.+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. If you have trouble initializing the disk do this at the Hyper-V server console.
  
-Type DISKPART at the command line.+Type ''diskpart'' at the command line:
  
 +<file>
 DISKPART> LIST DISK  DISKPART> LIST DISK 
    Note the disk number of the ISCSI disk.    Note the disk number of the ISCSI disk.
Line 80: Line 87:
 DISKPART> ATTRIBUTES DISK CLEAR READONLY DISKPART> ATTRIBUTES DISK CLEAR READONLY
 DISKPART> ONLINE DISK DISKPART> ONLINE DISK
-DISKPART> CONVERT MBR+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.+:!: 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 =====
- +
- +
-**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 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) +  - 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. 
-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. 
-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. +  - In the left pane right click on Hyper-V Manager and select "Connect to Server". 
- +  - Enter the Hostname or IP of server. 
-On Windows 8 PC from Start just type hyper-v and choose Hyper-V Manager. +  - Right click the Hyper-V server name and select New, Virtual machine.
- +
-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. +
- +
- +
- +
- +
  
virtualization/microsoft/hyper-v-create-virtual-machine.1365118961.txt.gz · Last modified: 2013/04/04 17:42 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
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki