Project Scenarios

Custom Scenarios: Don't see exactly the scenario your need? That doesn't mean it's not supported by SBSmigration.com, please contact pre-sales support to verify any special prerequisites or supplemental support we recommend. We can support almost any migration situation you might encounter with SBS or non-SBS platforms.
 

Your Swing It!! Kit product order includes a choice of a Project Scenario to define the scope for your project documentation and tools. You may also order a product bundle with more than one scenario provided in your Library.

Each of the Project Scenarios shown below has a "typical baseline" requirement, but also supports the variations in scope or platforms that are described.

 

Project Scenarios

Project Scenario Original Platforms (in any combination) Final Platforms (in any combination)
2008 Project Scenarios
2003 to SBS 2008
Server Platforms
  • Windows 2003 or R2
  • SBS 2003 or R2
  • Exchange 200x
  • SBS 2008 (Exchange 2007)
2003 Project Scenarios
2003 to 2003
Server Platforms
  • Windows 2003 or R2
  • SBS 2003 or R2
  • Exchange 200x
  • Windows 2003 or R2
  • SBS 2003 or R2
  • Exchange 2003
  • Exchange 2007(!)
2000 to 2003
Server Platforms
  • Windows 2000
  • SBS 2000
  • BackOffice 2000
  • Exchange 2000 or 5.x
  • Windows 2003 or R2
  • SBS 2003 or R2
  • Exchange 2003
  • Exchange 2007(!)
NT/SBS4.X to 2003
Server Platforms
  • NT 4.0
  • SBS 4.0, 4.01, 4.5
  • BackOffice 4.x
  • Exchange 5.x
  • Windows 2003 or R2
  • SBS 2003 or R2
  • Exchange 2003
  • Exchange 2007(!)

Typical Baseline

Typical Swing Process

Domain Swing

  • One or more DCs handled

Exchange Store (Options) 

  • Forklift
  • Exmerge
  • Mailbox Move if needed
Typical Criteria
  • Upgrading from original SBS 2000/2003 server to SBS 2003
  • New Server Hardware Introducing (to replace old server hardware)
  • Keep same server name, same domain name, same LAN IP
  • Retain Active Director: all Users, Groups, Computers, Group Policies
  • Any other DCs or Exchange Servers as DCs are deleted and reintroduced or can be maintained as member servers
  • No impact upon workstations, member servers
  • Construction work proceeds offline in 90% of the construction

Project Scope Variations

Same Server
Hardware
  • Typical Scenario: New Hardware Introduced
  • Alternate Scenario: Server Hardware Unchanged, Redeployed
Name and Identity
Variations
  • Rename: Server name
  • Rename: Domain name(not recommended, hasn’t been tested)
  • Rename: Exchange Organization
  • Change Server LAN IP
  • Change/add multiple Internet Domain Name & related Email addresses
Multi-Server
Variations
  • Member Servers (non-critical roles)
  • Handling Additional Existing DCs
  • Multiple Exchange Servers
  • Member Servers (critical roles)
Supported Platform
Scenarios
  • Windows Server Platforms
  • Exchange Server Platforms
  • Existing Domain Level
  • NT BDCs in AD Domain
Special Exchange
Scenarios
  • Pre-Migration Conditions
  • Post-Transition Conditions

Platform Variations

Hardware replacement Same or new hardware for final server is addressed
Virtual Server Physical or Virtual Server compatible construction path
X64 Platforms Transition from x32 to x64 platforms is addressed
Multi-server Consolidation to single or single to multi server expansion can be addressed
Windows Server Platforms Any release applies (OEM, Standard, Enterprise)
SBS Platforms May be Standard or Premium Edition on either endpoint, and even that may be changed as part of the project scope
Media Types Full Package Product, OEM, Open License, or "SBS Upgrade" retail media may be used in all cases

Exchange 2007 can be addressed in the project, but you must meet the unique product requirements to license and deploy it. Due to change in database format, you cannot Forklift an earlier version of Exchange Information Store to an Exchange 2007 server.