Difference between revisions of "Preparing a Windows 2008 Server to be used as an openQRM Hyper-V Host"
(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...") |
|||
| (9 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | Hyper-V | + | Step-by-step instructions on preparing a Windows 2008 Server to be used as an openQRM Hyper-V Host. |
| − | http://pshyperv.codeplex.com/releases | + | == Step-by-Step == |
| + | 1. In the Server configuration wizard, enable .NET[[File:1 Windows 2008 Hyper-V Server.png|none|thumb|390x390px]]2. In the Server Roles window, start Hyper-V[[File:2 Windows 2008 Hyper-V Server.png|none|thumb|390x390px]]3. [http://pshyperv.codeplex.com/releases Download Hyper-V cmdlet] and extract the files.[[File:3 Windows 2008 Hyper-V Server.png|none|thumb|390x390px]]4. Install the cmdlet. Be sure to run the terminal as Administrator[[File:4 Windows 2008 Hyper-V Server.png|none|thumb|390x390px]]5. When a Registry Editor warning pops up, click 'Yes'6. [[File:6 Windows 2008 Hyper-V Server.png|none|thumb|390x390px]]6. If you get the message pictured here after installation, Close PowerShell and proceed:[[File:7 Windows 2008 Hyper-V Server.png|none|thumb|390x390px]]7. 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]]8. 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]]9. 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]]10. 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]]11. 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: | |
| − | + | ||
| − | + | 1. If you receive this error message: | |
| − | + | [[File:13 Windows 2008 Hyper-V Server.png|none|thumb|390x390px]] | |
| − | + | 2.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]] | |
| − | # Navigate to the | + | |
| − | + | == Resource Links == | |
| + | Hyper-V PowerShell cmdlet - http://pshyperv.codeplex.com/releases | ||
# | # | ||
| + | __NOTOC__ | ||
| + | [[Category:Setting up]] | ||
| + | [[Category:Hyper-V]] | ||
| + | [[Category:Tutorial]] | ||
Latest revision as of 10:46, 30 October 2020
Step-by-step instructions on preparing a Windows 2008 Server to be used as an openQRM Hyper-V Host.
Step-by-Step
1. In the Server configuration wizard, enable .NET
2. In the Server Roles window, start Hyper-V
3. Download Hyper-V cmdlet and extract the files.
4. Install the cmdlet. Be sure to run the terminal as Administrator
5. When a Registry Editor warning pops up, click 'Yes'6.
6. If you get the message pictured here after installation, Close PowerShell and proceed:
7. 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. 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. Create a profile to auto start the cmdlet:
New-Item -path $profile -type file -force
10. 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. Navigate to the Global Profile and open it in Notepad. Insert and save this line:
Import-Module 'C:\Program Files\Modules\Hyperv\Hyperv.psd1'
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:
1. If you receive this error message:
2.Navigate to the Processor settings for that respective VM and change the values to the following:
Resource Links
Hyper-V PowerShell cmdlet - http://pshyperv.codeplex.com/releases
