Assignment Help, Cloud Based ERP System, Microsoft NAV Certification
WELCOME !!

Please Register, ask for assignment solutions & post the solutions if you know any.

LETS START POSTING YOUR IDEAS AND THOUGHTS AND BUILD THE COMMUNITY OF EXPERTS.

Assignment Help, Cloud Based ERP System, Microsoft NAV Certification

Stock Market, Online Tutoring, Cloud Based ERP System, Microsoft Dynamics Reporting, Microsoft Nav Certification


You are not connected. Please login or register

View previous topic View next topic Go down  Message [Page 1 of 1]

1 Creating virtual machines on 13th October 2013, 1:04 am

Formatted

avatar
Administrator
If you have not finish reading previous post , visit http://kantipur.friendhood.net/t783-deploying-and-confguring-virtual-machines

You can create new virtual machines on a Hyper-V host by using either Hyper-V Manager or
Windows PowerShell
Using Hyper-V Manager
Creating a new virtual machine using Hyper-V Manager is performed in the same way as in
previous versions of Windows Server  The steps in this process are as follows:
1.  Launch the New Virtual Machine Wizard by right-clicking on the host in Hyper-V
  Manager and selecting New and then Virtual Machine 
2.  Specify a descriptive name for the new virtual machine, and optionally specify a
  different location for storing the virtual machine’s fles (confguration fles, virtual hard
disks, and snapshots) if the default storage locations for the host are not the ones you
want to use 
3.  Specify the amount of startup memory to be used by the virtual machine’s guest
operating system, and specify whether Dynamic Memory is to be used for the virtual
machine 
4.  Select an existing virtual switch on the host that should be connected to the virtual
network adapter on the virtual machine, or leave the virtual machine unconnected
from any virtual switches on the host
5.  Create a new virtual disk as the system volume on the virtual machine, attach an
  existing virtual disk for this purpose, or create the virtual machine without any virtual
hard disks attached so that you can attach one later. If you choose the frst option, you
can specify whether to install the guest operating system later, install it from the virtual
CD/DVD drive or ISO image fle or virtual foppy disk, or install it from a network-based
installation server (if you have connected the virtual network adapter to a virtual
switch)  

Using Windows PowerShell
You can also use the New-VM cmdlet to create a new virtual machine using Windows
  PowerShell  For example, to create a new virtual machine named SRV-A on HOST4, assign
the virtual machine 1 GB of startup memory, attach it to the virtual switch named CONTOSO
  Virtual Switch, create a new virtual hard disk (VHDX fle) of size 500 GBs in the default loca-
tion, and make the virtual CD drive the default boot device, use the following command:
PS C:\> New-VM -ComputerName HOST4 -Name SRV-A -MemoryStartupBytes 1GB `
-BootDevice CD -SwitchName "CONTOSO Virtual Switch" -NewVHDSizeBytes 500GB `
-NewVHDPath SRV-A.vhdx
 
Name  State CPUUsage(%) MemoryAssigned(M) Uptime   Status
----  ----- ----------- ----------------- ------   ------
SRV-A Off   0           0                 00:00:00 Operating normally

Importing virtual machines
Importing existing virtual machines onto a Hyper-V host can also be performed using either
Hyper-V Manager or Windows PowerShell  For example, to import a virtual machine using
Hyper-V Manager, select the target host and click Import Virtual Machine in the Actions
pane  This launches the Virtual Machine Import Wizard, you can use this
wizard to perform the various import scenarios described earlier in post

To import virtual machines using Windows PowerShell, use the Import-VM cmdlet  For
help on using this cmdlet, see the examples at the end of the “Import-VM” topic at 
http://technet.microsoft.com/en-us/library/hh848495  
 and Videos :


_________________
REGISTER AND LOG-IN TO PARTICIPATE
START POSTING YOUR IDEAS AND THOUGHTS AND BUILD THE COMMUNITY OF EXPERTS.
View user profile http://kantipur.friendhood.net

2 Confguring virtual machines on 13th October 2013, 1:06 am

Formatted

avatar
Administrator
Once you have created a virtual machine, you might need to further confgure its virtual
hardware and management settings  You can do this either by opening the virtual machine’s
settings in Hyper-V Manager or by using Windows PowerShell  For example, to view or
modify the settings for a virtual machine using Hyper-V Manager, right-click on the virtual
machine and select Settings  Doing this displays a Settings dialog.
To view the settings of the same virtual machine using Windows PowerShell, you can use
the Get-VM cmdlet as shown here:
PS C:\> Get-VM -Name SRV-A | Format-List *

To modify these virtual machine settings, you can use the Set-VM cmdlet and other
  Hyper-V cmdlets  In the sections that follow, we will examine only a few of these different
virtual machine settings and how to confgure them. For additional information on confgur-
ing virtual machine settings, search the TechNet Library for the appropriate topic 
Adding virtual disks
You can use the IDE Controller 0, IDE Controller 1, and SCSI Controller pages of the virtual
machine settings dialog box in Hyper-V Manager to add new virtual disks to a virtual ma-
chine  You can also use subpages of these pages to inspect, browse, or edit an existing virtual
hard disk; remove a virtual disk that is attached to the virtual machine; or attach a physical
disk on the host’s storage system to the virtual machine 
When you add a virtual disk using the New Virtual Hard Disk Wizard, you have a choice of
using either the VHDX or VHD format for the new disk  (The default is VHDX ) The new Virtual
Hard Disk Wizard also lets you confgure a name for the new disk, the disk type (with the
default being dynamically expanding), the maximum size for the disk (with the default being
127 GBs), and whether the new disk should be blank or contain the data on a physical disk on
the host or on an existing virtual disk.
You can also use the Add Hardware page of the virtual machine settings dialog box to add
additional SCSI controllers to your virtual machine so that you can connect more virtual disks
to the virtual machine 
You can also use Windows PowerShell to create new virtual disks and add them to your
virtual machines  For example, let’s say you want to create and attach a 500-GB dynami-
cally expanding data disk to virtual machine SRV-A on HOST4  You can begin by using the
  Get-VHD command to display a list of disks attached to SRV-A as follows:
PS C:\> Get-VM -VMName SRV-A | Select-Object VMId | Get-VHD | `
Format-List Path,VhdFormat,VhdType,Size
 
Path                 : C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks\SRV-A.vhdx
VhdFormat            : VHDX
VhdType              : Dynamic
Size                 : 536870912000
The preceding command takes advantage of the pipeline capabilities of Windows
  PowerShell and works like this:
1.  The command Get-VM –VMName SRV-A returns an object representing virtual
  machine  SRV-A 
2.  The output of the preceding command is then piped into the command Select-Object
VMId, which returns an object representing the GUID for SRV-A
3.  The GUID for SRV-A is then piped into the Get-VHD command to indicate which virtual
machine is to be queried for its virtual disks
4.  The output of the Get-VHD command is then formatted as a list to display only those
properties of interest—namely, the path and fle name of the virtual disk fle, the
  format it uses, the type of the disk, and the disk’s size 
Next you can use the New-VHD cmdlet to create the new data disk as follows:
PS C:\> New-VHD -SizeBytes 500GB `
-Path "C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks\SRV-A-data.vhdx"
 
ComputerName      : HOST4
Path              : C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks\SRV-A-data.vhdx
VhdFormat         : VHDX
VhdType           : Dynamic
FileSize          : 4194304
Size              : 536870912000
...
Next you can use the Add-VMHardDiskDrive cmdlet to attach the new data disk to
  location 1 on IDE controller 0 as follows:
PS C:\> Add-VMHardDiskDrive -VMName SRV-A `
-Path "C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks\SRV-A-data.vhdx" `
-ControllerType IDE -ControllerNumber 0 -ControllerLocation 1

You can then use the Get-VHD cmdlet as before to verify the result:
PS C:\> Get-VM -VMName SRV-A | Select-Object VMId | Get-VHD | `
Format-List Path,VhdFormat,VhdType,Size
 
Path      : C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks\SRV-A.vhdx
VhdFormat : VHDX
VhdType   : Dynamic
Size      : 536870912000
 
Path      : C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks\SRV-A-data.vhdx
VhdFormat : VHDX
VhdType   : Dynamic
Size      : 536870912000
Alternatively, you can use the Get-VMHardDiskDrive cmdlet to display all disks connected
to the IDE controllers on the virtual machine:
PS C:\> Get-VMHardDiskDrive -VMName SRV-A | `
Format-List ControllerNumber,ControllerLocation,Path
 
ControllerNumber   : 0
ControllerLocation : 0
Path               : C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks\SRV-A.vhdx
 
ControllerNumber   : 0
ControllerLocation : 1
Path               : C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks\SRV-A-data.
vhdx
Viewing the IDE 0 Controller page and its subpages in the Settings dialog box for the
  virtual machine also confrms that the procedure was successful.


_________________
REGISTER AND LOG-IN TO PARTICIPATE
START POSTING YOUR IDEAS AND THOUGHTS AND BUILD THE COMMUNITY OF EXPERTS.
View user profile http://kantipur.friendhood.net

3 Adding and confguring virtual network adapters on 13th October 2013, 1:07 am

Formatted

avatar
Administrator
You can use the Add Hardware page of the virtual machine settings dialog box in Hyper-V
Manager to add new virtual network adapters to your virtual machine  You can choose from
two types of virtual network adapters to add:
  ■ Network adapter  Originally called a synthetic network adapter in the frst version of
Hyper-V, this type of virtual network adapter relies on Integration Components being
installed in the virtual machine to ensure optimal performance  Operating systems
such as Windows Server 2008 R2 and later have Integration Components built into
them  When you use older operating systems for the guest, you might need to install
Integration Components in the virtual machine 
  ■ Legacy network adapter  This type of virtual network adapter emulates a   multiport
DEC 21140 10/100TX 100-MB Ethernet adapter and is provided mainly for three
  reasons:
  ■ To support legacy guest operating systems that do not support the installation of
Integration Components 
  ■ To support non-Windows guest operating systems for which Hyper-V does not
provide Integration Components
  ■ To support network-based installations  (Legacy network adapters have the ability
to boot to the Pre-Boot Execution Environment [PXE] to start the network-based
installation process )

Once a virtual network adapter has been added to your virtual machine, you can   confgure
the adapter by selecting the appropriate page in the virtual machine settings dialog box as
shown in Figures 7-9, 7-10, and 7-11. The confguration settings available for the network
adapter type of virtual network adapter are as follows:
  ■ Virtual switch  You can connect the virtual network adapter to a different virtual
switch on the host or even remove all connectivity if needed 
  ■ Enable virtual LAN identifcation  You can enable VLAN identifcation and specify a
VLAN ID to segment or isolate network traffc for the virtual network adapter.
  ■ Bandwidth Management  This feature allows you to specify how much network
bandwidth the virtual network adapter should use for communications over the
  connected virtual switch 

  ■ Virtual machine queue (VMQ)  This technology allows supported network   adapters
to use hardware packet fltering to deliver packet data from an external virtual ma-
chine network directly to the virtual machine  The effect is to reduce the overhead of
routing and copying packets from the management operating system to the virtual
machine  VMQ is enabled by default on new virtual network adapters 
  ■ IPsec task offoading  This technology allows supported network adapters to
  perform IPsec processing to reduce the processing load on the host  IPsec task
offoading is enabled by default on new virtual network adapters.
  ■ Single-root I/O virtualization  SR-IOV-capable network adapters can be   assigned
directly to a virtual machine to maximize network throughput while minimizing
network latency and the CPU overhead required for processing network traffc.
  Implementing SR-IOV requires host frmware, such as Intel VT-d, that supports SR-IOV
and an SR-IOV-capable network adapter and driver installed in both the management
operating system and the virtual machine 

  ■ MAC address  You can confgure a virtual network adapter to obtain its MAC address
dynamically from the pool of available MAC addresses confgured on the host, or you
can assign a static MAC address to the adapter 
  ■ MAC address spoofng  This feature helps protect the virtual machine against
  attempts to use ARP spoofng to steal IP addresses from the virtual machine by

  allowing the virtual machine to change the source MAC address in outgoing packets to
an address that is not assigned to it 
  ■ DHCP guard  This feature helps protect the virtual machine against Dynamic Host
Confguration Protocol (DHCP) man-in-the-middle attacks by dropping DHCP server
messages from unauthorized virtual machines pretending to be DHCP servers 
  ■ Router guard  This feature helps protect the virtual machine against attempts to use
ARP spoofng to steal IP addresses from the virtual machine by allowing the virtual
machine to change the source MAC address in outgoing packets to an address that is
not assigned to them 
  ■ Port mirroring  This feature helps safeguard the virtual machine against
  unauthorized routers by dropping router advertisement and redirection messages
from unauthorized virtual machines pretending to be routers 
  ■ NIC Teaming  Also known as load balancing and failover (LBFO), this feature   allows
multiple virtual network adapters to be confgured as a team for the purpose of
  bandwidth aggregation or to ensure traffc failover in order to prevent connectivity
loss in the event of the failure of a network component  NIC teaming is supported at
both the host and guest levels in Windows Server 2012, and it can be confgured in the
guest if the physical network adapters of the host do not support it 

You can also use Windows PowerShell to view, add, remove, and confgure virtual netwo
adapters of both the network adapter type and legacy network adapter type  For example,
let’s say you want to add a second virtual network adapter to a virtual machine, connect it t
a virtual switch on the host, and enable both DHCP Guard and Router Guard on the adapter
To do this, you could begin by using the Get-VMNetworkAdapter cmdlet to display a list of
virtual network adapters installed on the virtual machine:
PS C:\> Get-VMNetworkAdapter -VMName SRV-B
 
Name            IsManagementOs VMName SwitchName        MacAddress   Status IPAddresse
----            -------------- ------ ----------        ----------   ------ ----------
Network Adapter False          SRV-B  CONTOSO Virtua... 00155D0BE600        {}
Next you can use the Add-VMNetworkAdapter to create the new adapter and connect it
to the desired virtual switch:
PS C:\> Add-VMNetworkAdapter -VMName SRV-B -VMNetworkAdapterName "Network Adapter 2" `
-SwitchName "MANAGEMENT Virtual Switch"
You can then use the Get-VMNetworkAdapter again to verify the result:
PS C:\> Get-VMNetworkAdapter -VMName SRV-B
 
Name              IsManagementOs VMName SwitchName      MacAddress   Status IPAddresse
----              -------------- ------ ----------      ----------   ------ ----------
Network Adapter   False          SRV-B  CONTOSO Virt... 00155D0BE600        {}
Network Adapter 2 False          SRV-B  MANAGEMENT V... 000000000000        {}
You can pipe the output of the preceding command into the Format-List cmdlet to deter
mine whether DHCP Guard and Router Guard are already enabled on the adapter:
PS C:\> Get-VMNetworkAdapter -VMName SRV-B -VMNetworkAdapterName "Network Adapter 2" `
| Format-List DhcpGuard,RouterGuard
 
DhcpGuard   : Off
RouterGuard : Off
Now use the Set-VMNetworkAdapter to enable both of these features on the adapter:
PS C:\> Set-VMNetworkAdapter -VMName SRV-B -VMNetworkAdapterName "Network Adapter 2" `
-DhcpGuard On -RouterGuard On
Running Get-VMNetworkAdapter again verifes the result:
PS C:\> Get-VMNetworkAdapter -VMName SRV-B -VMNetworkAdapterName "Network Adapter 2" `
| Format-List DhcpGuard,RouterGuard
 
DhcpGuard   : On
RouterGuard : On


_________________
REGISTER AND LOG-IN TO PARTICIPATE
START POSTING YOUR IDEAS AND THOUGHTS AND BUILD THE COMMUNITY OF EXPERTS.
View user profile http://kantipur.friendhood.net

Sponsored content


View previous topic View next topic Back to top  Message [Page 1 of 1]

Permissions in this forum:
You cannot reply to topics in this forum