FINAL PROJECT NETWORK ADMIN - 28/04/2018 15:28 EDT

PROJECT SCENARIO Orange Creek, Inc., a Fortune 500 company, has moved into Lexington and is requesting bids for implementing a network infrastructure for their banking software company. The primary function of the new building is to provide office space for software development and testing of their homegrown banking software. Both levels of the building are dedicated to development, test, on-site IT staff, management, and administration. Location: -Single structure consisting of two levels -Each level has 75-100 employees, with enough real estate to seat 180 employees. -80% of employees reside between two lab rooms (development/test), and 20% have offices. -Each lab consists of cubicles for each employee with associated VoIP telephones. -Tiled floors and drop ceilings Infrastructure Requirements: -Each floor requires five “servers” for development and test. One floor must contain two additional “servers” to serve as a QA environment. -The corporate backbone must have a robust email server, along with LDAP authentication and Active Directory permission for intranet sites. -The network must be speedy enough to accommodate large spikes of Web traffic. Success Criteria: -The implementation is cost-effective—as always, as cheap as possible while meeting needs. -Use quality hardware. Be prepared to explain why choices were made. -The deliverables are completed (Network Infrastructure Schematic, Server Configuration [with Active Directory Schema], Client Configuration). Things to Consider: -Data recovery hardware and software -Network latency -Hardware and software theft -Security (workstations and infrastructure) -Hardware implementation vs. employee needs -Growth expectations -Electricity costs and cooling costs -Orange Creek's required overhead to manage system Network Infrastructure Schematic: This document should be constructed in Visio and detail each piece of equipment with its name and a list of any major characteristics (e.g., Active Directory Server, Exchange, etc.), IP addresses, and how it’s interconnected to other devices. Server Configuration: This documentation is specific as to how the server is built and configured, along with challenges and solutions. Items to include consist of, but are not limited to: domain name, IP Address, Active Directory Schema, User accounts, Passwords, Service Pack, Services, Group Policy settings, Security settings, Shared Folders, etc. Essentially, if the server needed to be rebuilt from scratch, how would another person complete this task and configure it for the same network? Active Directory Schema: This schematic should include the contents, attributes, classes, and structure of the Active Directory. Example items to include are: forest, domain, containers, OUs, etc. Client Configuration: This documentation is specific as to how the server is built and configured, along with challenges and solutions. Items to include consist of, but are not limited to: IP Addresses, Local User Accounts, Administrative and Local accounts/passwords, how to connect to printers, etc. Essentially, if the client needed to be rebuilt from scratch, how would another person complete this task and configure it for the same network?