samba - Jul 2018 - Logging-in takes 1 hour when changing computers

Hello all,

I've got a simple active directory server set-up with 5 computers and 
about 5 users which works reasonably well, but recently, when an user 
changes to a different computer, it takes about a hour for the user to 
log in.  However, future log-ins on the same computer is pretty much 
instant, but the exact same problems occurs when the user changes 
computers - even to one they've used previously!

I get the feeling the whole profile is being downloaded from the server 
as the client computer's hard drive is thrashing for the whole hour, but 
it shouldn't be taking about a hour, but a couple minutes at most?

Any advice would be greatly appreciated!

With kind regards - Piers

On Wed, 18 Jul 2018 14:26:08 +0100
Piers Kittel via samba <samba at lists.samba.org> wrote:
> Hello all,
> 
> I've got a simple active directory server set-up with 5 computers and 
> about 5 users which works reasonably well, but recently, when an user 
> changes to a different computer, it takes about a hour for the user
> to log in.  However, future log-ins on the same computer is pretty
> much instant, but the exact same problems occurs when the user
> changes computers - even to one they've used previously!
> 
> I get the feeling the whole profile is being downloaded from the
> server as the client computer's hard drive is thrashing for the whole
> hour, but it shouldn't be taking about a hour, but a couple minutes
> at most?
> 
> Any advice would be greatly appreciated!
> 
> With kind regards - Piers
> 
> 
Go on, spoil us by actually giving us some information, such as what
distro is the DC running on ?, what is in smb.conf, what are your
clients running etc etc.

Rowland

I ran into a similar issue years ago with Samba 3.0.x in a classic 
domain with roaming profiles enabled.     You could try disabling an 
profile shares in smb.conf.   You should also unset any profile setting 
for the affected users (this had been with pdbedit but maybe different 
with an AD domain.)      I also believe there are group policy settings 
you can set to disable roaming profile support on the windows clients.

Roaming profiles seemed great in theory.  In practice Outlook, IE , and 
other browsers create large cache files that have to sync.   it also 
seemed to be that when someone logged in or out, the computer tried to 
sync ALL user profiles.







On 07/18/18 09:43, Rowland Penny via samba wrote:
> On Wed, 18 Jul 2018 14:26:08 +0100
> Piers Kittel via samba <samba at lists.samba.org> wrote:
>
>> Hello all,
>>
>> I've got a simple active directory server set-up with 5 computers
and
>> about 5 users which works reasonably well, but recently, when an user
>> changes to a different computer, it takes about a hour for the user
>> to log in.  However, future log-ins on the same computer is pretty
>> much instant, but the exact same problems occurs when the user
>> changes computers - even to one they've used previously!
>>
>> I get the feeling the whole profile is being downloaded from the
>> server as the client computer's hard drive is thrashing for the
whole
>> hour, but it shouldn't be taking about a hour, but a couple minutes
>> at most?
>>
>> Any advice would be greatly appreciated!
>>
>> With kind regards - Piers
>>
>>
> Go on, spoil us by actually giving us some information, such as what
> distro is the DC running on ?, what is in smb.conf, what are your
> clients running etc etc.
>
> Rowland
>

Roaming profiles DO work great yes, if you setup correct. 
Using it since WinXp and it works fine. ( win 3.x did not have roaming profiles
) ;-)

I suggest reading: 
https://docs.microsoft.com/en-us/windows-server/storage/folder-redirection/deploy-roaming-user-profiles


Greetz, 

Louis

> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens 
> Gaiseric Vandal via samba
> Verzonden: woensdag 18 juli 2018 16:06
> Aan: samba at lists.samba.org
> Onderwerp: Re: [Samba] Logging-in takes 1 hour when changing computers
> 
> I ran into a similar issue years ago with Samba 3.0.x in a classic 
> domain with roaming profiles enabled.     You could try disabling an 
> profile shares in smb.conf.   You should also unset any 
> profile setting 
> for the affected users (this had been with pdbedit but maybe 
> different 
> with an AD domain.)      I also believe there are group 
> policy settings 
> you can set to disable roaming profile support on the windows clients.
> 
> Roaming profiles seemed great in theory.  In practice 
> Outlook, IE , and 
> other browsers create large cache files that have to sync.   it also 
> seemed to be that when someone logged in or out, the computer 
> tried to 
> sync ALL user profiles.
> 
> 
> 
> 
> 
> 
> On 07/18/18 09:43, Rowland Penny via samba wrote:
> > On Wed, 18 Jul 2018 14:26:08 +0100
> > Piers Kittel via samba <samba at lists.samba.org> wrote:
> >
> >> Hello all,
> >>
> >> I've got a simple active directory server set-up with 5 
> computers and
> >> about 5 users which works reasonably well, but recently, 
> when an user
> >> changes to a different computer, it takes about a hour for the
user
> >> to log in.  However, future log-ins on the same computer is pretty
> >> much instant, but the exact same problems occurs when the user
> >> changes computers - even to one they've used previously!
> >>
> >> I get the feeling the whole profile is being downloaded from the
> >> server as the client computer's hard drive is thrashing 
> for the whole
> >> hour, but it shouldn't be taking about a hour, but a couple
minutes
> >> at most?
> >>
> >> Any advice would be greatly appreciated!
> >>
> >> With kind regards - Piers
> >>
> >>
> > Go on, spoil us by actually giving us some information, such as what
> > distro is the DC running on ?, what is in smb.conf, what are your
> > clients running etc etc.
> >
> > Rowland
> >
> 
> 
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
> 
>

> Go on, spoil us by actually giving us some information, such as what
> distro is the DC running on ?, what is in smb.conf, what are your
> clients running etc etc.
>
The exact same thing just happened to me today, after joining a new 
workstation to our domain. When a new user logged in to the computer for 
the first time, the profile creation phase went on a disk trashing 
rampage for a VERY LONG time, until the user gave up and finally pressed 
the power button. After reboot, however, he was able to log in very 
quickly and the user's environment had indeed been created and Group 
Policies properly applied.

The workstation is running Windows 10. The domain is served by two DCs, 
both running Samba 4.8.3, one of them over CentOS 6.9 and the other over 
CentOS 7.4. The Kerberos used is the Heimdal one.

On 18/07/2018 14:43, Rowland Penny wrote:
> Go on, spoil us by actually giving us some information, such as what
> distro is the DC running on ?, what is in smb.conf, what are your
> clients running etc etc.
>
> Rowland
>
Hello Rowland, Gaiseric, LPH & Miguel,

Thanks for all of your replies!

Not having much time at the moment, but to answer some questions...

The server is running Debian 9, our clients all are running Windows 10 
Professional - there's 4 desktops altogether.  Two desktops are a couple 
of years old but very poor, they're slow (my advice was ignored when 
they were ordered), the other two are a year old but of a much better 
specification (this time they listened to me), but the issue is the same 
on all computers.  All are connected via gigabit Ethernet.  At moment, 
the server is a *very* low-end Toshiba laptop started as a trial, but 
we've now got a PowerEdge R230 that we haven't commissioned yet (due to 
a different issue I'm currently trying to resolve).  Here's the smb.conf
below (note, the printer drivers bit don't work, I've left it for now).

Many thanks for your time again!

With kind regards - Piers

# 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/xxx.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