Re: Umove to Migrate SBS to new hardware
- From: "Gregg Hill" <bogus@xxxxxxxxxxx>
- Date: Sat, 7 Apr 2007 20:31:36 -0700
I beg to differ on the value of the swing migration kit. You are judging
something you have never used. I bought it and I have used it and the TOOLS
that Jeff wrote and included in the kit. Yes, the kit is based upon
Microsoft documentation and every step is an action supported by Microsoft.
I doubt your product would result in a system that is supported by Microsoft
should you ever have to contact their support.
One nice thing is that the server name, IP, UNC share paths, SIDs, etc, all
remain the same as the server being replaced, so there is no need to touch a
single workstation.
No, I do not get a cut. I just know that it is much easier to use the kit to
do certain migrations than it would be to rebuild an entire domain.
The $200 gets a consolidation of MS articles, plus the tools, plus unlimited
support for your first migration. The consolidation of articles in to one
spot is in itself worth $200 of my time.
This "whole integrated piece of crap" SBS 2003 has not caused me any grief
above what any other OS has done.
If you are a Novell guy, are you sticking to the old ways and being too
stubborn to do it the MS way? If so, then "Duh!" comes to mind for the
problems you have had.
If a small company bought Windows Server 2003 and Exchange for their only
server, then it would take MORE time to set it up and recover than it does
for SBS.
Just my take on the matter!
Gregg Hill
"Homer J. Simpson" <homer@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:xLmdneJmzrcKmIXbnZ2dnUVZ_t-mnZ2d@xxxxxxxxxxxxxxx
Well at this point I am trying to avoid this "swing" migration for several
reasons. First off, Umove costs $129, and as a piece of software if it
operates as advertised, should completely ease the move. This swing
migration is nothing more than a set of documents, a method, that quite
frankly MS should have (#*@ing provided in the first place.
Swingmigration.com is nothing more than documents that MS should have
provided in the first place. Better yet, they should have actually
provided a proper tool to migrate SBS servers.
Do they not anticipate that hardware fails, or people sometimes just wish
to replace the current server? Obviously not since this whole integrated
piece of crap requires honestly steps that are just plain idiotic.
I find it quite objectionable that all the SBS-MVPs want to just forward
people to your "friends" $200 collection of documents. Are you all getting
a cut out of this? I sure hope so, seeing as this is all that certain
people seem to recommend.
Quite frankly I agree 100% with a many that Microsoft SBS is an OS that
just needs to be avoided. I know if this was Novell SBS this would take a
matter of minutes, with no requirements to even shut anything down...in
fact come to think about I just recently moved a Suse PDC to another
machine during the day without any downtime.
Cris Hanna [SBS-MVP] wrote:
Understand that a standard windows server is not the same as an SBS
server...which holds all the roles for the AD and Exchange etc.
The swing migration was created by an SBS MVP, its been tried and proven
by hundreds if not thousands now. If you are going to spend money for a
tool, get one designed to do the job
.
- References:
- Umove to Migrate SBS to new hardware
- From: Homer J. Simpson
- Re: Umove to Migrate SBS to new hardware
- From: Cris Hanna [SBS-MVP]
- Re: Umove to Migrate SBS to new hardware
- From: Homer J. Simpson
- Umove to Migrate SBS to new hardware
- Prev by Date: Re: Floppy drive still required for 2003R2 ASR recovery
- Next by Date: Re: Connect Computer
- Previous by thread: Re: Umove to Migrate SBS to new hardware
- Next by thread: Re: Umove to Migrate SBS to new hardware
- Index(es):
Relevant Pages
|
