Network Windows

  • Thread starter Thread starter Jim Phelps
  • Start date Start date
J

Jim Phelps

Years ago, I worked in a company which ran network Windows
3.1. In other words, the user's CONFIG.INI, SYSTEM,INI,
and other config information, was kept in his network
folder, rather than on his C: drive.

I now work in a company which is 99% Windows 2000, and 1%
Windows XP. All user info is kept on the C: drive. This
presents lots of problems whenever someone moves from one
PC to another, even if only for a few minutes: all manner
of settings must be set on the second PC, or it won't be
ready for the user to use.

Can anyone explain to me if Windows 2000 / XP can be set
up that way, and if so, how to do it? It seems to me that
you would first set up Windows the "regular" way (oriented
to the C: drive), and then convert it. If that is the way
to do it, then it would be easy to convert all of the
users.

Thanks for any help you can give me.

Jim Phelps
 
eeeeek

enforce a base system image using GPO and roaming profiles. Then, any
changes that a user makes to thier desktop will follow them to any other
computer they use.
 
or...you could just get a copy of 3.11 for workgroups and
revert to that ancient networking solution. Be sure to
install the single copy on all of your workstations and
servers. That way you'll be sure to be in compliance on
licenses.
 
or a little better sugestion he could dunp microsoft all to gether and
instsall linux and map all the home directories to a nfs share on a remote
server this would guearentee complience and performance from every
workstation.

but it shouldn't be a problem to get it working like described 2 posts above
this
 
Back
Top