The Good, the Bad, the Ugly of Migrating to 2008 Platforms Jeff Middleton

2008 Platforms Options Windows 2008 SBS 2008 EBS 2008

SMB Scale Deployments

SBS 2003: Service-Rich Product Suite Windows Domain Controller Exchange Server Fax / Print & File Server Sharepoint Server / Collaboration Remote Web Workplace Automated Deployment and Management Tools Monitoring and Remote Management Extremely nice OS & CALs price point

SBS 2008: Service-Rich Product Suite Windows Domain Controller Exchange Server Fax / Print & File Server Sharepoint Server / Collaboration Remote Web Workplace Automated Deployment and Management Tools Monitoring and Remote Management Extremely nice OS & CALs price point

SBS 2008 Platform Changes X64 Hardware Hyper-V Virtual Machines SBS Image Based Backup Extended familiar concepts: RWW, etc Multi-Server SKU for SBS Plus…Everything else that is Different

SBS & EBS Clients/Servers 1 or 2 Servers - SBS 2008 –SBS Standard: 1 Server –SBS Premium: Standard + add 1 Windows Server + SQL Server –Client Stations/Users: 1-75 CALs 3 or 4 Servers - EBS 2008 –EBS Standard: 3 Servers –EBS Premium: Standard + add 1 Windows Server + SQL Server –Client Stations/Users: CALs

1,2,3 or 4 Server Solutions

Server Expansion Limits??

SBS & EBS Solutions Roles Matrix

How has Microsoft addressed Migration to date? Migration is not their best subject/product –SBS 4.0 through SBS 2000 –In-Place Upgrades –ADMT –OEM Preinstall –Transition Pack

SBS 2003 Upgrades: Business Continuity and Optimization Issues In-Place Upgrade –Hardware upgrade – Not good option for new –Inconsistent deployment – Sometimes a complex process –Difficult to troubleshoot – Dirty server conditions ADMT Upgrade –Server-Down Method – Disrupts Operations –Domain Name Change – Unfriendly to Customer Values –Server Name Change – Breaks Namespace, shares, scripts, shortcuts –Mailbox Move – Breaks Single-Instance Storage –Modifies Old Server – Requires DR Preparations –Workstation Migration – Requires touch at each desk –Client/Server Applications – May cause more issues New Domain Installation (including 15 Min. OEM Setup) –Abandon Domain – Breaks SIDs, Group Policies, Security Groups –Mailbox Move – Breaks Single-Instance Storage –Workstation Migration – Requires touch at each desk –User Profile Breaks – Familiar Desktop conditions lost –Transition – Messy on-site deployment looks bad to customer –Clean Start? – Doesnt look that way to customer at workstations

How Will Microsoft Support Migration? SBS 2008 has two setup options now –Join to Domain: The ANSWER file –New Install Both install as a packaged image –No in-place Upgrade, no pause install –No repair or component install

How Will SBSmigration Support Migration? Swing for 2008: Yes Join to domain: Yes Multi-Server: Yes

Why call it the Swing Method?

Phase 1 Phase 2 Phase 3 Phase 4 Phase 5 Swing Migration: Step Summary ResumeProduction ProductionOnline TransitionShutdown

Results Consistent to all variations of Swing Migration with New Hardware Same Domain Name (and SIDs) Same Server Name and IP Same Information Store intact No Impact to Workstations or User profiles Business online during construction Work offsite and/or offline, open timeline Nothing to undo migration in progress

Questions? Jeff Middleton

SBS 2008 – Two Editions Standard vs Premium (2 nd Server)

Windows Essential Business Server 2008 Standard vs Premium (Add 1 Server)

DC + SCEISA + Exch Internet Firewall? DC + Exch SBSSBS EBSEBS standardpremium