similar to: [Samba} Can't do roaming profiles (Solved)

I need a little advice on finishing off a Samba PDC. I have Samba 3.0.0RC1 installed and working as a PDC on a Redhat AS 3.0 machine. It authenticates users nicely but the "roaming" profiles don't work. Tailing the samba log, I see the an attempt to access the users ntuser.dat file, which doesn't exist before the first logon, when logging in. The profile directory

Hi, We are using Samba 3.0.22 on FreeBSD 5.5 PDC with ldap backend and roaming profiles. We meet some difficulties when users logout from some Windows 2000 SP4 clients, and storing their profiles back to the Samba server. The file NTUSER.DAT seems to be uploaded and stored in lowercase, as ntuser.dat. Then, when users try to reopen a win session, they get a corrupted new profile. This new

Hello everyone! I'm facing a big problem with the samba server I just set up: System: FreeBSD 5.4 Samba ver: 3.0.20 (previuosly 3.0.12) Client(s): Windows XP Professional I configured the server to make use of roaming profiles. I was able to copy local profiles to the server, to login and voila - got my desktop. Also after creating a new user, the new profile gets copied to the server,

Winbind seems to have broke my roaming profiles. I have a 3.0.1Pre1 DC on RH AS 3.0 running with Win2000 SP4 clients logging in. Remote profiles worked well and then I added: winbind separator = + idmap uid = 10000-20000 winbind gid = 10000-20000 winbind enum users = yes winbind enum groups = yes template homedir = /home/win2000/%D/%U template shell = /bin/bash Added it to nsswitch.conf and

I had the same problem. We used samba 3.0.14 and upgraded to 3.0.20 After that profile were not loaded anymore. Th problen you are discribing looks like Windows is loading the local copy of your profile and after you deleted it it tries to load the profile from samba and fails. I found out that we had problems with "profile acls = Yes" wich was needed by the earlier samba releases.

I'm running Samba version 2.2.8a on redhat 8.0. i have been working with roaming profiles without problems, but since Win2000-SP4 i get the following error message: /rpc_server/srv_samr.c:api_samr_set_userinfo(670) api_samr_set_userinfo: Unable to unmarshall SAMR_Q_SET_USERINFO./ I changed the local policy to: * Do Not Check for Ownership of Roaming Profile Folders * Add the

I am seeing these in smb.log and each time I do it appears that the user in question is unable to retrieve their roaming profile. Does anyone know what is going on and more importantly, how to cure it? . . . [2017/03/28 16:24:37.426162, 0] ../source3/smbd/oplock.c:713(oplock_timeout_handler) Oplock break failed for file Administrator/AppData/Roaming/Microsoft/Internet Explorer/Quick

Hi, Yesterday I found big problems concerning my roaming profiles. They seem to work on some computers where they are always used, on some other the did not load properly (i.e. a default profile was loaded instead). After some debugging with userenv.log I found the very strange problem: case sensitivity for ntuser.dat!: [...] IsCentralProfileReachable: Testing <F:\testuser\ntuser.dat>

Well, I put it here. All the experience gained in about-half-an-year-management of Samba-PDC + numerous NT4 workstations is included. Also, I'd be glad to hear from you what did I miss! 1) when NT4-workstations are organised into "domain", there's some action assosiated to this: "to log into domain". samba ain such case acts as PDC (primary domain controller),

----- Original Message ----- From: Daniel Ruiz Jimenez To: samba@lists.samba.org Sent: Saturday, October 29, 2005 6:44 PM Subject: Roaming and local profiles EXTRANGE problem!! Hi, I'm from Spain, and my name is Daniel. I am desesperated by a problem with samba, and i don't find any solution in google, forums, and so. I know that you are really tired about stupid questions from

Hello, I have seemed to run into a snag and am wondering if any kind soul on here has any thoughts of what the problem may be, I have roaming profiles setup for a network of Windows XP Pro computers, using a domain controller. I am currently using Samba 3 on SUSE LINUX 10.1 (i586) with the 2.6.16.21-0.25-bigsmp kernel, the following folders in the users profiles are redirected for performance

Hi :) I'm working with Samba 2.2.5 (Debian unstable) and have been trying to get roaming profiles working correctly. My test client is NT4 (SP5) which is able to log onto the domain correctly, however even if I do things like change the background colour, change registry entries, put stuff on the desktop, when I log off the account, only some of the profile is uploaded. I say 'some'

Hi there I am setting up a PDC with Centos 5 + Samba 3.5.4 + Openldap with Roaming profiles using kixstart tools to mount shared folder and modifing some registry entries on windows workstations, The Roaming profiles works fine between Win2000 and WinXP. but when I tried to join a Win7 or Vista workstations i get mixed errors. Sometimes the profiles loads sometimes not, or loads badly

Hi, since rolling out roaming profiles, some user profiles are growing very fast. I like to keep the profiles small and think about changing ExcludeProfileDirs default settings in Software\Microsoft\Windows NT \CurrentVersion\Winlogon by System Policies to remove caches, cookies, recent and other "useless" stuff. Which paths could be excluded without "killing" the benefits

How to set up roaming profiles that samba doesn't download whole profiles, only necessary files ntuser.ini ntuser.dat eg. end rest of registry settings? I would like to setup profiles running (downloading) fast from server when clients login. Clients XP PRO SP3. Samba ver. 3.0.33-3.29.el5_5 Which file form samba registry should I use to force using roaming profiles :

[samba v3.0.24, gentoo w/ kernel 2.6.15] I'm hoping someone has some insight into the following problem that I've recently encountered: Basically, winxp seems to be creating roaming profiles that are incompatible with another winxp client. I've got two sets of winxp clients, which I'll call 'new' and 'old'. Profiles created (and perfectly usable) by the old

Hello friends, how are you? After Windows 10 may 2019 upgrade, roaming profiles stop working. I'm still able to join the machine to the domain, but after logging, Windows was unable to download the profile from the server. I already check the SMB 1.0 protocol at Windows 10 and it?s working fine too. Without the may 2019 upgrade, everything is working fine. My samba version is Samba version

.. Retry, oliver knows .. Have you seen: https://4sysops.com/archives/new-gpo-settings-in-windows-10-1903-enforce-updates-storage-sense-and-logon/ https://www.bleepingcomputer.com/news/microsoft/windows-10-version-1903-drops-password-expiration-policies/ https://www.windowscentral.com/whats-new-sign-experience-windows-10-may-2019-update Hmm, and the more i see the more i dislike.. :-/

I'm having a problem wtih 2.2.6pre2 that I seem unable to resolve. When logging out of my Win2K SP3 machine, I receive the error "Windows cannot update the roaming profile. The system cannot find the file specified." Checking the archives and google brings up several references to errors around the copying of ntuser.dat from the local machine, to a temporary file on the

Hi, i've finally have my LDAP backend working for authentication for my DC. Logon scripts are executed, user is authenticated, but my roaming profiles are not found. here is what i have in my config files: smb.conf [global] printing = bsd netbios name = PDC server string = PDC (%h) workgroup = workgroup interfaces = eth0,lo security = user encrypt passwords =