Unable to register device (4376817)

Error: Unable to register device "ComputerName" on domain "domain.local"
Error thrown from the server: {"Message":"Device [ComputerName] on domain [domain.local] was not found."}

This issue is related to HTTPS bindings on IIS websites. Only one IIS site (either DirSync or Default Web Site) can use HTTPS.

• If DirSync site is using HTTPS, then the Default Web site must use HTTP (port 80) for device registration.
• Conversely, if the Default Web site is using HTTPS for device registration, then DirSync must not use HTTPS.

1. Default Web Site:
   Bind the SSL certificate to enable HTTPS (if device registration is intended to use HTTPS).
   
   
2. DirSync Site:
   Remove any SSL bindings (i.e., do not use HTTPS).
   
   
3. Restart IIS:
   Apply the changes by restarting IIS.
   
   
4. Restart the Quest Directory Sync / Quest AD Migrator Agent Service
   
   

Note related to IIS configuration:
When the Default Web Site is bound to HTTPS (port 443) for device registration, the DirSync site should use HTTP on port 8080.
This avoids port conflicts and ensures that both services can run simultaneously on the same IIS server.

Using port 8080 for DirSync avoids the need for SSL binding, which is important because only one site should use HTTPS in this scenario.

IIS Configuration Summary:

• Default Web Site:

  • Protocol: HTTPS
  • Port: 443
  • Purpose: Device registration
    
    

• DirSync Site:

  • Protocol: HTTP
  • Port: 8080
  • Purpose: DirSync dashboard

Note related to the antivirus (AV) running on the client:
Connectivity issues between the Migrator Pro Agent and MPAD server can also be caused by AV network scanning. For example, if the client AV scans HTTP/HTTPS traffic, it may lead to connectivity problems. Adding the FQDN of the MPAD server to the exclusion list can resolve the issue. 
It is recommended to test the client without a virus scanner to verify whether the device can be registered successfully.