Why does an azure joined device look to itself as ad server instead of local ad server?
I am trying to get my mobile azure joined laptops using Desktop Authorities off network feature. I'm told that you have to log into the local network once for the laptop to receive it's local copy of the required files to know how to touch the azure share for future updates to policies. According to information and some reports the laptop has guest rights on the local domain instead of normal rights and cannot seem to access or find the sysvol even though I can manually navigate to it. The laptops name is listed as the ad server so for all intents and purposes it will never be able to get the necessary files. Support said "Found the user machine logonserver is the same machine and for this reason is not able to find the Sysvol share to load the Off-Network support.
The customer will look for a solution to get the sysvol available for the machines contacting Azure.Foudn the user privilege in the domain is Guest, the customer is aware and they will fix this.
Found the machine shows No AD site defined and they need to review this issue as well."
Has anyone else had this type of experience and if so were you able to work through it
I would appreciate any help in this matter.
Answers (0)
Be the first to answer this question
