Reference no: EM132309168 , Length: word count : 2000

Assignment

Learning Outcomes

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

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.

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).

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.

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.