MCSE Boot Camp Notes :

Networking Guide
Chapter 7, Configuring the Network Information Service (NIS)

About managing users

About managing users

Two types of account exist on an NIS network: those that are distributed (and must be administered from the master machine) and those that are local (and must be administered from the local computer). Distributed accounts allow users to access any machine on the NIS network, while local accounts allow users access to the local host machine only:

distributed
Provides account information that is uniform on each machine in an NIS domain. Changes made to distributed accounts are automatically propagated through NIS maps to other NIS nodes. You can easily manage distributed accounts from a central node, the master server.

local
Provides account information that can be unique to a particular machine. Because they are not affected by maps that are propagated between servers, local accounts allow you to exempt certain users from NIS management. In addition, changes that you make to local accounts do not affect NIS.


NOTE: When NIS is installed, preexisting accounts become local accounts by default, on both master and slave machines.

NIS password information is maintained by the following files in the /etc directory: 

passwd.yp
Contains entries for distributed accounts. After entries are added using the Account Manager, The passwd map is created from this file. 

passwd.local
Contains entries for local accounts. Entries are created by default when NIS is initialized on a system or added later using the Account Manager. 

passwd
Contains entries for all active accounts, local and distributed. On the master server, passwd contains all entries from passwd.yp and passwd.local. On slave and copy-only servers, it contains entries from passwd.local and ASCII translations of the passwd map received from the master.

Entries in passwd.local take precedence over entries in passwd.yp. That is, if the two files include a user with the same name, the information in passwd.local is incorporated into passwd and the corresponding information in passwd.yp (and the passwd map) is overridden.

On clients, you can use NIS maps to augment local password information in the /etc/passwd file. See ``Using NIS maps in the password file'' for more details. 

ptmp
Is a locking file used by yppasswd (see ``Special NIS password change'' later on in this chapter).
NIS group permissions information is maintained by the following files in the /etc directory: 

group.yp
contains entries for distributed groups. After entries are added manually, the group map is created from this file. Each NIS domain has a unique group.yp file existing only on the master server. 

group.local
contains entries for local groups. Entries are created by default when NIS is initialized on a system or added later manually.


group
contains entries for all active groups, local and distributed. On the master server, group contains all entries from group.yp and group.local. On slave and copy-only servers, it contains entries from group.local and ASCII translations of the group map received from the master.

Entries in group.local take precedence over entries in group.yp. That is, if the two files include a group with the same name, the information in group.local is incorporated into group and the corresponding information in group.yp (and the group map) is overridden.

On clients, you can use NIS maps to augment local group information in the /etc/group file. See ``Using NIS maps in the group file'' for more details.

If you want to create local user accounts on an NIS server, do so before you configure NIS. Refer to Chapter 1, ``Administering user accounts'' in the System Administration Guide for more information on creating user accounts. For information regarding account creation after initializing NIS, refer to ``Administering NIS users and groups''.


NOTE: Unless distributed users have access to home directories on each machine they access, their login attempts will fail. For more information, see ``Distributing home directories''.


You can manipulate NIS account files directly from the command line or scripts using the useradd(ADM), userdel(ADM), and usermod(ADM) commands.

Networking guide
Call : 800-519- 2267

MCSE CCNA Certification boot camp
Testimonials
 Join MCSE Boot Camp & CCNA Boot Camp Back to Back Certification Today.
MCSE Boot Camp links  MCSE Boot Camp 270  MCSE Boot Camp  290  MCSE Boot Camp  291  MCSE Boot Camp 293  MCSE Boot Camp  294  MCSE Boot Camp 298  MCSE Boot Camp 299  MCSE Boot Camp Security  MCSE Boot Camp 640-801  MCSE Boot Camp routing MCSE Boot Camp 811  MCSE Boot Camp 821  MCSE Boot Camp 831  MCSE Boot Camp Resources MCSE Boot Camp MCSE + CCNA  MCSE Boot Camp Training  MCSE Boot Camp Card pay  MCSE Boot Camp Papal  MCSE Boot Camp MCSE Notes  MCSE Boot Camp CCNA Notes    MCSE Boot Camp index MCSE Boot Camp main  MCSE Boot Camp root MCSE Boot Camp link  MCSE Boot Camp resources MCSE Boot Camp home    Ref1 Ref2
Microsoft MCSE Boot Camp
MCSE Boot Camp, MCSE Certification boot camp, MCSE Training boot camps, MCSE certification  boot camp training at California and Maryland USA. Also CCNA, CCNP, CISSP, Red Hat Linux Certification notes.

Vibrant boot camp offers MCSE, CCNA, CCNP Certification back to back

Vibrant offers MCSE certification training boot camp for $5400 all inclusive, instructor led at California and Baltimore.

Vibrant Bootcamp Participants come from All Around the World. Vibrant has trained students from more than 15 countries like USA, UK, (Scotland, Ireland, Wales), Switzerland, Germany, Australia, Canada, France, Holland, Japan, Belgium, Bahrain, New Zealand, Tanzania, Turkey, Kenya and more.

Preboot Sequence, Process Accounting, Publishing Resources, Publishing Software Packages, Redeploying Software, Refreshing Group Policy at Established Intervals, Remote Assistance, Remote Desktop for Administration, Removing a Service Pack or Hotfix, Removing or Disabling Software, Requesting Assistance, Reroute Requests with Redirects, Resolving Conflicts Between Group Policy Settings, Restoring Active Directory Directory Services, Restoring Files and Folders, Roaming User Profiles, Security, Setting Up and Managing Published Printers, Setting Up and Managing Published Shared Folders, Setting Up Auditing, Shared Folder Permissions, Slipstreaming Service Packs and Hotfixes, Software Deployment, Software Installation and Maintenance Technology, Software Update Services, Support_388945a0 account credentials instead of the users credentials to perform specific administrative, System Requirements, TABLE OF CONTENTS : Installing and Deploying Windows Server 2003, Taking Ownership, Terminal Server Role, Terminal Services Components, Terminal Services,  The Boot.ini File, The Deny Permission, The File Signature Verification Utility, The Logman Utility, MCSE Boot Camp Training get MCSE join MCSE Bootcamp, The Recovery Console, The relog Utility, MCSE Boot Camp Training get MCSE join MCSE Bootcamp, The Remote Desktop Connection Utility, The Remote Desktops Snap-In, The Session Manager, The Shutdown Event Tracker, The System Monitor, The typeperf Utility, The Windows Server 2003 Boot Process, Troubleshooting NTFS Permission Problems, Troubleshooting Terminal Services, Unattended Installation, Upgrading Software, Using a Saved File to Request Assistance, Using an Audit Policy, Using an Unattended Answer File, Using Configure Your Server Wizard and Add or Remove Programs to Install IIS, Using Driver Signing, Using E-Mail to Request Assistance, Using Event Viewer to View Security Logs, Using Event Viewer, Using Group Policy, Using Remote Installation Services, Using Scripting to Manage Website Content, Using Task Manager to Monitor Performance, Using the Recovery Console, Using the System Preparation Tool, Using User Profiles, Using Windows Messenger to Request Assistance, Viewing Security Logs, Virtual Directories, Volume Mounting, Web-Based Administration, Windows Server 2003 Licensing, Windows Server 2003 network, Windows Update Catalog, Windows Update