Closed CravateRouge closed 1 year ago
I just updated AADInternals as it had some bugs related to writing binary files. Could be reason for that, so just update with Update-Module AADInternals
and try again.
If the problem still exists, please try again with -Verbose
switch to see what's happening.
Finally, you can't get access token to join a device from a device that is already AAD joined. That is, if you are running AADInternals on AAD joined device to get the AADJoin token, it will fail. This is due to some internals Windows stuff I haven't figured out yet.
I'm in the last case so this is why it's not working. If you figure this out I would be curious to know!
I want to join a fake device but I have the following result doing so:
I don't understand because
Get-AADIntAccessTokenForAADJoin
generates a token specifically for this purpose but it is still considered as invalid? Could you enlight me on what's happening? Is it because of a policy or MFA?