April 22, 2003

The meeting was called to order by John Melo at 8:30 a.m. Those in attendance were:

· Jesse Luckhardt from server group.
· Brian McGarry from Router group.
· Roland Atkinson from Communications Services.
· Shawn Denny from Security group.
· Maxine Werner from Clients group.

Brian McGarry suggested and John agreed that all documentation to be put on the share file on WC106-00 so the data is not lost.

John requested status reports from all the groups as to what is completed:

Server:
· Has created an IP Plan
· Is co-ordinating with communications group in regards to email and web servers
· Is starting RIS server trials

Router:

· Has created Router rules
· Has basic IP plan

Communication Services:

· Creation of web pages
· Email planning

Clients:

· Doing application installations(trial)
· Using RIS clients
· Using RI Prep to do push down

Security:

· Working pol templates and testing settings
· Have routers/ servers name scheme
· Have workstation name scheme
· Narrowing IDS probably using SNORT

John then requested what issues/questions groups have:

Router:

· Where are the servers located
· Total number of servers

 

Communication services:

· What is the domain name being used.
· DNS pointers
· Who is doing DNS in DMZ

Clients:

· Domain Name
· RIS server IP
· Hostname

Note: At 11:00 a.m. a memo from security group was sent to all team leaders in regards to naming conventions.

Server location: Edmonton:

Adtran
Router
· exchange/Web
· DC/DHCP/DNS
· File and Prints/ RIS {F/P/R}

Router

· Web/RAS-DNS forwarder

Router
Internet

 

 

Server location: Calgary and Winnipeg

Adtran
Router
· Exchange/Web
· DC/DHCP/DNS
· F/P/R

Router

Router
Internet

Total Servers: 10
Domain Name: SPACEBOUND.NRU
ADDENUM: John informed the team leads that at this time there are no email servers in the DMZ.

 

Things to do:

Location- Where are the servers to be located to be done by Security and Server group.
Access List - Security to hand over to Routing group
Active Directory- To be done by Security and Server Group
Net meeting- is for EXECUTIVES only!!
RAS server- to be handled by the Routing Group
Exchange/web updates- how often to be done by Communication Group
Security to do all naming conventions
Server group to create image to help client
Clients to create basic desktop to push down
then via policy stop gap any holes

Possibilties: (things that might be done in phase 3)

· Segregation of DHCP
· Mirror Webs
· Web Cams
· Proxy server with content filter

-------

April 24, 2003

Project Team Leads Meeting

The meeting was called to order by Ralph Worgul, at 8:30 a.m. Those in attendance were:

· Liana Skribis from Server group
· Brian McGarry from Router group
· Roland Atkinson from Communications Services
· Shawn Denny & Ruth Hansen-Taylor from Security group
· Maxine Werner from Clients group
· Karla Ramdeen - Recorder

Each team provided the following status updates:

SERVER TEAM

· Has setup RIS for Advanced Server Server deployment but is having problem pushing the image down to the Servers
· RIS Server will be required in each city, could use File/Print Server to do this
· All Servers to be promoted to Domain Controllers by Friday April 25th
· Question was raised about the Lab layout - How is the Lab going to be broken down in relation to our site topologies
· Updated Network Diagram distributed to each team

TASKS

· Install a Domain Controller in the Edmonton site by 1:15 p.m. April 24, 2003
· Install a Domain Controller in Winnipeg by 3:00 p.m. April 24, 2003

ROUTER TEAM

· Routers are up and communications is being tested for Edmonton
· Encountering problems with routing using IGRP for a specific city
· Determine if Switches are VLAN compatible

TASKS

· Communications between cities (sites) using Wan Link to be completed by 9:00 a.m. April 25 2003 (1st priority)
· Investigate the possibility of setting up VLAN's using Switches, to be completed by 1:00 p.m. April 24, 2003 (2nd priority)

COMMUNICATION SERVICES TEAM

· Basic external Web Page completed, still need to refine and add content
· Question raised regarding who will configure RAS. Brian agreed that the Router team would accept responsibility for this task.

TASKS

· Install first Exchange Server (Edmonton) by 4:15 p.m. April 24, 2003

CLIENT TEAM

· Encountering Riprep problems, configured a client computer but getting error message
· GPO's for clients completed

TASKS

· Ralph to assist team with resolving problem
· RIS image completed and deployed by 12:00 p.m. April 24, 2003.
· Client team to assist with Active Directory - building OU's and Users for Edmonton, to be completed by 10:00 a.m. April 25, 2003

SECURITY TEAM

· GPO's and Security Templates for workstations are completed
· Naming conventions for clients are completed

TASKS

· Investigate the possibility of using PGP for encryption, to be completed by 1:00 p.m. April 24, 2003
· Create dial-up policies, to be completed by 1:00 p.m. April 24, 2003
· Investigate software, to be completed by 1:00 p.m. April 24, 2003

Ralph reviewed the Network Layout Diagram as it relates to the Lab Layout. All in agreement with the Layout of the Network in the Lab:

Next meeting to be held at 2:00 p.m. April 24, 2003

----------

Meeting April 25, 2003

Time 8:25-8:50

Completed so far

Router Team
-Connectivity in city

Client Team
-Ris image
-DC in Edmonton

Server Team
-DC Edm- DHCP-DNS
-File+Print, Ris server

Security Team
-Creating VPN Servers

Communications Team
-Exchange in Edm

Things to be done

Router Team
-Wan by 12pm
- select an member to install Linux with a print server
Client Team
-Demo from HELL at 10:00am
-GPO's done by 4pm

Server Team
-All DC's in place by 2pm
-All other servers done by 4pm

Security Team
-VPN between cities by 4pm

Communication Team
-Exchange in all cities by 4pm

EVERYTHING HAS TO BE COMPLETED BY MONDAY @ 3pm
On each monitor there should be a description of the:
-Machine Name
-Function
-City
-IP address

*** Quick meeting today after lunch at 1:15 to see where the groups are****

***Phase 3*** scheduled to start on Tuesday April 29th, 2003

---

April 29, 2003 Minutes from 8:15am meeting

Objectives for Phase 3:

Server Team:
· Research hardware requirements
· Which DC to upgrade
· Research operation master and exchange

Communications Team:
· Install Netmeeting, Webcam
· Do research on deployment of the above
· Research server hardware and protocol requirements
· Research client hardware and protocol requirements
· Research authentication and security requirements
· Router considerations

Client Team:
· Terminal services
· Research Office Suite deployment
· Who, what, where, when and how

Security:
· Research on C.A. (Certificate Authority)
· Research IDS (Intrusion Detection System), example SNORT, or other similar programs
· CA, what are they used for, e-mail, internal or IPSEC

TEST BED for WINDOWS 2003 and PHASE 3

Considerations:

· Use a separate room with a number of machines to do deployment, will discuss at 11:00am meeting, for probable deployment between 1:00pm and 2:00pm today.
· Need to know how many machines needed
· Which applications to use, example: RIS, Exchange

John Melo's comments:

We have done a very good job implementing this project, and we are ahead of were other previous classes have been. Instructors are impressed. Consideration is being done for a presentation on our project on Friday to Telecom instructors, this will be discussed further at 11:00am meeting.

---

April 29, 2003 Minutes from 10:30am update meeting

Update:

Server Team:
· Hardware requirements:
· 550 mhz
· 256
· 4 gig
· Exchange 2000 requires service pack 3

Communications Team:
· Same requirements as above
· Protocol requirements are TCP/IP, Winsock, H323
· Deploy Netmeeting
· Deploy server software, answer file, IIS installed on second partition
· User list

Client Team:
· Terminal services requires Windows 2003
· Requires port 2504 on member server

Security:
· CA used for E-mail, Exchange and Netmeeting
· Not external
· CA to be Enterprise

TEST BED for WINDOWS 2003 and PHASE 3

Configuration:

· DC - 3 machines, Edmonton, Calgary, Winipeg
· Client machine - 2
· Terminal Services - 1
· Member server for Exchange - 1
· CA servers - 2
· IDS - 1
· Netmeeting - 1
· Total - 11 machines

Sequence of Installation:

I Install
· 9 servers
· 2 clients
· Complete by 1:30 pm

II 3 Domain Controllers
· Edmonton plus other 2 DC's
· Complete by 3:00 pm

III Exchange, CA installation, Office for Terminal Services
· 4:00 pm target
· 12:00 pm Wednesday April 30 approximate testing time

-----