Chapter 7, Configuring the Network Information Service (NIS)
CAUTION: Do not use the following procedure to remove a master server. If you do, you must reconfigure your NIS network. Rather, refer to ``Changing the master NIS server''. When SCO NIS is removed from a system, the /etc/passwd.local file is removed. The /etc/passwd file, which under NIS included both distributed and local accounts, becomes the authoritative password file. This means that distributed NIS accounts become regular user accounts when NIS is removed. If you want to restrict users with distributed NIS accounts from using the old server, you must remove their accounts before returning the old server to multiuser mode. NOTE: Although you can prevent NIS maps from reaching a server by killing its NIS daemon processes, the master still attempts to reach the server during map propagation, adding an unnecessary burden to the system. For this reason, you should remove NIS from the server. Follow these steps to remove a server:
|
Networking
guide Call : 800-519- 2267
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.
|
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