@osxadmin Thankfully we don't have a big user base on our AD bound side that likes the latest and greatest right away, so I'm the only one testing 10.13 at the moment. So I can't report any issues with passwords as of yet though.

macOS doesn't gracefully handle issues with the home directory; it just fails the login. Our Windows estate has a different mechanism in place for mapping user shares, so the homeDirectory attribute SHOULD be blank in our case. Some users tested using that field a long time ago and it wasn't cleared, and one of our configs for binding checked the box to mount that share. Seems to handle a blank attribute fine, but if there's a bad path (or one you don't have permissions to), the login just seems to fail without much of a helpful indication as to why.

Edit: meant to say this has been true since before High Sierra.

@cindySingh unfortunately I can't do that in our enviroment with our users (deleting home folder and logging in as a new user), all of our mac users "don't have time" for us, so what I've done is block the upgrade in our enviroment until Apple releases the patch/fix.

Thanks.

Well, it seems that today's update to 10.13.1 fixed the UNC path issue and now I am able to bind the machine as expected (with network home locations) without a problem.

One less thing to worry about!

Still no good for me unless I uncheck the UNC path box, even after updating to 10.13.1.

@rusty.adams Yes, you're right. I did it again, confident on these changes, and it failed. Back to unchecking UNC paths.