The document provides a summary of the project to migrate the technology infrastructure of Legg Company to the standards of Continental. Key aspects of the project included replacing desktops and laptops, modifying the network mapping and email/communication solution, and ensuring compatibility with Continental systems. Several issues arose during implementation, such as network and file access problems, delayed server setup, and lack of communication. The migration was completed through replacement of hardware, establishment of new file structures and accounts, and training of users on the new systems.

1. Continental Migration Review
1
I
Legg Company Migration after action Report
Project Name: Migration Report
Prepared by: William Baldwin
Date (MM/DD/YYYY): 03/20/2014
Version History (insertrows as needed):
Version Date
(MM/DD/YYYY)
Comments
1.0 03/20/2014 Initial creation
Contents
1. Executive Summary........................................................................................................... 2
2. Project Objectives .............................................................................................................. 2
3. Project Description............................................................................................................. 2
For each area below, provide sufficient detail to define this project adequately: ................. 2
3.1 Project Scope.................................................................................................................... 2
4. Project Milestones.............................................................................................................. 5
5. Authorizations (Modify lists as needed) ........................................................................... 6

2. Continental Migration Review
2
1. Executive Summary
Provide below a briefoverview of this project(e.g., projectpurpose and justification):
Provide an understanding of the elements necessary for the migration of the Legg Company Technology
Infrastructure to the Continental technology standards. This report is for potential assistance for other
sites for historical reference and understandings of possible items necessary for new implementation and
resolutions utilized by this site for its project completion.
2. Project Objectives
2.1 Project Description (Solution):
Implementation of Technology Infrastructure of Legg Company Inc
2.2 Business Objectives:
The overall objectives of the Migration was to modify the current technological infrastructure to a
solution acceptable to Continental standards in its day to day information technology standards:
 Implementation of new HP Desktops Laptops devices with standardized software loads and services
 Modification of current networking mapping from servers,switches, and proxy solution.
 Modification of imaging services (printers) and solutions.
 Provide customer understanding of changes of technology business processes for new environment.
 Identify legacy non-standard software requirements and problem resolution of migration effort.
 Implementation of new communicationemail software solution and retirement of existing email
environment.
3. Project Description
For each area below,provide sufficient detail to define this project adequately:
3.1 Project Scope
The current Legg Company network and computing devices are identified for replacement to the new
Continental structure. Work will include, but not be limited to:

3. Continental Migration Review
3
3. Project Description
A. Computing:
1. Identification of non-standard software on computing devices and configurations
2. Identification of computing requirements vs business requirements for employee work
requirements (hardware performancesoftware specifications)
3. Hardware replacement of computing devices, printers, as necessary.
a. Reimage of legacy hardware for resale or donation
b. Software inventory for reuse, resale,or donation
c. Ordering and placement of new devices.
d. HPAM (training) adding new devices to HPAM
e. HPSM (training)
f. Active Directory Training.
g. QIP (Training)
B. Networking:
1. User Security and account creation.
a. User accounts
b. Group accounts (Tandem with File server process)
c. Service Accounts
2. Implementation/Addition of Proxy Server (K82C201A)
a. Configuration with Contitech Admin personnel
3. Implementation/Addition of File Server (K8FS001)
a. Old server migration plan
b. Identification of files for transfer
c. File security process
d. New identified File structure
e. Cutover plan (Network Trust? / added 2nd
network card)
4. Implementation/Addition of Print Server (K8PS001)
a. Creation of print queues for network printers (print drivers)
b. Identification of direct attached devices and retirement plan (application association with
direct attached printers, legacy programs, UPS device)
5. Implementation /Addition of Domino/Lotus Notes Server (K8LC001/K8LC002)
a. Configuration with Domino team
b. Identification of storage space for new mail server
c. iNotes setup
d. Afaria (phone) ACL access with new server
e. Cutover plan (transition of mail, vendorcustomer notification, user notification, user
training, migration plan, achieving of existing mail)
f. Mail accounts requests (Individual, Group, Distribution lists)
6. Company Website
a. Contitech control of hosting and web services. Registration.
3.2 Project Completion Criteria:

4. Continental Migration Review
4
3. Project Description
Document, Design, Implementation, and Maintenance:
Document (Phase 1):
 Current Network architecture Infrastructure
 Hardware devices (Computers, Printers, Faxes, Switches, Servers, Wireless Access Points),
accessibility, and requirement
 Users accounts, access rights, roles, responsibilities
 Building layouts, device locations, power locations, network locations
Design (Phase 2)
 Modification of existing network architecture. (New cabling, channeling, plug-ins.
 Identify necessary replacement solutions for:
Computing
Printing
MFP (Multi-Function Printing)
Switches
Servers
Server room re-modification or replacement
Wireless Access Points
Network cabling
 Define new Workgroups model for data access rights and roles
 Define new File Server architecture, project groups, mailbox groups,
 Validate Network layouts, device migration plan, phase model, communication plan, mail
changeover plan
 Phone server plans, Notes mail accounts, ACL (Access Control List request prep for Notes)
Implementation (Phase 3)
 Training for personnel (Office, Administration, Production)
 Ongoing maintenance process
- Scheduling server updates
- PC updates
- Phase out of legacy technology equipment
 Communication processes (Continental – standards?)
- Intercompany communication
- Mail address change notification to vendors, distributors, retiring old mail server
- Use r ticketing or technology request process
 Physical change out of hardware (PCs, printing, switches, WAP, technology devices)
 New networking drops for potential network restructure
 Establishment of Technology responsibility list (Service groups mail, phone, contact support,
SLA)
 Establishment of T-Systems setup for network VPN connectivity to Continental and fail over.
3.3 External Dependencies:

5. Continental Migration Review
5
3. Project Description
Customer requirements and approval
External Support
- Lotus Notes Administration
- Proxy Server Administration
- T-Systems Administration
3.4 Assumptions:
3.5 Constraints:
4. Project Milestones
Estimated Schedules – List key projectmilestones relative to project start. (Insert rowsas needed)
Project Milestone Target Date
(MM/DD/YYYY)
Project Start (LTFP Phase) 08/01/2014
PC Change out 02/21/2014
Lotus Email System setup (accounts,groups established) 03/01/2012
MS Exchange Sever (Legacy) mail forwarded to new accounts 03/01/2014
Training Users on Lotus Notes Mail, Training videos, etc..
MS Exchange Server (Legacy) ports disabled (Sunsetlegacymail server) 08/29/2014
Legacy PCs wiped,sold,destroyed 06/01/2014
T-Systems Implementation
ImplementHPSMTicketing System
5. Project Issues
Identification Conflicts – List projectissues relative to projecttimeline.(Insertrows as needed)
Project Issues Target Date
(MM/DD/YYYY)
Project Start (LTFP Phase) 08/01/2014
Network lines notworking after new VPN network established 02/21/2014
File Server Security violations – Delay in permissions picked up allowing users to
access files notauthorized to them. Accounting information.
02/21/2014
File mapping ofcommon work processes were broken and new links had to be
established.
02/21/2014
Lotus Notes Server administration failed to complete prior to migration ofnetwork. 02/23/2014

6. Continental Migration Review
6
5. Project Issues
Setup redundantserver in Hungry to maintain email operations.Created overburden
Server in Hungry due to added latency.
Communication notpassed to all employees bymanagementofactivities even though
placards were posted ofevent.
02/21/2014
Legacy File Server structure in poor organization.Forced implementation ofnew
structure withoutopportunity to discuss with all state holders
02/21/2014
T-Systems Implementation was notthoroughlycommunicated to local IT and would
often have stage implementation happening with no advanced notice
02/30 – 06/30
Users adaptation to new mail system created unwanted challenges 02/21/2014
Server Trustunable to be approved requiring multiple facets ofmaintaining existing
legacy network servers and operations and processes
02/21/2014
Employees attempting to access old network file systems rather than using new
network file server creating data file integrity issues
02/30/2014
Exchange mail system was notassumed byContinental to create a proper file
forwarding process.Work around to file forwarding had to be implemented
02/21/2014
Local IT inexperienced (still learning work processes) with Continental operations and
provided insufficientresponsibilitycontactlist for conflictresolution.
02/30/2014
6. Authorizations (Modify lists as needed)
Project performance baseline changes will be approved by the:
 William Baldwin
 Jan Faerber
Project deliverableswill be approved/accepted by the:
 William Baldwin