On Tue, 2012-12-18 at 02:45 +1100, Stephen Jones wrote:
The problem is your smb.conf [profiles]. The only options you need are
the path and read only = no. Control access from Windows with an ACL
applied to the profiles share security properties rather than forcing
permissions from Samba.
Hi,
The problem is your smb.conf [profiles]. The only options you need are
the path and read only = no. Control access from Windows with an ACL
applied to the profiles share security properties rather than forcing
permissions from Samba. S4 is different from S3. I'm not sure if those
mask
I've performed a *successful* domain migration from S3/LDAPSAM to
S4.0.0. Yay! I can browse and connect to the server from a
workstation [logged in as a local account]. DNS looks good. kinit
klist work. I was able to *add* a workstation to the domain.
But I can't get roaming profiles to
