Adding to the fun and excitement of High Sierra...
I have my first 10.13 (17A365) test box in Jamf. My (2) local admin accounts were siccessfully created during the Casper Imaging process, but I'm unable to authenticate with them.
-Can't log into the Login window.
-Can't SSH with them (SSH is on).
-Can't log in locally from the Terminal from another account ("login xxx").
-Can't authenticate to ARD with them (ARD is active but I cant connect).
Observations:
1) My local accounts are unusable regardless if the Mac is bound to AD or not.
2) Macs upgraded in-place from Sierra 10.12.6 work fine. Only Macs that are imaged "clean" from Casper Imaging 9.99 are effected.
3) The (2) local accounts are valid, and they have the correct UIDs according to DSCL. They are also in the correct local admin group (GID 80).
4) My AD accounts work (i.e the Mac recongnizes AD users/groups and allows me to log in and create a managed mobile account).
5) One of my local admin accounts is my Jamf service account (used for the Jamf client/agent). Casper Remote can't authenticate to run any remote tasks (packages, scripts, etc). However, most login policies appear to work (map printers, mount network SMB drives etc).
6) I'm still on Jamf 9.99 (I can't update to 9.101 for a couple weeks)
If anyone has seen this please let chime in. I have searched all over, but haven't found anyone else experiencing this problem on 10.13 High Sierra.