Hey there! I am setting up a network for a company. They want to be able to log into their account from any computer in the offices. I'm not sure what it's called, but I think its called Personal Profile. All the computers run Windows 2000 Professional and I can put anything on the server (Win, Linux, BSD, etc...)
![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
Navigation
Install the app
How to install the app on iOS
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
More options
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Log on w/ personal desktop
- Thread starter Carp
- Start date
SJConsultant
2[H]4U
- Joined
- Jan 14, 2004
- Messages
- 3,599
With a win2k or 2k3 server you can do roaming profiles. This will work for their data, but you need to ensure the programs are installed to the desktops they log on to or create server based images that install on the workstation.
jeffmoss26
2[H]4U
- Joined
- Aug 1, 2002
- Messages
- 2,267
yeah, we have roaming profiles at school so we can log on to any computer in the building and then access our documents.
Soldier101
Gawd
- Joined
- Jan 8, 2002
- Messages
- 639
active directory, and then set profile paths
SJConsultant
2[H]4U
- Joined
- Jan 14, 2004
- Messages
- 3,599
Maybe I wasn't clear in my post........
Roaming profiles only work for the users *profile* , not applications. You'll need to ensure either the required applications that they will use are *already* installed on *every* workstation OR setup server based images of the applications that install automatically no matter which workstation the user logs in to.
Personally, if you want a "dumb terminal" you would be better off checking out terminal services in application mode.......
Roaming profiles only work for the users *profile* , not applications. You'll need to ensure either the required applications that they will use are *already* installed on *every* workstation OR setup server based images of the applications that install automatically no matter which workstation the user logs in to.
Personally, if you want a "dumb terminal" you would be better off checking out terminal services in application mode.......
Zwitterion
Gawd
- Joined
- Dec 15, 2002
- Messages
- 938
For your purpose:
Windows 2000 Server.
Windows 2000 Server.
Doc Holiday
2[H]4U
- Joined
- Jan 22, 2001
- Messages
- 2,363
Be careful with roaming profiles they look good on paper but can very quickly eat up tons of bandwith and server storage space. I say skip the roaming profiles and just teach the users to find what apps they need.
Also I don't know about your network layout but I have yet to see a place where users switch there desktops on a regular basis.
Also I don't know about your network layout but I have yet to see a place where users switch there desktops on a regular basis.
This is what you should do:
1. Install Windows 2000/2003 Server
2. Install Active Directory.
3. Configure roaming profiles for your users by defining a network path for the profile, and configuring appropriate permissions.
4. Configure "Redirected Folders" (in the GPO) for your users to redirect their "My Documents" "Application Data" and "Desktop" FROM their user profile to a network path. Unlike roaming profiles (which are copied from the server to the workstation during logon - then back again at log off), redirected folders work directly on the network share. Nothing is copied back and forwards, accessed files are opened directly from the server - you save a lot of hassle and a good deal of bandwidth.
5. Determine which software should be mandatory on all workstations. Assign such software to your domain computers via GPO.
6. Assign the rest of the software to users via GPO. - if the software is not available on the PC when the user logs on, it will be automatically installed when the users runs the software.
I recomend using DFS for storing software packages, profiles and redirected folders if you've got more then one network location. That way you can take advantage of replication, and clients will (by default) always try to access the closest server hosting the replica first.
You should probably log on to www.microsoft.com and read up on folder/share permissions requiered to host roaming profiles, and redirected folders.
1. Install Windows 2000/2003 Server
2. Install Active Directory.
3. Configure roaming profiles for your users by defining a network path for the profile, and configuring appropriate permissions.
4. Configure "Redirected Folders" (in the GPO) for your users to redirect their "My Documents" "Application Data" and "Desktop" FROM their user profile to a network path. Unlike roaming profiles (which are copied from the server to the workstation during logon - then back again at log off), redirected folders work directly on the network share. Nothing is copied back and forwards, accessed files are opened directly from the server - you save a lot of hassle and a good deal of bandwidth.
5. Determine which software should be mandatory on all workstations. Assign such software to your domain computers via GPO.
6. Assign the rest of the software to users via GPO. - if the software is not available on the PC when the user logs on, it will be automatically installed when the users runs the software.
I recomend using DFS for storing software packages, profiles and redirected folders if you've got more then one network location. That way you can take advantage of replication, and clients will (by default) always try to access the closest server hosting the replica first.
You should probably log on to www.microsoft.com and read up on folder/share permissions requiered to host roaming profiles, and redirected folders.