Re: [Samba] Profile Location Best Practice
If you're using the tdbsam or ldap backends for accounts, you can specify profile locations on a per-user basis. I have the LDAP backend and that was the only way I had found was to modify the sambaProfilePath value. I wanted to make sure there is not another way to make this change. Thats the only way I know... -- Best regards, Charles -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Profile Location Best Practice
On Tue, 16 Oct 2007, Eric J. Feldhusen might have said: > Mike Eggleston wrote: > >> Well... I created a new directory structure: > >> > >> home directory = \server\home\username (unchanged) > >> profile directory = \server\home\profiles\username (new) > >> > >> I've already switched one user over who was having a weird problem with > >> a printer not appearing on the receptionist computer (she covers for the > >> receptionist when she goes to lunch, etc). That problem is now resolved, > >> while nothing else I tried worked. > >> > >> So, I'm hopeful that this will indeed fix these other mysterious > >> problems. After some reading on this, I'm embarrassed that I never > >> encountered this 'best practice' knowledge before... > >> > >> Many thanks to Eric for the whack upside the head... > > > > How do you switch only a single user at a time? > > > > Mike > > If you're using the tdbsam or ldap backends for accounts, you can > specify profile locations on a per-user basis. I have the LDAP backend and that was the only way I had found was to modify the sambaProfilePath value. I wanted to make sure there is not another way to make this change. Mike -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Profile Location Best Practice
Mike Eggleston wrote: >> Well... I created a new directory structure: >> >> home directory = \server\home\username (unchanged) >> profile directory = \server\home\profiles\username (new) >> >> I've already switched one user over who was having a weird problem with >> a printer not appearing on the receptionist computer (she covers for the >> receptionist when she goes to lunch, etc). That problem is now resolved, >> while nothing else I tried worked. >> >> So, I'm hopeful that this will indeed fix these other mysterious >> problems. After some reading on this, I'm embarrassed that I never >> encountered this 'best practice' knowledge before... >> >> Many thanks to Eric for the whack upside the head... > > How do you switch only a single user at a time? > > Mike If you're using the tdbsam or ldap backends for accounts, you can specify profile locations on a per-user basis. -- Eric Feldhusen Network Administratorhttp://www.remc1.org [EMAIL PROTECTED] PO Box 270 (906) 482-4520 x239 809 Hecla St(906) 482-5031 fax Hancock, MI 49930 (906) 370 6202 mobile -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Profile Location Best Practice
On Mon, 15 Oct 2007, Charles Marcus might have said: > >Eric Feldhusen, you've pretty much convinced me that best practice is > >having profiles stored in one place, and home folders in another. > >But I'm still curious if you have also experienced these problems > >even with such a configuration. Either way, I think the merits of > >such a configuration are clear; I just wonder if I can expect even > >these problems to go away, or if I shouldn't get my hopes up quite > >that much. > > Well... I created a new directory structure: > > home directory = \server\home\username (unchanged) > profile directory = \server\home\profiles\username (new) > > I've already switched one user over who was having a weird problem with > a printer not appearing on the receptionist computer (she covers for the > receptionist when she goes to lunch, etc). That problem is now resolved, > while nothing else I tried worked. > > So, I'm hopeful that this will indeed fix these other mysterious > problems. After some reading on this, I'm embarrassed that I never > encountered this 'best practice' knowledge before... > > Many thanks to Eric for the whack upside the head... How do you switch only a single user at a time? Mike -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Profile Location Best Practice
I have been under the impression that it would indeed be two completely separate shares, one for the profile and one for the home directory. But I currently have the same setup you do, so I'd also like to hear someone else's answer to this question. Charles Marcus wrote: Yes; I've got about 200 users who sign on and off every day. PDC is Samba; profiles in one share, home directory its own share. No issues. Hmmm... Just noticed something about what you guys are saying... I have both my home directories and profiles coming from the SAME parent SHARE: \\server\home Each users home directory (H:) is mapped to: \\server\home\username The new directory I created for Profiles is: \\server\home\profiles\username Isn't this accomplishing the same thing? Or does it actually need to be two different, separate SHARES? I prefer not to create more SHARES than is needed, but if I need to, now is the time to do it, since I'm getting ready to migrate everyones profile to fix this. Thanks! -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Profile Location Best Practice
Yes; I've got about 200 users who sign on and off every day. PDC is Samba; profiles in one share, home directory its own share. No issues. Hmmm... Just noticed something about what you guys are saying... I have both my home directories and profiles coming from the SAME parent SHARE: \\server\home Each users home directory (H:) is mapped to: \\server\home\username The new directory I created for Profiles is: \\server\home\profiles\username Isn't this accomplishing the same thing? Or does it actually need to be two different, separate SHARES? I prefer not to create more SHARES than is needed, but if I need to, now is the time to do it, since I'm getting ready to migrate everyones profile to fix this. Thanks! -- Best regards, Charles -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Profile Location Best Practice
On Mon, 15 Oct 2007, Adam Tauno Williams wrote: Yes; I've got about 200 users who sign on and off every day. PDC is Samba; profiles in one share, home directory its own share. No issues. Likewise. -steve -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Profile Location Best Practice
Eric Feldhusen, you've pretty much convinced me that best practice is having profiles stored in one place, and home folders in another. But I'm still curious if you have also experienced these problems even with such a configuration. Either way, I think the merits of such a configuration are clear; I just wonder if I can expect even these problems to go away, or if I shouldn't get my hopes up quite that much. Well... I created a new directory structure: home directory = \server\home\username (unchanged) profile directory = \server\home\profiles\username (new) I've already switched one user over who was having a weird problem with a printer not appearing on the receptionist computer (she covers for the receptionist when she goes to lunch, etc). That problem is now resolved, while nothing else I tried worked. So, I'm hopeful that this will indeed fix these other mysterious problems. After some reading on this, I'm embarrassed that I never encountered this 'best practice' knowledge before... Many thanks to Eric for the whack upside the head... -- Best regards, Charles -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Profile Location Best Practice
> Eric Feldhusen, you've pretty much convinced me that best practice is > having profiles stored in one place, and home folders in another. But > I'm still curious if you have also experienced these problems even with > such a configuration. Either way, I think the merits of such a > configuration are clear; I just wonder if I can expect even these > problems to go away, or if I shouldn't get my hopes up quite that much. Yes; I've got about 200 users who sign on and off every day. PDC is Samba; profiles in one share, home directory its own share. No issues. Has worked well for a very long time. -- Consonance: an Open Source .NET OpenGroupware client. http://code.google.com/p/consonance/ - Searching for a bored Cairo# hacker. Contact:[EMAIL PROTECTED] http://www.opengroupware.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Profile Location Best Practice
Server Gremlin wrote: > Eric Feldhusen, you've pretty much convinced me that best practice is > having profiles stored in one place, and home folders in another. But > I'm still curious if you have also experienced these problems even with > such a configuration. Either way, I think the merits of such a > configuration are clear; I just wonder if I can expect even these > problems to go away, or if I shouldn't get my hopes up quite that much. At the moment, I'd have to say I'm just "channeling" the advice of the Samba team and their postings on the email lists roaming profiles, since their advice is straightforward, it's just the listening part I've had to work for. Yes, with the profiles stored under a "Profiles" share, I have problems with broken profiles, but much less, and of the times I'm working through my head to remember, I "think" most of those were problems with the workstation configuration, bad Windows XP install, user assisted us by installing spyware/virii, wrong network drivers detected and installed from Windows update, etc... I've been going back through our RT system and I had forgot we have 4 "types" of samba file/print doing PDC control. We have RHEL4 servers, and there's two types of file system's, those with acl and user attribute and those with no acl or user attributes on. Then, each of those groups are split again with profiles in user home and profiles in profile share. Looking at our support tickets, our least problems go from the systems with acl/user attribute and profiles shares to systems with acl/user attributes and profiles in home directories to systems with no acl/user attributes and profiles to finally, systems with no acl/user attributes and no profile shares. So, to make an executive summary at the end, basically I've done what has been documented in the official documentation and suggested on the email lists by Samba team members. Off-topic, the question on why aren't all our systems quite the same? I had to sneak file system acl's, user attribute's and profiles shares onto a couple of servers, because I was adamant from what I had read on the samba lists was that separate profile shares, and acl/user attribute would give us the best ability to support our windows clients. Not quite professional to sneak around my co-worker's back, but... Eric -- Eric Feldhusen Network Administratorhttp://www.remc1.org [EMAIL PROTECTED] PO Box 270 (906) 482-4520 x239 809 Hecla St(906) 482-5031 fax Hancock, MI 49930 (906) 370 6202 mobile -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Profile Location Best Practice
Adam Tauno Williams wrote: Wasn't it the case a while back that if there were older clients on the network (Win95-Win98, etc.) that the Samba profile HAD to be inside the home directory? Probably many Samba installations still have them there from those days if they've been using Samba long enough, and IF that was the case. (?) I am not aware of any documentation that said that the Win9X profile HAD to be stored in the users' home directory. I'd appreciate a pointer to where this is stated so ti can be fixed. Also, regarding where profiles should be stored, I wrote to this list a while back (5/17/07) regarding an Office 2007 read-only issue that was fixed by setting "profile acls = no" on the user's home directory. Well, it fixed the Office 2007 read-only problem but *broke* the roaming profiles. Is the ONLY solution to this issue likely to be moving our hundreds of Samba profiles scattered across many servers into seperate directories? OR, can/should this particular item be considered a Samba bug? Sounds to be like you have answered your own question; do *not* put profiles in user's home directories. The 'default' behavior for windows is to not store user's profiles in any share the user explicitly maps, so don't do that. The user shouldn't be diddling around in their profile folders so putting them somewhere the user is going to inevitably diddle is a bad idea anyway. Not really. I asked if that was the ONLY solution. It likely isn't, but it is the only one *possible* at this time. It appears that the default config of Samba when first installed according to other posts here, same subject, is to put the profiles in the user's home directory in smb.conf. If that is so, maybe that ought to be changed as it is apparently misleading to Samba users - regardless what the docs say. It also appears that a few people are possibly misled by a belief that older versions of Windows (See Server Gremlin original post) may have required just such a configuration. In the environment I'm in, for instance I inherited this config and was also told that it was due to older versions of Windows clients requiring it. While the documentation may not state that anywhere, that doesn't mean it *wasn't* the case (or that it was). Documentation can't possibly cover all assumptions erroneous or otherwise, but default configs when Samba is loaded can endeavor to follow whatever the 'best practice' might be and if that is to place profiles in a separate share than home directories, and that is not how a fresh install is configured, maybe that should be changed? Just a suggestion. Anyway, thanks for answering this question. D -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Profile Location Best Practice
Eric J. Feldhusen wrote: Charles Marcus wrote: The key advantage is that if the profile is stored within the user's home directory, the Windows workstations will sometimes discconnect the user's home directory network drive mapping during logout before the profile has finished synchronizing between the workstation and the server, and your users may have broken profile problems. Wow... maybe this explains the mysterious problems I've been having... Currently, user profiles are stored in: \\server\home\user\system\profile system is a hidden folder in the users home dir, so they don't even 'see' it (unless they enable 'Show hidden files and folders'). Home folder is mapped to H:, target = \\server\home\user 'My Documents' folder is mapped to H: It has worked very well - with the OCCASIONAL exception of mysterious problems with deleted icons from the desktop reappearing, and OCCASIONAL corrupted files in the users profile Are you saying that this could be causing these problems? I thought it would be ok, since the Profile path is an UNC path, not a mapped drive letter? That is what I used to think as well, but after 5+ years of Samba experience on about 19-20 Linux servers, a lot of reading of the Samba Official How-to and Official By-Example and samba email lists, my experience is that a separate profile share not under the user's home directory works best. >From the Samba Official How-to, check out the "Note" section just a few paragraphs down from the top of this link that explains why a separate profile share http://us1.samba.org/samba/docs/man/Samba-HOWTO-Collection/ProfileMgmt.html#id418314 Also, I can't recommend the Samba Official How-to and Official By-Example enough. They both take time to read through, but each is well written, easy to read, and real "glue" together understanding how Samba and Windows clients interact. Also, you can download the latest versions of each document from http://www.samba.org ,but I've purchased one edition of each once to support the authors, because both books are that good. I have the exact same setup as what Charles Marcus described, with user profiles in the home directory (save that my path is \\server\share\username\profile, and it's not hidden), and the exact same strange OCCASIONAL problems he described. Desktop icons mysteriously reappear on the desktop over and over, the user can't permanently delete them. File corruption seems to be less of an issue, but it has happened. Eric Feldhusen, you've pretty much convinced me that best practice is having profiles stored in one place, and home folders in another. But I'm still curious if you have also experienced these problems even with such a configuration. Either way, I think the merits of such a configuration are clear; I just wonder if I can expect even these problems to go away, or if I shouldn't get my hopes up quite that much. Thanks, - SG -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Profile Location Best Practice
> >> Wasn't it the case a while back that if there were older clients on the > >> network (Win95-Win98, etc.) that the Samba profile HAD to be inside the > >> home directory? Probably many Samba installations still have them there > >> from those days if they've been using Samba long enough, and IF that was > >> the case. (?) > > I am not aware of any documentation that said that the Win9X profile HAD to > > be > > stored in the users' home directory. I'd appreciate a pointer to where > > this > > is stated so ti can be fixed. > >> Also, regarding where profiles should be stored, I wrote to this list a > >> while back (5/17/07) regarding an Office 2007 read-only issue that was > >> fixed by setting "profile acls = no" on the user's home directory. Well, > >> it fixed the Office 2007 read-only problem but *broke* the roaming > >> profiles. Is the ONLY solution to this issue likely to be moving our > >> hundreds of Samba profiles scattered across many servers into seperate > >> directories? OR, can/should this particular item be considered a Samba > >> bug? Sounds to be like you have answered your own question; do *not* put profiles in user's home directories. The 'default' behavior for windows is to not store user's profiles in any share the user explicitly maps, so don't do that. The user shouldn't be diddling around in their profile folders so putting them somewhere the user is going to inevitably diddle is a bad idea anyway. > > How can it be a Samba bug, when it is the Windows client that can > > disconnect > > its connections to network shares before the profile has been written to > > the > > server? > You misunderstand me. I was not referring to the disconnection issue but > rather another issue related to where roaming profiles are stored. > Please read the second paragraph above regarding Office 2007 read-only > issue. THAT is what I asked about. Sorry if I confused you. > Having the profile inside the users home directory (and apparently some > people *do* have Samba configured that way), Sure, I've seen Samba configured in some pretty mind boggling ways. That never implies that doing so is "right", "proper", "accepted", or even "useful". > When the profile is in the user's home directory and profile acls = yes > is set, Office 2007 will save files to the home directory as read-only, > causing the user to be unable to modify them after that. Setting profile > acls = no fixes that problem - but breaks the roaming profile. I asked > if the only solution to this is moving the roaming profiles out of home > directories in this case? I'm willing to go on record with "Yes". Change your configuration and the problem goes away - indicates the problem was your configuration. -- Adam Tauno Williams, Network & Systems Administrator Consultant - http://www.whitemiceconsulting.com Developer - http://www.opengroupware.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Profile Location Best Practice
On Sunday 14 October 2007 20:38, deann corum wrote: > >> Wasn't it the case a while back that if there were older clients on the > >> network (Win95-Win98, etc.) that the Samba profile HAD to be inside the > >> home directory? Probably many Samba installations still have them there > >> from those days if they've been using Samba long enough, and IF that was > >> the case. (?) > > > > I am not aware of any documentation that said that the Win9X profile HAD > > to be stored in the users' home directory. I'd appreciate a pointer to > > where this is stated so ti can be fixed. > > I did not SAY the documentation said that, I simply asked if that was > the case for roaming profiles and older clients! Thank you for your > answer. Documentation often does not explicity or implicity apply. > > >> Would having the profiles inside the home directory also cause slow > >> logins, by chance with roaming profiles? We have issues with that EVEN > >> when the roaming profiles are *not* large. > >> > >> Also, regarding where profiles should be stored, I wrote to this list a > >> while back (5/17/07) regarding an Office 2007 read-only issue that was > >> fixed by setting "profile acls = no" on the user's home directory. Well, > >> it fixed the Office 2007 read-only problem but *broke* the roaming > >> profiles. Is the ONLY solution to this issue likely to be moving our > >> hundreds of Samba profiles scattered across many servers into seperate > >> directories? OR, can/should this particular item be considered a Samba > >> bug? > > > > How can it be a Samba bug, when it is the Windows client that can > > disconnect its connections to network shares before the profile has been > > written to the server? > > You misunderstand me. I was not referring to the disconnection issue but > rather another issue related to where roaming profiles are stored. > Please read the second paragraph above regarding Office 2007 read-only > issue. THAT is what I asked about. Sorry if I confused you. > > Having the profile inside the users home directory (and apparently some > people *do* have Samba configured that way), it is required that > profile acls = yes be set on the directory where the profile is stored - > wherever that is. > > When the profile is in the user's home directory and profile acls = yes > is set, Office 2007 will save files to the home directory as read-only, > causing the user to be unable to modify them after that. Setting profile > acls = no fixes that problem - but breaks the roaming profile. I asked > if the only solution to this is moving the roaming profiles out of home > directories in this case? > > > Suggest you learn how Microsoft Windows NT4 and 200X network > > infrastructures implement roaming profile support, then do the same with > > a Samba-based environment. If that fails - its a Samba bug. If it > > works, but your Samba configuration does not work I wonder where the bug > > is! > > I suggest you learn to read thoroughly before answering please. Again > you misunderstand me. I'm referring to the Office 2007 read-only issue I > wrote about above in regards to where the user profile is kept, not the > disconnection issue. > > > The Samba documentation was written to follow the same methods Microsoft > > Windows NT4 domains implement roaming profile support. If goes against > > the flow of how Samba users would prefer to configure their networks > > perhaps it is time for someone to contribute documentation that captures > > that approach. What would be even better, is documentation of several > > explicite case histories from large-scale working systems. > > > > How will rise to the occassion to help update the HOWTO and the ByExample > > documents (books)? Sorry. You are correct, I did not carefully read your posting. Mea Culpa. The Office 2007 issue may be a Samba bug. What version of Samba are you using? What platform is your Samba running on? Best practice has always been to keep the roamin profile separate from the user's home directory. Even so, I believe the official documentation that deals with roaming profiles can benefit from a make-over and I welcome anyone who is willing to put his/her hand up to help refine this. Cheers, John T. Cheers, John T. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Profile Location Best Practice
Wasn't it the case a while back that if there were older clients on the network (Win95-Win98, etc.) that the Samba profile HAD to be inside the home directory? Probably many Samba installations still have them there from those days if they've been using Samba long enough, and IF that was the case. (?) I am not aware of any documentation that said that the Win9X profile HAD to be stored in the users' home directory. I'd appreciate a pointer to where this is stated so ti can be fixed. I did not SAY the documentation said that, I simply asked if that was the case for roaming profiles and older clients! Thank you for your answer. Documentation often does not explicity or implicity apply. Would having the profiles inside the home directory also cause slow logins, by chance with roaming profiles? We have issues with that EVEN when the roaming profiles are *not* large. Also, regarding where profiles should be stored, I wrote to this list a while back (5/17/07) regarding an Office 2007 read-only issue that was fixed by setting "profile acls = no" on the user's home directory. Well, it fixed the Office 2007 read-only problem but *broke* the roaming profiles. Is the ONLY solution to this issue likely to be moving our hundreds of Samba profiles scattered across many servers into seperate directories? OR, can/should this particular item be considered a Samba bug? How can it be a Samba bug, when it is the Windows client that can disconnect its connections to network shares before the profile has been written to the server? You misunderstand me. I was not referring to the disconnection issue but rather another issue related to where roaming profiles are stored. Please read the second paragraph above regarding Office 2007 read-only issue. THAT is what I asked about. Sorry if I confused you. Having the profile inside the users home directory (and apparently some people *do* have Samba configured that way), it is required that profile acls = yes be set on the directory where the profile is stored - wherever that is. When the profile is in the user's home directory and profile acls = yes is set, Office 2007 will save files to the home directory as read-only, causing the user to be unable to modify them after that. Setting profile acls = no fixes that problem - but breaks the roaming profile. I asked if the only solution to this is moving the roaming profiles out of home directories in this case? Suggest you learn how Microsoft Windows NT4 and 200X network infrastructures implement roaming profile support, then do the same with a Samba-based environment. If that fails - its a Samba bug. If it works, but your Samba configuration does not work I wonder where the bug is! I suggest you learn to read thoroughly before answering please. Again you misunderstand me. I'm referring to the Office 2007 read-only issue I wrote about above in regards to where the user profile is kept, not the disconnection issue. The Samba documentation was written to follow the same methods Microsoft Windows NT4 domains implement roaming profile support. If goes against the flow of how Samba users would prefer to configure their networks perhaps it is time for someone to contribute documentation that captures that approach. What would be even better, is documentation of several explicite case histories from large-scale working systems. How will rise to the occassion to help update the HOWTO and the ByExample documents (books)? Cheers, John T -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Profile Location Best Practice
On Sunday 14 October 2007 13:31, deann corum wrote: > Eric J. Feldhusen wrote: > > Charles Marcus wrote: > >>> The key advantage is that if the profile is stored within the user's > >>> home directory, the Windows workstations will sometimes discconnect the > >>> user's home directory network drive mapping during logout before the > >>> profile has finished synchronizing between the workstation and the > >>> server, and your users may have broken profile problems. > >> > >> Wow... maybe this explains the mysterious problems I've been having... > >> > >> Currently, user profiles are stored in: > >> > >> \\server\home\user\system\profile > >> > >> system is a hidden folder in the users home dir, so they don't even > >> 'see' it (unless they enable 'Show hidden files and folders'). > >> > >> Home folder is mapped to H:, target = \\server\home\user > >> > >> 'My Documents' folder is mapped to H: > >> > >> It has worked very well - with the OCCASIONAL exception of mysterious > >> problems with deleted icons from the desktop reappearing, and OCCASIONAL > >> corrupted files in the users profile > >> > >> Are you saying that this could be causing these problems? I thought it > >> would be ok, since the Profile path is an UNC path, not a mapped drive > >> letter? > > > > That is what I used to think as well, but after 5+ years of Samba > > experience on about 19-20 Linux servers, a lot of reading of the Samba > > Official How-to and Official By-Example and samba email lists, my > > experience is that a separate profile share not under the user's home > > directory works best. > > > > >From the Samba Official How-to, check out the "Note" section just a few > > > > paragraphs down from the top of this link that explains why a separate > > profile share > > > > http://us1.samba.org/samba/docs/man/Samba-HOWTO-Collection/ProfileMgmt.ht > >ml#id418314 > > > > Also, I can't recommend the Samba Official How-to and Official > > By-Example enough. They both take time to read through, but each is > > well written, easy to read, and real "glue" together understanding how > > Samba and Windows clients interact. > > > > Also, you can download the latest versions of each document from > > http://www.samba.org ,but I've purchased one edition of each once to > > support the authors, because both books are that good. > > Wasn't it the case a while back that if there were older clients on the > network (Win95-Win98, etc.) that the Samba profile HAD to be inside the > home directory? Probably many Samba installations still have them there > from those days if they've been using Samba long enough, and IF that was > the case. (?) I am not aware of any documentation that said that the Win9X profile HAD to be stored in the users' home directory. I'd appreciate a pointer to where this is stated so ti can be fixed. > Would having the profiles inside the home directory also cause slow > logins, by chance with roaming profiles? We have issues with that EVEN > when the roaming profiles are *not* large. > > Also, regarding where profiles should be stored, I wrote to this list a > while back (5/17/07) regarding an Office 2007 read-only issue that was > fixed by setting "profile acls = no" on the user's home directory. Well, > it fixed the Office 2007 read-only problem but *broke* the roaming > profiles. Is the ONLY solution to this issue likely to be moving our > hundreds of Samba profiles scattered across many servers into seperate > directories? OR, can/should this particular item be considered a Samba > bug? How can it be a Samba bug, when it is the Windows client that can disconnect its connections to network shares before the profile has been written to the server? Suggest you learn how Microsoft Windows NT4 and 200X network infrastructures implement roaming profile support, then do the same with a Samba-based environment. If that fails - its a Samba bug. If it works, but your Samba configuration does not work I wonder where the bug is! The Samba documentation was written to follow the same methods Microsoft Windows NT4 domains implement roaming profile support. If goes against the flow of how Samba users would prefer to configure their networks perhaps it is time for someone to contribute documentation that captures that approach. What would be even better, is documentation of several explicite case histories from large-scale working systems. How will rise to the occassion to help update the HOWTO and the ByExample documents (books)? Cheers, John T. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Profile Location Best Practice
Eric J. Feldhusen wrote: Charles Marcus wrote: The key advantage is that if the profile is stored within the user's home directory, the Windows workstations will sometimes discconnect the user's home directory network drive mapping during logout before the profile has finished synchronizing between the workstation and the server, and your users may have broken profile problems. Wow... maybe this explains the mysterious problems I've been having... Currently, user profiles are stored in: \\server\home\user\system\profile system is a hidden folder in the users home dir, so they don't even 'see' it (unless they enable 'Show hidden files and folders'). Home folder is mapped to H:, target = \\server\home\user 'My Documents' folder is mapped to H: It has worked very well - with the OCCASIONAL exception of mysterious problems with deleted icons from the desktop reappearing, and OCCASIONAL corrupted files in the users profile Are you saying that this could be causing these problems? I thought it would be ok, since the Profile path is an UNC path, not a mapped drive letter? That is what I used to think as well, but after 5+ years of Samba experience on about 19-20 Linux servers, a lot of reading of the Samba Official How-to and Official By-Example and samba email lists, my experience is that a separate profile share not under the user's home directory works best. >From the Samba Official How-to, check out the "Note" section just a few paragraphs down from the top of this link that explains why a separate profile share http://us1.samba.org/samba/docs/man/Samba-HOWTO-Collection/ProfileMgmt.html#id418314 Also, I can't recommend the Samba Official How-to and Official By-Example enough. They both take time to read through, but each is well written, easy to read, and real "glue" together understanding how Samba and Windows clients interact. Also, you can download the latest versions of each document from http://www.samba.org ,but I've purchased one edition of each once to support the authors, because both books are that good. Wasn't it the case a while back that if there were older clients on the network (Win95-Win98, etc.) that the Samba profile HAD to be inside the home directory? Probably many Samba installations still have them there from those days if they've been using Samba long enough, and IF that was the case. (?) Would having the profiles inside the home directory also cause slow logins, by chance with roaming profiles? We have issues with that EVEN when the roaming profiles are *not* large. Also, regarding where profiles should be stored, I wrote to this list a while back (5/17/07) regarding an Office 2007 read-only issue that was fixed by setting "profile acls = no" on the user's home directory. Well, it fixed the Office 2007 read-only problem but *broke* the roaming profiles. Is the ONLY solution to this issue likely to be moving our hundreds of Samba profiles scattered across many servers into seperate directories? OR, can/should this particular item be considered a Samba bug? Thanks, -- Deann Corum -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Profile Location Best Practice
Charles Marcus wrote: >> The key advantage is that if the profile is stored within the user's >> home directory, the Windows workstations will sometimes discconnect the >> user's home directory network drive mapping during logout before the >> profile has finished synchronizing between the workstation and the >> server, and your users may have broken profile problems. > > Wow... maybe this explains the mysterious problems I've been having... > > Currently, user profiles are stored in: > > \\server\home\user\system\profile > > system is a hidden folder in the users home dir, so they don't even > 'see' it (unless they enable 'Show hidden files and folders'). > > Home folder is mapped to H:, target = \\server\home\user > > 'My Documents' folder is mapped to H: > > It has worked very well - with the OCCASIONAL exception of mysterious > problems with deleted icons from the desktop reappearing, and OCCASIONAL > corrupted files in the users profile > > Are you saying that this could be causing these problems? I thought it > would be ok, since the Profile path is an UNC path, not a mapped drive > letter? That is what I used to think as well, but after 5+ years of Samba experience on about 19-20 Linux servers, a lot of reading of the Samba Official How-to and Official By-Example and samba email lists, my experience is that a separate profile share not under the user's home directory works best. >From the Samba Official How-to, check out the "Note" section just a few paragraphs down from the top of this link that explains why a separate profile share http://us1.samba.org/samba/docs/man/Samba-HOWTO-Collection/ProfileMgmt.html#id418314 Also, I can't recommend the Samba Official How-to and Official By-Example enough. They both take time to read through, but each is well written, easy to read, and real "glue" together understanding how Samba and Windows clients interact. Also, you can download the latest versions of each document from http://www.samba.org ,but I've purchased one edition of each once to support the authors, because both books are that good. -- Eric Feldhusen Network Administratorhttp://www.remc1.org [EMAIL PROTECTED] PO Box 270 (906) 482-4520 x239 809 Hecla St(906) 482-5031 fax Hancock, MI 49930 (906) 370 6202 mobile -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Profile Location Best Practice
The key advantage is that if the profile is stored within the user's home directory, the Windows workstations will sometimes discconnect the user's home directory network drive mapping during logout before the profile has finished synchronizing between the workstation and the server, and your users may have broken profile problems. Wow... maybe this explains the mysterious problems I've been having... Currently, user profiles are stored in: \\server\home\user\system\profile system is a hidden folder in the users home dir, so they don't even 'see' it (unless they enable 'Show hidden files and folders'). Home folder is mapped to H:, target = \\server\home\user 'My Documents' folder is mapped to H: It has worked very well - with the OCCASIONAL exception of mysterious problems with deleted icons from the desktop reappearing, and OCCASIONAL corrupted files in the users profile Are you saying that this could be causing these problems? I thought it would be ok, since the Profile path is an UNC path, not a mapped drive letter? -- Best regards, Charles -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Profile Location Best Practice
Server Gremlin wrote: > it seems like the convention has shifted to that of storing profiles > in one place (/sambaprofiles/john/profile) while storing home > directories in another (/sambahomes/john). > > What is the advantage of this setup, if any? The key advantage is that if the profile is stored within the user's home directory, the Windows workstations will sometimes discconnect the user's home directory network drive mapping during logout before the profile has finished synchronizing between the workstation and the server, and your users may have broken profile problems. I have multiple samba servers running at several sites, some with profiles in the home directory and some with the profiles stored under a separate profile share. From experience, the samba servers with a separate profile share have much less problems with profiles breaking. Unfortunately, I've seen several distros ship their samba smb.conf with the users' profiles in the users' home directory, which is where my coworker and I have argued endlessly about. -- Eric Feldhusen Network Administratorhttp://www.remc1.org [EMAIL PROTECTED] PO Box 270 (906) 482-4520 x239 809 Hecla St(906) 482-5031 fax Hancock, MI 49930 (906) 370 6202 mobile -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Profile Location Best Practice
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, and it seems like the convention has
shifted to that of storing profiles in one place
(/sambaprofiles/john/profile) while storing home directories in another
(/sambahomes/john).
What is the advantage of this setup, if any?
Thanks,
- SG
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
