Append a domain to Intune, set up a custom domain

 


 Append a domain to Intune, set up a custom domain




An external client ran into an issue where Azure AD–joined devices were not recognizing an application license hosted on an on-premises app server. This came up after migrating to Autopilot devices.
From the investigation, it looks like the application relies on communication with the on-prem server to validate its license. While reviewing the device configuration in the registry, it became clear that the domain information is responsible in how this communication is handled.

On the affected devices, the default domain is set to WORKGROUP instead of the expected domain (aztik.net). This indicates that the devices are not domain-joined, which is likely why the application cannot properly validate the license against the on-prem server.

a temporal solution will fix this. also we contacted the app vendor that will bring a new method to apply the license.






for testing porpuses i decided to manually place the domain name and surprisely the application accepted the license. once confirmed, I started to built a silent win32app deployment so can add the domain append domain local script.








PS Script :
 $regPath = "HKLM:\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters"
$domainValue = "aztik.net"

# Set or update the 'Domain' value
Set-ItemProperty -Path $regPath -Name "Domain" -Value $domainValue











Domain Sucesfully added and the application has accepted the license with no issues.

See you next time !









































Comments

Popular posts from this blog

Mapping printers on Intune