Re: SBS Migrations



But keep in mind that new installations means that profiles get horked, icons moved.

This post is a bit interesting. Because quite frankly the "kit" ... it's plain old active directory migration information. That's it. There's no magic here. You could piece it together yourself from MS KB's in fact.

The "kit" and value comes from Jeff holding you hand.

It teaches you in the process what active directory is all about.

Is it worth it for a small firm where there's one or two workstations? Maybe not.

Your money here is spent on the support value. Not the kit.

Recognize it for what it is.

Iakov wrote:
There are many queries about how to migrate one or more components of SBS from point A to B. A very common response to them is "sbsmigration.com." That kit is good, which is why people recommend it, however, it is about $200, has a learning curve, and so it is not exactly a plug-and-play quick-fix. It is over-kill unless you do many migrations. For component migrations like Active Directory, Exchange, and so forth, and even for an entire SBS migration, a much better solution is the built-in tools. One can export data and import back into a new installation.

sbsmigration.com is not a panacea for all migrations, and so novices to SBS should avoid the temptation. There are other third-party solutions, but like sbsmigration, they also cost money and time to learn. Your time and money would be better spent learning about the built-in features of SBS. Each component has a data-management feature for backing up or exporting or importing data. There is one for SQL, Exchange, SharePoint, WSUS, etc.
.



Relevant Pages

  • Re: SBS Migrations
    ... It is over-kill unless you do many migrations. ... sbsmigration.com is not a panacea for all migrations, ... I don't know how many migrations you've done, but having done somewhere approaching 50 - half using the MS method involving the ADMT etc, and the other half using the Swing method - I can find nothing bad to say about the Swing method. ... I don't actually use the kit any more. ...
    (microsoft.public.windows.server.sbs)
  • Re: Migrating XP Pro Clients from NT4 Server to SBS2003 Server
    ... to the client are greater than the cost of the kit. ... Skipping versions has not increased the complexity much. ... NT4 to SBS 4.5, I ...
    (microsoft.public.windows.server.sbs)
  • Re: Migrating XP Pro Clients from NT4 Server to SBS2003 Server
    ... > _my charges_ to the client are greater than the cost of the kit. ... > workstations I need to touch (which Swing It! ... > Skipping versions has not increased the complexity much. ... NT4 to SBS 4.5, I ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange question
    ... for minimising downtime and purchasing the kit, the money saved by having as ... purchase). ... Les Connor [SBS Community Member - SBS MVP] ... You can exmerge the existing mailboxes out to PST files, ...
    (microsoft.public.windows.server.sbs)
  • Re: Swing migration from SBS4.5 to SBS 2003
    ... > Hi Neil ... > Frank McCallister SBS MVP ... >> hardware I need in place (e.g. temporary servers) to make the move, ... After finding this kit, it seems ideal ...
    (microsoft.public.windows.server.sbs)