Closed Nepoxx closed 10 months ago
It means intune-portal realized you are not using Ubuntu, which is supported.
Could you make sure you have updated /etc/os-release
file correctly? If you did, could you reboot your computer to restart intune service (sorry I forgot the name) and try again?
Of course!
$ cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04.6 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.6 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal
I have rebooted and I get the same error :(
For what it's worth, I've also tried the following, rebooted and then it still gave the same error
PRETTY_NAME="Ubuntu 22.04.3 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.3 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
It means intune-portal realized you are not using Ubuntu
That's interesting. I'm trying to figure out how that's being done. I used lurk to trace calls and I can't figure out how it is done
Note that lurk or strace mostly cannot tell you what happened. intune does all these checks with background systemd services, such as
intune-daemon.socket, intune-daemon.service, intune-agent.timer, and microsoft-identity-broker.service
. intune-agent frontend is just showing the result.
I got past the error by updating my /etc/lsb_release
as mentioned here (Although intune definitely accesses /etc/os-release
as well). I'm stuck a bit further
Feb 02 11:42:39 nepoxx-xps intune-portal[4598]: enroll{device_name=nepoxx-xps version=0.0.0}: Starting new device enrollment
Feb 02 11:42:39 nepoxx-xps intune-portal[4598]: enroll{device_name=nepoxx-xps version=0.0.0}: Submitting enrollment request attempt=1
Feb 02 11:42:39 nepoxx-xps intune-portal[4598]: oneauth{tag="9a8hm"}: HTTP status: 404
Feb 02 11:42:39 nepoxx-xps intune-portal[4598]: oneauth{tag="5fsch"}: Failed to get image from Graph
Feb 02 11:43:03 nepoxx-xps intune-portal[4598]: enroll{device_name=nepoxx-xps version=0.0.0}: Non-retryable error encountered while attempting to enroll error=HTTP error 400: Bad Request
Closing in favor of #1
Hi, did you find solution to the new error "Couldn't enroll your device"? I am having the same error...
Hi, did you find solution to the new error "Couldn't enroll your device"? I am having the same error...
I was able to get it to work by modifying /etc/lsb_release
and using the packages in this repo, not the ones from AUR. The ones in AUR use newer versions and I think MS is now using other methods to detect the OS, but that's pure speculation on my part.
Here's my lsb_release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.3 LTS"
I got past the error by updating my
/etc/lsb_release
as mentioned here (Although intune definitely accesses/etc/os-release
as well). I'm stuck a bit furtherFeb 02 11:42:39 nepoxx-xps intune-portal[4598]: enroll{device_name=nepoxx-xps version=0.0.0}: Starting new device enrollment Feb 02 11:42:39 nepoxx-xps intune-portal[4598]: enroll{device_name=nepoxx-xps version=0.0.0}: Submitting enrollment request attempt=1 Feb 02 11:42:39 nepoxx-xps intune-portal[4598]: oneauth{tag="9a8hm"}: HTTP status: 404 Feb 02 11:42:39 nepoxx-xps intune-portal[4598]: oneauth{tag="5fsch"}: Failed to get image from Graph Feb 02 11:43:03 nepoxx-xps intune-portal[4598]: enroll{device_name=nepoxx-xps version=0.0.0}: Non-retryable error encountered while attempting to enroll error=HTTP error 400: Bad Request
Note that I did enroll test on manjaro... I didn't update /etc/lsb_release
file but the enrollment process was working perfectly fine.
That's why I was not suggesting updating this file... It looks unnecessary.
Got more information today, and put the correct solution into README.md.
I have tried to run this multiple times and I always end up with this error
ERROR Error calling IWS for Terms of Use: Unexpected failure: Bad Request
This is a fresh arch install (EndeavourOS)
Debug steps taken:
journalctl --user -u microsoft-identity-broker.service
-> no errorssudo journalctl -u microsoft-identity-device-broker.service
-> no errorsseahorse
to validate keyring being default and populatedldd /usr/lib/libmsal_dbus_client.so
everything definedjournalctl -xe
shows same error as title (which is also shown when runningintune-portal