Assessment Details and Submission Guidelines

Assessment Details and Submission Guidelines
Trimester T1, 2019
Unit Code MN506
Unit Title System Management
Assessment
Author
Dr Mohammad Mohammad
Assessment Type Group report, with individual demonstration.
Assessment Title Design, Installation and Configure Enterprise Network Servers.
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 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
Weight 20% of Total Assessment
Total Marks 50
Word limit 2000
Due Date Report: Week-11, Wednesday, 11:55 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 directly to the School’s Administration Officer, in
Melbourne on Level 6 or in Sydney on Level 7. You must submit this application
three working days prior to the due date of the assignment. Further information is
available at:
http://www.mit.edu.au/about-mit/institute-publications/policies-procedures-and
guidelines/specialconsiderationdeferment
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.

MN506 System Management Page 2 of 4
Prepared by: Dr Mohammad Mohammad Moderated by: Dr Javed Baloch March, 2019
Assignment Description
Form a group of three students and inform your lab tutor of the names and student IDs of your group
members. Choose one (1) requirement scenario given in the list below. 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 analyse client requirements, design the 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. 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 to realise the 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 cover 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 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 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 student ID numbers of the group members, which needs to be stored on and displayed from
the created IIS (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 the implemented scenario during your week-12
lab. Individual understanding will be tested during your demonstration.
Scenarios (Choose one only for your group to work on):
Scenario 1: Local Area Network (LAN) to support Windows Server and Client Environment
Thinktank company is a Sydney based SME (Small and medium-sized enterprise). They had 10 computers in
the office when they started, now they have 50 computers, and their business is rapidly expanding. Thinktank
has planned to open up another new branch in Melbourne, and will be connected to HQ (Head Quarter) in
Sydney. They hired new staff for these branches. The new branch will have the same number of staff as it
does in Sydney. They need to buy new machines, and printers for the new branch. They also need to centralise
Authentication, Authorisation, and Data location – so it can be shared across the branches.
One more requirement is that the company want to make sure that the Finance department across the
branches have separate folders on the network that can only be accessed by them. In addition, the Sales
department need to see their respective folders only. Managers should have authority over the entire Data
folder.
MN506 System Management Page 3 of 4
Prepared by: Dr Mohammad Mohammad Moderated by: Dr Javed Baloch March, 2019
Currently, Thinktank stores all their data centrally on two machines. These are workgroup computers, but
data is shared with 28 other staff from different departments: 5 in Finance, 20 in sales, and 3 managers.
The IT staff assigning manual IP addresses to each network device, which creates lot of confusion in
maintaining records, i.e., which computer holds what IP address; and most of the time ending up with
assigning same IP address to two, or more computers that causes duplication, and disruption in network
activities.
Users are having problem in accessing central data by computer IP address as it becomes difficult to remember
server IP addresses. Thinktank intend to use internet and access resources in internet using names. Each user
needs space under the network for storing his own folders that no one else can access. Current workgroup
network model does not meet their requirements. There is no accountability in place, Thinktank also, needs
to reduce the down time for the important Enterprise Network Services by implementing the fault tolerance,
i.e., in-case a server goes down, their business should not be affected.
Thinktank looking into security policy solution for their entire network based on the industry best practices.
Based on the information given above, and the requirements of the Thinktank structure, your task is to suggest
a suitable design and present the implementation prototype with virtual machines using Oracle VirualBox Tool.
1) Choose a domain name for your organization (e.g. Adatum.com).
2) The network will be constructed as an active directory domain tree with its root domain.
3) Two Domain controller for a chosen Domain in the network for redundancy.
4) Centralised user authentication.
5) Print server for users.
6) All computers should acquire the IP addresses automatically from a server.
7) Hosting of their own website using their own server.
8) Describe how many OUs, Groups, Users and Access Levels will be created.
9) 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.
10) Provide a diagram that shows your Active Directory Domain Structure, not limited to the HQ, Branch
location, domain tree and the clients in each domain. See Figure 1: Sample Active Directory Design.
Figure 1: Sample Active Directory Design Diagram (just as an example)
MN506 System Management Page 4 of 4
Prepared by: Dr Mohammad Mohammad Moderated by: Dr Javed Baloch March, 2019
Scenario 2: Local Area Network (LAN) to support Windows Sever and Linux Client Environment
With the growing base of users of Linux, People Software, a software 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.) belong 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 3: Setting up technology/features for Linux Server and Windows Client Environment
A Canberra 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.
MN506 System Management Page 5 of 4
Prepared by: Dr Mohammad Mohammad Moderated by: Dr Javed Baloch March, 2019
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
Conclusion 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 6 of 4
Prepared by: Dr Mohammad Mohammad Moderated by: Dr Javed Baloch March, 2019

Grade
Mark
HD
>80%
DI
70%-79%
CR
60%-69%
P
50%-59%
Fail
<50%
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