Traditional SBS Upgrades
Comparisons apply to typical Windows & SBS 2000/2003 Domains, and with Exchange
Scratch Install
(Reinstall server/domain from scratch as clean install to new domain)
Abandons the domain accounts and configurations Workstation profiles for users are abandoned, require transition at every station All settings and preferences are recreated from scratch No specific solution provided for maintaining security preference in data, or Exchange configuration, Group Policies, Security Groups, and similar items Essentially this implies significant work at all workstations, all servers, replacement of any other DCs, in addition to the server
In-Place Upgrade
(install over the current installation)
Puts the production server at risk with interactively performed live transfers Doesn’t directly support change of hardware Requires preliminary clean-up of current server prior to install Fails to provide a clean server configuration
Microsoft ADMT Method
Requires rename of server, domain, and therefore all namespace paths are broken including shortcuts, printer connections to the SBS, URLs in the LAN Extensive interaction required between the production domain and the new SBS under construction, including modifications to the existing SBS configuration Requires hardware replacement Requires substantial recreation of server configuration Unfamiliar tools required that essentially have no particular value for any other situation other than a migration Result is not identical to what results in a scratch installation of Active Directory