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

Groups module issue in version 5.4 #27

Closed
IndyJoeA opened this issue Feb 26, 2025 · 11 comments
Closed

Groups module issue in version 5.4 #27

IndyJoeA opened this issue Feb 26, 2025 · 11 comments

Comments

@IndyJoeA
Copy link

When using the -AddToGroup parameter with version 5.4 of get-windowsautopilotinfocommunity.ps1, there is now an error message "Get-MgGroup: The term 'Get-MgGroup' is not recognized...", and the device does not get added to the requested group. I believe this is because the Groups module is no longer being imported but there is still one reference to it in the script.

@BertVangeel
Copy link

we have the same issue since a few weeks

@andrew-s-taylor
Copy link
Owner

Should be fixed in 5.0.5 which is online now

@andrew-s-taylor
Copy link
Owner

we have the same issue since a few weeks

Can only have been a few days, 5.0.4 hasn't been online for a few weeks

@BertVangeel
Copy link

we still see it happening even today

@andrew-s-taylor
Copy link
Owner

we still see it happening even today

Even on 5.0.5 which I've just added?

@BertVangeel
Copy link

that's correct

@andrew-s-taylor
Copy link
Owner

that's correct

I've removed all reference of the groups module in 5.0.5, can you include a screenshot of both the error and the script details?

@BertVangeel
Copy link

Image

Download and run AutoPilot scripts

[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
Install-Script -name Get-WindowsAutoPilotInfoCommunity -Force
Set-ExecutionPolicy -Scope Process -ExecutionPolicy RemoteSigned
Get-WindowsAutoPilotInfoCommunity -AddToGroup -Assign -Reboot -Online

@andrew-s-taylor
Copy link
Owner

That looks like it's 5.0.4 still

@BertVangeel
Copy link

so how do we force it to use 5.0.5 instead?

@andrew-s-taylor
Copy link
Owner

Clear out the installed script and re-install it, that should grab the latest version

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants