Forum Discussion

Ajit Terdalkar's avatar
Ajit Terdalkar
Copper Contributor
Feb 04, 2025

Device registration issue in Entra

Log Name:      Microsoft-Windows-User Device Registration/Admin
Source:        Microsoft-Windows-User Device Registration
Date:          2/4/2025 1:12:48 AM
Event ID:      304
Task Category: None
Level:         Error
Keywords:      
User:          SYSTEM
Computer:    Servername.domain.com
Description:
Automatic registration failed at join phase. 
Exit code: Unknown HResult Error code: 0x801c03f3 
Server error: The device object by the given id (b1aa9a2c-e64c-4c8e-bfb9-1aaab093f9ff) is not found. 

Tenant type: Managed 
Registration type: sync 
Debug Output: 
joinMode: Join
drsInstance: azure
registrationType: sync
tenantType: Managed
tenantId: 5432c24e-7d1f-4efc-9410-01b73ea021e7
configLocation: undefined
errorPhase: join
adalCorrelationId: 043451f3-ad83-4b52-b48a-e9be735a446f
adalLog:
undefined
adalResponseCode: 0x0 
 
Log Name:      Microsoft-Windows-User Device Registration/Admin
Source:        Microsoft-Windows-User Device Registration
Date:          2/4/2025 1:12:48 AM
Event ID:      204
Task Category: None
Level:         Error
Keywords:      
User:          SYSTEM
Computer:     Servername.domain.com

Description:
The get join response operation callback failed with exit code: Unknown HResult Error code: 0x801c03f3. 
Activity Id: 9d9f9396-134e-471e-8fc2-b16871520149 
The server returned HTTP status: 400 
Server response was: {"code":"invalid_request","subcode":"error_missing_device","message":"The device object by the given id (b1aa9a2c-e64c-4c8e-bfb9-1aaab093f9ff) is not found.","operation":"DeviceRenew","requestid":"9d9f9396-134e-471e-8fc2-b16871520149","time":"02-04-2025 6:12:52Z"}

  • luchete's avatar
    luchete
    Steel Contributor

    Hi Ajit Terdalkar!

    The device object with the given ID can't be found, causing errors during the registration process. The error code 0x801c03f3 and the HTTP status 400 indicate that the server couldn't process the request due to the missing device object. This could be a configuration issue or the device might not be properly registered in Azure AD. I'd recommend checking the device registration status or re-registering the device.

    To fix this device registration issue, start by checking if the device is listed in Azure Active Directory. If it's not there, try re-registering the device. Next, make sure your sync settings are correct, since this is a sync registration. If the device isn't connecting to Azure properly, check the network to ensure it's not blocking access to Azure AD. A reboot of the device might help clear up temporary issues, so give that a try. Also, review any group policies related to device registration to make sure they’re set correctly. If you're using Active Directory, unjoining and then rejoining the domain could fix the problem. Clearing cached credentials might also help, as they can sometimes cause issues. You can also try manually triggering the registration using PowerShell with the command dsregcmd /join. If these steps don't work, check the Event Viewer for more detailed error messages or contact Microsoft support for further assistance.

    Regards

Resources