Forum Discussion
The term '...' is not recognized as the name of a cmdlet
- May 24, 2020
OK, please try the following commands in PowerShell;
Install-Module MSOnline
then,
Import-Module MSOnline
then try to connect to the MS Online service by entering;
Connect-MsolService
You should be prompted now for your M365 Global Admin credentials. Login and you can run the Get-MsolUser commands.
In order to execute the Get-ADUser commands, try running Import-Module activedirectory
Hi, what are you trying to do it PowerShell please? There are any number of modules you may need. It would help if you could explain what you want to achieve and then we can try and advise you.
Hi PeterRising
I would like to run some commands to extract some data. A couple of it will be Get-ADUser and Get-MsolUser
Thanks.
- PeterRisingMay 24, 2020MVP
OK, please try the following commands in PowerShell;
Install-Module MSOnline
then,
Import-Module MSOnline
then try to connect to the MS Online service by entering;
Connect-MsolService
You should be prompted now for your M365 Global Admin credentials. Login and you can run the Get-MsolUser commands.
In order to execute the Get-ADUser commands, try running Import-Module activedirectory
- DonPham12Aug 25, 2020Copper Contributor
I am trying to run the Set-CsUser command but it throws an error "The term 'Set-CsUser' is not recognized as the name of a cmdlet." I guess I am missing that cmdlet in a module? Can you please guide me on how to fix this. Thank you.
- betelhemkdeliverictNov 11, 2020Copper Contributor
when i installing exchange server i face error on the prerequisite
Install–WindowsFeature : The term 'Install–WindowsFeature' is not recognized as the name of a cmdlet, function, script
file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:1 char:1
+ Install–WindowsFeature RSAT–Clustering–CmdInterface, NET–Framework–45 ...
+ ~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (Install–WindowsFeature:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundExceptionthis is the error
- clleeMay 24, 2020Brass Contributor
- PeterRisingMay 24, 2020MVP
Sounds like you may be behind a proxy server? If so, please try the following commands in PowerShell;
$webclient=New-Object System.Net.WebClient $webclient.Proxy.Credentials = [System.Net.CredentialCache]::DefaultNetworkCredentials
Then try the commands again. Alternatively, can you break straight out to the internet and bypass your proxy server?