Discussion Locked

Uniformity on Multiple Workstations

0 helpful
41 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am the sole administrator of about 20 computers, some are old but most are new. They are all running Win 2000 Pro. The server is 2000 server. I am very interested in making all the computers look and feel exactly the same, and eliminating the needfor doing detailed configuration on each machine. In particular, I want to:
Make all Start Menus look the same
Make drive mapping the same (with exception of the user's personal folder)
Make Network Places look the same
Make power management settings the same
Move the Documents and Settings folder (or as much as possible) to the server.

I don't even mind micromanaging the computers that much, but I'd really like to be able to do it via the server. (I just hate kicking people off their computer in the middle of their work.) I'd really appreciate tips and hints from other Admins who strive for efficiency.

41 replies

by steven a

I too am the sole admin of about 30 computers. I use admin installs for all software whenever possible, which leads to uniformity in start menu, etc. For drive mappings I use scripts (net use command) so all workstations are (or at least each workgroup) identical. For network places to be the same, they would need to be in the same Domain or workgroup. Most programs, like MSOffice, allow you to move the documents folder wherever you want and specify its location under options.

by lee v.

Sounds like you may want to implement "manditory" policies, and maybe some login scripts. Using the Policy Editor you can do much of what you mentioned, assuming the Policy Editor hasn't been eliminated in Win2K. General login scripts can also allow you to map network drives including the User's personal folder, if those reside in a consistent place on the network. Or you can set up the user's home directory in the Win2K equivalent of User Manager for Domains. As a little side topic, just don't be too stringent on what you make a manditory setting. While you must make your job as do-able as possible, try not to take away all of the freedoms a user has on the PC, such as their own personal wallpaper, etc. You want to keep the machines as consistent and reliable as possible, without killing the morale of the people using them.

by dale

Sounds like what you need is a little configuration management. Though you have some new computers and some old, you will probably find that you only have three or four different combinations of hardware that must be supported. The thing to do is get a machine that represents each class of hardware you have on the floor, i.e. one from each CPU type, and do what you would consider to be the perfect install on each one. Configure desktop the way you like it and install the applications where you would like them to live. Copy each of these machines to its own image file with software like Ghost or Drive Image. Then download this image to each of the other machines in production. Use profiles and or scripts to manage drive mappings with consistency. This can be a pain to perform on machines you've already deployed but once the process is complete managing existing machines and deploying new ones becomes extremely easy. So does trouble shooting - the computer doesn't work, reimage it. The biggest problem will

by dale

Damn this 1000 character limit! Anyway, the biggest problem will be managing the different NIC and video drivers. The fewer of these variables you have, the better. Standardize the NIC's and video cards in your workstations if you can... Once you doyou will get the the point where you have a few images that cover all the computers in your network. User's personal data should be stored on the server and backed up regularly. If they ever have major trouble with the machine, simply re-image it and your back in business in 30 minutes or less. You need to get some more PC's up - no problem. Purchase the same hardware config that you have in house, and you can image and deploy the PC's in minutes.

The main thing is that you have to develop standards. Standard NIC, standard video card, standard location for user data and application files, etc. Once you have developed the standards, and acquired a few tools for deploying them, configuration management makes you work SO easy...

I hope this helps!

Dale H

by jesselou

since you are the sole administrator you can implement the remote installation service feature of the win2000 server as you would like to uniformly configure in each of your workstation i think this is the best feature you can use.try to read more about it that will address your plannings.

by donhuffman

Is this a TEST or what? All your needs are standard fare for anyone that has taken the MSSERVER CORE class. Policies,profiles,user directories on the file server..All standard stuff......

by billy.j

Impliment standard policies and profiles - make them roaming if users do not always use the same PC - create logon scripts for the drive mappings or manipulate the adm file accordingly - assuming 2000 works the same as NT4 (dont know haven't had a proper look at it yet.)

by rickrkr

To define the default policies of everyone you use the systems policy editor. From the start menu choose administrative tools (common), then system policy editor. From the File menu select New Policy, configure the user policies and the computer policies accordingly, you are changing the registry. When you have made the changes (shade or check) save the file as NTCONFIG.POL and put it in the PDC-s scripts file. You have to set up dir replication if you have a BDC.
This will take care of NT4, Ihope it will help you on W2K.

by aaron v

Since you say you are all running Win2k, verify your servers are all Win2k and make to switch to Native Mode. After switching, you will have access to Group Policy Objects. These can make your life significantly easier once you understand them.

by mcse lee

While all of the above are good answers (and, coincidentally, are pretty much the same answer), I have a different suggestion...

TERMINAL SERVER!! It's built into Win2K, and will do everything you want and more. Not enough room here to go into detail, but this is something you whould definitely look into.

by csheltcomp

#5 and #10 are your best solutions for win2k. Win2k was highlighed for its remote installation. It works along the lines of MS SMS. And MCSE Lee is right on it also wityh Terminal Server. Win2k Server has it built in and also allows you to prepare the clients with permissions and you can select to have specific applications running for the clients. Just set it up as an application server through termainal services. Make sure though that you watch your permissions closely since they are working off of the server.

by markguer9

Terminal Server is a good solution, I prefer Metaframe from Citrix. It extends Terminal Server to a point where it is actually useful. Remote printing would not be a problem anymore. By connecting to a Metaframe server you will have pretty high RAM requirements (16-24 mb's per user) plus whatever you need on server to run efficiently. This will also allow users to customize their desktops and retain some individuality.

by xqgo

I'm running Win 2K at home and have it setup on my lap top and I have trained my self from just using the help menus. Some times it took a little studing, but I usually find away to get what I want out of this very different O/S. Setup your self up with an administrative floating profile along wiht making your workstatioin a master console. The nice thing about WIN 2K is the fact that it gives your log in scripts that you can adjust to the needs to the network. I would also look into the self healing attribute which will automaticaly down load software to a machine according to a user profile. This is where you would want to create a general profile contain the application download scripts so all you would have to do is copy and past to make new user profiles or go around to each computer and use the same profile to standardise your environement just make sure that when you do not to overload the network due to the bottleneck created from too many machines down loading at the same time. If there is

by istal

..there's only one way as MCSE Lee says
terminal server, and it's a GOOD ONE...

All best

by baadil

Along with some suggestions by other about policies, profiles, and login scripts, you may want to try active directory. It may ease some of your micro-managing pains.

I would, for sure, try to keep the hardware consistent.

by paultalb

Sounds like you have the machines set up, so I would create a profile on a machine then copy the profile to the server, then point everones roaming profile to the one you created using user manager. Then use the policy editor to keep them from changing it. Expect a rebelion, may the force be with you.

by brianbarber

Install Active Directory and define a Group Policy Object with all of the parameters you listed. Make all of the users whose workstations you want to manage a member of the group you assing the group policy object to. Et viola! (trans. And there itis!)

BB

by philthegreat

Philip wrote: details as follows (besides, you can check in www.microsoft.com/ in support menu chooses "knowledge base"

SUMMARY
=======
The installation behavior of the Microsoft Windows Installer tool can be configured by an administrator using the Group Policy Editor (GPE) and the Active Directory.

There are also several user and machine policies that can be configured on a local computer. This article describes user polices and then the machine
policies.

MORE INFORMATION
================

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved.Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys and
Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete
Information in the Registry" and "Edit Registry Data" Help topics in
Reged

by on-site

Since You are soley using 2000 why not use the Terminal services. This will allow you server based administration of each account and complete control over all desktops program menus etc ! I've done it ! It's great !

This discussion is closed to new replies.