Hello @Daniel-Fiore ,
We are updating our Microsoft Windows Server 2016 MCSA track starting next week. We plan to start filming 70-740 and 70-742 on Monday. The previous shows were recorded in the last quarter of 2017, and many things have changed since then!
As for the current content, is is accurate. Lets see if we can get it working for you.
- You should be able to install the NuGet package provider. This command hasn't changed. There is a newer version of NuGet available (2.8.5.208). The computer will need an internet connection for the command to work. Also make sure you are running PowerShell with administrative rights. (There is a way to download the package on another machine if you needed to do an offline install) Try leaving the MinimumVersion parameter out and see if that works. Something like this...
Install-PackageProvider -Name NuGet
You can verify the package provider was successfully installed by running
Get-PackageProvider
Here is a link to check out as well...
https://docs.microsoft.com/en-us/powershell/module/packagemanagement/install-packageprovider?view=powershell-5.1
- New-VHD and New-VirtualDisk are different cmdlets that do two very different things. New-VHD is the cmdlet for creating VHDs to use with virtual machines in Hyper-V. New-VirtualDisk is the cmdlet for creating new virtual disks in Storage Pools.
The PowerShell command New-VHD is part of the hyper-v module. You will need to make sure this module is installed. You can install the module using the Add Roles and Features Wizard, or by using the Install-WindowsFeature cmdlet.
In the Add Roles and Features wizard, click next till you get to Select Features. In the list of features, navigate to Remote Server Administration Tools -> Role Administration Tools -> Hyper-V Management Tools and select Hyper-V Module for Windows PowerShell.
To install the Hyper-V module using PowerShell, use the following...
Install-WindowsFeature -Name Hyper-V-PowerShell
You should now be able to use the New-VHD cmdlet. You can verify the module is installed by running...
Get-Module
I've verified all of the above commands on Windows Server 2016 version 1607, running PowerShell 5.1.
I hope this helps, if you have any more questions or issues, just let me know.
Thanks for watching and being a member!!
Mike Rodrick
Edutainer, ITProTV
**if the post above has answered the question, please mark the topic as solved.