Weird issue accessing netlogon
Got a bit of a weird issue here...... We have just started using AAD machines via autopilot & intune and doing testing on them accessing resources on our current onprem domain, got things sorted so they can access file shares and DFS namespace shares perfectly fine and thats all going through, but having an issue with intermittent issues with netlogon. There seems to be no pattern but when trying to hit \\domain\netlogon that will work but when trying \\domain.fqdn.gov.uk\netlogon that wont work. However without doing anything trying again a little while later and it will be the opposite way around that can access on the full fqdn but not the short name, and then to make it worse, sometimes both work at the same time. Different devices have been tried and had 2 side by side where one could access short but not fqdn and the other could access fqdn but not short. At the same time if i try to access any server shares on either short name or fqdn then those are fine, seems to just be issues with netlogon on the domain. at all times i can run to \\domain & \\domain.fqdn.gov.uk and the folder list of sysvol and netlogon both appear but its just guess work which is going to work. This happens the same on both our internal network and when connected via cisco anyconnect vpn back into our network. Hopefully someone has come across a similar issue and fixed it! Thanks if you have managed to read this far :)
Login from Non Domain Joined Devices with UPN for Network Share not working with Powershell
Hi, we have two Domaincontrollers (2012 R2, 2016 - will be replaced next week with 2x 2022, Domain Level yet 2012, will be 2019), all Users are synced to MS365 via AAD Connect. All of our new clients are AzureJoined only and managed by intune, not directly joined to the local Active Directory. Users are login into their devices via UPN email address removed for privacy reasons . I'm trying to mount some network shares with the users UPN email address removed for privacy reasons which are provided by the Domain Controller. Unfortunatly this isnt working somehow, and i don't know why. If i login manually or via powershell with the pre-windows 2000 login def\abc everything is working. anybody here who can help to give my intune managed clients access to the network shares via UPN?
DirectAccess(VPN) + Windows Hello - Fingerprint connexion
Bonjour, Nos utilisateurs utilisent DirectAccess pour la connexion depuis l'extérieur. J'ai récemment activé via Intune la fonctionnalité Windows Hello afin qu'ils puisse utiliser le capteur d'empreinte digital. Dans le réseau local, la connexion à l'environnement RDS se fait de manière automatique. A noter que notre réseau local est lié via VPN site à site au Datacenter où sont tous stockés les serveurs. En réseau externe(4G par exemple), lorsqu'ils souhaitent se connecter au RDS, il demande l'empreinte digital. La lecture de l'empreinte se fait bien mais une erreur de connexion survient juste après comme si un paramètre est mal configuré. Voici l'erreur : Un problème s'est produit lors de la connexion à la ressource distante Savez-vous quelles sont les options à activer (via GPO ou Intune) pour que le Fingerprint soit fonctionnel ? D'avance je vous remercie.