Код ошибки 80180002

Disable MDM and MAM security policies to regain access

by Claire Moraa

Claire likes to think she’s got a knack for solving problems and improving the quality of life for those around her. Driven by the forces of rationality, curiosity,… read more


Updated on

  • When you set up Intune, you create a Microsoft account tied to your organization.
  • You may be locked out if you try to access it from a personal PC. Your admin must disable conditional access to remove the account restrictions.

When trying to join a domain such as Azure AD, you must fulfill various requirements before your account can be successfully created. Things don’t seem to be going as planned because users are met with the error 80180002 when doing so.

Further, the error code is accompanied by a message that says The Mobile Device Management (MDM) server failed to authenticate the user. Stay with us as we unpack what this error means and how to resolve it.

What is error code 80180002?

The error code 80180002 is what happens to users who try to create or add a Microsoft work account on their personal PCs. You may be wondering why this is happening, and below are some possible reasons:

  • Insufficient permissions – Your organization manages most work Microsoft 365 accounts. This is usually because of some security settings. So while the account may belong to you, you are somewhat restricted in how you manage it.
  • Wrong configurations – If your device or account does not meet the prerequisites to join Azure AD, your account may be denied access.
  • Network change – If the user’s account is linked with a Microsoft account, it’s possible that the user has changed their network, and you need to link them with the correct Azure AD tenant again.
  • Device not on MDM – MDM is a security policy that determines the devices that can access Azure. If your device is not enrolled in Mobile Device Management (MDM), you might get the error 80180002.

How do I fix error 80180002?

Before any advanced troubleshooting, check the following:

  • Ensure you have administrative privileges.
  • Check your network again and ensure it reflects your location.

1. Add the account to your device

  1. Hit the Windows key and click on Settings.settings windows 11
  2. Click on Accounts on the left pane, then select Access work or school.access workor school option
  3. Locate the account you’re trying to log in using, then disconnect it.
  4. Wait for a few moments, then add the account again.

2. Disable conditional access

  1. Sign in to your Azure account.
  2. Click on the Menu at the top left corner and select Azure Active Directory.
  3. Select Protect & secure on the left pane, then click on Conditional Access.
  4. Under the Access policy option, toggle it off.

Azure AD conditional access allows you to control access to your applications and data based on the location of your users, their identity, and their device. When you disable this option, you allow users to join with any device without restrictions.

Read more about this topic

  • Fix: No Internet, Secured Error on Windows 11
  • Fix: Keyboard Shortcuts are Not Working in Photoshop
  • Fix: Keyboard Shortcuts Are Not Working in Chrome
  • Fix: NAS Drive Not Showing in Windows 11

3. Remove the account credentials 

  1. Hit the Windows Search icon, type Credential Manager in the search bar, then click Open.
  2. Click on Windows Credentials.going windows credentials windows 11
  3. Select MicrosoftAccount, click on it to expand, then hit Remove.
  4. You’ll get a command prompt asking you to confirm whether you want to remove the credentials, so click Yes.

4. Change MDM and MAM settings

  1. Sign in to your Azure account.
  2. Click on Azure Active Directory under Azure services.
  3. Select Mobility (MDM and MAM) on the left pane.
  4. Click on Microsoft Intune under Mobility (MDM and MAM).
  5. Find MDM user scope and MAM user scope options, set them to None then, click on Save.

MDM stands for mobile device management, and MAM stands for mobile application management. They are two ways to manage your company’s mobile devices. MDM is a more comprehensive solution that allows you to manage all aspects of the device. 

MDM and MAM are two security features that can be used to provide a secure workspace for employees. However, they also have some drawbacks. MDM allows you to control the devices that can connect to your network.

When enabled, they can restrict the devices trying to add user access. Once disabled, you can get rid of the 80180002 error.

Elsewhere, you may get an error where your Microsoft account doesn’t exist, but we have answers on how to fix this issue.

For any additional thoughts don’t his topic, leave a comment down below.

newsletter icon

При регистрации устройства Windows в школьной или рабочей сети некоторые пользователи получили сообщение об ошибке 80180002. Серверу управления мобильными устройствами (MDM) не удалось аутентифицировать пользователя. Эта ошибка не позволяет пользователям присоединять свои устройства к Azure Active Directory и регистрироваться в MDM (управление мобильными устройствами).

Серверу управления мобильными устройствами (MDM) не удалось аутентифицировать пользователя.

Полное сообщение об ошибке:

Код ошибки 80180002

Серверу управления мобильными устройствами (MDM) не удалось аутентифицировать пользователя. Повторите попытку или обратитесь к системному администратору.

Если вы входите в число тех пользователей, которые столкнулись с этой ошибкой, вам помогут решения, представленные в этом посте.

Что такое аутентификация MDM?

MDM или Mobile Device Management позволяет ИТ-администраторам управлять мобильными устройствами. Он имеет различные методы проверки подлинности, которые администраторы могут включить для безопасного входа в систему для назначенных пользователей. MDM играет решающую роль в корпоративной среде. Когда организация запускает все из облака, сотрудники могут безопасно получить доступ к сети компании. Аутентификация MDM — это процесс аутентификации пользователя при доступе к сети компании.

Следующие решения помогут вам исправить Ошибка 80180002, серверу управления мобильными устройствами (MDM) не удалось аутентифицировать пользователя. ошибка при регистрации устройства в Azure Active Directory.

  1. Убедитесь, что ваша учетная запись не отключена
  2. Изменение настроек MDM и MAM

Ниже мы подробно представили все эти решения.

1]Убедитесь, что ваша учетная запись не отключена

Azure Active Directory позволяет пользователям отключать свои устройства. Используя эту функцию, вы можете отключить потерянные устройства и устройства, которые больше не используются. Проверьте, отключено ли ваше устройство или нет. Вам помогут следующие шаги:

Просмотр отключенных устройств в Azure AD

  1. Войдите в Azure AD.
  2. Перейдите в «Устройства > Управление устройствами».
  3. Разверните вкладку вашего устройства.

Если отображается сообщение «Устройство отключено», обратитесь к системному администратору, чтобы повторно включить устройство.

2]Изменить настройки MDM и MAM

Если ваше устройство уже включено, сообщение об ошибке появляется из-за неверных настроек MDM или MAM в Microsoft Intune. Только ваш администратор может изменить настройки MDM или MAM. Также у администратора должна быть подписка на Microsoft Intune. Если вы являетесь администратором, следуйте приведенным ниже инструкциям, чтобы устранить проблему. Без подписки на Intune вы не сможете изменить настройки MDM или MAM.

Изменение параметров MDM и MAM в Azure AD

  1. Войдите на портал Azure и перейдите в Azure Active Directory.
  2. Выберите Мобильность (MDM и MAM) с левой стороны.
  3. Выберите Microsoft Intune.
  4. Измените параметры области пользователя MDM и области пользователя MAM на None.
  5. Сохранить изменения.

Связано: код ошибки 8018004. Ваша учетная запись не была настроена на этом устройстве, поскольку не удалось включить управление устройством. Это устройство может не иметь доступа к некоторым ресурсам, таким как Wi-Fi, VPN или электронная почта.

Что такое код ошибки 0x80180003?

Код ошибки 0x80180003 возникает, когда пользователь не авторизован для регистрации в Microsoft Intune или Azure AD. При возникновении этой ошибки вы увидите следующее сообщение:

Что-то пошло не так. Этот пользователь не авторизован для регистрации. Вы можете попробовать сделать это еще раз или обратиться к системному администратору с кодом ошибки 80180003.

Эта ошибка может возникать по многим причинам, например, у пользователя установлена ​​домашняя версия Windows 11/10, устройство пользователя заблокировано администратором, он уже зарегистрировал максимальное количество разрешенных устройств в Intune и т. д.

Я надеюсь, что решения, представленные в этой статье, помогли вам решить проблему.

Связано: устройства Windows не могут синхронизироваться с Intune после регистрации.

Microsoft Error Code 80180002

The Microsoft error code  80180002 shows up when you are trying to set up an account on the device.

This is the issue that occurs because of the failure of the device management system. 

Usually, users face this issue when they are trying to set up a work account and do not have admin privileges.

The Microsoft team regularly keeps an eye on the problems that the users face on their platform and also suggests fixes for the same. 

We will talk about the error code  80180002 that shows up while setting up a Microsoft account.

What additional problems can it cause, and what can be done to solve those issues will be discussed in this blog.

Let’s get you into the account as soon as possible.


How to solve the error code 80180002 on Microsoft?


This is one of the problems on Microsoft that is more on the technical side. You might find it difficult to conduct the troubleshooting processes on your own but that is why we are here to help you.

We will explain all the solutions in easy steps so that solving this error code does not seem like a monumental task for you.

Fix 1: Run the hardware troubleshooter

This is to identify any problems that might be on the hardware of the device that you are using.

Here are the easy steps to run the hardware troubleshooting tool on your device.

  • Press the Windows and the R key together.
  • It will open the Run dialog box
  • In the dialog box, type msdt.exe -id DeviceDiagnostic
  • This will initiate the device hardware troubleshooting process and the problem will be solved.

Fix 2: The Microsoft Intune settings are not correctly configured

According to the support page, there might be issues with Microsoft Intune that could lead to this issue of not being able to set up your account.

You need to change the MAM/MAM settings on Microsoft Intune to none.

Then try to log in once again. In most cases, you will now be able to set up your account without any trouble.


Fix 3: The device management system is not properly integrated

Turning on the device management will also help you eliminate the error code on your device. 

Even if you have turned this on before, still go through the process once again to make sure that it is working correctly.

Here is how you can turn on the device management on Microsoft.

  • Follow this link on your browser through an administrator account.
  • When you open the link, find the tab that reads Devices
  • Click on Users and then click on Settings
  • Now click on Windows settings
  • The Desktop Security setup option will be visible. Click on it
  • Click on the Windows Device management option
  • Now click on the Enable option
  • The Windows Device Management will now be turned on.

This is how you can turn on Windows Device Management and makes sure that it is working.


Fix 4: Make sure that you have activated Microsoft 365 

For running several processes on Microsoft especially,  integrated accounts, you will need to ensure that you have an active package for Microsoft 365.

Here are the steps for checking if you have Microsoft 365 enabled on your device.

  • Launch any Microsoft application.
  • Click on the File tab
  • Click on the option that reads Account
  • Now you will be able to stake a look at the product information and the active package of Microsoft 365 if it is enabled.

If you find that you do not have an active package, you will need to get one before you can move forward with any account setup.


Fix 5: Contact the Microsoft support

Since we have already mentioned that this problem could be a little technical, there might be a point where you will need to contact the Microsoft support team with your issue.

However, we have tried to provide you with all the tried and tested solutions, sometimes the issue might run deep and you will not be able to solve it on your end.

You can also drop a query with the user support forums where developers and other experienced users may be able to help you with the issue.


To conclude


The error code 80180002 on Microsoft is one of the fairly technical errors on the platform and you might need to solve that with the help of a technician.

However, before that stage arrives, there are some solutions that we have suggested above that might be able to help you eliminate the error code on your own.

We hope that this was a helpful article, keep following for more technical advice.


Like This Post? Checkout More

  • How To Fix Microsoft Error Code 80090034?
  • How To Fix Microsoft Office Error Code 30015-11?
  • How To Fix Microsoft Windows OS Error 0x80070570?
  • How To Fix Microsoft Error Code 80180014?

While registering a Windows device to a school or work network, some users received Error 80180002, The Mobile Device Management (MDM) server failed to authenticate the user. This error prevents users from joining their devices to Azure Active Directory and enrolling into MDM (Mobile Device Management).

The Mobile Device Management (MDM) server failed to authenticate the user

The complete error message is:

Error code 80180002

The Mobile Device Management (MDM) server failed to authenticate the user. Try again or contact your system administrator.

If you are among those users who encountered this error, the solutions provided in this post will help you.

What is MDM authentication?

MDM or Mobile Device Management, allows IT administrators to manage mobile devices. It has different authentication methods that administrators can enable for secure sign-in for the designated users. MDM plays a crucial role in the corporate environment. When an organization runs everything from the cloud, employees can access the company’s network securely. MDM authentication is the process of authenticating a user while accessing the company’s network.

Mobile Device Management (MDM) server failed to authenticate the user, Error 80180002

The following solutions will help you fix Error 80180002,Mobile Device Management (MDM) server failed to authenticate the user error while registering your device on Azure Active Directory.

  1. Make sure that your account is not disabled
  2. Change MDM and MAM settings

Below, we have provided all these solutions in detail.

1] Make sure that your account is not disabled

Azure Active Directory allows users to disable their devices. Using this feature, you can disable your lost devices and the devices that are no longer in use. Check if your device is disabled or not. The following steps will help you:

View disabled devices in Azure AD

  1. Login to Azure AD.
  2. Go to “Devices > Manage Devices.”
  3. Expand your device tab.

If it shows the “Device is disabled” message, contact your system administrator to re-enable your device.

2] Change MDM and MAM settings

If your device is already enabled, the error message occurs due to the incorrect MDM or MAM settings in Microsoft Intune. Only your Administrator can change the MDM or MAM settings. Also, the administrator should have a subscription to Microsoft Intune. If you are an administrator, follow the instructions below to fix the issue. Without a subscription to Intune, you will not be able to change the MDM or MAM settings.

Change MDM and MAM settings in Azure AD

  1. Log in to the Azure portal and go to Azure Active Directory.
  2. Select Mobility (MDM and MAM) from the left side.
  3. Select Microsoft Intune.
  4. Change the MDM user scope and MAM user scope options to None.
  5. Save changes.

Related: Error Code 8018004, Your account was not set up on this device because device management could not be enabled. This device might not be able to access some resources, such as Wi-Fi, VPN, or email.

What is the error code 0x80180003?

The error code 0x80180003 occurs when a user is not authorized to enroll in Microsoft Intune or Azure AD. When this error occurs, you will see the following message:

Something went wrong. This user is not authorized to enroll. You can try to do this again or contact your system administrator with error code 80180003.

This error can occur due to many causes, such as the user has Windows 11/10 Home edition, the user’s device is blocked by the administrator, he has already enrolled the maximum number of allowed devices to Intune, etc.

I hope the solutions provided in this article helped you resolve the issue.

Related: Windows devices can’t sync with Intune after enrollment.

The Mobile Device Management (MDM) server failed to authenticate the user

Some customers have reported that an error message prevents them from adding work access to Microsoft 365. In this blog, we will go over the most effective solutions to help you resolve the error code 80180002 when adding work access to Microsoft 365. Follow through for more information on how to resolve error code 80180002.

How to fix error code 80180002 when adding work access to a PC running the Windows operating system:

  1. Firstly, sign in to Office 365.
  2. Click on the launcher.
  3. Now click on “Admin”.
  4. Under “Admin centers” click on “Azure Active Directory”.
  5. Click on “All services”.
  6. Now click on “Azure AD Conditional Access”.
  7. In my example, there is a policy that causes the error.
  8. Select and remove it to resolve the issue.

In this blog post, I’ll explain the causes of this error and demonstrate the steps you must undertake to fix it, including screenshots along the way.


Causes of the error 80180002 in Microsoft 365

When the error occurs a warning similar to the one shown above will display complete with the error code ID and the code itself. This allows you to reference this issue and find a solution to help mitigate the error. The error correlation ID is your maid ID liked with your account. You may require this if you have the issue fixed by a professional group of individuals.

Error Code 80180002 can be caused by a number of various problems. The following are the most Prevalent reasons for this error message:

  • Errors in the registry
  • System files that have been mistakenly associated with and removed by other applications.
  • Viruses or malware that cause application or system file corruption
  • Installations that haven’t been completed to their full potential

Common symptoms include:

  • Runtime issues with previously working apps
  • Your computer’s reaction time to commands input using the keyboard or mouse is slow.
  • You’re having trouble shutting down or setting up your computer.
  • An error notice about your registry, updates, or response time has shown.

You can try a variety of different techniques to try to fix Error Code 80180002. Because the problem has various roots, some of the approaches used to properly resolve the issues are rather easy, while others require extensive knowledge or expertise. If the procedures listed below aren’t effective in resolving the problem, or if you aren’t confident in your ability to use them, hire a competent Windows repair professional to help you.

security office365 windows 11

info Recommended Software

Additional Information and Repair Instructions for error code 80180002

There are several strategies you may take to try to fix the difficulties underlying Error Code 80180002 due to the variety of circumstances that might lead to the error. While some of these procedures are simple to follow, others may necessitate the use of applications such as registry cleaners and driver installation wizards. If you are unsure about using such software, call a trained Windows repair specialist for assistance.

Fix error code 80180002 in Microsoft 365 by cleaning out the registry

There are many different registry cleaning software available on the Internet, but not all of them come from reliable sources. You can use the registry cleaning utility included in your Windows software package instead of trusting a file from an unknown vendor.

Run this utility to do a file scan and determine which ones may need to be repaired. Most of the time, the registry cleaner can repair the relevant files and fix the problem on its own.

It’s a good idea to restart your computer after using the registry cleaner to ensure that your computer can appropriately examine the newly restored files.

Fix error code 80180002 in Microsoft 365 by making sure your drivers and software are up-to-date

Error Code 80180002 occurs when drivers are out of date in some circumstances. If you feel this is the case, you may check the status of your different drivers by going into your operating system’s settings and selecting “Update Drivers.”

You may also check your system for any essential Windows software updates that may help you resolve the problem code.

After you’ve double-checked and installed any required drivers, restart your computer to completely implement any changes made during the installation process.

  • Firstly, sign in to Office 365.

Use your regular login details to sign into to your account.

  • Click on the launcher.

The launcher is illustrated by nine dots, click on this to access it.

  • Now click on “Admin”.

  • Under “Admin centers” click on “Azure Active Directory”.

I have Azure Active Directory, pinned to the Admin page, however, if you haven’t click on “Show all”.

  • Click on “All services”.

All service is a feature within to allow users to access the entire Azure directory feature page.

  • Now click on “Azure AD Conditional Access”.

  • Select and remove it to resolve the issue.

That’s it for this Blog thank you for taking time out to read our content, please feel free to email our team about how it went if you followed the steps or if you need more help with the questions we answered in this Blog.

One of my customers recently decided it was time to upgrade their systems. Their entire operation is home-based for each employee, so we had their systems delivered directly to their homes. We got started with the process of logging in and activating Office 365 (they are running E3 licenses), and ran into a number of errors that all basically just give a code and say «Something went wrong…»
Documentation is very sketchy on the errors, and they all seem to reference InTune, but InTune has never been part of this customer’s setup, and all of their pre-existing systems work fine.

We managed to find a work-around for one user, and got their system fully activated, but that was followed by Outlook being unable to access their email account. An Exchange engineer from MS was able to get us the rest of the way working, but after several hours of messing with it and doing repairs with the SARA tool on 1 system, I wasn’t about to do this on all the systems. And it’s a good thing I didn’t, because 3 days later Outlook is hanging for up to a minute followed by kicking the user out and asking for a log in every 10 minutes.

I have spent inordinate amounts of time troubleshooting this myself over the last several weeks, with no results. I have been able to prove that these systems have no problem logging into my own O365 account as normal (we’re running MS 365 Business Standard, not E3) and I’ve also wiped one of them and found that even a fresh version of Win10 Pro and Office is still unable to sign-in/activate (so it can’t be anything the system integrator did).

We’re approaching 4 weeks since the systems were purchased, the customer is pissed, the systems integrator is willing to help, but there is a limit to the ways they can help, and MS is basically incompetent as they can’t even get someone on their Azure team on the phone to speak with me, but have had the Exchange team speak with me twice, even though I was very clear that I needed to speak with the Azure team.

I would appreciate any help or advice anyone has to offer. (Yes, I plan to cross-post this in r/O365 or wherever makes sense.) Also going to see about adding screenshots of the errors.

fix-microsoft-teams-error-code-80180002-something image

WebJun 18, 2021 Steps to Fix Microsoft Teams Error Something Went Wrong Error Code 80180002 Unknown Error Code 0x80180002 Step 1) Disconnect Old Work and school account, then sign out …
From youtube.com
Author AarohanTechSol
Views 33.6K
See details »


[SOLVED] ERROR JOINING AZURE AD DOMAIN — THE …

solved-error-joining-azure-ad-domain-the image

WebJan 8, 2020 We have a client using 365 business, fully Azure AD, no hybrid. We have a new Windows 10 PC and are getting Server error code: 80180023 when trying to join the domain. PC has internet, DNS is fine, …
From community.spiceworks.com
See details »


80180002 ERROR — MICROSOFT COMMUNITY

80180002-error-microsoft-community image

WebJan 20, 2023 Created on July 11, 2020 80180002 error Hi there, I’ve use Windows 7 before so was time to get windows 10 on my PC so now I have PC and laptop running Windows 10. When try sign in to my one of …
From answers.microsoft.com
See details »


SOMETHING WENT WRONG ERROR CODE 8018001C ENTERING …

something-went-wrong-error-code-8018001c-entering image

WebAug 20, 2021 1. Sign in to the Microsoft Endpoint Manager admin center https://go.microsoft.com/fwlink/?linkid=2109431 . 2. Go to Users > All Users. 3. Select the affected user account, and then click Devices. 4. Select any …
From answers.microsoft.com
See details »


FIX UNKNOWN ERROR 0X80070002 IN MICROSOFT OUTLOOK — SPICEWORKS

WebBy default Outlook creates its data files (PST) at one of the two following locations: • AppDataLocalMicrosoftOutlook • DocumentsOutlook Files
From community.spiceworks.com
See details »


YOUR ACCOUNT WAS NOT SET UP ON THIS DEVICE BECAUSE …

WebApr 16, 2021 According to the Error code:80070002, you might be experiencing Windows activation issues, but since you post in Microsoft 365 community, we should confirm with …
From answers.microsoft.com
See details »


CAN’T ADD OFFICE 365 EMAIL TO MY MICROSOFT ACCOUNT

WebWhen I try to add my school’s Office 365 account on my computer, I repeatedly get the error code 80180002 and a message that reads «your account was not set up on this …
From answers.microsoft.com
See details »


OFFICE ERROR «ACCOUNT NOTICE: WE’VE RUN INTO A PROBLEM WITH YOUR …

WebStep 1: Make sure your Microsoft 365 for Home, Personal, or University subscription is active Close all Office apps. Go to your Services & subscriptions page. If prompted, …
From support.microsoft.com
See details »


ERROR CODE 80180014 — MICROSOFT COMMUNITY

WebJan 20, 2023 You may need to contact the admins of the Office 365 tenant for help. In this article: Troubleshoot Windows device enrollment problems in Microsoft Intune. We can …
From answers.microsoft.com
See details »


MDM ENROLLMENT ERROR 0X8018002B ON WINDOWS 10 1709

WebDec 28, 2017 MDM Enrollment Error 0x8018002B on Windows 10 1709 1 1 34 Thread MDM Enrollment Error 0x8018002B on Windows 10 1709 archived cdacf477-87ac-42d5 …
From social.technet.microsoft.com
See details »


TROUBLESHOOT WINDOWS 10 INTUNE AUTO-ENROLLMENT ERROR …

WebOct 28, 2022 Solution Use the following steps to fix the issue. On the affected device, open an elevated Command Prompt window, and then run the dsregcmd /leave command. …
From learn.microsoft.com
See details »


USER GETTING 8018002 ERROR WHEN TRYING TO REGISTER DEVICE …

WebAug 23, 2020 In Windows 10>Settings>Account>Access Work> Connect, device registration fails and returns 80180002 error. Activating Office 365 desktop apps returns …
From learn.microsoft.com
See details »


ERROR CODE 0X80080002 — MICROSOFT COMMUNITY

WebDec 5, 2009 To do this, follow these steps: Click Start, click Run, type services.msc, and then click OK. Right-click the Automatic Updates service, and then click Stop. …
From answers.microsoft.com
See details »


ERROR CODE 80180002 — MICROSOFT COMMUNITY HUB

WebJan 12, 2023 If you’re a client only, you need to ask your IT admin to fix this. While, if you’re the IT admin, you need to change the Scope to None for both MDM and MAM via …
From techcommunity.microsoft.com
See details »


80180002 ERROR CODE — MICROSOFT COMMUNITY

WebMar 10, 2021 ZE zeyer Created on March 8, 2021 80180002 error code Your account was not set up on this device because device managenement could not to be enabled.This …
From answers.microsoft.com
See details »


Related Search


Hi I am getting the following error when trying to auto-enroll hybrid Ad joined devices to Intune.

Auto MDM Enroll: Device Credential (0x0), Failed (Unknown Win32 Error code: 0x8018002b)

I ran dsrecmd /status and go the following.

===========================================

PS C:Usersuser> dsregcmd /status                                                             

                                                                         
                                                  
+———————————————————————-+
| Device State                                                         |
+———————————————————————-+

             AzureAdJoined : YES
          EnterpriseJoined : NO
              DomainJoined : YES
                DomainName : contoso

+———————————————————————-+
| Device Details                                                       |
+———————————————————————-+

                  DeviceId : 34b1d597-68f2-4d59-86ce-b2fc0exxxxxx
                Thumbprint : B6B241987D54D10468FE74FAExxxxxxxxxxx
 DeviceCertificateValidity : [ 2020-04-16 04:37:38.000 UTC — 2030-04-16 05:07:38.000 UTC ]
            KeyContainerId : 4c0a6fbf-1e4a-469d-b740-b8353bxxxxxx
               KeyProvider : Microsoft Platform Crypto Provider
              TpmProtected : YES

+———————————————————————-+
| Tenant Details                                                       |
+———————————————————————-+

                TenantName : Contoso, Inc.
                  TenantId : 3db4791b-32eb-4576-a3bb-42b6e4c0d3a5
                       Idp : login.windows.net
               AuthCodeUrl : https://login.microsoftonline.com/3db4791b-32eb-4576-a3bb-42b6e4c0d3a5/oauth2/authorize
            AccessTokenUrl : https://login.microsoftonline.com/3db4791b-32eb-4576-a3bb-42b6e4c0d3a5/oauth2/token
                    MdmUrl :
                 MdmTouUrl :
          MdmComplianceUrl :
               SettingsUrl :
            JoinSrvVersion : 1.0
                JoinSrvUrl : https://enterpriseregistration.windows.net/EnrollmentServer/device/
                 JoinSrvId : urn:ms-drs:enterpriseregistration.windows.net
             KeySrvVersion : 1.0
                 KeySrvUrl : https://enterpriseregistration.windows.net/EnrollmentServer/key/
                  KeySrvId : urn:ms-drs:enterpriseregistration.windows.net
        WebAuthNSrvVersion : 1.0
            WebAuthNSrvUrl : https://enterpriseregistration.windows.net/webauthn/3db4791b-32eb-4576-a3bb-42b6e4c0d3a5/
             WebAuthNSrvId : urn:ms-drs:enterpriseregistration.windows.net
    DeviceManagementSrvVer : 1.0
    DeviceManagementSrvUrl : https://enterpriseregistration.windows.net/manage/3db4791b-32eb-4576-a3bb-42b6e4c0d3a5/
     DeviceManagementSrvId : urn:ms-drs:enterpriseregistration.windows.net

+———————————————————————-+
| User State                                                           |
+———————————————————————-+

                    NgcSet : NO
           WorkplaceJoined : NO
             WamDefaultSet : YES
       WamDefaultAuthority : organizations
              WamDefaultId : https://login.microsoft.com
            WamDefaultGUID : {B16898C6-A148-4967-9171-64D755DA8520} (AzureAd)

+———————————————————————-+
| SSO State                                                            |
+———————————————————————-+

                AzureAdPrt : YES
      AzureAdPrtUpdateTime : 2020-04-17 15:21:59.000 UTC
      AzureAdPrtExpiryTime : 2020-05-01 22:38:04.000 UTC
       AzureAdPrtAuthority : https://login.microsoftonline.com/3db4791b-32eb-4576-a3bb-42b6e4c0d3a5
             EnterprisePrt : NO
    EnterprisePrtAuthority :

+———————————————————————-+
| Diagnostic Data                                                      |
+———————————————————————-+

        AadRecoveryEnabled : NO
               KeySignTest : PASSED

+———————————————————————-+
| Ngc Prerequisite Check                                               |
+———————————————————————-+

            IsDeviceJoined : YES
             IsUserAzureAD : YES
             PolicyEnabled : NO
          PostLogonEnabled : YES
            DeviceEligible : YES
        SessionIsNotRemote : YES
            CertEnrollment : none
              PreReqResult : WillNotProvision

===============================

I have assigned proper group policy, configure MDM auto enrollment in Azure Ad and assigned (E5, P2, and Intune) license to the user. The user is also local admin on the computer. 

I get the error even when I am using autopilot to register computer as Azure AD and enroll in Intune. The computer registers in Azure Ad but not in Intune. 

  • Ok, as an update, I’ve managed to get it sorted out on my boss’s computer. I’m not as up on using the acronyms as others, so I’ll explain what I did in layman’s speak.

    It seemed to me the issue was something to do with user accounts, so after working my way through the posts above of how to fix it, and spending more time searching what the abbreviations meant than anything else, I tried searches on «Microsoft Accounts»,
    «Windows 365» and «enrolling devices». It said somewhere about deleting the «Work/School» account by going to settings > accounts > Access work or school, then highlight the account and selecting disconnect and saying yes
    to the warnings. So that the account could be disconnected.

    When I tried to delete the the ‘Work/School’ account from the computer, I was getting an error message that read «This PC isn’t connected to a domain». I then searched on that error message. The internet search told me that you could log onto a
    PC now with either a local account or a microsoft account. And that if you logged on with a local account, you could delete that error message, whereas you couldn’t with a microsoft account. The error message was described as an «unexpected behaviour»
    in the help article I read. So I found out how to set up a local account (settings > accounts > sign-in options) and logging in with that account successfully enabled me to delete the work/school account. I then was able to log out as the local user
    and log back in under the microsoft account, return to settings > accounts > Access work or school and selected «connect» to connect to work’s Azure AD. This needed access to my boss’s phone, so I waited til I could have it alongside me so
    I could easily enter the necessary codes.

    It gave me one further error message/code (0x80180002b) at this point. Something about the enrollment process not working properly. I searched on that, and the search took me here: https://support.microsoft.com/en-us/help/4469913/troubleshooting-windows-device-enrollment-problems-in-microsoft-intune.
    I investigated the MDM user scope first of all (Azure Portal > Azure Active Directory > Mobility (MDM and MAM) > Microsoft Intune), and discovered that the MDM User scope was set to none. I changed this to All, and made sure MAM User scope was set
    to None.

    I then returned to settings > accounts > Access work or school hit connect, put in the necessary codes and passwords and it worked! I rebooted the computer and logged in again and it continued to work, no error messages, no nothing, just connections
    to office 365, outlook, onedrive and so forth.

    Vignesh, that worked for me, in any case, hopefully it can work for you as well.

    I also see that the troubleshooting page gives a link to an end user guide to enroll Windows 10 devices. That might assist you as well, Vignesh.

    Is it possible that this was caused by a recent upgrade to one or more aspects of the Microsoft software? Nothing was done at our end to cause the problems to start happening, at least nothing that we know of.

    Once again, thanks and I hope this is helpful to others.

    Russell

    • Marked as answer by

      Monday, August 12, 2019 2:29 AM

  • Понравилась статья? Поделить с друзьями:

    Интересное по теме:

  • Код ошибки 8015d003 на xbox 360
  • Код ошибки 8015d002 на xbox 360
  • Код ошибки 8014
  • Код ошибки 8015402b xbox 360
  • Код ошибки 80151901 xbox 360

  • Добавить комментарий

    ;-) :| :x :twisted: :smile: :shock: :sad: :roll: :razz: :oops: :o :mrgreen: :lol: :idea: :grin: :evil: :cry: :cool: :arrow: :???: :?: :!: