I can answer the question about user profiles when converting a workstation from standalone to domain logon as I've done quite a bit of winders networking.
When a user logs on the first time, winders will create a profile and a set of "home" directories. They're all located under /winnt/ in "users" I think. (It's been a while since I've done this under NT) The user's subdirectory is named with their username. When you add the computer to the domain, winders suddenly sees them as a different user. This is why the default settings are present again. The new user folders are called "username.000", but they're in the same directory structure. I've known people to "rename profiles" to get around this, but I've also known this proceedure to be glitchy. My preferred approach is to copy the contents of the "username" folder to the "username.000" folder and be done with it. Hope this helps on that much anyway. Joebewan On Saturday 06 July 2002 11:54 am, Chris Mason wrote: > Background: > I have setup a small network for a local company of about 10 windows > workstations and a Redhat 7.3 server. > All the workstations are W2K, some new and some existing. > There is a permenant internet feed and a Linksys VPN gateway. > The gateway currently provides DHCP as well as internet access and VPN > for an external road warrior. > The server provides DNS, email via IMAP and Webmail (squirrelmail), > website for documents and manuals, and users home directories. The > server is backed up using a tape drive and Arkeia software. > The server also acts as the windows PDC via Samba. > There are more employees than workstations as many are not deskbound and > use "hotseat" office cubicles. Each user logs in to the domain and their > settings are loaded from the server, irrespective of which workstation > they use. > Some users, the office workers, have their own workstations. > At login, each user gets assigned a drive H as their home directory on > the server and all data should be saved there. Any data saved on the > workstation may be lost as they are not backed up. > There are other shared directories on the server for sharing files, > secure directories with limited access, etc. > > All this is pretty standard, there are other network features that are > not important here. In setting up this system from scratch over the last > couple of months, I have come across a couple of issues I am not sure of > and I expect other users of this list know the solution to. > > 1: When converting a standalone workstation into the domain, how do you > keep the user's settings, bookmarks, etc? When I have them log into the > domain all the settings are those of the default user. > > 2: At the moment all workstations get an IP/DNS/gateway via DHCP from > the gateway. > One of the clients requirements is to only allow internet access to > certain users for obvious reasons, as email is handled by the internal > server. > I'm not sure how that can be done. I could make that only certain > workstations, and give no gateway in the dhcp settings, setting it by > hand on the workstations that need it. Any other ideas? > > 3: We have networked printers connected to the network directly with > network interfaces. I'd like to have restricted access to some of the > printers. How can I do that? I'm guessing group permissions but I am not > sure if the HP printers will work with that. > > 4: How can I set up the named so that the workstations can tell named > what IP they are using? I'm talking about windows dynamic dns updates, I > suppose. I know I often see this in my server logs as named rejects the > updates, will adding "allow updates from 192.168.100" allow the > workstations to add a zone entry for themselves? Do I have to add each > workstation's name to the zone to start? How do you get a Linux > workstation to do the same thing? Would I be better off using the server > for DHCP and can I tie DHCP and DNS together so each IP allocated gets a > name? > > 5: I'd like to prevent users getting access to the local hard drive at > all to prevent them from saving documents anywhere except their home > directories, is there a way to do that? > > Finally, if anyone needs any info on setting up a network as I have, let > me know. > > Chris Mason > > > > > > > > > > _______________________________________________ > Redhat-list mailing list > [EMAIL PROTECTED] > https://listman.redhat.com/mailman/listinfo/redhat-list -- Valhalla -- Linux good, Fire bad _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
