Re: SBS migration (without using Swing-IT), from SBS2k to SBS2003

Tech-Archive recommends: Fix windows errors by optimizing your registry



actually Q, you could use a 'live' system as a test, that's the beauty of
it. The only change to the original AD is the addition of the swingserver as
a DC (assuming it's not a 'swing to same hardware'), there is no reason
clients should call you during the process because this change in no way
effects the day2day operation of the AD.

I have complained bitterly to Jeff about the size of the documentation.
Opening a 200+ page pdf file causes me to groan too. However, some thoughts:
Much of the space of the document is taken by 'layout', there's a_lot_ of
whitespace. The document is also in a large font to be easily viewable on
PC.
A significant proportion of the document is explanatory of something going
wrong at the point of mention. If you don't get NTFRS errors you don't
really need to read how to fix them, it can be 'skimmed'.
Nobody ever said it was going to be simple. You are taking on a major
project, 'fighting' against SBS' limitations in order to achieve your goal.
Having developed the procedure independently of Jeff I can tell you the
whole thing can be done 'flying by the seat of your pants', as long as you
understand SBS, it's limits, and how to chase KB articles. You'll probably
read more than 200 pages of KB articles though, and they are not laid out so
sparsely.

The swing documentation I recently got from Jeff is clear, concise (for Jeff
:-), but more importantly WORKS. _at least_ many hundreds of systems have
been 'swung' (I know from just those people I am aware of using the
procedure that it exceeds a few hundred). One of the main goals of swing is
to minimise disruption to the existing network, if your clients started
calling you due to something caused by the process you did something wrong.

"Q Logic" <QLogic@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1CE4C85E-4722-4DD7-B00F-0475B06B241B@xxxxxxxxxxxxxxxx
Larry,

Just wanted to let you know, that after all the suggestions I called and
had
a long conversation with Jeff about the product... After speaking to him,
I
agreed to setup a test envirnment and attempt his proceedures again...
Working in a test envirnment I will not be faced with endless phone call
from
clients saying they need to be back up by yesterday, demanding I stop what
I
doing and fix the problem... Who knows, given a week or so of testing I
may
yet become yet another tech singing the prases of Swing-IT....

Q Logic, Ltd.

"Larry Struckmeyer" wrote:

Q:

I read your other thread after reading the first two posts in this one,
and
agree with you. Your question was not answered, at least not in the
first
few replies. I think a better response on the part of those who replied
may
have been to answer your question and then give you links or
recomendatations to sbsmigration.com.

The question was answered your other post, but I agree, it took more than
a
little effort on your part to get it done.

The reason you got all the comments defending sbsmigration.com is because

1.) No one wants to see you do more work than is necessary,

2.) If I posted that the sky is falling and no one else agreed, I would
get
a few "alternative" viewpoints as well.

3.) Many in this space have a long history with the creator of
sbsmigration.com, and know both he and his proceedure intimently.
Further
more, we/they/I know him to be the most up front honest person you could
wish for in your corner.

Larry


"Q Logic" <QLogic@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:66CB28D3-176D-4560-BCFC-A24EA194238D@xxxxxxxxxxxxxxxx
That's fine, but I paid the few hundred for the product last year and
all
I
got were some PDF files and a few VB scripts no real diffinitive
instruction
on how to do a migration unless I wanted to sit and read a few hundred
more
pages... It also required in each situation I actually bring a third
temp
server on-site... I could not figure out what anything was refuring to
or
in
what order any of the documentation went in, I called support for
assistance
and got no responce... So I deemed the money spent as a donation... And
utterly usless to me.... I posted in the last weeks just some quick
definitions of Exmerge as I had not used in a while and all I got were
people
ignoring my question telling me to by Swing-IT... So this became very
frustrating...

"Q Logic" wrote:

Larry,

Please keep your sales pitches to yourself, swing-it is nothing more
then
a
collection of disorganized ramblings of an exspencive wannabe
solution...
Capatolism at it's finest... And the more you answer my post with the
same
suggestions, the more that I will continue to post that this kit is a
complete rip-off...
If you keep posting I will be sure to let everyone know...

"Larry Struckmeyer" wrote:

and, perhaps, the extensive documentation that comes with swing-it.

Larry Struckmeyer

"Henry Craven {SBS-MVP}" <sme@xxxxxxxxxxxxxx> wrote in message
news:FCAAC043-6827-4002-ABB2-090EEADB8B5A@xxxxxxxxxxxxxxxx
No.
Please read the extensive documentation that comes with Exmerge.

--
Henry Craven {SBS-MVP}


"Q Logic" <QLogic@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5BD5888E-F384-4E20-8610-5CAE32A26751@xxxxxxxxxxxxxxxx
Please do not try to sell me swing-it, I already bought it and
found
it
useless...
I would like to know when I import with Exmerge, will the user
accounts
be
automatically created?

Q Logic, Ltd.









.



Relevant Pages

  • Re: SBS migration (without using Swing-IT), from SBS2k to SBS2003
    ... "Larry Struckmeyer" wrote: ... Please keep your sales pitches to yourself, swing-it is nothing more then ... Please read the extensive documentation that comes with Exmerge. ...
    (microsoft.public.backoffice.smallbiz)
  • Re: SBS migration (without using Swing-IT), from SBS2k to SBS2003
    ... Please keep your sales pitches to yourself, swing-it is nothing more then ... "Larry Struckmeyer" wrote: ... Please read the extensive documentation that comes with Exmerge. ...
    (microsoft.public.backoffice.smallbiz)
  • Re: SBS migration (without using Swing-IT), from SBS2k to SBS2003
    ... You are certainly entitled to your opinion. ... "Larry Struckmeyer" wrote: ... Please read the extensive documentation that comes with Exmerge. ...
    (microsoft.public.backoffice.smallbiz)
  • Re: SBS migration (without using Swing-IT), from SBS2k to SBS2003
    ... I'm sure Jeff would be the first to say that the information in his "Swing Migration" process is based on information readily available ... But once you actually do a Swing all the way through, then go back to his documentation, it starts to make sense - again, at least for me it did. ... Also be aware that in the Exmerge import process the admin accounts will NOT ...
    (microsoft.public.backoffice.smallbiz)
  • Re: first boot AFTER cloning
    ... The documentation says set it to 0 if you want to manually ... >> What phase do you set for your command? ... > Jeff is maybe running into the same problem as I am. ... > to '0', in order to get a chance to set some custom configuration, install ...
    (microsoft.public.windowsxp.embedded)