Download
1 / 33
330 likes | 434 Views
chapter 5. Network Operating Systems. CHAPTER OVERVIEW.
E N D
chapter 5 Network Operating Systems
CHAPTER OVERVIEW • Network operating systems provide services such as file storage and network printing that support many of the business activities we conduct on a daily basis, including real-time interaction with financial and production applications or real-time sharing of project data.
CHAPTER OBJECTIVES • Identify common features of network operating systems. • Discuss the historical development of network operating systems. • Develop business perspectives on network operating system implementations, upgrades, updates, service packs, maintenance, and system replacement.
CHAPTER OBJECTIVES (cont’d) • Describe the four major network operating systems and provide a brief discussion of their histories. • Identify common network operating system management utilities and add-on products. • Describe other network management tools.
NETWORK OPERATING SYSTEMS – AN INTRODUCTION • A network operating system is: • software that interfaces between server hardware and the network to which the server is attached. • software that runs on a server computer and which provides users with controlled access to shared services on a network.
NOS – COMMON FEATURES • Common features of modern NOSs include: • File system services • Printing services • Application services • Web folder sharing • Web-based management • Desktop management
NOS – COMMON FEATURES (cont’d) • Server clustering • Directory services • Metadirectory integration • Open source technologies • Advanced security services • Internet and Web services
NOS – RECENT HISTORY • NOSs evolved for business reasons. • In the early 1980s, hard drives were expensive to install in each individual PC. • Users were developing growing needs to store increasing numbers of files. • With the implementation of PCs, organizations had need to easily and cost effectively share files between departments. • Distributed processing could be cheaper for a department than accessing a mainframe or developing an application for a corporate mainframe.
NOS – BUSINESS PURPOSE • Shared access to expensive resources. • Shared access to applications such as databases, email, and Web services. • Data storage. • Integration of companywide business functions. • Efficient workflow. • Enhanced transmission of information between points A and B. • Extended reach beyond an organization’s internal boundaries.
NOS – BUSINESS COSTS • NOS management and maintenance. • System updates. • Wages for experienced technicians. • Hardware upgrades to support new NOS versions. • Administrator and user training. • Application program updates.
NOS – RESPONSE TO BUSINESS COSTS • Centralized server farms coordinate the management of servers and network operating systems in a single location. • NOS vendors developed tools that allow network administrators to access and manage servers from remote locations. • Consolidating NOS services to fewer, more powerful, servers.
NOS IMPLEMENTATIONS • Requirements: • Plan for the NOS to meet business needs. • NOS software and NOS license. • Server hardware. • Client computers and their local operating systems. • Connectivity hardware including NICs, hubs, switches, routers, media, etc. to build the network infrastructure. • Carrier service connections for Internet connectivity. • Experienced technicians to perform the installation and then maintain it.
NOS UPGRADES • An NOS upgrade is the next generation of a network operating system vendor’s NOS software. • Steps for implementation are generally different than a brand new installation. • Business owners and managers should always ask, “What will this upgrade do for the business – today and tomorrow?”
NOS UPGRADES (cont’d) • NOS upgrades generally provide enhanced functionality developed to meet the needs of changing business requirements. • Internet access was once part of NOS vendor upgrades. • Tools that reduce the total cost of ownership (TCO) are popular in today’s NOS upgrades.
NOS UPGRADES (cont’d) • Planning an NOS upgrade deployment: • See if new features meet business needs. • Determine whether updated application programs will be required. • Determine if new versions of workstation operating systems will be required. • Determine whether new hardware be required for servers or for workstations. • Decide how data will be migrated or converted. • Determine when to perform the upgrade.
NOS UPDATES, SERVICE PACKS, and MAINTENANCE • NOS vendors receive continuous feedback from their customers about NOS problems. • As vendors fix these problems, they release support packs, service packs, or NOS updates. • It’s best to install a service pack on a test system before implementing it in a production environment.
NOS UPDATES, SERVICE PACKS, and MAINTENANCE (cont’d) • Network administrators often wait from a few weeks to a few months before installing service packs in their production networks in anticipation of feedback from other companies that have already installed the service pack. • Network administrators can obtain service packs and feedback about service packs from the NOS vendors’ websites
NOS REPLACEMENT • NOS replacement generally involves the business requirements of reducing costs and standardizing on one NOS platform. • Consolidation to a single NOS can reduce licensing fees, system update/upgrade costs, general network administration costs, and technical support costs. • Consolidation can also require the replacement of expensive applications that ran on the NOS that’s being replaced. • Hardware might need to be upgraded. • NOS Administrators might need to be retrained or replaced.
NOS – Novell NetWare • Novell history dates back to 1979. • Company went public in 1983. • Track record of innovative operating systems that met business needs. • Missed the boat with the public launch of the Internet in the mid-1990s – slow to migrate from IPX protocol to IP. • Introduced Directory Services with NetWare 4.0. • Over time has launched NetWare 2.x, 3.x, 4.x, 5.x, and 6.x versions of their NetWare NOS. • Today, much of their NOS functionality is based on Linux and open source technologies.
NOS - Microsoft • Microsoft didn’t get into the NOS game until the late 1980s with the introduction of Windows NT. • Windows NT went through several iterations including versions 3.1, 3.5, and 4.0. • Windows NT was initially adopted for application services in a networked environment. • Windows NT introduced the concept of domains. • Microsoft incorporated IP into Windows NT early on. • Windows 2000 Server introduced Active Directory as Microsoft’s new directory service. • Windows 2000 Server fully integrated Internet services and Internet access. • Windows Server 2003 is Microsoft’s latest NOS iteration.
NOS - Linux • Linux has its roots in UNIX. • Linux as a separate operating system dates back to 1991 with development work performed by Linus Torvalds. • Linux version 1.0 was released in 1994. • It is based on open source technology. • It provides most of the services of Novell’s NetWare or Microsoft’s Windows Servers. • Large percentage of Internet Web servers are powered by Linux. • Fewer trained and skilled technicians than are available for Novell or Microsoft networks. • IBM, HP, and Novell are big supports of Linux.
NOS - UNIX • UNIX history dates back to the 1960s with work performed at MIT, General Electric, and AT&T Bell Labs. • Ultimately the first version of UNIX was released by AT&T Bell Labs in 1971. • Several updated versions were released throughout the 1970s, and AT&T gave it away for free. • Another popular version, known as BSD UNIX was developed using AT&T source code. The BSD version was the first to include a word processing/text editing program. • Other versions of UNIX were released in the 1980s, namely SCO UNIX, Sun Microsystem’s Solaris, HP-UX, and IBM’s AIX.
NOS MANAGEMENT UTILITIES and ADD-ON PROGRAMS • Novell provides NetWare Administrator, ConsoleOne, NetWare Remote Manager, and iManager for managing NetWare networks. • Novell sells ZENworks for policy-based desktop and server management. There is also a version of ZENworks that can be implemented to manage and control PDAs. • ZENworks can be used to deploy applications and manage hardware and software inventory.
NOS MANAGEMENT UTILITIES and ADD-ON PROGRAMS • Microsoft provides the Microsoft Management Console (MMC) for managing NOS functions. • Microsoft’s NOS also incorporates powerful policy-based administration into Active Directory. • Systems Management Server (SMS) can provide additional policy-based management functions as well as centralized application deployment and hardware and software inventory management.
Linux and UNIX • Provide built-in utilities for adding users and groups as well as utilities to manage file services, print services, and remote connection services. • Linux and UNIX do not provide a built-in utility, such as Novell’s iManager or Microsof’t MMC, to consolidate network management functions. • Secure Shell (SSH) is a utility that administrators can use to manage and control remote Linux and UNIX computers. • X-windows is a GUI interface that can be used to manage local and remote computer functions.
OTHER MANAGEMENT SERVICES and PRODUCTS • DNSandDHCP • These are key management components that are incorporated with all modern NOSs. • DHCP automatically assigns IP addresses and other IP-related information to client computers. • DNS facilitates access to internal and external network resources by resolving host names to IP addresses.
OTHER MANAGEMENT SERVICES and PRODUCTS • Network Traffic and Protocol Analyzer • This is a diagnostic application or device that can monitor and capture data packets on a network for subsequent analysis.
