Re: [Samba] XP/W2K on Samba 3
You can easily redirect the typical data store for user documents (i.e. My Documents) to any network share you want. That isn't difficult. Additionally, you can configure just about any mail client on the planet (Outlook included) to put the data store there. No big deal. There are several problems with that: 1) If the network is down, mail isn't available (or any documents in My Documents for that matter). 2) If this is a road warrior, mail isn't available while they are on the road. 3) This doesn't solve the "application settings" requisite that I thought I understood. You can solve #1 and #2 by any number of synchronization options out there and direct the mail client to a local data store and sync the data to a network store. #3 is a whole different issue. I am not aware of any other reliable method of retaining settings from desktop to desktop (assuming a fat client) than roaming profiles. If you are using the standard store for some mail clients (Outlook for example) that creates the massive data push/pull I mentioned. You can work around that with some planning by putting all heavy stores such as email in places that aren't profile specific (i.e. not in C:\Documents and Settings\username\.). Doing that creates even more headaches if you are concerned about security for user separation and would require quite a bit of work. Oh, and let's not forget the non-homogenous client issues. Doug VanLeuven wrote: Aaron Kincer wrote: I am having trouble envisioning a network where people are constantly signing onto different computers (outside of schools and libraries). If users move around that much, perhaps a VNC/Citrix/Terminal Services approach would be better. Roaming profiles are a solution to a problem that existed before email boxes measured in hundreds of megabytes or even gigabytes. They will work (for Windows clients), but can bring your network to its knees. And as mentioned, the mixing of client OS has an amusing effect sometimes. Think certificates. Certificates encrypt files, establish VPN's, sign & encrypt email, things like that. There are long standing alternatives to local store for email. The main and easiest way to keep one's certificates in windows is to use roaming profiles else manually export and import and manually renew. Actually kind of cutting edge, not a throwback to earlier times. Users don't typically move around, but what if the hard drive fails? Does one roll out windows with something like ghost and consider workstations disposable? If yes, the certificates and any private user data are lost. System admins move around. Want to use the machine in the conference room for a presentation. Frequently easier with roaming profiles. Regards, Doug -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] XP/W2K on Samba 3
Hello, everybody in this thread and thank you for contributing! First of all I'll change the [profile]settings in my smb.conf and see what happens. I am not sure if that hits the problem. Do I really want roaming profiles? The user should not be allowed to have personal settings on the client. No changes on the desktop. He is automatically connected to his samba-share for saving data. How do I tell the W2k/XP *not* to create a users profile locally, no local user-directory, nothig to be copied to and from the server. Greetings Bernd Kloss Am Donnerstag, 5. Oktober 2006 06:24 schrieb Peter Ulrich Kruppa: > On Wed, 4 Oct 2006, Paul-Erik Törrönen wrote: > > I'm going to side on B_Kloss here, since I grew frustrated with the > > local profiles a long time ago. > > > > On Tue, 2006-10-03 at 19:46 +0200, Peter Ulrich Kruppa wrote: > >>> This is working fine, but as soon as a user is logging into the > >> > >> domain on one of the WIN2000 or XP-clients for the first time on this > >> client, the client is creating a local user-directory. > >> Are you sure this is a problem? > >> As long as you have enough diskspace, I don't see what should be > > > > Remember that all the settings are also per computer, which in turn > > means that the user will in the end do a set up of his desktop n times > > (n equals the computers available). Also the application settings need > > to be manually copied/set each time. This becomes very frustrating in no > > time for the normal user, and roaming profiles can fix that. And if the > > user decides to change some setting, well... > > This is absolutely correct, but B_Kloss mentioned Win98 clients. > I don't think they can use Win2k/WinXP roaming profiles. > If B_Kloss' users tend to use just 2 or 3 favourite computers, > this won't be too much setup for them and he will save a lot of > network traffic, produced by down- and uploading the profiles. > > > However there are a few things which needs to be addressed, as pointed > > earlier. > > > > 1. The mixing of W2k and WXP will create some fabulous fireshows, > > non-lethal but nonetheless spectacular. > > Yes, but this will surely work. > > > 2. Due to the way how the profile is managed in Windows, > > copy-all-on-login-from-server, copy-all-on-logout-to-server, the normal > > user must be made aware of this. Don't save anything on the desktop, > > instead use the X: (automatically mounted to \\yourserver\). > > Minimize the browser cache. Configure applications to explicitly use a > > local tmp-dir (usually setting the TMP and TEMP-variables on the > > workstation suffices). And anything else that minimizes the size of the > > profile directory. > > Just out of interest: Do you delete the roaming profiles > after log off or do you leave them on the local machine? > > > 3. Occasionally the profile goes *bonk* on the workstation. Usually > > removing the local copy is enough but nonetheless requires > > administrative action. > > > > And probably some other things which my scarred memory supresses. > > > > As for setting up the shared profiles, the keywords in smb.conf are: > > > > [Global] > >logon drive = X: > >logon path = \\%L\profiles\%U > >logon script = scripts\logon.bat > > > > [netlogon] > >path = /path/to/netlogon > >read only = no > >nt acl support = Yes > > > > [profiles] > >comment = Roaming Profile Share > >path = /path/to/profiles > >read only = no > >profile acls = Yes > >nt acl support = Yes > > Uli. > > +-+ > > | Peter Ulrich Kruppa | > | - Wuppertal - | > | Germany | > > +-+ -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] XP/W2K on Samba 3
On Wed, 4 Oct 2006, Paul-Erik Törrönen wrote: I'm going to side on B_Kloss here, since I grew frustrated with the local profiles a long time ago. On Tue, 2006-10-03 at 19:46 +0200, Peter Ulrich Kruppa wrote: This is working fine, but as soon as a user is logging into the domain on one of the WIN2000 or XP-clients for the first time on this client, the client is creating a local user-directory. Are you sure this is a problem? As long as you have enough diskspace, I don't see what should be Remember that all the settings are also per computer, which in turn means that the user will in the end do a set up of his desktop n times (n equals the computers available). Also the application settings need to be manually copied/set each time. This becomes very frustrating in no time for the normal user, and roaming profiles can fix that. And if the user decides to change some setting, well... This is absolutely correct, but B_Kloss mentioned Win98 clients. I don't think they can use Win2k/WinXP roaming profiles. If B_Kloss' users tend to use just 2 or 3 favourite computers, this won't be too much setup for them and he will save a lot of network traffic, produced by down- and uploading the profiles. However there are a few things which needs to be addressed, as pointed earlier. 1. The mixing of W2k and WXP will create some fabulous fireshows, non-lethal but nonetheless spectacular. Yes, but this will surely work. 2. Due to the way how the profile is managed in Windows, copy-all-on-login-from-server, copy-all-on-logout-to-server, the normal user must be made aware of this. Don't save anything on the desktop, instead use the X: (automatically mounted to \\yourserver\). Minimize the browser cache. Configure applications to explicitly use a local tmp-dir (usually setting the TMP and TEMP-variables on the workstation suffices). And anything else that minimizes the size of the profile directory. Just out of interest: Do you delete the roaming profiles after log off or do you leave them on the local machine? 3. Occasionally the profile goes *bonk* on the workstation. Usually removing the local copy is enough but nonetheless requires administrative action. And probably some other things which my scarred memory supresses. As for setting up the shared profiles, the keywords in smb.conf are: [Global] logon drive = X: logon path = \\%L\profiles\%U logon script = scripts\logon.bat [netlogon] path = /path/to/netlogon read only = no nt acl support = Yes [profiles] comment = Roaming Profile Share path = /path/to/profiles read only = no profile acls = Yes nt acl support = Yes Uli. +-+ | Peter Ulrich Kruppa | | - Wuppertal - | | Germany | +-+-- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] XP/W2K on Samba 3
Aaron Kincer wrote: I am having trouble envisioning a network where people are constantly signing onto different computers (outside of schools and libraries). If users move around that much, perhaps a VNC/Citrix/Terminal Services approach would be better. Roaming profiles are a solution to a problem that existed before email boxes measured in hundreds of megabytes or even gigabytes. They will work (for Windows clients), but can bring your network to its knees. And as mentioned, the mixing of client OS has an amusing effect sometimes. Think certificates. Certificates encrypt files, establish VPN's, sign & encrypt email, things like that. There are long standing alternatives to local store for email. The main and easiest way to keep one's certificates in windows is to use roaming profiles else manually export and import and manually renew. Actually kind of cutting edge, not a throwback to earlier times. Users don't typically move around, but what if the hard drive fails? Does one roll out windows with something like ghost and consider workstations disposable? If yes, the certificates and any private user data are lost. System admins move around. Want to use the machine in the conference room for a presentation. Frequently easier with roaming profiles. Regards, Doug -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] XP/W2K on Samba 3
I am having trouble envisioning a network where people are constantly signing onto different computers (outside of schools and libraries). If users move around that much, perhaps a VNC/Citrix/Terminal Services approach would be better. Roaming profiles are a solution to a problem that existed before email boxes measured in hundreds of megabytes or even gigabytes. They will work (for Windows clients), but can bring your network to its knees. And as mentioned, the mixing of client OS has an amusing effect sometimes. Also, roaming On 10/4/06, Paul-Erik Törrönen <[EMAIL PROTECTED]> wrote: I'm going to side on B_Kloss here, since I grew frustrated with the local profiles a long time ago. On Tue, 2006-10-03 at 19:46 +0200, Peter Ulrich Kruppa wrote: > > This is working fine, but as soon as a user is logging into the > domain on one of the WIN2000 or XP-clients for the first time on this > client, the client is creating a local user-directory. > Are you sure this is a problem? > As long as you have enough diskspace, I don't see what should be Remember that all the settings are also per computer, which in turn means that the user will in the end do a set up of his desktop n times (n equals the computers available). Also the application settings need to be manually copied/set each time. This becomes very frustrating in no time for the normal user, and roaming profiles can fix that. And if the user decides to change some setting, well... However there are a few things which needs to be addressed, as pointed earlier. 1. The mixing of W2k and WXP will create some fabulous fireshows, non-lethal but nonetheless spectacular. 2. Due to the way how the profile is managed in Windows, copy-all-on-login-from-server, copy-all-on-logout-to-server, the normal user must be made aware of this. Don't save anything on the desktop, instead use the X: (automatically mounted to \\yourserver\). Minimize the browser cache. Configure applications to explicitly use a local tmp-dir (usually setting the TMP and TEMP-variables on the workstation suffices). And anything else that minimizes the size of the profile directory. 3. Occasionally the profile goes *bonk* on the workstation. Usually removing the local copy is enough but nonetheless requires administrative action. And probably some other things which my scarred memory supresses. As for setting up the shared profiles, the keywords in smb.conf are: [Global] logon drive = X: logon path = \\%L\profiles\%U logon script = scripts\logon.bat [netlogon] path = /path/to/netlogon read only = no nt acl support = Yes [profiles] comment = Roaming Profile Share path = /path/to/profiles read only = no profile acls = Yes nt acl support = Yes Poltsi -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] XP/W2K on Samba 3
I'm going to side on B_Kloss here, since I grew frustrated with the local profiles a long time ago. On Tue, 2006-10-03 at 19:46 +0200, Peter Ulrich Kruppa wrote: > > This is working fine, but as soon as a user is logging into the > domain on one of the WIN2000 or XP-clients for the first time on this > client, the client is creating a local user-directory. > Are you sure this is a problem? > As long as you have enough diskspace, I don't see what should be Remember that all the settings are also per computer, which in turn means that the user will in the end do a set up of his desktop n times (n equals the computers available). Also the application settings need to be manually copied/set each time. This becomes very frustrating in no time for the normal user, and roaming profiles can fix that. And if the user decides to change some setting, well... However there are a few things which needs to be addressed, as pointed earlier. 1. The mixing of W2k and WXP will create some fabulous fireshows, non-lethal but nonetheless spectacular. 2. Due to the way how the profile is managed in Windows, copy-all-on-login-from-server, copy-all-on-logout-to-server, the normal user must be made aware of this. Don't save anything on the desktop, instead use the X: (automatically mounted to \\yourserver\). Minimize the browser cache. Configure applications to explicitly use a local tmp-dir (usually setting the TMP and TEMP-variables on the workstation suffices). And anything else that minimizes the size of the profile directory. 3. Occasionally the profile goes *bonk* on the workstation. Usually removing the local copy is enough but nonetheless requires administrative action. And probably some other things which my scarred memory supresses. As for setting up the shared profiles, the keywords in smb.conf are: [Global] logon drive = X: logon path = \\%L\profiles\%U logon script = scripts\logon.bat [netlogon] path = /path/to/netlogon read only = no nt acl support = Yes [profiles] comment = Roaming Profile Share path = /path/to/profiles read only = no profile acls = Yes nt acl support = Yes Poltsi -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] XP/W2K on Samba 3
To prevent users from changing their profile you could assign to them a
"mandatory profile", that is not stored back to the server and is
deleted from the client upon logout. (I haven't used such a thing, I
only know that it is supposed to exist.)
An easier way of making the user's profile go away upon logout is
to put him/her into the guest's group. (I am not shure which other
consequences this will have.)
To modify the default storage location for documents etc., you use a
policy that does folder redirection. (You can also use folder
redirection without using policies by directly editing the registry of
the [mandatory] profile assigned to the users.)
Some of these topics are covered in Chapter 5 ("Making happy users")
of "Samba-3 by Example" aka "The Samba Guide", see
http://www.samba.org/samba/docs/man/Samba-Guide/
and in Chapter 27 ("Desktop Profile Management") of the
"Samba Howto Collection", see
http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/
HTH
Wolfgang Ratzka
> Okay, let me try to explain it the simple way as I understand it.
> We are running a debian-server with debian-clients and also a mixture of
> WIN98SE, WIN2000 and XP-clients. Users are logging in from all these four
> types of clients. They have one personal share on /home/username accessible
> from all types of clients (via SAMBA for Win-clients).
> This is working fine, but as soon as a user is logging into the domain on one
> of the WIN2000 or XP-clients for the first time on this client, the client is
> creating a local user-directory.
>
> In a first step I would like to avoid this creating of local
> user-directories,
> because after a while each user has a local home-directory on every
> win2000/XP-client. Opening the explorer he should only find one home
> directory, which is his samba-share on the server.
>
> In a second step it would be great, if he is trying to save data, WORD or
> what
> ever automatically offers the users samba-share for saving data.
>
> What I do not want to offer is a personal desktop that is available from
> every
> computer he is logging in. I want to have the Win2000 or XPdesktop the same
> for all users. They can use the Linux-KDE-computers if they want their own
> desktop.
>
> How can this be achieved?
> Thank you for helping.
>
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] XP/W2K on Samba 3
On Tue, 3 Oct 2006, B_Kloss wrote: Okay, let me try to explain it the simple way as I understand it. We are running a debian-server with debian-clients and also a mixture of WIN98SE, WIN2000 and XP-clients. Users are logging in from all these four types of clients. They have one personal share on /home/username accessible from all types of clients (via SAMBA for Win-clients). This is working fine, but as soon as a user is logging into the domain on one of the WIN2000 or XP-clients for the first time on this client, the client is creating a local user-directory. Are you sure this is a problem? As long as you have enough diskspace, I don't see what should be wrong about that. All your users have to know is, that they have to save their work in their home shares to make it accessible from all machines. And your Linux Boxes can't use Windows profiles anyway. Regards, Uli. In a first step I would like to avoid this creating of local user-directories, because after a while each user has a local home-directory on every win2000/XP-client. Opening the explorer he should only find one home directory, which is his samba-share on the server. In a second step it would be great, if he is trying to save data, WORD or what ever automatically offers the users samba-share for saving data. What I do not want to offer is a personal desktop that is available from every computer he is logging in. I want to have the Win2000 or XPdesktop the same for all users. They can use the Linux-KDE-computers if they want their own desktop. How can this be achieved? Thank you for helping. Am Dienstag, 3. Oktober 2006 15:09 schrieb Aaron Kincer: I am not sure from Bernd's email what he is trying to accomplish, but there are things to consider if you are trying to do roaming profiles. With the volume of data often stored in today's profile, it is non-trivial to enable this option and I do not recommend doing so for the average user. There are other ways to accomplish some of the benefits of profiles without the mess. The first thing is to decide what you want to accomplish and then find the solution that best fits those needs. Bruno Rodrigues Neves wrote: Greetings! So Bernd, previously I wanted do the same, but I didn´t get success because the profiles from Windows 2000 and Windows XP are differents (when a user logs in on a Windows 2000 and after that he tries to log in on a Windows XP, it returns some errors)... But, if you want, you can look for the "profiles section" that will avoid you do that. When you configure it with this option, the Windows client will use remote profiles automagically! : ) [ ]´s On 10/3/06, Bernd Kloss <[EMAIL PROTECTED]> wrote: Hello, maybe it is not the right place to ask Windows-related questions, but i'll give it a try. I am running a Debian-Etch-Server with Samba 3 and Windows2000 and XP-clients. Everything is working fine except: For every user logging in from a Win-client, the client generates a local user-profile and local user-directories. What has to be done within Samba and what has to be done on the clients to avoid that and get all userdata stored in the user's share. Thank you! ___ Viren-Scan für Ihren PC! Jetzt für jeden. Sofort, online und kostenlos. Gleich testen! http://www.pc-sicherheit.web.de/freescan/?mc=02 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba +-+ | Peter Ulrich Kruppa | | - Wuppertal - | | Germany | +-+-- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] XP/W2K on Samba 3
Okay, let me try to explain it the simple way as I understand it. We are running a debian-server with debian-clients and also a mixture of WIN98SE, WIN2000 and XP-clients. Users are logging in from all these four types of clients. They have one personal share on /home/username accessible from all types of clients (via SAMBA for Win-clients). This is working fine, but as soon as a user is logging into the domain on one of the WIN2000 or XP-clients for the first time on this client, the client is creating a local user-directory. In a first step I would like to avoid this creating of local user-directories, because after a while each user has a local home-directory on every win2000/XP-client. Opening the explorer he should only find one home directory, which is his samba-share on the server. In a second step it would be great, if he is trying to save data, WORD or what ever automatically offers the users samba-share for saving data. What I do not want to offer is a personal desktop that is available from every computer he is logging in. I want to have the Win2000 or XPdesktop the same for all users. They can use the Linux-KDE-computers if they want their own desktop. How can this be achieved? Thank you for helping. Am Dienstag, 3. Oktober 2006 15:09 schrieb Aaron Kincer: > I am not sure from Bernd's email what he is trying to accomplish, but > there are things to consider if you are trying to do roaming profiles. > With the volume of data often stored in today's profile, it is > non-trivial to enable this option and I do not recommend doing so for > the average user. There are other ways to accomplish some of the > benefits of profiles without the mess. > > The first thing is to decide what you want to accomplish and then find > the solution that best fits those needs. > > Bruno Rodrigues Neves wrote: > > Greetings! > > > > So Bernd, previously I wanted do the same, but I didn´t get success > > because the profiles from Windows 2000 and Windows XP are differents > > (when a user logs in on a Windows 2000 and after that he tries to log > > in on a Windows XP, it returns some errors)... > > > > But, if you want, you can look for the "profiles section" that will > > avoid you do that. > > > > When you configure it with this option, the Windows client will use > > remote profiles automagically! : ) > > > > [ ]´s > > > > On 10/3/06, Bernd Kloss <[EMAIL PROTECTED]> wrote: > >> Hello, > >> > >> maybe it is not the right place to ask Windows-related questions, but > >> i'll give it a try. > >> > >> I am running a Debian-Etch-Server with Samba 3 and Windows2000 and > >> XP-clients. > >> Everything is working fine except: > >> > >> For every user logging in from a Win-client, the client generates a > >> local user-profile and local user-directories. > >> > >> What has to be done within Samba and what has to be done on the clients > >> to avoid that and get all userdata stored in the user's share. > >> > >> Thank you! > >> ___ > >> Viren-Scan für Ihren PC! Jetzt für jeden. Sofort, online und kostenlos. > >> Gleich testen! http://www.pc-sicherheit.web.de/freescan/?mc=02 > >> > >> -- > >> To unsubscribe from this list go to the following URL and read the > >> instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] XP/W2K on Samba 3
I am not sure from Bernd's email what he is trying to accomplish, but there are things to consider if you are trying to do roaming profiles. With the volume of data often stored in today's profile, it is non-trivial to enable this option and I do not recommend doing so for the average user. There are other ways to accomplish some of the benefits of profiles without the mess. The first thing is to decide what you want to accomplish and then find the solution that best fits those needs. Bruno Rodrigues Neves wrote: Greetings! So Bernd, previously I wanted do the same, but I didn´t get success because the profiles from Windows 2000 and Windows XP are differents (when a user logs in on a Windows 2000 and after that he tries to log in on a Windows XP, it returns some errors)... But, if you want, you can look for the "profiles section" that will avoid you do that. When you configure it with this option, the Windows client will use remote profiles automagically! : ) [ ]´s On 10/3/06, Bernd Kloss <[EMAIL PROTECTED]> wrote: Hello, maybe it is not the right place to ask Windows-related questions, but i'll give it a try. I am running a Debian-Etch-Server with Samba 3 and Windows2000 and XP-clients. Everything is working fine except: For every user logging in from a Win-client, the client generates a local user-profile and local user-directories. What has to be done within Samba and what has to be done on the clients to avoid that and get all userdata stored in the user's share. Thank you! ___ Viren-Scan für Ihren PC! Jetzt für jeden. Sofort, online und kostenlos. Gleich testen! http://www.pc-sicherheit.web.de/freescan/?mc=02 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] XP/W2K on Samba 3
Greetings! So Bernd, previously I wanted do the same, but I didn´t get success because the profiles from Windows 2000 and Windows XP are differents (when a user logs in on a Windows 2000 and after that he tries to log in on a Windows XP, it returns some errors)... But, if you want, you can look for the "profiles section" that will avoid you do that. When you configure it with this option, the Windows client will use remote profiles automagically! : ) [ ]´s On 10/3/06, Bernd Kloss <[EMAIL PROTECTED]> wrote: Hello, maybe it is not the right place to ask Windows-related questions, but i'll give it a try. I am running a Debian-Etch-Server with Samba 3 and Windows2000 and XP-clients. Everything is working fine except: For every user logging in from a Win-client, the client generates a local user-profile and local user-directories. What has to be done within Samba and what has to be done on the clients to avoid that and get all userdata stored in the user's share. Thank you! ___ Viren-Scan für Ihren PC! Jetzt für jeden. Sofort, online und kostenlos. Gleich testen! http://www.pc-sicherheit.web.de/freescan/?mc=02 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- Bruno Rodrigues Neves [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] XP/W2K on Samba 3
Hello, maybe it is not the right place to ask Windows-related questions, but i'll give it a try. I am running a Debian-Etch-Server with Samba 3 and Windows2000 and XP-clients. Everything is working fine except: For every user logging in from a Win-client, the client generates a local user-profile and local user-directories. What has to be done within Samba and what has to be done on the clients to avoid that and get all userdata stored in the user's share. Thank you! ___ Viren-Scan für Ihren PC! Jetzt für jeden. Sofort, online und kostenlos. Gleich testen! http://www.pc-sicherheit.web.de/freescan/?mc=02 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
