Installing PlexGuide on Windows 10 Hyper-v
or Windows Server Hyper-v
the steps are almost identical.
To begin well assume your Windows Server local user account your using now is an Administrator account!
First step is to install the Hyper-v
role to windows Server : -
- Right click the start button - then click "Windows Powershell (Admin"
- in the open Powershell window prompt paste without the quotes "Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-v -All" and hit enter
- Once Hyper-v is installed you will be prompted to restart windows which you must do to proceed.
Second step is to configure Hyper-v
's global settings using the installed Hyper-v
manager snap in found in your Start Menu - Windows Administrator tools: -
- In Hyper-v manager snap in select your local machine name in the left nav bar
- Click "Virtual Switch Manager" in the right nav bar
- The "Virtual Switch Manager" windows should now be open and this is where the networking is setup that your VM's will use, so now on the left nav bar click "New Virtual Network Switch"
- Next you should see in the middle nav pane "External", "Internal" & "Private". Select External so you VM's will have internet access and click the "Create Virtual Switch" button bellow
- Now you will name the created VSwitch to a name you choose for easy reference later on,
- Below you will see the External network option pre-selected and a drop down listing the NIC's of your Windows 10 machine, this NIC selection you have 2 options. 1st you only have 1 NIC on your Win 10 machine or 2nd you have an additional NIC which you want to use specifically for your VM to use separate. Either option will work just fine but if you only have the 1 NIC you must make sure to tick the "Allow management operating system to share this network adaptor" option otherwise you will lose your internet completely, but if you do have a 2nd NIC spare to use for your VM then again you can again tick that "Allow management operating system to share this network adaptor" or personally if you have the 2nd NIC to use for VM's then id recommend unticking "Allow management operating system to share this network adaptor" here so that your traffic is separated. So choose the NIC and options depending on your Machines NIC numbers
- Once you have set all the options click OK at the bottom of this window and Hyper-v will create your set Virtual Networking switches and adaptors
Third step is to create a Virtual Machine using the installed Hyper-v
manager snap in found in your Start Menu - Windows Administrator tools
- In hyper-v manager snap in select your local machine name in the left nav bar
- Click Create new - Virtual machine from the right hand nav bar. This launches the New Virtual Machine Wizard.
- In the New VM Wizard click next then Specify a name for your VM and optionally store the Virtual Machine in a custom location of your choosing (making sure you have the full space needed for the resulting VM files) and click next.
- Now select Generation 1 option from the available options and click next (If using an older Linux Distro such as Ubuntu 18.04 it uses an MBR only boot disc / iso, so Gen 1 must be used as it supports MBR disks, Gen 2 doesnt support MBR disks so if you have a GPT iso Gen 2 can be used then)
- The Assign Memory window you have a choice to either set the actual RAM size overall i.e. 4048MB or 4GB or use the Dynamic Memory tick box which personally i normally use with the RAM size set to 1024MB (the fine tuning can always be set / changed later) and again click next
- You now should see the "Configure Networking" screen with a drop-down containing the VSwitches you created in the second step above, so select the name of the VSwitch you created earlier and click next
- Now you should see the "Connect Virtual Hard Disk" screen preset to the location you specified in step 3 above, again specify a name for the VHD associated with your VM and check the location is correct then bellow you will see "Size" which will be your VM's hdd capacity so pls make sure to set this right as you can expand this later but you cannot shrink at all once the VHD is created so please think how much capacity you need and also think about if you will be using additional Drives in PlexGuide if you want to go the multihd route rather than Google Drive route. Normally i recommend starting at 200gb which will be enough for your apps and working data with GDrive route. Once your sure you have set the required capacity size and location click next to proceed
- You should now see "Installation Options" screen where you will need to find and use the required ISO file for the Linux OS you choose for PlexGuide normally for the majority of users this would be Ubuntu Server 18.04 LTS. So browse to where your ISO is saved and open it to attach to your VM and click next
- Finally you should see the "Summary" screen where you can check your using the required resources and assets before finally clicking finish which will compile and create your Hyper-V Virtual Machine
Hopefully you should now see your Setup Virtual Machine in the Hyper-V manager middle pane named as set above,
- Now you can select the created VM to show its actions in the right Nav bar again one being "Settings" which if you set your VM to use "Dynamic Memory" size as recommended earlier you will want to go into "Settings" of your VM and click Memory in the left nav bar of the VM's "Settings" which you should see the Startup RAM Size you set earlier 1024 and below the "Enable Dynamic Memory" option ticked or unticked if you prefer to set the VM's total RAM usage statically. If you choose Static RAM then ignore this step and proceed on to 2. but if you choose "Dynamic Memory" for your VM then in the "Minimum RAM" and "Maximum RAM" fields Min must be equal too or smaller than your set RAM size called your Startup RAM size in the very top field, but below for the "Maximum RAM" field this defaults to a very high value which means if this isnt set your VM is allowed to use as much RAM as your Windows 10 host has available when needed so please set this "Max RAM" value to a value of the maximum size of RAM or limit for your VM to not go over! RAM can be changed up or down in size when powered down or increased while running but without set checkpoints.
- Next select Security from the Left nav bar and make sure "Secure boot" is Disabled which is very important to check! Also "Encryption Support" is also disabled optionally and below that "Security Policy" also should be disabled.
- Select "Processor" option from the left nav bar next and here specify the VCPU count / cores you can spare for your VM to utilise also try not to use 4 VCPU's if your Win 10 host is only a 4 core CPU also as it can bog your host machine down when your VM is running so set this value as needed min 2 processors up i recommend but normally 4 processor count would be the max needed but this value again can be changed as long as the VM is shutdown.
- Now select "Integration Services" from the left nav bar and its recommended to untick "Data Exchange" & "Guest Services" here but again this is optional.
- Finally select "Checkpoints" from the left bar and optionally tick "Enable Checkpoints" if you want to be able to create Checkpoints / Snapshots for your VM for quick rollbacks when needed, Production or Standard will work as well as automatic checkpoint options. Personally I use "Standard Checkpoints" created manually but as i say this is optional and is a handy feature to utilise too. Once your done here click OK to Save all your VM "Setting" changes.
Once your at this point your VM has been created and configured to meet your needs, so now just right click on your VM from the "Hyper-V manager" window and click "Connect" to launch a Remote console to your VM and finally click the "Start" button to boot your VM. This will then boot from the ISO file you specified during creation, which you can now use just as you would as it were a local system so follow the same steps HERE
This is a 1st revision,