1 / 34

Unit 27: Network Operating Systems

Unit 27: Network Operating Systems. Theory leading to Assignment 1 By James Tedder. Unit Aim. To provide learners with the knowledge, skills and techniques necessary to install, configure, troubleshoot and maintain a reliable network operating systems service. Abstract.

waltery
Download Presentation

Unit 27: Network Operating Systems

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Unit 27: Network Operating Systems Theory leading to Assignment 1 By James Tedder

  2. Unit Aim To provide learners with the knowledge, skills and techniques necessary to install, configure, troubleshoot and maintain a reliable network operating systems service.

  3. Abstract • Modern enterprise organisations rely on the use of a range of network operating systems (NOS), to establish the networking services necessary to run their IT infrastructure. • Supporting a NOS is considered one of the primary roles of a professional network administrator. It is part of their duties to identify the NOS as required, undertake the installation and deployment of network servers, and configure, support and maintain the NOS. • This may also involve routine administration, the management of systems and user security policies as well as more specific specialist tasks.

  4. Assignments • Assignment 1 – Theory (Small) • Assignment 2 – Planning, implementing and testing a network (Large)

  5. Network Operating Systems(NOS) • Designed to support networks • Networks are a collection of many computers and devices that are connected together • By installing a NOS onto a computer it becomes what is know as a Server. • Servers can provide many different functions. NOS installed on a server and configured to distribute files.

  6. NOS/Server types: Standalone • Not dependent to others but is independent to itself • Do not usually provide network logon services • Are independent of domain controllers on the network.  • An example use of a standalone server is for the distribution of files or documents in a small office setting. Documents on the server is set to share mode and read-only mode so user can access files but not modify. Another example could be having a standalone print or Intranet server

  7. NOS/Server types: Infrastructure based • A NOS/Server configured to support a network of hardware and software resources belonging to an entire network • Enables network connectivity, communication, operations and management of an network. • Provides the communication path and services between users, processes, applications, services and external networks/the Internet.

  8. NOS/Server types: Cluster based • A group of servers that work together and act like a single system • Enables high availability, if a server in the cluster fails the remaining servers take up the strain. • Enables load balancing • Enables parallel processing

  9. NOS services: • File: Allows resources to be shared between clients on the network. System admin can regulate who has access to what. • Web: Server configured to store, process and deliver web pages to clients. • Print: Manages the print queue, usage and potentially user credit. Print queue could be shared between multiple printers. • Remote access: Using software such as Virtual Machine Manager the server can be remotely managed. Using VPN connection to the remote server, clients can access their files and folders after logging in. • Firewall/Proxy: A proxy firewall acts as an intermediary between in-house clients and servers on the network. Proxy firewalls are considered to be the most secure type of firewall because they prevent direct network contact with other systems. A proxy firewall has its own IP address so an outside network connection will never receive packets from the sending network directly.

  10. NOS services continued: • Terminal services: With remote access configured a user or admin can take full control of a computer or virtual machine desktop on the network. • Access control: Allows the server admin to authorize users, groups, and computers to access or restrict access to objects on the network or computer. • Infrastructure management: Allows you to connect and manage the objects on the network. • Ecommerce: Website hosting, secure (SSL) certificate installed and email management can be set up.

  11. Windows Server 2016 – Services Services in Windows Server 2016 can be installed through server roles

  12. Windows Server 2016 – Interface Uses a familiar Windows 10 style interface

  13. Unit 27 – Network Operating SystemsAssignment 1 – Task 1.1 You are required to evaluate types of NOS and NOS services of a selection of Network Operating Systems such as standalone, infrastructure based and cluster based systems. • NOS: types eg standalone, infrastructure based, cluster based • NOS services: types eg file, web, print, remote access, proxy, terminal services, firewall, access control, infrastructure management, ecommerce Use Harvard referencing and examples whenever possible.

  14. Disaster recovery Theory leading to Assignment 1

  15. Disaster recovery: Backup MythologyFull Backups • Stores a copy of all files and typically occurs automatically according to a pre-set schedule. • Files are usually compressed to save space, however, even when compressed full backups may consume a lot of storage.

  16. Disaster recovery: Backup MythologyFull Backups • Disadvantages include causing heavy access to the backup disk, which shorten disk life and consume network bandwidth. • More robust than many businesses require. Only a small percentage of files change from one backup to another. • Will yield multiple identical copies of files and consume valuable storage space on the backup medium. • An advantage is the ease of restoration. Restoring a file requires only the file name, location, and date from which to restore the data.

  17. Disaster recovery: Backup MythologyIncremental Backups • Backup only the files that have been created or changed since the last backup. • Usually backup strategies include a combination of full backups and incremental backups. • Running a full backup once per week—on weekends when network and computing resource demands are lower—and scheduling incremental backups on weekdays. • Backing up files with this combination enables a restoration that does not require looking through or merging more than a week’s worth of iterations.

  18. Disaster recovery: Backup MythologyIncremental Backups • An advantage is that the volume of data backed up at each iteration is much smaller, which in turn saves space on the backup medium and uses less network bandwidth. • Disadvantages include backups increasing computing overhead, each source file must be compared with the last full backup as well as the incremental iterations to determine whether data is new or changed. • More complex to locate a specific file to restore as it may require searching several iterations. To completely restore all files requires merging all iterations while taking care to keep only the most recent version of each file.

  19. Disaster recovery: Backup MythologyDifferential Backups • Differential backups are similar to incremental backups, except that each backup operation stores the new and updated files since the last full backup. • For example, if a full backup was performed on Sunday and a file changed on Monday, that file will be part of every differential backup until the next full backup is run.

  20. Disaster recovery: Backup MythologyDifferential Backups • Using differential backups simplifies recovery because only the last full backup and the last differential backup is needed to create a complete restoration. • As with incremental backups, differential backups need to compare current and already-backed-up files to identify any changes. • However, differential backups require more space and network bandwidth compared with incremental backups.

  21. Disaster recovery: • Data Recovery: If data has been backed up it can be recovered by simply installing the backup. If not, through the use of specialised software deleted or corrupted data can be recovered. • Mirrored Systems: A second backup server has an exact copy of another server. If one goes down the other takes over meaning no downtime to the network. • Virtualisation: One physical server split into multiple isolated virtual environments. Reduces physical space and cost. • UPS (Uninterruptible Power Supply)/Backup Power supply: Battery devices that connect to a physical server to give it power when the primary source of power fails.

  22. Disaster recovery: • Off site management: Off site backup allows copied server data stored physically away from the main site. Should the server and data be damaged at one site through fire or flooding for example there is a backup still available. • High availability: How operational the server is. By having regular backups, UPS’s set up and offsite management available your server should be 99% available and therefore considered to have high availability. • Fault tolerance: No single point of failure, fault isolation, backups. Combination of previous and this slides topics. • By having two separate machines that are mirrored.  In the event that the main system has a hardware failure, the secondary system takes over and there is zero downtime.

  23. Unit 27 – Network Operating SystemsAssignment 1 - Task 1.2 • Add a section to your report that discusses the benefits of disaster recovery. • Cover the following points; backup methodology, data recovery, mirrored systems, virtualisation, UPS (Uninterruptible Power Supply), backup-power supply, off site management, high availability and fault tolerance. • Use Harvard referencing and examples whenever possible.

  24. NOS Security Theory leading to Assignment 1

  25. NOS security: • Management of updates/patches: Keeping your server software and client installed software uptodate will eliminate potential holes in security. • Anti-virus protection: Essential on a server. Microsoft Endpoint is an example that protects servers and devices on the network. Alerts can be set to notify the Admin but usual kills viruses automatically. • Physical access policies: Who can access your server? Key coded or locked servers rooms are essential. Access should be restricted only to admin. • Service access policies: Examples include e-mail, file, web and printing. Who needs access to what? Policy's should ensure that only users who need services have access to them.

  26. NOS security cont. • User access policies: Who has access to the network? Users should have username and passwords setup and only access to data essential to their role. • Policy management: Through group policy management network admins can restrict user access and control what they can add and change. • User and group audits: Maintaining a log and monitoring users network usage to maintain security. Can be set in Group policy. Firewalls and filters could restrict access to undesirable websites. • Continual vetting of access: Consistent consideration of who should have access to what. Based on job role and audits. Disclosure and Barring Service (DBS) check and References should be gathered for new employees.

  27. NOS security cont. • Authentication policies and practice: Methods put in place to safeguard access to network services including internet. Password or fingerprint scanners could be considers as ways to authenticate access. • Password policy: Passwords could be set to change every 90 days or have a minimum of 8 characters with numbers, uppercase and lowercase lettering.

  28. Unit 27 – Network Operating SystemsAssignment 1 - Task 1.2 • Now as part of 1.2 discuss the benefits of NOS security. • Cover the following points:management of updates/patches, anti-virus protection, physical access policies, service access policies, user access policies, policy management, user audits, group audits, continual vetting of access, authentication policies and practice, password policy • Use Harvard referencing and examples whenever possible.

  29. Unit 27 – Network Operating SystemsAssignment 1 - Task 1.3 • Discuss and critically compare a selection NOS. These could be: • Open source • Proprietary • General purpose • Task specific • Software include: • Windows Server • MacOS Server • Apache • Linux(e.g Ubuntu Server, RedHat, SUSE, CentOS, Debian, Oracle, ClearOS, Solaris, FreeBSD) Use Harvard referencing and examples whenever possible.

  30. Open-Source (UNIX and Linux) • Free • Various NOS distros available • Ubuntu Server, Red Hat Enterprise, CentOS, Debian,Oracle and many, many more. • Accessible code open for development by anyone. • Extremely wide customization range, meaning that they can perform many tasks to suit the host. • Known for is its stability because processes are separate from those of the operating system. • Even if an application crashes, unless it somehow manages to take down the X Windows system with it (which does happen), the operating system keeps going. • With Windows or Mac however, if an application crashes it can often cause the OS to crash along with, resulting in the server going down with it.

  31. Proprietary • Such as Mac OS X or Windows Server. • Compatible and easily integrate with Windows or Mac OS and their associated eco systems respectively. • Familiar GUI’s • Cost’s money. • Different to open source operating systems in a sense that they may or may not be allowed to use certain software, especially if it doesn’t support a particular file format. • Closed NOS’s that cannot be customized beyond the developers original intention. Users cannot modify or access Windows Servers' underlying code for example. • Open-source NOSs which are free to use can be a great benefit for smaller organisationswith smaller budgets.

  32. General Purpose • A general purpose NOS or setup refers to a server which can be used for a multitude of tasks all at the same time. • General purpose tasks include handling users and access policies and managing files & applications. • Windows Server is used widely because of a few reasons, but typically for its accessibility, maintenance costs and security. • These servers are typically used to communicate with all other devices on the network and commonly used as a computing server. • Distribute computing resources over a network, helping local machines to perform tasks such as domain services, distributing and running applications and storage.

  33. Task Specific • Implemented into a network for specificity. • Servers that are dedicated to computing one task, and one task only. • Could be multiple servers set up on a network all assigned just one task each. • They don’t interact with the network the same way that a general purpose server would • Generally a lot easier to implement and more cost efficient to maintain. • Will not include domain services.

  34. Unit 27 – Network Operating SystemsAssignment 1 • 1.1 You are required to evaluate types of NOS and NOS services of a selection of Network Operating Systems such as standalone, infrastructure based and cluster based systems • 1.2 Discuss the benefits of NOS security and disaster recovery. • 1.3 Discuss and critically compare a selection NOS. Software could include: • Windows Server • MacOSServer • Apache • Linux(e.g Ubuntu Server, RedHat, SUSE, CentOS, Debian, Oracle, ClearOS, Solaris, FreeBSD)

More Related