My Question? How do I interconnect and reengineer my network.
The organization has decided to upgrade the existing network operating system from their corporate office in Boston to their other two offices in Phoenix and also one office in Los Angeles to a newer, more robust, efficient NOS. A re-engineering of the current NOS to a more secure, manageable platform for current and future network requirements is necessary to achieve the networking capabilities we shall discuss in our recommendation for a network re-infrastructure. Justification for this proposal will be outlined with the following considerations of productivity, cost effectiveness, network systems compatibility, total cost of ownership, and competitive advantage.
Currently, the existing organizational network structure consists of the following architecture:
- Corporate office located in Boston with 100 employees/users
- Phoenix office has 50 employees and Los Angeles office has 50 employees
- Organization is 80% paperless – data is electronically transferred
- Eleven departments have an intranet site using one in-house IIS Server
which is frequently updated at/for each location
- Clients/users operating environment are a mixture of Windows 98 (25%),
NT Workstation (75%), and Windows 2000 (25%)
- Two Servers are located in Boston, two Servers in Phoenix, and one Server in
Los Angeles – the current NOS for each location is Novell 3.12
- Email is cc:Mail; Productivity applications are MS Office and Lotus Notes
- Organization has data on a legacy system (IBM Mainframe and database is
DB2) located at terminal site in Boston
- Current hardware LAN interconnection equipment are Terminal Server for
for remote access to each site, and Unix HP K220 running 10.x for
programmers to connect thru x-windows
- Browsers are all Netscape; all users are envisioned to connect to the intranet via
the LAN pipe with T1 cable connection to and from each site
- Cisco 2600 Routers connect each site with three to four switches at each site
- One SQL database on a SQL Server at Boston terminal for all departments/users
- Each location has its own IP with Network Address Translation
II. Recommendations
1. NOS-Windows 2003 Server
TCP / IP will be the only network protocol
Three Active Directory domain controllers will handle one domain[Windows 2000]
TN 3270 terminal programs will be used for Mainframe access
cc:Mail will be phased out in favor for Lotus Notes
All Clients will be upgraded to Windows 2000 Professional
All browsers will be Internet Explorer 6.0
The organization has decided to upgrade the existing network operating system from their corporate office in Boston to their other two offices in Phoenix and also one office in Los Angeles to a newer, more robust, efficient NOS. A re-engineering of the current NOS to a more secure, manageable platform for current and future network requirements is necessary to achieve the networking capabilities we shall discuss in our recommendation for a network re-infrastructure. Justification for this proposal will be outlined with the following considerations of productivity, cost effectiveness, network systems compatibility, total cost of ownership, and competitive advantage.
Currently, the existing organizational network structure consists of the following architecture:
- Corporate office located in Boston with 100 employees/users
- Phoenix office has 50 employees and Los Angeles office has 50 employees
- Organization is 80% paperless – data is electronically transferred
- Eleven departments have an intranet site using one in-house IIS Server
which is frequently updated at/for each location
- Clients/users operating environment are a mixture of Windows 98 (25%),
NT Workstation (75%), and Windows 2000 (25%)
- Two Servers are located in Boston, two Servers in Phoenix, and one Server in
Los Angeles – the current NOS for each location is Novell 3.12
- Email is cc:Mail; Productivity applications are MS Office and Lotus Notes
- Organization has data on a legacy system (IBM Mainframe and database is
DB2) located at terminal site in Boston
- Current hardware LAN interconnection equipment are Terminal Server for
for remote access to each site, and Unix HP K220 running 10.x for
programmers to connect thru x-windows
- Browsers are all Netscape; all users are envisioned to connect to the intranet via
the LAN pipe with T1 cable connection to and from each site
- Cisco 2600 Routers connect each site with three to four switches at each site
- One SQL database on a SQL Server at Boston terminal for all departments/users
- Each location has its own IP with Network Address Translation
II. Recommendations
1. NOS-Windows 2003 Server
TCP / IP will be the only network protocol
Three Active Directory domain controllers will handle one domain[Windows 2000]
TN 3270 terminal programs will be used for Mainframe access
cc:Mail will be phased out in favor for Lotus Notes
All Clients will be upgraded to Windows 2000 Professional
All browsers will be Internet Explorer 6.0