Project Description

 

Overview

Each student will create a, organized, technical solutin given the described below. The submission will be in a format, at diagram, and may include diagrams, charts or tables. The assignment is meant students to their mastery of the and to provide a and realistic way in which to apply knowledge from course.

Scenario

Overall Advertising, Inc. (alluded to as "WAI") has enlisted you as an IT specialist. WAI is another publicizing firm, and they are at present procuring staff, building up two areas, and have a need to get their inward IT administrations designed. They don't yet have an IT staff, however when they do, the IT staff will assume control over all parts of IT organization. You are required to supply WAI with an answer which depicts the execution and setup of their center IT administrations. Expense is not a critical concern – WAI wishes to execute the "right" answer for fit their needs now and for the following 2-3 years.

 

 There are a few insights about WAI which will affect your decisions:

 

WAI will begin with 30 representatives, in the accompanying offices:

 

o Executives (3 representatives) – oversee and run the organization

 

o Accounts and Sales Department (5 representatives) – perform statistical surveying and look after records

 

o Creative, Media and Production Department (15 representatives) – publicizing

 

o Human Resources and Finances (4 representatives) – perform HR and money related obligations

 

o IT (3 representatives) – oversee IT for the organization

 

WAI will have two locales, one in Los Angeles and one in New York. Most staff will be situated in LA, with no less than 1 individual from each of the offices above situated in NY.

 

Organizing gear is as of now set up for both locales. A protected passage (utilizing IPSec) will be built up between the two destinations so that between website movement will be safely burrowed over the Internet. You may make whatever different presumptions you wish about intra-and between site network.

 

Security components (e.g., firewalls, interruption recognition) will be taken care of independently, and there is no compelling reason to portray them.

 

A few offices will need their information to stay private from different offices (e.g., Finances work force won't need Production staff to see the organization's money related points of interest). Your group may make suppositions about how information ought to be shared or kept private.

 

Suppositions can be made with respect to any data excluded here; all presumptions ought to be distinguished, be that as it may.

 

Points to Cover

 

Your archive ought to cover the substance displayed in the course. The blueprint beneath contains prescribed focuses to cover. You are allowed to include other related data.

 

Portray the specialized and business purposes behind every decision, refering to different assets as proper.

 

Provide rough estimates of and manpower required for your solution. You may summarize schedule and manpower at the end of the or individually for each section.

 

The Windows Server 2008/2008R2 operating system should be used for all aspects of the solution.

The topics include:

Sending and Server Editions

 

What number of servers aggregate are required? Which parts will be consolidated?

 

What release of Windows Server will be utilized for every server (e.g., Standard, Enterprise, Web)?

 

Will Server Core be utilized on any servers?

 

What number of desktops are required and what OS will they run?

 

Where are each of the servers found (which of the two locales)?

 

By what method will the servers be sent?

 

In the case of utilizing answer records, what settings will be arranged with the System Image Manager?

 

DNS and DHCP

 

DHCP scope outline (e.g., lease times, number of extensions, location range)

 

Will a type of DHCP adaptation to non-critical failure be executed?

 

Will DHCP reservations be utilized for servers?

 

DNS namespace outline (e.g., space name(s) picked, split DNS for Internet/intranet, zones)

 

In what capacity will DNS be taken care of for the second site?

 

Dynamic Directory

 

Number of AD spaces (see p. 103 in reading material) and names of areas

 

Will there be any Read-Only Domain Controllers?

 

In what capacity will the second site element into space controller position? In what manner will AD locales be arranged?

 

In what manner will AD hierarchical units be sorted out (considering how gather arrangement will be utilized and clients will be composed)?

 

What gatherings will probably be required at first (counting bunch extension and sort, p. 96 of reading material)?

 

Application Services

 

By what method will applications be conveyed? In the case of utilizing Group Policy, what are the points of interest on how Group Policy will be utilized to convey the product? Which programming applications will probably be required?

 

In what manner will an Internet-confronting site conceivable?

 

Record and Printer Sharing

 

What shares may be required? (Consider a portion of the thinking supplied on p. 161 of the reading material)

 

By what means will quantities/FSRM be designed? (Consider all viewpoints, for example, limits, alarming, record screens, and reporting.)

 

Will a DFS namespace be executed?

 

Capacity

 

On the majority of the servers, by what method will neighborhood plates be arranged? (Consider Windows volume types,RAID levels, plate sorts, and parcel table organizations on p.216-222 of the course book.)

 

In what manner will mass stockpiling, (for example, for record shares) be taken care of? (Consider the utilization of direct-attachedstorage, a SAN or NAS, as portrayed on p.214-216 of the course reading.)

 

What are harsh appraisals for the measure of capacity required?

 

In the case of utilizing a SAN, will iSCSI or Fiber Channel be utilized? What programming is required for running/dealing with the SAN (from the Windows Server side)? In what manner will the SAN be designed?

 

Assignment Requirements

There are specific requirements for the assignment: The final submission should contain at least 10 pages’ worth of text written by the student (not counting title page, images, diagrams, tables, or quotations), but may be longer, not to exceed approximately 15 pages’ worth of student-supplied text. (With the required diagram, and other images, title page, etc., the final submission may end up being more than 10 pages in length.) It must be double-spaced, have 1-inch margins, and use 12-point Times New Roman or 10-point Arial/Helvetica font. A title page is required; APA format for the title page is optional.

At least one diagram must be included (not counted towards the minimum length described above); this could be a diagram describing Active Directory components, storage layout, DHCP/DNS design, file share hierarchy, or anything else that is worth displaying graphically to enhance the reader’s understanding of the proposal. Additional diagrams, images, or tables are welcome.

The submission must cover all of the 6 major topics outlined above. Each choice should be explained with technical and business reasoning. The solution should be reasonably detailed. The Windows Server 2008/2008R2 OS must be leveraged for the solution. Rough manpower and scheduling requirements for each topic (or a summary of manpower and schedule at the end of the document) must be included. Additional topics may be covered as desired.

The structure of the final submission is flexible. There is no specific format required, although it should be organized logically and represent a single, unified solution. It is likely that the format will include separate sections for each of the 6 topics required, as well as a summary.

At least one non-textbook, non-LabSim, non-Wikipedia reference is required; preferably, this would be a “best practice” guide or similar content from Microsoft or an experienced provider of Microsoft solutions.

Be sure to properly quote or cite any sources used. APA format is required for in-text citations and the list of works cited at the end. It is expected that you are already familiar with UMUC's "Policy on Academic Dishonesty and Plagiarism." It is available in the Academic Policies section of the Syllabus; there are also links in the Webliography. In its simplest form, if you are using text from a source, you must cite and/or quote it. If plagiarism is found, then there will be a penalty to the grade.

 

 

Grading Criteria

 

The assignment is 15% of your grade, following this point distribution:

 

Points Possible	Criteria	How to earn full points
15	Design and Accuracy	- Design choices are explained and are reasonable - Technical information is reasonably accurate - Any specific technical information is based on research/textbook as appropriate - Assumptions are identified/described - The overall design is “unified” (limited inconsistencies) - Explanation of business/technical reasons for decisions provided
10	Topic Coverage, Level of Detail	- All of the topics are addressed to a reasonable depth - The paper includes a sufficient level of technical detail - Paper provides manpower/scheduling estimates
10	Organization, Quality of Writing, Grammar and Spelling	- Submission is organized logically - Ideas are presented coherently - Writing style is appropriate - There are very few errors in grammar or spelling
8	Paper Requirements	- Formatting requirements met - Paper length requirements met - At least one diagram used - Title page provided
7	Citations and Quatations	- Any external sources were cited/quoted - Citations and quotations used appropriately - APA format followed properly for citations - At least one non-textbook, non-LabSim, non-Wikipedia resource referenced