Difference between revisions of "Preparing a Windows 2008 Server to be used as an openQRM Hyper-V Host"

From openQRM
(Created page with "Hyper-V PowerShell cmdlet http://pshyperv.codeplex.com/releases # In the Server configuration wizard, enable .NET # In the Server Roles window, start Hyper-V # [http://pshyp...")
 
Line 3: Line 3:
 
http://pshyperv.codeplex.com/releases
 
http://pshyperv.codeplex.com/releases
  
# In the Server configuration wizard, enable .NET
+
=== In the Server configuration wizard, enable .NET ===
# In the Server Roles window, start Hyper-V
+
[[File:1 Windows 2008 Hyper-V Server.png|none|thumb|390x390px]]
# [http://pshyperv.codeplex.com/releases Download Hyper-V cmdlet] and extract the files.
+
 
# Install the cmdlet. Be sure to run the terminal as Administrator
+
=== In the Server Roles window, start Hyper-V ===
# When a Registry Editor warning pops up, click 'Yes'
+
[[File:2 Windows 2008 Hyper-V Server.png|none|thumb|390x390px]]
# If you get the message pictured here after installation, Close PowerShell and proceed:
+
 
# Navigate to the Hyper-V folder in your modules directory. Open the properties menu for every item in this folder, click 'unblock' in all of them.
+
=== [http://pshyperv.codeplex.com/releases Download Hyper-V cmdlet] and extract the files. ===
# Import the midule and test it's function. This is done by openign PowerShell and inputing:
+
[[File:3 Windows 2008 Hyper-V Server.png|none|thumb|390x390px]]
# Import-Module 'C:\Program Files\Modules\Hyperv\Hyperv.psd1'
+
 
# Create a profile to auto star the cmdlet:
+
=== Install the cmdlet. Be sure to run the terminal as Administrator ===
## New-Item -path $profile -type file -force
+
[[File:4 Windows 2008 Hyper-V Server.png|none|thumb|390x390px]]
# Navigate to your newly created profile and open it in notepad
+
 
# Insert this line into the document and save it:
+
=== When a Registry Editor warning pops up, click 'Yes' ===
## Import-Module 'C:\Program Files\Modules\Hyperv\Hyperv.psd1'
+
[[File:6 Windows 2008 Hyper-V Server.png|none|thumb|390x390px]]
# Navigate to the Global Profile and open it in Notepad. Insert and save this line:
+
 
## Import-Module 'C:\Program Files\Modules\Hyperv\Hyperv.psd1'
+
=== If you get the message pictured here after installation, Close PowerShell and proceed: ===
 +
[[File:7 Windows 2008 Hyper-V Server.png|none|thumb|390x390px]]
 +
 
 +
=== Navigate to the Hyper-V folder in your modules directory. Open the properties menu for every item in this folder, click 'unblock' in all of them. ===
 +
[[File:8 Windows 2008 Hyper-V Server.png|none|thumb|390x390px]]
 +
 
 +
=== Import the module and test it's function. This is done by opening PowerShell and inputting: ===
 +
<blockquote>
 +
=== ''Import-Module 'C:\Program Files\Modules\Hyperv\Hyperv.psd1'' ===
 +
</blockquote>
 +
[[File:9 Windows 2008 Hyper-V Server.png|none|thumb|390x390px]]
 +
 
 +
=== Create a profile to auto start the cmdlet: ===
 +
<blockquote>
 +
=== ''New-Item -path $profile -type file -force'' ===
 +
</blockquote>
 +
[[File:10 Windows 2008 Hyper-V Server.png|none|thumb|390x390px]]
 +
 
 +
=== Navigate to your newly created profile and open it in Notepad ===
 +
 
 +
=== Insert this line into the document and save it: ===
 +
<blockquote>
 +
=== ''Import-Module 'C:\Program Files\Modules\Hyperv\Hyperv.psd1''' ===
 +
</blockquote>
 +
[[File:11 Windows 2008 Hyper-V Server.png|none|thumb|390x390px]]
 +
 
 +
=== Navigate to the Global Profile and open it in Notepad. Insert and save this line: ===
 +
<blockquote>
 +
=== ''Import-Module 'C:\Program Files\Modules\Hyperv\Hyperv.psd1''' ===
 +
</blockquote>
 +
[[File:12 Windows 2008 Hyper-V Server.png|none|thumb|390x390px]]
 +
 
 +
== Known Bugs ==
 +
Hyper-V 2008 does not support all CPUs. [https://support.microsoft.com/en-us/kb/2568088 Refer to Windows Support]
 +
 
 +
There is a known workaround with the AMD CPU AVX bug:
 +
 
 +
If you recieve this error message:
 +
[[File:13 Windows 2008 Hyper-V Server.png|none|thumb|390x390px]]
 +
Navigate to the Processor settings for that respective VM and change the values to the following:
 +
[[File:14 Windows 2008 Hyper-V Server.png|none|thumb|390x390px]]
 
#
 
#

Revision as of 09:52, 30 October 2020

Hyper-V PowerShell cmdlet

http://pshyperv.codeplex.com/releases

In the Server configuration wizard, enable .NET

1 Windows 2008 Hyper-V Server.png

In the Server Roles window, start Hyper-V

2 Windows 2008 Hyper-V Server.png

Download Hyper-V cmdlet and extract the files.

3 Windows 2008 Hyper-V Server.png

Install the cmdlet. Be sure to run the terminal as Administrator

4 Windows 2008 Hyper-V Server.png

When a Registry Editor warning pops up, click 'Yes'

6 Windows 2008 Hyper-V Server.png

If you get the message pictured here after installation, Close PowerShell and proceed:

7 Windows 2008 Hyper-V Server.png

Navigate to the Hyper-V folder in your modules directory. Open the properties menu for every item in this folder, click 'unblock' in all of them.

8 Windows 2008 Hyper-V Server.png

Import the module and test it's function. This is done by opening PowerShell and inputting:

Import-Module 'C:\Program Files\Modules\Hyperv\Hyperv.psd1

9 Windows 2008 Hyper-V Server.png

Create a profile to auto start the cmdlet:

New-Item -path $profile -type file -force

10 Windows 2008 Hyper-V Server.png

Navigate to your newly created profile and open it in Notepad

Insert this line into the document and save it:

Import-Module 'C:\Program Files\Modules\Hyperv\Hyperv.psd1'

11 Windows 2008 Hyper-V Server.png

Navigate to the Global Profile and open it in Notepad. Insert and save this line:

Import-Module 'C:\Program Files\Modules\Hyperv\Hyperv.psd1'

12 Windows 2008 Hyper-V Server.png

Known Bugs

Hyper-V 2008 does not support all CPUs. Refer to Windows Support

There is a known workaround with the AMD CPU AVX bug:

If you recieve this error message:

13 Windows 2008 Hyper-V Server.png

Navigate to the Processor settings for that respective VM and change the values to the following:

14 Windows 2008 Hyper-V Server.png