I can report a bug on Sierra: I got a Active Directory issue since I've upgraded to Sierra 10.12.0. My network home folder doesn't mount at the login session. But i'm still correctly bind-ed on the Active Directory server so network sessions can be opened. According to my screenshot, the icon for the network home folder is wrong too (Apple Server App icon). But if I click on my network home folder, the content appears in a new window with a 'MacOS copy sound'. П˜Š Have tried to re-bind my iMac, also delete the Active Directory records on the server but it still the same. If anyone got an idea 😉 My iMac's bind-ed on a Active Directory 6.3 service provided by a Windows Server 2012 R2.
![Osx Bind9 Sierra 2017 Osx Bind9 Sierra 2017](/uploads/1/2/5/6/125613891/461049752.jpg)
The active directory network home folder is mount on a SMB3 (SMB NTFS) volume. I use the 'mobile' function of Sierra's Directory Utility. If you use Active Directory, it's very easy: Go to System Preferences Users & Groups Click the Option button below your users (make sure padlock is open, to be able to do it) Click ' binding.'
Aside 'network accounts' This opens the right utility. Expend ' show advanced hidden options' & make sure you had checked ' Create a mobile account at login window'. You don't need the sub option 'confirm.' Then you can bind your Mac with your Active Directory. This will create a local copy of the user home folder when doing his first login.
Like a local account. After that, it will sync automatically when the Active Directory server is visible & reliable to the Mac at startup. That's my favorite option to bind Mac's to A.D in my company (laptop et desk-computers) because if your A.D is busy or down, the user continue to login (without network home folder of course) since his first login (when A.D was ok on the Mac). And we all had experienced a A.D who refuse client login sometimes due to traffic. Hope this will be helpful for you. Hi, has anyone gotten any updated information on this issue? I'm in the same boat.
I have been testing MacOS 10.12 and this issue is a complete show stopper for us with the new OS. Currently, we have about 40 Macs in our environment all running Mac OSX 10.11, bound to active directory.
It works 100% flawlessly on OSx 2017 (High Sierra) and has a great battery life! It also features BONUS INSTALLS of i-2017 (iWork & iLife 2017)! (iWork suite includes Pages, Numbers & Keynote and is similar to the Microsoft Office suite) When you buy it now it will come with a FREE charger.
Currently, each Mac user's computer is bound to Active Directory and they have their Home folder specified on the AD server in the Profile tab of their account as follows: Home folder Connect: H: To: servername users username In the above example, replace 'servername' with FQDN of the server and replace 'username' with the user's AD network name. On each Mac, in the Active Directory section of Directory Utility, we have the Mac bound to AD, we have 'Create mobile account at login' checked and we have 'Use UNC path from Active Directory to derive network home location' checked as well. When a Mac OSX 10.11 user logs in with the current setup, the 'Users' share is automatically mounted to the desktop and their network folder shows up in their Dock with the correct 'folder' icon. When a test MacOS 10.12 user logs in, no drive gets automatically mapped, and instead of a folder icon in the dock for their home folder, a 'globe' icon appears.
If the user then clicks on this 'globe' icon, a new share with the user's AD username gets mounted to the desktop, instead of the root 'Users' share. The biggest issue this change causes for us is that test 10.12 users in our environment are unable to access their desktop or documents folder, because we have everyone's desktop and documents folder redirected to their network folder through symbolic links. Since their desktops are stored exclusively on our server, when they log in and their network folder has not mapped itself, they get an empty desktop. Any thoughts on how to fix this issue or at least work around the problem?
Hi, With Sierra we've encountered an issue regarding joining computers to the domain. El Capitan works. Has anyone tried to join a Sierra to the domain? Was anyone successful? In all honesty we have about twenty something domain controllers and some of them (including the flexible single master of operations) are firewalled. Enabling debug on the opendirectory service with 'odutil set log debug' shed some light on the issue. It seems to be a kerberos one for us at least.
Ours might prove to be a totally different problem. However, what is certain is, integration with M$ ADDS services has somehow broke with Sierra. Yep that's a shame emmtv! But if you needs A.D connexion even on latest Apple computers, downgrade to El Capitan. That's the latest MacOS that works great with. They're still compatible, ouf!
(maybe the latest Macbook Pro with touch bar isn't.) Starting MacOS from a mobile hard-drive & launching the El Capitan installer App previously downloaded from the AppStore (you'll need to format the targeted disk). I only use Sierra for test purpose in my office. Still today, it is not a MacOS reliable. Hope it helps.
Apple Footer. This site contains user submitted content, comments and opinions and is for informational purposes only. Apple may provide or recommend responses as a possible solution based on the information provided; every potential issue may involve several factors not detailed in the conversations captured in an electronic forum and Apple can therefore provide no guarantee as to the efficacy of any proposed solutions on the community forums. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the.
Binding and Unbinding to Active Directory from Mac OS via Command Line. Open the Terminal Application. Type in sudo -i and type in your Mac Administrator account password. Sudo gives you root level or administrator level privileges. To View current Active Directory Settings dsconfigad -show To Unbind a Computer from an Active Directory Domain dsconfigad -f -r -u Note: needs to be replaced with domain administrator who has binding/unbinding rights. To Bind a Mac Laptop Computer to an Active Directory Domain - replace this with the computer name you want to bind to Active Directory - needs to be replaced with domain administrator who has binding/unbinding rights. replace with domain you want to join.
Dsconfigad -a -u -ou 'CN=Computers,DC=network,DC=pcpc,DC=org' -domain -mobile enable -mobileconfirm enable -localhome enable -useuncpath enable -groups 'Domain Admins,Enterprise Admins' -alldomains enable To Bind a Mac Desktop Computer to an Active Directory Domain - replace this with the computer name you want to bind to Active Directory - needs to be replaced with domain administrator who has binding/unbinding rights. replace with domain you want to join.
Dsconfigad -a -u -ou 'CN=Computers,DC=network,DC=pcpc,DC=org' -domain -localhome enable -useuncpath enable -groups 'Domain Admins,Enterprise Admins' -alldomains enable.