Forum / NoMachine for Mac / Problems on MacOSX if in an AD domain? / Reply To: Problems on MacOSX if in an AD domain?
$ sudo -V
Sudo version 1.7.4p6a
$ sudo -l -U samod
Matching Defaults entries for samod on this host:
env_reset, env_keep+=BLOCKSIZE, env_keep+=”COLORFGBG COLORTERM”,
env_keep+=__CF_USER_TEXT_ENCODING, env_keep+=”CHARSET LANG LANGUAGE LC_ALL LC_COLLATE
LC_CTYPE”, env_keep+=”LC_MESSAGES LC_MONETARY LC_NUMERIC LC_TIME”, env_keep+=”LINES COLUMNS”,
env_keep+=LSCOLORS, env_keep+=SSH_AUTH_SOCK, env_keep+=TZ, env_keep+=”DISPLAY XAUTHORIZATION
XAUTHORITY”, env_keep+=”EDITOR VISUAL”, env_keep+=”HOME MAIL”
User samod may run the following commands on this host:
(ALL) ALL
(ALL) NOPASSWD: ALL
/etc/sudoers:
samod ALL=(ALL) NOPASSWD: ALL
When you join the mac to the domain, the user can use their short name. For example: samod@mydomain.com, then use samod. SSH will also accept samod@mydomain.com as the username. However it’s better to use the short name.
The mac is setup so, that when you first login as a domain user, an account is created.
BTW: I’m still experiencing 1. in 2.2.25.