SBS 2003 to 2008 Migration Best Practices Post Has Been Updated

SBS 2003 to 2008 Migration Best Practices Post Has Been Updated

  • Comments 3
  • Likes

We have updated the SBS 2003 to SBS 2008 Migration Best Practices blog post with a few new recommendations.  Please review the following post before attempting an SBS 2003 to 2008 migration: SBS 2008 Migrations from SBS 2003 – Keys to Success

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
Comments
  • Also, useful tips:

    - Make sure you uncheck "Run unattended" when generating the answer file.

    - Burn the answer file to a CD and just use that, getting various servers to see the USB drive is a pain.

    - You'll know if you're in migration mode after the first reboot. (The documentation is not clear on this.) Don't soldier on if you don't see the migration mode text like I did, because once you realize that you're not in migration mode after all, it's already too late and you have to start the install all over again.

    - Make sure you make the partition larger than 60 GB. It's in the minimum requirements, but coming from SBS 2003 I was surprised at how large the system partition actually needed to be.

    (For migration, I don't understand why setup couldn't have just had two radio buttons "Is this a new install or a migration?" instead of this answer file nonsense.)

  • I am following the ms whitepaper and reviewed the migration post but at the point where the target server is running dcpromo and joining the existing domain I this in the log file

    ------

    [1808] 090707.100922.3906: Task: Running Task("ChangeComputerName") with TaskProcessor("NET").

    [1808] 090707.100922.4062: Task: Beginning of task ChangeComputerNameTask

    [1808] 090707.100922.4218: Task: Changed the computer name to SERVER

    [1808] 090707.100922.4218: Task: In Task ChangeComputerName:

    [1808] 090707.100922.4218: Setup: Task ChangeComputerName succeeded.

    [1808] 090707.100922.4218: Task: End of Task ChangeComputerNameTask

    [1808] 090707.100922.4218: Task: Task ("ChangeComputerName") execution complete.

    [1808] 090707.100922.4531: Task: Running Task("DcPromo_JoinDomain") with TaskProcessor("NET").

    [1808] 090707.100922.7500: Task: The password required field has been set successfully

    [1808] 090707.100922.7500: Task: dcpromo will be called with args: /unattend:"C:\Users\Administrator\AppData\Local\Temp\tmp48D6.tmp"

    [1808] 090707.100932.5000: Task: dcpromo returned ExitRidMasterOffline (89)

    [1808] 090707.100932.5000: Task: Error: DCPromo failed. You can find the output of dcpromo at "C:\Program Files\Windows Small Business Server\Logs\DCPromo_090707.100922.log"

    [1808] 090707.100932.5312: Task: Deleted the secure registry key.

    [1808] 090707.100932.5312: Task: In Task DcPromo_JoinDomain: The server was not promoted to a domain controller.

    [1808] 090707.100932.5312: TaskManagement: In TaskScheduler.ReportStatus(): Task("DcPromo_JoinDomain") requested the engine stop processing Tasks!  Completed=True, Success=False

    ---

    Summary: the server was not promoted to a domain controller

    I have got this 3 times now.

    Am I missing something?

  • I painstakingly checked the SBS2003 system with dcdiag, netdiag, SBS BPA and Exchange BPA. Still the migration wizard has twice failed. Endlessly restoring the AD and rerunning the wizard is not practical. The wizard needs a 'pick up from where it failed last time' option.