Re: Migrating SBS 2003 To new hardware - Need Help!
- From: Jim <Jim@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 8 Jul 2008 03:30:08 -0700
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...
- Follow-Ups:
- Re: Migrating SBS 2003 To new hardware - Need Help!
- From: Charlie Russel - MVP
- Re: Migrating SBS 2003 To new hardware - Need Help!
- References:
- Re: Migrating SBS 2003 To new hardware - Need Help!
- From: Cliff Galiher
- Re: Migrating SBS 2003 To new hardware - Need Help!
- Prev by Date: Re: Backups HELP!
- Next by Date: Re: Proliant ML350 G4 Server SBS 2003 & Server 2003 Console Freeze
- Previous by thread: Re: Migrating SBS 2003 To new hardware - Need Help!
- Next by thread: Re: Migrating SBS 2003 To new hardware - Need Help!
- Index(es):
Relevant Pages
|
Loading
