Windows PowerShell 5.1 is required to load modules using Windows PowerShell compatibility feature. Import-Module: Detected Windows PowerShell version 4.0. When you do as the error message suggests and run the Import-Module ActiveDirectory command, you get another error message. For more information, run 'Import-Module ActiveDirectory'. Get-ADUser: The 'Get-ADUser' command was found in the module 'ActiveDirectory', but the module could not be loaded. Get-ADComputer: The 'Get-ADComputer' command was found in the module 'ActiveDirectory', but the module could not be loaded. After spinning up the VM and installing PowerShell 7 and the standalone RSAT package for Windows 8.1, I got the following error messages when trying to query AD: PowerShell 7 is supported on both systems, but the AD module is not. My last test was done on Windows 8.1, which is the same core as Windows Server 2012 R2. Is there another inconsistency in Microsoft's own documentation, or is there a specific reason to leave version 2016 out of support? Windows Server 2012 R2 and Windows 8.1 What a surprise! The module works well, even on Windows Server 2016. Testing the PowerShell 7 AD module on Windows Server 2016
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |