[Samba] Roaming profiles don't work properly on newly joined Windows clients
Rowland penny
rpenny at samba.org
Thu Oct 3 20:45:19 UTC 2019
On 03/10/2019 20:52, Piers Kittel via samba wrote:
>> Can we start by seeing your smb.conf from the Samba machine that holds
>> the profiles share.
>>
>> Rowland
> Rowland, thanks for your prompt reply as usual!
>
> Yeah sure, have pasted it below. Just an update - I've double checked
> the other donated computer - it works perfectly fine, roaming profiles
> gets written to the server and no error message. So in fact, it's just
> one of the donated computers that has this problem - roaming profiles
> don't get written to the server. Odd.
>
> Thanks again for continued help!
>
> --------------------------------------------------------------------------
>
>
> # Global parameters
> [global]
> netbios name = AD
> realm = xxx.INTRANET
> workgroup = xxx
> dns forwarder = 192.168.0.1
> server role = active directory domain controller
> rpc_server:spoolss = external
> rpc_daemon:spoolssd = fork
> printing = CUPS
> spoolss: architecture = Windows x64
>
>
> [netlogon]
> path = /var/lib/samba/sysvol/cfd.intranet/scripts
> read only = No
>
> [sysvol]
> path = /var/lib/samba/sysvol
> read only = No
>
> [Profiles]
> path = /home/samba/Profiles
> read only = no
> veto files = /*sync*/
>
> [users]
> path = /home/samba/users
> read only = no
>
> [printers]
> path = /var/spool/samba
> printable = yes
>
> [print$]
> path = /srv/samba/printer_drivers/
> read only = no
>
Try reading this:
https://lists.samba.org/archive/samba/2019-September/226138.html
Also, if you are going to sanitise things, then do it everywhere ;-)
Rowland
More information about the samba
mailing list