Moving an SBS2K Server

We need to move an SBS/Win2K Server from old hardware to new hardware. The
trick is, the new server has to have the same name as the old one, but we're
not allowed to just backup the old one and restore to the new one. Any ideas?

Merv
Wed Jan 26 07:14:20 CST 2005

While written around SBS 2003, I think this should apply to SBS 2000 as
well...

How do I move my server to new hardware
http://www.smallbizserver.net/Default.aspx?tabid=99

--
Merv Porter [SBS MVP]
===================================
"briandwest" <briandwest@discussions.microsoft.com> wrote in message
news:FEDEF2E7-2F9F-4B00-B469-6E93756B0729@microsoft.com...
> We need to move an SBS/Win2K Server from old hardware to new hardware. The
> trick is, the new server has to have the same name as the old one, but
we're
> not allowed to just backup the old one and restore to the new one. Any
ideas?

briandwest
Wed Jan 26 12:39:03 CST 2005

Unfortunately, that's not the situation we have. I probably used the wrong
terminology. We ordered a new Dell server w/no OS (we'll be getting a new OS
for the old server). The old HD/RAID is likely corrupted in all kinds of odd
places by a virus attack a year or so ago, so we hope to use the new server
as a clean slate of sorts.

We can install the primary application (an Access-based database) afresh on
the new server, and copy over all its data files, but I was hoping to get the
user info copied over via Active Directory somehow. I'd like to avoid having
to reconfigure all the client workstations, copying all their data, settings,
etc. from their old user folder to the new one that would be created by
connecting to a new server.

Does that clarify the problem?

"Merv Porter [SBS-MVP]" wrote:

> While written around SBS 2003, I think this should apply to SBS 2000 as
> well...
>
> How do I move my server to new hardware
> http://www.smallbizserver.net/Default.aspx?tabid=99
>
> --
> Merv Porter [SBS MVP]
> ===================================
> "briandwest" <briandwest@discussions.microsoft.com> wrote in message
> news:FEDEF2E7-2F9F-4B00-B469-6E93756B0729@microsoft.com...
> > We need to move an SBS/Win2K Server from old hardware to new hardware. The
> > trick is, the new server has to have the same name as the old one, but
> we're
> > not allowed to just backup the old one and restore to the new one. Any
> ideas?
>
>
>

SuperGumby
Wed Jan 26 13:06:09 CST 2005

What you want to do, it would seem, is what we refer to as a migration.

www.sbsmigration.com

"briandwest" <briandwest@discussions.microsoft.com> wrote in message
news:43709201-EF36-481C-8285-7E535CB7F660@microsoft.com...
> Unfortunately, that's not the situation we have. I probably used the
> wrong
> terminology. We ordered a new Dell server w/no OS (we'll be getting a new
> OS
> for the old server). The old HD/RAID is likely corrupted in all kinds of
> odd
> places by a virus attack a year or so ago, so we hope to use the new
> server
> as a clean slate of sorts.
>
> We can install the primary application (an Access-based database) afresh
> on
> the new server, and copy over all its data files, but I was hoping to get
> the
> user info copied over via Active Directory somehow. I'd like to avoid
> having
> to reconfigure all the client workstations, copying all their data,
> settings,
> etc. from their old user folder to the new one that would be created by
> connecting to a new server.
>
> Does that clarify the problem?
>
> "Merv Porter [SBS-MVP]" wrote:
>
>> While written around SBS 2003, I think this should apply to SBS 2000 as
>> well...
>>
>> How do I move my server to new hardware
>> http://www.smallbizserver.net/Default.aspx?tabid=99
>>
>> --
>> Merv Porter [SBS MVP]
>> ===================================
>> "briandwest" <briandwest@discussions.microsoft.com> wrote in message
>> news:FEDEF2E7-2F9F-4B00-B469-6E93756B0729@microsoft.com...
>> > We need to move an SBS/Win2K Server from old hardware to new hardware.
>> > The
>> > trick is, the new server has to have the same name as the old one, but
>> we're
>> > not allowed to just backup the old one and restore to the new one. Any
>> ideas?
>>
>>
>>

Merv
Wed Jan 26 13:19:54 CST 2005

What SG said... And you'll need a spare workstation (with a drive that can
be formatted) to use as a secondary Domain Controller during the migration.

--
Merv Porter [SBS MVP]
===================================
"briandwest" <briandwest@discussions.microsoft.com> wrote in message
news:43709201-EF36-481C-8285-7E535CB7F660@microsoft.com...
> Unfortunately, that's not the situation we have. I probably used the
wrong
> terminology. We ordered a new Dell server w/no OS (we'll be getting a new
OS
> for the old server). The old HD/RAID is likely corrupted in all kinds of
odd
> places by a virus attack a year or so ago, so we hope to use the new
server
> as a clean slate of sorts.
>
> We can install the primary application (an Access-based database) afresh
on
> the new server, and copy over all its data files, but I was hoping to get
the
> user info copied over via Active Directory somehow. I'd like to avoid
having
> to reconfigure all the client workstations, copying all their data,
settings,
> etc. from their old user folder to the new one that would be created by
> connecting to a new server.
>
> Does that clarify the problem?
>
> "Merv Porter [SBS-MVP]" wrote:
>
> > While written around SBS 2003, I think this should apply to SBS 2000 as
> > well...
> >
> > How do I move my server to new hardware
> > http://www.smallbizserver.net/Default.aspx?tabid=99
> >
> > --
> > Merv Porter [SBS MVP]
> > ===================================
> > "briandwest" <briandwest@discussions.microsoft.com> wrote in message
> > news:FEDEF2E7-2F9F-4B00-B469-6E93756B0729@microsoft.com...
> > > We need to move an SBS/Win2K Server from old hardware to new hardware.
The
> > > trick is, the new server has to have the same name as the old one, but
> > we're
> > > not allowed to just backup the old one and restore to the new one. Any
> > ideas?
> >
> >
> >

briandwest
Wed Jan 26 21:37:02 CST 2005

Yeah, after I posted my clarification, I started digging deeper in this
forum. I had assumed (rashly) that our situation was rare and odd, having
hundreds of files witn UNC's hard-coded into them, needing to keep the server
name. I've been perusing the sbsmigration site, and almost put down the
dough for the Swing kit, but I want to have someone tell me (sooner rather
than later) this: the site repeatedly affirms that the kit can take any
platform to SBS2003; it Can do SBS2K-->SBS2K as well, right?

One reason I'm excited about this is that I actually came up with this
concept, and "almost" pulled it off. I have an "in-between" server (a Dell
workstation borrowing a Win2K Server license for a short time) that
replicated from our old SBS2K server, but now that it's on a mini-network
alone with the new SBS2K server, I can't get the two to replicate. I'm
guessing that I didn't prepare the machines or do the steps in the right
order. Am I right that the Swing Kit will walk me through such steps?

Thanks for everyone's input.

Merv
Wed Jan 26 21:45:31 CST 2005

I wouldn't presume to speak for Jeff Middleton, so why don't you contact him
directly with your questions:

http://www.sbsmigration.com/content.php?display=contact

--
Merv Porter [SBS MVP]
===================================
"briandwest" <briandwest@discussions.microsoft.com> wrote in message
news:E26BC1B3-88AC-4093-A098-A3B3D486F983@microsoft.com...
> Yeah, after I posted my clarification, I started digging deeper in this
> forum. I had assumed (rashly) that our situation was rare and odd, having
> hundreds of files witn UNC's hard-coded into them, needing to keep the
server
> name. I've been perusing the sbsmigration site, and almost put down the
> dough for the Swing kit, but I want to have someone tell me (sooner rather
> than later) this: the site repeatedly affirms that the kit can take any
> platform to SBS2003; it Can do SBS2K-->SBS2K as well, right?
>
> One reason I'm excited about this is that I actually came up with this
> concept, and "almost" pulled it off. I have an "in-between" server (a
Dell
> workstation borrowing a Win2K Server license for a short time) that
> replicated from our old SBS2K server, but now that it's on a mini-network
> alone with the new SBS2K server, I can't get the two to replicate. I'm
> guessing that I didn't prepare the machines or do the steps in the right
> order. Am I right that the Swing Kit will walk me through such steps?
>
> Thanks for everyone's input.
>

Jeff
Wed Jan 26 22:34:26 CST 2005

Yes, the Swing It!! Kit does provide you the tools and docs to do the SBS
2000 to SBS 2000 loop installation. I'm still finalizing additional
documentation for other variations of swing, at which point I will revise
the website. In the meantime, I'm providing the addendum documentation on
demand for SBS 2000 looped migrations as well as for NT4 and SBS 4.5
migrations to SBS 2003.

If you have specific concerns you can contact me directly from the contact
addresses at the website, or I can clarify anything specific you want here
as well.

The swing process for SBS 2000 to SBS 2000 is basically the same as outlined
at the website. As you have determined, the problem isn't entirely solved by
just putting a DC into the middle of the process. The steps required are
specific, and must be in the correct order. The Swing It!! Kit docs provide
the entire project end-to-end for you to go through.


"briandwest" <briandwest@discussions.microsoft.com> wrote in message
news:E26BC1B3-88AC-4093-A098-A3B3D486F983@microsoft.com...
> Yeah, after I posted my clarification, I started digging deeper in this
> forum. I had assumed (rashly) that our situation was rare and odd, having
> hundreds of files witn UNC's hard-coded into them, needing to keep the
server
> name. I've been perusing the sbsmigration site, and almost put down the
> dough for the Swing kit, but I want to have someone tell me (sooner rather
> than later) this: the site repeatedly affirms that the kit can take any
> platform to SBS2003; it Can do SBS2K-->SBS2K as well, right?
>
> One reason I'm excited about this is that I actually came up with this
> concept, and "almost" pulled it off. I have an "in-between" server (a
Dell
> workstation borrowing a Win2K Server license for a short time) that
> replicated from our old SBS2K server, but now that it's on a mini-network
> alone with the new SBS2K server, I can't get the two to replicate. I'm
> guessing that I didn't prepare the machines or do the steps in the right
> order. Am I right that the Swing Kit will walk me through such steps?
>
> Thanks for everyone's input.
>