Implementation of a new Active Directory environment based on alternative domain name and migrate all objects within existing Active Directory environment to the newly established domain.

The following represents the scope of the work to be performed.

1) Perform an examination of the existing Microsoft Active Directory and Office 365 environments as it relates to the current configuration.  This will include reviewing the current Active Directory structure including DNS, WINS, DHCP, current Office 365 integration

2) Create a design and implementation plan that meets the business needs of CLIENT and will function properly within the existing network topology.

3) Conduct a thorough review of the recommended design and implementation plan with the IT staff at CLIENT and modifications made to the design and plan if deemed necessary.

4) Perform the implementation of the design and implementation plan laid out in activity #2.  At a high level and based upon preliminary design considerations (subject to change during deliverable #2) the work to be performed at each location will include but is not limited to:

·      Microsoft Assessment and Planning toolkit components that we determine will provide useful information to assist with the creation of the design architecture and implementation & migration plan.

• Active Directory Topology Diagrammer or similar tools to gather detailed outlines of all Active Directory components to be leveraged while creating the design architecture and implementation & migration plan.
• PowerShell scripts to gather environmental reports from various systems as needed to create the design architecture and implementation & migration plan.
• Install and configure a new CLIENT, Inc. Corporate on premise Active Directory Domain Controller(s) at the location.
• Build new redundant DNS, DHCP, WINS (if needed) services within the new Active Directory domain.
• Install and configure the migration tools that will be leveraged during this engagement as per the design.  (this could be ADMT, Quest AD Migrator\migration tools, etc.)
• Execute simulated migrations of all computer, user, server, etc. Active Directory objects between the existing and new domains.
• Provide the IT staff at each location a list of all objects that failed during the simulations and request that the local IT staff determine which of those objects no longer exist and can be cleaned up from the domain.  The remainder of failed objects that do still exist will need to be addressed individually to determine the cause of migration failure.
• Execute the domain migration process using the tools previously configured and migrate all computer, user, server, etc. objects to the CLIENT Corporate domain.

 5)        Testing of all modifications to the environment at the location.

 The following outline will be the framework we use to successfully complete the migrations.  Please note the details of the individual steps in this outline may change due to additional information or to avoid interfering with day-to-day business operations.  The Quest migrations will be performed in this order:

 ·        Active Directory user, group, and computer objects & Office 365 end user mapping.

o   The user and group objects will be active in both domains.  This is so that users can log into resources in both domains during a co-existence period.

o   The computer objects will only be active in one domain.

·        Workstations

o   Workstations are migrated next because this allows Quest to set up permissions for both domains on the workstation.  This typically makes the server migrations easier because we do not have to reconfigure the workstations a second time when servers are migrated.

·        Servers

o   Servers are migrated last because they have the most impact on day-to-day operations.  Rebooting the servers usually requires advance scheduling to minimize the impact on the users.  This stage can stretch out because of scheduling issues.