Discussion Locked

HUH?!

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

Checking out an IDG book "Windows NT Secrects
(Option Pack Edition)" Copyright 1999
ISBN: 0764531301 by Harry M. Brelsford. Found many errors in this book including an entire chapter that has all the illustrations out of sync. But in "chapter 3: Windows NT Server 4.0 Implementation" we find the following: "In a Windows NT (Single) Domain, it's just as easy to assign individual users to local groups that you create, thus eliminating the global group step altogther." Further we find: "Why notjust move the users to the local groups, and eliminate the global groups altogether?" To which we reply: HUH?!

How in the world is this done when you have Application (Member) Servers?! After creating these local groups on the member servers, even though they show up in User Manager for Domains, they are not available when setting access to shares or setting permissions. Why can't we see these local groups when they are created on the member servers? What is Harry talking about in the above quotes??!!!!! or is this yet another mistake in his book?

His advice sounds good, but seems impossible to implement! No matter how we try, we can't see any of these local groups.

5 replies

by ian mclaws

Even though I do not agree with his rationale of eliminating Global groups (they considerably reduce admin time), it is possible to assign access to them.
On the member server, log on to it's local SAM database as the built in administrator(by selecting the member server in the logon to box at log on) logged on this way you will see the local groups created on the member servers when you attempt to assign access on that servers resources.
Again, I must add that this methodology, whereas it isno harder to assign access, it does not give you the flexibility that using global groups does. If you follow the model of user accounts into local groups, any changes to access must be managed at each member server. With the AGLP (accounts into global groups into local groups getting permissions) you can subsequently add or remove accounts from the global groups at the domain controller level and the accounts immediately gain access at all member servers properly configured. Much easier to administer!!

Good luck
Ian

by kahunanui

Duhh, the problem was we weren't chosing the correct machine in User Mgr and User Mgr for Domains! Therefore the local groups created were not available on that particular machine. A very simple solution. However, we will look into what you are saying and thank you for your response!

by ustutz

How much either local or global groups help administration depends on how well they have been designed. If you have several "departments" with resources spread over several members servers, global "departement" groups will help. If your departements are aligned with single member servers (i.e., all of Accounting uses the 'Accounting Server' exclusively), it would be just as easy to just assign [global - i.e., domain wide] users to local groups on the memeber servers. Of course that requires you to touch the member server anytime you change a user account along with the domain controller.

by kahunanui

We found out why the local groups we were creating were not available. See response above. We thank you for your response!

This discussion is closed to new replies.