Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Select-MgProfile : The term 'Select-MgProfile' is not recognized as the name of a cmdlet #119

Open
Tularis1 opened this issue Apr 29, 2024 · 1 comment
Labels
type/bug Non-urgent code defect

Comments

@Tularis1
Copy link

When running "Start-HawkTenantInvestigation" after the connection to Microsoft Graph is made, the script throws up;

Select-MgProfile : The term 'Select-MgProfile' 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:31 char:9
+         Select-MgProfile -Name "v1.0"
+         ~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (Select-MgProfile:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

Tested on a new Windows 10 Install.

To Reproduce
Steps to reproduce the behavior:

Run "Start-HawkTenantInvestigation"
Make connection to MS-Graph

Expected behavior
No Error ?

Screenshots
If applicable, add screenshots to help explain your problem.
2024-04-29 16_20_28-Windows 10 x64 - VMware Workstation

File (please complete the following information):

  • File Name:

Additional context

3.4.0 ExchangeOnlineManagement
3.1.0 Hawk
2.18.0 Microsoft.Graph
1.1.183.66 MSOnline
1.10.318 PSFramework
2.1.0 RobustCloudCommand
0.9.6 PSAppInsights
2.0.2.182 AzureAD

@Tularis1 Tularis1 added the type/bug Non-urgent code defect label Apr 29, 2024
@syne0
Copy link

syne0 commented May 12, 2024

I ran into the same error and ended up downgrading some of my modules. I also fully reinstalled HAWK. You also need to be careful to connect the modules in the exact order they are in the documentation.
Try to downgrade below modules to the provided versions:
AzureAD - 2.0.2.180
Microsoft.Graph - 1.28.0

Sucks you need to be running outdated modules, but just a sacrifice that needs to be made I suppose.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Non-urgent code defect
Projects
None yet
Development

No branches or pull requests

2 participants