similar to: Samba Domain Best practice - Backing up Local Profiles

Hi, I'm setting up Samba 3.0.2a & ldapsam in my home lab and everythin appears to be working correctly except for profiles. Using Samba 3.02a openldap-2.1.22 smbldap-tools-0.8.4 When a user 'debra' tries to logon from a XP system that has joined the domain she gets the following error message "Windows did not load your roaming profile and is attempting to log you on with

Rob, When u use a TNT2-M64, why dont you use the Windows drivers for this card, as i believe the TNT2 is good supported within windows xp. You only should use the NVIDIA driver when your gaming... and you probely dont do that with the TNT2-M64 card. Also thank you for testing this. i cant think of any which will resolve your problem besides above. Louis -----Oorspronkelijk bericht----- Van:

I've found that with roaming profiles enabled, some users experience extremely slow logoffs when using NT/XP/2000. I've discovered that this is usually due to very large email folders in the user's profile. OUTLOOK: As Outlook saves ALL messages in a single .pst file, any activity in Outlook will result in the .pst file being changed and therefore needing to be synchronized with the

I have quite a few samba installations, and I've had problems with roaming profiles when upgrading from Samba 2.2 to 3.0. My servers run Debian stable, which uses Samba 2.2.3, with security patches. At some point Debian will release a new stable version with a recent Samba 3.0 release. Right now I'm testing a few servers with a samba 3.0.10 backport to make sure the transition will go

Hello. Whenever I attach a 2000 Pro workstation to a Samba server, a directory is created under the user's home directory called "profile", and the local profile syncs with this directory. Its not usually bothersome until someone leaves 2 GIG of data on their desktop and when they logoff, Windows syncs the entire 2 GIG of data to the server. How do I disable this? Attaching a 2000

Hello, i must admit that i'm totally lost. After working a lot of hours my new samba server is still not running fine. I had read a lot of papers but i have no idea what's going wrong. My goal: --------- Samba 3.0.9 (Fedora Core 2) working as a PDC for windows 2000 professional client (with sp4 and all hotfixes applied) _with_ roaming user profiles. My status: ---------- *

We have been directed to move off a SAMBA domain to a server 2003R2 domain. We run roaming profiles with samba and would like to continue this on 2003R2. After bringing all the XPSP3 desktops into the 2003R2 domain, roaming profiles wont work. I'm not even trying to use the SAMBA generated profiles. The error I get when logging on is: *Windows cannot locate the server copy of your

I am having some issues with Samba with roaming profiles running on Ubuntu server. When a user logs in they get prompted with an error: ----windows error---------- Windows cannot locate the server copy of your roaming profile and is attempting to log you on with your local profile. Changes to the profile will not be copied to the server when you logoff. Possible causes of this error include

Hi all, Runing Samba 3.0.14a-3sarge1 PDC, using an LDAP backend Problem is I cant seem to load Roaming Profiles, as it gives the following error "Windows did not load your roaming profile and is attempting to log you on with your local profile. Changes to the profile will not be copied to the server when you logoff. Windows did not load your profile because a server copy of the profile

John, I have tried the suggestions you provided. I have setup Dynamic DNS as per the Samba 3 By Example book and this is all updating correctly. I have run the validation steps indicated in the book and all names are resolvable and reachable via hosts, DNS and WINS. I am not sure why winbind would need to be turned off, but seeing as I do not need that currently, I have tried disabling it; the

We've applied SP1 for WinXP on several machines and now roaming profiles don't work them. I tried swithching "nt acl support = yes" as previously mentioned on this list but this still doesn't work for us and we continue to get the following error: Windows did not load your roaming profile and is attempting to log you on with your local profile. Changes to the profile

Hello, After a great deal of tweaking, I finally got the Samba server working, so that it would accept domain logins. However, the problem I now have regards roaming profiles, which refuse to function. After successfully authenticating the user, the following 2 messages appear: Message 1: ---------- Windows cannot locate the server copy of your roaming profile and is attempting to log you on

On 08-08-2018 7:48, Ian Evans wrote: > My webserver also houses our mailserver. There's about six users on > that mail system and I'm thinking it would be good to back up the > mailboxes to my always on HTPC computer at home, which is reachable > via a dynamic IP service. > > I know (or think) I need to use doveadm-backup for this but rather > than reinvent the wheel

My webserver also houses our mailserver. There's about six users on that mail system and I'm thinking it would be good to back up the mailboxes to my always on HTPC computer at home, which is reachable via a dynamic IP service. I know (or think) I need to use doveadm-backup for this but rather than reinvent the wheel (or use the wrong wheel altogether) I'm wondering if anyone can

Hi, I'm setting up Samba with ldap backend and everythin appears to be working correctly except for profiles. Using: samba-3.0.2 openldap-2.1.26 smbldap-tools-0.8.4 When a user 'testa' tries to logon from a Win2K system that has joined the domain he gets the following error message: "Windows did not load your roaming profile and is attempting to log you on with your local

[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

I'm running FreeBSD 5.4-STABLE with Samba 3.0.20 configured as a PDC serving a small-ish network (10 XP hosts). My problem concerns roaming profiles - some XP clients take ages to logon and logoff. On doing some Googling I identified the 'profile acls' parameter as being a likely fix. However, I seem to have got myself into one of two scenarios: a) With 'profile acls'

Hi, I've a samba server set up with a ldap backend an I'v configured it to use roaming profiles (ie: logon path = \\%L\%U\profile), the users homes are exported by nfs to the server. My problem is that the profile of the user always end up in C:/Documents and Settings/$user . I've already erased the local profile and the profile directory in the users home dir, but every time that

I have a question about using roaming profiles in a Samba PDC controlled domain. I know that with Windows 95 and that generation or so, the profile had to be stored in the same directory as the home folder. ("/sambahomes/john/profile" for example.) You didn't have a choice because of technical reasons. But that restriction no longer applies with modern versions of Windows,

Been playing around with Samba as a domain controller a lot lately, with a rather nice setup. Latest samba and openldap backend, running on hardware SATA raid 5, with for the moment the only shares on XFS /home partition ontop of LVM running XFS quotas. It's all nice and spangley, expect for one thing.. It completely breaks when saving the roaming profile at logoff, and the quota is reached.