System Management
Prepared by: Dr Mohammad Mohammad Moderated by: Dr Imran Jokhio May, 2022
| Assessment Details and Submission Guidelines | |
| Trimester | T1, 2022 |
| Unit Code | MN506 |
| Unit Title | System Management |
| Assessment Author |
Dr Mohammad Mohammad |
| Assessment Type |
Assignment 2 – Group report, with individual demonstration. |
| Assessment Title |
Network Servers, Installation and Configuration |
| Unit Learning Outcomes covered in this assessment |
This assignment is designed to assess students’ knowledge and skills related to the following learning outcomes: a. Analyse and compare various server management systems; b. Compare emerging tools and techniques for system management; c. Analyse human usability in systems and documentation within the context of constantly changing modern industry requirements; d. Plan and implement various application servers for an organisation e. Manage servers and resources to support enterprise information systems |
| Weight | 25% of Total Assessment |
| Total Marks | 50 |
| Word limit | 2000 |
| Due Date | Week-11, Wednesday, 01/06/2022 at 11:59 PM. Demo: Week-12 lab. |
| Submission Guidelines |
All work must be submitted on Moodle by the due date along with a completed Assignment Cover Page. The assignment must be in MS Word format, 1.5 spacing, 11-pt Calibri (Body) font and 2 cm margins on all four sides of your page with appropriate section headings. Reference sources must be cited in the text of the report, and listed appropriately at the end in a reference list using APA or IEEE referencing style for School of Business and School of Information Technology and Engineering respectively. |
| Extension | If an extension of time to submit work is required, a Special Consideration Application must be submitted online to AMS follow the link below you may require to login. You must submit this application three working days prior to the due date of the assignment. https://online.mit.edu.au/ams/PublicDocs/Student/MIT_Special_Consideration_Ap plication.pdf |
| Academic Misconduct |
Academic Misconduct is a serious offence. Depending on the seriousness of the case, penalties can vary from a written warning or zero marks to exclusion from the course or rescinding the degree. Students should make themselves familiar with the full policy and procedure available at:http://www.mit.edu.au/about mit/institute-publications/policies-procedures-and-guidelines/Plagiarism Academic-Misconduct-Policy-Procedure.For further information, please refer to the Academic Integrity Section in your Unit Description. |
AssignmentTutorOnline
MN506 System Management Page 2 of 4
Prepared by: Dr Mohammad Mohammad Moderated by: Dr Imran Jokhio May, 2022
Assignment Description
Form a group of (3) students and inform your lab tutor of the names and student IDs of your group members.
Assume that your group is hired by a client company to develop a networked system for their required services
as described in the scenario.
Your task in this assignment is to analyse client requirements, design solutions, implement, configure, and
troubleshoot implemented solutions, and finally to prepare a system documentation report meeting the client
requirements and following a standard industry template. Detailed requirements are provided below:
1. Based on the scenario given below, (i) analyse client requirements, (ii) identify and propose the required
servers and server roles (services), and (iii) provide required configurations for the scenario.
2. Perform the configurations using either virtually or physically installed server OS to realise the scenario.
Students can use Windows Server 2012 or a higher version, or Linux server if appropriate. Your
submission should include screenshots of each important step.
3. Prepare a detailed system documentation report. This report will serve as an important part of backup
and disaster recovery documentation. As such, you must consider human usability factors and include
the configurations using description of each important step, and screenshots corresponding to those in
a way that will be useful to the target users of the document. Essential sections of the documentation
are provided in the marking guide, however, you can include additional sections if deemed useful. You
should explain how documentation of network changes should be handled and how documentation can
aid the troubleshooting process by keeping a record of common issues.
This documentation report (one report per group) is to be submitted on Moodle in Week-11.
4. Use your configured system to demonstrate individually the implemented scenario during your week-12
lab. Individual understanding will be tested during your demonstration.
Scenario
You are the system administrator for a private company, called Servers and Services PTY, that is moving into
a new building. The Servers and Services has 100 full-time employees, as well as up to another 50 that either
work part-time or perform short-term contract work. Each full-time employee will have a dedicated
workstation; most also have a laptop. The part-time/contract staff have their own or company-supplied
laptops. There will also be several spare workstations. They have four departments: IT, HR, customer service,
and Marketing. All objects (e.g., users, computers, etc.) belonging to these departments need to be created
within their respective OU for their own department. The client requires the following LAN services:
Workstations, Laptops and Servers
The Servers and Services PTY has grown quite quickly. Initially when there were just a few friends, they used
all online services (e.g. Google Docs, GitHub, DropBox). But now as they move into the new building, they have
decided to use their own infrastructure. Most of the employees work in a distributed mode, working on their
own computers and sharing resources direct with colleagues, however there are several centralised services
required. Specifically, they have identified the need for the following. Included are the selected names.
1) Windows web server, called Servers and Services, to host a simple company website. The website is
developed using, CSS, JavaScript, and ASP by one full-time employee, with assistance by one
contractor.
MN506 System Management Page 3 of 4
Prepared by: Dr Mohammad Mohammad Moderated by: Dr Imran Jokhio May, 2022
2) Backup server, called BackSS, to store a backup of the web, and other servers on the network.
3) DHCP server, called DHCPSS, to provide dynamic IP addresses to workstations and laptops, and fixed
IP addresses to other servers (based on MAC addresses). Only necessary full-time staff have access.
4) Centralised user authentication
5) All computers should acquire the IP addresses automatically from a server
6) Hosting of their own website using their own server
7) The company wants to store all the files on a separate file server and only users with appropriate
access will be able to access them (not every user should have access to the files). You can assume
which users/groups will have access to these files, and state your assumption clearly.
8) Table of servers, with MAC addresses, allocated IP addresses, client IP address ranges.
9) Installation and configuration details of all the servers.
10) Explain why you designed the backup in the way you did, for example, explain your recommended
frequencies of backup.
11) Details of a password policy and its implementation. The policy should be appropriate to the
organisation, and detail exactly how it is implemented in the system.
Marking Criteria:
Table 1: Marking criteria for Assignment 2
| Section to be included in the report |
Description of the section | Marks |
| Introduction | Introduces the purpose of the documentation report, and a clear road map of the report (which section presents which topic). |
2 |
| Requirement Analysis and identification of server roles & technologies |
Analysis of requirements, clear identification & listing of server roles/features/technologies needed for realising the scenario. |
8 |
| Configuration process description |
All steps are described for the implementation of each identified technology/feature/server role(s). Description refers to corresponding diagrams /screenshots using figure numbers. Description is clear and easy to follow. |
8 2 |
| Configuration screenshots or commands |
Screenshots of commands and GUI configurations for each identified technology/feature are provided using labelled diagrams with caption. |
10 |
| Summary | Summary of all configuration performed. | 5 |
| Demonstrations (Will take place during Week-12 lab) |
Demonstrate the understanding of the system implemented on a virtual or real system, and/or the report. |
10 |
| Conclusions | Conclusion of what has been achieved in this assignment | 3 |
| Reference style | All resources referenced properly using IEEE format | 2 |
| Total | 50 |
MN506 System Management Page 4 of 4
Prepared by: Dr Mohammad Mohammad Moderated by: Dr Imran Jokhio May, 2022
Marking Rubric
| Grade Mark |
HD >40% |
DI 35%-39% |
CR 30%-34% |
P 25%-29% |
Fail |
| Introduction /2 |
Clear and relevant purpose of the documentation report, with a clear road map of the report. |
Clear and relevant purpose of the documentation report, with unclear road map of the report. |
Purpose of the documentation report has some relevance but lacks clarity, and unclear road map of the report. |
Either purpose of the documentation report is not relevant, or road map is not provided. |
Irrelevant introduction. |
| Requirement analysis and identification of server roles and technologies /8 |
Identification and analysis of all requirements, listing of correct server roles/features/technolo gies for ALL of the requirements. |
Identification and analysis of most of the requirements, listing of correct server roles/features/technol ogies for all identified requirements. |
Identification and analysis of most of the requirements, listing of correct server roles/features/technol ogies for some of the identified requirements. |
Identification and analysis of up to two (2) requirements, listing of correct server roles/features/technolo gies for the identified requirements. |
Identification and analysis of less than two (2) requirements, or incorrect analysis. |
| Configuration process description /8 Clarity /2 |
All steps are described for the implementation of all required technology/feature/serv er role(s). Description refers to the corresponding diagrams /screenshots using figure numbers. Description is clear and easy to follow. |
All steps are described for most of the required technology/feature/se rver role(s). Description refers to the corresponding diagrams /screenshots using figure numbers. Description is clear and easy to follow. |
Steps are described for most of the required technology/feature/se rver role(s), but some important steps are missing. Some of the description lacks the reference to the corresponding diagrams /screenshots using figure numbers. Description is clear and easy to follow. |
Steps are described for up to two (2) of the required technology/feature/serv er role(s), some steps are missing. The description does not include the reference to the corresponding diagrams /screenshots using figure numbers. Description is unclear and not possible to follow. |
Steps are described for only one (1) of the required technology/feature/serv er role(s), some steps are absent. The description does not include the reference to the corresponding diagrams /screenshots using figure numbers. Description is unclear and not possible to follow. |
| Configuration screenshots or commands /10 |
Screenshots of commands and GUI configurations for all required technology/feature are provided, using labelled diagrams with caption. |
Screenshots of commands and GUI configurations for most of the required technology/feature are provided, using labelled diagrams with caption. |
Screenshots of commands and GUI configurations for most of the required technology/feature are provided, but missing either diagram labels or captions. |
Screenshots of commands and GUI configurations for most of the required technology/feature are provided, but missing diagram labels and captions. |
Inadequate/absent configuration screenshots. |
| Summary /5 |
Clear and concise summary of implementations of all required configurations for the chosen scenario. |
Clear and concise summary of the implementations of most of the required configurations for the chosen scenario. |
Summary of the implementations of most of the required configurations for the chosen scenario is provided, but clarity needs improvement. |
Summary of the implementations covers up to two (2) of the required configurations for the chosen scenario. |
Summary is not relevant to the implemented configurations, or summary covers only one (1) of the required configurations for the chosen scenario. |
| Demonstration /10 |
Demonstrate the full understanding of the system implemented using a real system. |
Demonstrate the full understanding of the system implemented using the report. |
Demonstrate partial understanding of the system implemented using a real system. |
Demonstrate partial understanding of the system implemented using the report. |
Inadequate demonstration of understanding. |
| Conclusion /3 |
Clear conclusion covering of all that has been achieved in this assignment. |
Clear conclusion covering most of what has been achieved in this assignment. |
Clear conclusion, but missing some of the important points. |
Conclusion somewhat clear. |
Inadequate conclusion. |
| Reference Style /2 |
Clear styles with excellent source of references. |
Clear referencing style | Generally good referencing style |
Sometimes clear referencing style |
Lacks consistency with many errors |