<background>
Current setup is a mix of Linux desktops (40), Windows 7 Ultimate
desktops (10) and OS X desktops (4).
openLDAP is the work horse doing the uid/gid mappings for *nix and OS
X workstation. For the handful of Windows workstations, I have
configured Samba3 as NT4 domain controller with openLDAP as the
backend for authentication. With two registry mods in Win7, the
machines are able to join the domain. Users are able to authenticate
against domain controller with roaming profiles. After initial
hiccups, the first couple of weeks, this has been working well.
Occassionally, a few Windows app like Maya crash, when users login
with domain credentials but the same app works fine when the users
login with local credentials (defined on each Win7 desktop).
After searching, I have deduced the problem to be with the roaming
profiles. Randomly it gets corrupted and app like Maya crash.
</background>
The client CTO claims that at his previous company, Windows 7 desktop
with Maya worked flawlessly with the MS - AD DC (MS Windows server)
and is anxious to get AD (Samba4). However, for the *nix side he
wants to maintain NFS file share. I have done some reading on this
subject and realize that this will only work with NFSv4 Kerberized.
Search on the subject also shows, people who have tried this have
encountered issues in getting Kerberized NFSv4 on file server/client
to work with AD.
I would appreciate guidance and gotchas from anyone here who has done
Kerberized NFSv4 with Samba 4 AD Auth. (Samba 4 platform is Ubuntu
12.04.3 amd64).
TIA.
--
Arun Khan