Re: Migrating SBS 2003 To new hardware - Need Help!

This is a one time migration and I don't anticipate migrating this site or any other site to new hardware. Is it worth purchasing the software and learning the software to migrate one site? If the consensus isyes, I may try it after dealing with this messy situation...

Thanks - Jim

"Charlie Russel - MVP" <charlie@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:96A60BF0-309C-4EFD-9C20-7486FC85627F@xxxxxxxxxxxxxxxx
Honestly, the MS migration strategy isn't what I would use in the first place. I've done a few Swing Migrations (www.sbsmigration.com) and it's a far superior way to go.

--
Charlie.
http://msmvps.com/blogs/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel

"Jim" <Jim@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:56A8295A-2900-47A3-B767-743F03470482@xxxxxxxxxxxxxxxx
Thanks - the frustrating thing about this is this is my first SBS migration.
I wasn't sure what to expect so I took it as far I could before contacting
the third party vendor. As I mentioned, they purchased licenses for both
servers with the new licenses on a Select Agreement. There should be a
cleaner way out of this for customers trying to do the right thing.

MSoft - if you are listening - this is a problem! As a minimum, please add
a warning in Technet article regarding the 14 days. I read it before
starting and didn't see it. If it is in there, please make it more
prominent. Also, there should be a way to contact Msoft to reset the timer
if this happens. Taking down an office every hour to prove a point doesn't
seem reasonable - especially when your customer has purchased everything you
want them to.

"Cliff Galiher" wrote:

Nope, not funny at all. But yes, you can reverse all of the steps in step 2
and remove the new server from the network. That will prevent the
rebooting. Make sure your roles transfer BACK to the old server before
removing the new machine from the domain and you'll be fine. Just go slow
and steady, and make backups.

As far as the 4 or 5 hours, honestly that is not a lot of time in the scope
of a whole server migration. Yeah, it is time lost, but you should really
be planningon dedicating two working days (or more if this is your first
time) to the migration...and you should do it all at once. Leaving both
servers on the network for an extended period of time is just asking for
various components to get out of sync...

-Cliff

"Jim" <Jim@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6E8B18CF-00C6-4E80-BF9F-E137B032732A@xxxxxxxxxxxxxxxx
> Sorry for this, but I really need some advice... I am moving an old > SBS
> 2003
> installation to new hardware (with new licenses). I am following the
> Technet
> whitepaper "Migrating Windows Small Business Server 2003 to New > Hardware".
> I
> completed Step 2 of the white paper and was waiting for "Line of > Business"
> application developer to set a date of when they can be on site to > move
> their
> application before I proceeded to migrate Exchange.
>
> In the mean time, the server started rebooting today every hour with > event
> codes 1001, 1012, 1011. The event codes say that I am in violation of
> EULA
> since I have two SBS servers in the same domain (following the
> instructions
> from Technet as described in the white paper above). It appears that
> there
> is a two week limit on having two domain controllers on the same SBS
> Domain!
>
> So... with my customer's application server rebooting every hour (this
> really isn't funny - Nagware at its worst!), does anyone have a
> suggestion?
> - Is there a way to lengthen or reset the timer? Two more weeks would > do
> it.
> - Can I reverse the steps in the white paper and restart when the > vendor
> is
> ready? This would be painful as the original process took 4 - 5 hours > to
> get
> this far (the old hardware is lacking).
> - Proceeding with the installation cannot occur for a couple of days,
> which
> means the Doctor's office server will reboot 20 - 30 times...
>
> Thanks for any and all advice...



.

Relevant Pages

  • Re: Migrating SBS 2003 To new hardware - Need Help!
    ... Jim - I have also used the swing migration kit, ... used it to migrate a SBS box to new hardware with 60 user accounts, ... any other site to new hardware. ... Make sure your roles transfer BACK to the old server before ...
    (microsoft.public.windows.server.sbs)
  • Re: Justification for creating a new Domain
    ... We also have a SQL Server, Application Server, SAN. ... hardware was purchased as a life cycle purchase to replace Dell 2650 servers. ... DNS and AD in the same server? ... That is on top of the the migration of shares that must be done when a server is replaced anyway. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Migrate to new Hardware and/or SBS2003
    ... to SBS2003 first on your current server, ... My first swing migration was an SBS server with 20 users, ... Do you axpect any problems on the new Hardware ... > and should we Upgrade to SBS2003 to avoid strange problems. ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: Migrate to new Hardware and/or SBS2003
    ... > There's more than one way to do a migration, and a lot of things add into ... > to SBS2003 first on your current server, ... >> Migrating to new Hardware. ... >> and should we Upgrade to SBS2003 to avoid strange problems. ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: MS Action Pack w/SBS 2003
    ... Lets back off the hardware for a second and talk more about the action pack. ... I'd skip purchasing anything if you are jsut testing. ... strong workstation will more than do for a test server. ...
    (microsoft.public.backoffice.smallbiz2000)