MN506 Unit Title System Management Assessment Group report, with individual demonstration.
September 26th, 2018 by admin
Assessment Details and Submission Guidelines
Trimester T2 2018
Unit Code MN506
Unit Title System Management
Assessment Group report, with individual demonstration.
Assessment System documentation for an enterprise network system incorporating the
Title design, installation, configuration and management of required servers and
services using appropriate server systems.
Purpose of the This assignment is designed to assess students’ knowledge and skills related
assessment (with to the following learning outcomes:
a. Analyse human usability in systems and documentation within the
context of constantly changing modern industry requirements
b. Plan and implement various application servers for an organisation
Total Marks 50
Word limit 2000
Due Date Report: Week-11, Sunday, 11:55 PM. Demo: Week-12 lab.
Submission All work must be submitted on Moodle by the due date along with a
Guidelines title Page.
The assignment must be in MS Word format, 1.5 spacing, 11-pt Calibri
(Body) font and 2.54 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 IEEE referencing style.
Your submission must be your own work, and will be checked for
originality using Turnitin originality checking system, and subject to
MIT’s academic misconduct policy.
Extension If an extension of time to submit work is required, a Special Consideration
Application must be submitted directly through AMS. You must submit this
application three (3) working days prior to the due date of the assignment.
Further information is available at:
Without a granted special consideration, late submissions will be subject to
penalty as per the information on late penalty in the unit description.
Academic Academic Misconduct is a serious offence. Depending on the seriousness of
Misconduct 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:
Procedure. For further information, please refer to the Academic Integrity
Section in your Unit Description.
Prepared by: Dr Jahan Hassan Moderated by: Dr Nandini Sidnal July, 2018
MN506 System Management Page 2 of 5
Form a group of three students and inform your laboratory tutor of the names and student IDs of your group members. Choose one (1) scenario given in the list below as your assignment topic. Assume that your group has been hired by the client company to develop a networked system for their required services as described in your chosen scenario. Your task in this assignment is to (i) analyse client requirements, (ii) design the solutions, (iii) implement, configure, and troubleshoot implemented solutions, and finally, (iv) prepare a system documentation report meeting the client requirements and following a standard industry template. Detailed requirements are provided below:
1. For your chosen scenario, (i) analyse client requirements, (ii) identify and propose the required servers and server roles (services), and (iii) provide required configurations for your chosen scenario.
2. Perform the configurations using either virtually or physically installed server OS for your chosen scenario. Students can use Windows Server 2008 or a higher version, or Linux server if appropriate, which will depend on the scenario chosen. Your submission should include screenshots of each important step.
3. Prepare a detailed system documentation report to record your work done in steps 1 and 2 above, using a standard template. You have the freedom to create a template, with company name, logo, etc., for your client and use that for your documentation report. This report will serve as an important part of backup and disaster recovery documentation for the organisation in your chosen scenario, and can be used for training new IT staff in the organisation. As such, you must consider human usability factors and include the configurations using a 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 that must be included in the documentation are provided in the marking guide, however, you can include additional sections if deemed useful.
You must configure the domain(s) using group members’ names (e.g., sajeen-joy-sam). If the chosen scenario requires a web server, the group must create a simple webpage (using html header tag only) to display the company’s name, and student ID numbers of the group members; this page needs to be stored on and displayed from the created web server.
This documentation report (one report per group) is to be submitted on Moodle in Week-11.
4. Use your configured system to demonstrate individually your understanding of the implemented scenario during your week-12 laboratory class.
Scenarios (Choose one scenario for your group to work on):
Scenario 1: Local Area Network (LAN) to support Windows Server and Client Environment
CharlieChocolates is a renowned chocolate manufacturing business requiring the setting up of a LAN for their office located in east Perth. They have four departments: Inventory, Marketing, Sales, and Accounting. All objects (e.g., users, computers, etc.) belonging to these departments need to be created within their respective Organisational Unit (OU) for their own department. CharlieChocolates requires the following LAN services:
1) Centralised user authentication
2) Print server for users
3) All computers should acquire the IP addresses automatically from a server
4) Hosting of their own website using their own server
`MN506 System Management Page 3 of 5
5) 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.
Scenario 2: Local Area Network (LAN) to support Windows Server with multiple domains
TechGuru is an IT consulting company needing to setup a LAN for their main office which is located in Melbourne. They have three different departments named Operations, Consultants, and Marketing. All objects (e.g., users, computers, etc.) belonging to those departments should have their own Organisational Unit (OU). The clients require the following technologies to be implemented within their LAN:
1. Two different domains. One is allocated for the administrator and the other is allocated for everyone else (users)
2. Centralised user authentication for different domains
3. All computers should acquire their IP addresses automatically from a server
4. The Company should host a website from their own server
5. Your configuration should reflect the above criteria and display different privileges assigned to the different domains’ users belonging to these domains.
Scenario 3: Local Area Network (LAN) to support Windows Sever and Linux Client Environment
With the growing base of users of Linux, MacroSoft Software, a software development company which was planning to create a Windows server based LAN decided to also support Linux clients to authenticate using the Active Directory. The company has three different departments named Operations, Finance and Marketing. All objects (e.g., users, computers, etc.) belonging to these departments should have their own different OU. The clients require the following technologies to be implemented within their LAN:
1. The company requires a centralised user authentication support for Linux clients
2. All computers should acquire IP addresses from a server
3. The company should host a website through their own server
4. There should be hardware virtualisation platform
Scenario 4: Setting up technology/features for Linux Server and Windows Client Environment
Adventura, a Sydney-based new company is looking at setting up a LAN for their office. They have three different departments named General, Finance, and Marketing. All objects (e.g., users, computers, etc.) belonging to these departments should have their own different OU. The users require the following technologies to be implemented within their LAN:
1. The client wants to use the Linux operating system as a server side operating system with the LDAP/SAMBA service to communicate between windows client machines and a Linux server
2. Centralised user authentication for Windows clients
3. 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; state your assumptions clearly, as well as configure accordingly.
Prepared by: Dr Jahan Hassan Moderated by: Dr Nandini Sidnal July, 2018
MN506 System Management Page 4 of 5
Table 1: Marking criteria for Assignment 2
Section to be included in Description of the section Marks
Introduction Introduces the purpose of the documentation report, and 2
a clear road map of the report (which section presents
Requirement analysis Analysis of requirements, clear identification and listing 8
and identification of of correct server roles/features/technologies needed for
server roles and realising the scenario.
Configuration process All steps are described for the implementation of all 8
description required technology/feature/server role(s). Description
refers to corresponding diagrams /screenshots using
Description is clear and easy to follow. 2
Configuration Screenshots of commands and GUI configurations for 10
screenshots or each identified technology/feature are provided using
commands labelled diagrams with caption.
Summary Summary of all configuration performed. 5
Demonstrations Demonstrate the understanding of the system 10
(Will take place during implemented on a virtual or real system, and/or the
Week-12 lab) report. This is individual mark awarded based on each
student’s level of understanding of the work
accomplished by the group.
Conclusions Conclusion of what has been achieved in this assignment 3
Reference style All resources referenced properly using IEEE format 2
Marking Rubric is provided on page 5.
Prepared by: Dr Jahan Hassan Moderated by: Dr Nandini Sidnal July, 2018
MN506 System Management Page 5 of 5
Requirement analysis and identification of server roles and technologies /8
Configuration process description /8
Configuration screenshots or commands /10
Reference Style /2
HD DI CR P
>80% 70%-79% 60%-69% 50%-59%
Clear and relevant Clear and relevant Purpose of the Either purpose of the
purpose of the purpose of the documentation report documentation report is
documentation report, documentation has some relevance not relevant, or road
with a clear road map of report, with unclear but lacks clarity, and map is not provided.
the report. road map of the unclear road map of
report. the report.
Identification and Identification and Identification and Identification and
analysis of all analysis of most of the analysis of most of the analysis of up to two (2)
requirements, listing of requirements, listing requirements, listing requirements, listing of
correct server of correct server of correct server correct server
roles/features/technolo roles/features/technol roles/features/technol roles/features/technolo
gies for ALL of the ogies for all identified ogies for some of the gies for the identified
requirements. requirements. identified requirements.
All steps are described All steps are described Steps are described Steps are described for
for the implementation for most of the for most of the up to two (2) of the
of all required required required required
technology/feature/serv technology/feature/se technology/feature/se technology/feature/serv
er role(s). rver role(s). rver role(s), but some er role(s), some steps
important steps are are missing.
Description refers to the Description refers to missing.
corresponding diagrams the corresponding The description does not
/screenshots using diagrams /screenshots Some of the include the reference to
figure numbers. using figure numbers. description lacks the the corresponding
reference to the diagrams /screenshots
Description is clear and Description is clear corresponding using figure numbers.
easy to follow. and easy to follow. diagrams /screenshots
using figure numbers. Description is unclear
and not possible to
Description is clear follow.
and easy to follow.
Screenshots of Screenshots of Screenshots of Screenshots of
commands and GUI commands and GUI commands and GUI commands and GUI
configurations for all configurations for configurations for configurations for most
required most of the required most of the required of the required
technology/feature are technology/feature technology/feature technology/feature are
provided, using labelled are provided, using are provided, but provided, but missing
diagrams with caption. labelled diagrams with missing either diagram labels and
caption. diagram labels or captions.
Clear and concise Clear and concise Summary of the Summary of the
summary of summary of the implementations of implementations covers
implementations of all implementations of most of the required up to two (2) of the
required configurations most of the required configurations for the required configurations
for the chosen scenario. configurations for the chosen scenario is for the chosen scenario.
chosen scenario. provided, but clarity
Demonstrate the full Demonstrate the full Demonstrate partial Demonstrate partial
understanding of the understanding of the understanding of the understanding of the
system implemented system implemented system implemented system implemented
using a real system. using the report. using a real system. using the report.
Clear conclusion Clear conclusion Clear conclusion, but Conclusion somewhat
covering of all that has covering most of what missing some of the clear.
been achieved in this has been achieved in important points.
assignment. this assignment.
Clear styles with Clear referencing style Generally good Sometimes clear
excellent source of referencing style referencing style