Get Out Of Dodge–Migration Resources



As part of the TechEd Session I did at TechEd NorthAmerica with all of its video Switcher issues AND to keep the resources flowing on this topic – I have put together this resource blog post including embedded video screencasts of each of the demos. The original presentation pace was fast (too fast) – so here you can grab a Pint / Coffee and watch the demos at your leisure.

TechEd New Zealand and TechEd Australia – here’s dome demo love for you too.

SlideShow on SlideShare.Net

Demo 1 – Migration Tools install

Demo 2 – Active Directory Migration (link to AD Migration Session)

Demo 3 – DHCP Migration

Demo 4 – Print Server Migration

Demo 5 – File Server Migration

Demo 6 – Certificate Server Migration

Additional Resource Links to Migration Guides.

About author View all posts


6 CommentsLeave a comment

  • Hi,
    is there another place where I can watch the videos? Youtube told me a second ago that the uploader closed his youtube-account and the vids are not longer available.


    • Thanks for the comment – looks like I had some issues with an account reset. I actually blogged about it, but that’s annother story. The videos have been re-uploaded and I’ve embedded the new links into the original post.

  • Great Videos! You mention there are switches to change the listening port from tcp/udp 7000 to a custom port. What are the switches for changing the listening port?


  • Hi Rick:

    May I know is the user’s PC connected to the printer via UNC path or IP after the migration?

    The problem I have I my company is planning to migrate the print server from server 2003 to server 2008, where server 2008 will have a different VLAN and also new VLAN for printers.

    The way we assign IP to printer’s are via DHCP, where we map the MAC of the printer to a reserved IP range of the DHCP. Would it work for the user’s without remove and re-add the printer after the migration?

    Thanks and hope to hear from you soom


    • Hey @joe,

      The printer in the user profile is associated with whatever UNC name you used when mapping it. If you mapped it to serverprinter, it will stay as serverprinter. How you handle the migration on the server side is really just about getting the shares, drivers and settings migrated. You need to take the old server “offline” and assume the name of the old server to the new server.

      I hope this helps!

      • Hi Rick:

        Many thanks for taking your valuable time to reply my question.

        “ou need to take the old server “offline” and assume the name of the old server to the new server.” Do you mean I have to use the same hostnameFQDN of old print server to the new print server?the server name has to be identical?


Warning: sizeof(): Parameter must be an array or an object that implements Countable in D:\home\site\wwwroot\wp-content\plugins\projectnami-blob-cache\project-nami-blob-cache.php on line 416

Fatal error: Uncaught WindowsAzure\Common\ServiceException: Fail: Code: 400 Value: The account being accessed does not support http. details (if any): <?xml version="1.0" encoding="utf-8"?><Error><Code>AccountRequiresHttps</Code><Message>The account being accessed does not support http. RequestId:0ec8c057-501e-0065-2f19-6a0be1000000 Time:2022-05-17T18:14:10.1192313Z</Message><AccountName>ritgcache</AccountName></Error>. in D:\home\site\wwwroot\wp-content\plugins\projectnami-blob-cache\library\WindowsAzure\Common\Internal\Http\HttpClient.php:382 Stack trace: #0 D:\home\site\wwwroot\wp-content\plugins\projectnami-blob-cache\library\WindowsAzure\Common\Internal\Http\HttpClient.php(275): WindowsAzure\Common\Internal\Http\HttpClient::throwIfError(400, 'The account bei...', '\xEF\xBB\xBF<?xml versio...', Array) #1 D:\home\site\wwwroot\wp-content\plugins\projectnami-blob-cache\library\WindowsAzure\Common\Internal\RestProxy.php(141): WindowsAzure\Common\Internal\Http\HttpClient->send(Array, Object(WindowsAzure\Common\Internal\ in D:\home\site\wwwroot\wp-content\plugins\projectnami-blob-cache\library\WindowsAzure\Common\Internal\Http\HttpClient.php on line 382