Hi,

This is a popular subject so I will relate what I've learned and just ask
for comments / criticism re any oversights I have in my plan.

Background: I have a new client with a SBS 2000 installation using ISA,
Exchange, OWA, Trend antivirus, file sharing. His business has grown to 18
users. No second DC, no RAID, backup inconsistent, current server is an
over-burdened AMD desktop PC with a lot of memory but misconfigured hard
disks, and is a single point of failure. Running Health Monitor actually
crashes server (all red marks!)

Prior to my coming on-site, they purchased a new "server" (actually a P4
workstation class machine) to upgrade the facility but the previous provider
couldn't figure out how to migrate. (Being used as print server presently!)
At this point I am afraid to try to migrate him to SBS 2003 due to license
costs, lack of immediate bang-for-buck for problems above. Perhaps the next
phase after I am established as a consultant to his business.

Plan - I will:

1. Configure RAID 1 on the new server. (Preformat with NTFS using WINPE
environment?)
2. Install SBS 2000 on the new server. (How far? Use "fake" domain name?)
Configure volumes like old server, but with appropriate sizes.
3. Install compatible backup device on old server. Do a full NTbackup of the
existing SBS domain including file shares, Exchange & sysvol. (Can I backup
to new "fake" SBS domain volume instead? Permission issues, with no domain
trust relationship possible in SBS?)
4. Remove backup device from old server and install in new server (if
network backup not possible.)
5. Reboot new server offline (or on isolated subnet?) and do Directory
Services Restore Mode using backup of old server. New server now "thinks" it
is DC for existing network. (Which password do I use for Restore Mode, old
server or new?)
6. Configure network IP configurations on new server identical to old
server. Shutdown.
7. Physically replace old server with new, network-wise (internal/external
connections.) Take old server offline.
8. Reboot new server and test. Restore old server if new one has issues.
9. New server SBS elements work?! Install anti-virus server if OK.
10. Flush old server, upgrade processor and install new Windows 2000 Server
Standard.
11. Add old server to domain as member server, then run DCPromo. Replicate AD.
12. Split off anti-virus server duties, add print services to second DC.
13. DFS for file shares?

Thanks in advice for comments, any answers to questions you can provide.

And Jeff Middleton, TIA for your swing method, but not in budget. As a
private consultant, I have to spend time unpaid rather than buy stuff and
charge clients. My time is both invaluable and valueless, as long as I still
sleep once in a while.

Re: Server Migration SBS 2000 to New Server Box by Cris

Cris
Mon Jan 24 10:50:57 CST 2005

You might start by looking here although it deals with 2003
http://www.smallbizserver.net/Default.aspx?tabid=99

This article should be helpful as well
http://support.microsoft.com/default.aspx?scid=kb;en-us;278439
NOTE: Although the exact steps may differ, the same basic concepts apply
when you migrate a SBS 2000 installation to new hardware.

--
Cris Hanna [SBS - MVP]
---------------------------------------
Please reply only to the newsgroup and not to me directly so that everyone
can benefit from the information
"PMC" <pmchefalo-spamfree@hotmail.com> wrote in message
news:B5AF2B4D-8A3F-4A20-BA2E-8379421B6015@microsoft.com...
> Hi,
>
> This is a popular subject so I will relate what I've learned and just ask
> for comments / criticism re any oversights I have in my plan.
>
> Background: I have a new client with a SBS 2000 installation using ISA,
> Exchange, OWA, Trend antivirus, file sharing. His business has grown to 18
> users. No second DC, no RAID, backup inconsistent, current server is an
> over-burdened AMD desktop PC with a lot of memory but misconfigured hard
> disks, and is a single point of failure. Running Health Monitor actually
> crashes server (all red marks!)
>
> Prior to my coming on-site, they purchased a new "server" (actually a P4
> workstation class machine) to upgrade the facility but the previous
> provider
> couldn't figure out how to migrate. (Being used as print server
> presently!)
> At this point I am afraid to try to migrate him to SBS 2003 due to license
> costs, lack of immediate bang-for-buck for problems above. Perhaps the
> next
> phase after I am established as a consultant to his business.
>
> Plan - I will:
>
> 1. Configure RAID 1 on the new server. (Preformat with NTFS using WINPE
> environment?)
> 2. Install SBS 2000 on the new server. (How far? Use "fake" domain name?)
> Configure volumes like old server, but with appropriate sizes.
> 3. Install compatible backup device on old server. Do a full NTbackup of
> the
> existing SBS domain including file shares, Exchange & sysvol. (Can I
> backup
> to new "fake" SBS domain volume instead? Permission issues, with no domain
> trust relationship possible in SBS?)
> 4. Remove backup device from old server and install in new server (if
> network backup not possible.)
> 5. Reboot new server offline (or on isolated subnet?) and do Directory
> Services Restore Mode using backup of old server. New server now "thinks"
> it
> is DC for existing network. (Which password do I use for Restore Mode, old
> server or new?)
> 6. Configure network IP configurations on new server identical to old
> server. Shutdown.
> 7. Physically replace old server with new, network-wise (internal/external
> connections.) Take old server offline.
> 8. Reboot new server and test. Restore old server if new one has issues.
> 9. New server SBS elements work?! Install anti-virus server if OK.
> 10. Flush old server, upgrade processor and install new Windows 2000
> Server
> Standard.
> 11. Add old server to domain as member server, then run DCPromo. Replicate
> AD.
> 12. Split off anti-virus server duties, add print services to second DC.
> 13. DFS for file shares?
>
> Thanks in advice for comments, any answers to questions you can provide.
>
> And Jeff Middleton, TIA for your swing method, but not in budget. As a
> private consultant, I have to spend time unpaid rather than buy stuff and
> charge clients. My time is both invaluable and valueless, as long as I
> still
> sleep once in a while.



Server Migration SBS 2000 to New Server Box by Ed

Ed
Mon Jan 24 15:25:30 CST 2005

Hi,
We have just performed (last week) a very similar migration
for a new client whose existing server went ill but was
still operable (just). The way we went about the migration
was as follows:
Backup all company and user data to USB hard drive
Run the Exmerge utility to produce pst files for each user.
Produce a pst file to backup the public folders from Outlook.
Build the new server with SBS 2K, add all service packs and
reproduce the same Domain.local, users, group policy, ISA,
anti-virus etc.
Restore all company and user data
De-commission the old server and replace with new server.
Run ICW to get Internet connection running.
Run magic disk on each client PC but install NO client apps.
Import each pst's to each user PC and Public folder pst.
Set permissions on public folders for those users who
create and modify public folders.
Go through the usual procedure for backups etc...

I hav'nt included every detail of every step but this
procedure has worked well and the new server is now up and
running and we completed the migration over a weekend.
Hope this is of some use to you.
Best wishes
Ed


>-----Original Message-----
>Hi,
>
>This is a popular subject so I will relate what I've
learned and just ask
>for comments / criticism re any oversights I have in my plan.
>
>Background: I have a new client with a SBS 2000
installation using ISA,
>Exchange, OWA, Trend antivirus, file sharing. His business
has grown to 18
>users. No second DC, no RAID, backup inconsistent, current
server is an
>over-burdened AMD desktop PC with a lot of memory but
misconfigured hard
>disks, and is a single point of failure. Running Health
Monitor actually
>crashes server (all red marks!)
>
>Prior to my coming on-site, they purchased a new "server"
(actually a P4
>workstation class machine) to upgrade the facility but the
previous provider
>couldn't figure out how to migrate. (Being used as print
server presently!)
>At this point I am afraid to try to migrate him to SBS
2003 due to license
>costs, lack of immediate bang-for-buck for problems above.
Perhaps the next
>phase after I am established as a consultant to his business.
>
>Plan - I will:
>
>1. Configure RAID 1 on the new server. (Preformat with
NTFS using WINPE
>environment?)
>2. Install SBS 2000 on the new server. (How far? Use
"fake" domain name?)
>Configure volumes like old server, but with appropriate sizes.
>3. Install compatible backup device on old server. Do a
full NTbackup of the
>existing SBS domain including file shares, Exchange &
sysvol. (Can I backup
>to new "fake" SBS domain volume instead? Permission
issues, with no domain
>trust relationship possible in SBS?)
>4. Remove backup device from old server and install in new
server (if
>network backup not possible.)
>5. Reboot new server offline (or on isolated subnet?) and
do Directory
>Services Restore Mode using backup of old server. New
server now "thinks" it
>is DC for existing network. (Which password do I use for
Restore Mode, old
>server or new?)
>6. Configure network IP configurations on new server
identical to old
>server. Shutdown.
>7. Physically replace old server with new, network-wise
(internal/external
>connections.) Take old server offline.
>8. Reboot new server and test. Restore old server if new
one has issues.
>9. New server SBS elements work?! Install anti-virus
server if OK.
>10. Flush old server, upgrade processor and install new
Windows 2000 Server
>Standard.
>11. Add old server to domain as member server, then run
DCPromo. Replicate AD.
>12. Split off anti-virus server duties, add print services
to second DC.
>13. DFS for file shares?
>
>Thanks in advice for comments, any answers to questions
you can provide.
>
>And Jeff Middleton, TIA for your swing method, but not in
budget. As a
>private consultant, I have to spend time unpaid rather
than buy stuff and
>charge clients. My time is both invaluable and valueless,
as long as I still
>sleep once in a while.
>.
>

Re: Server Migration SBS 2000 to New Server Box by Jeff

Jeff
Mon Jan 24 18:06:01 CST 2005

This process differs dramatically from the plan he was going to do. I'm
going to comment directly on his plan to clarify the issues. Basically, you
did a clean OS install, he's trying to scratch install then DSRM restore.
You only restored the data and the Exchange was exmerged. I'm going to
comment on his plan separately.



"Ed Clark" <anonymous@discussions.microsoft.com> wrote in message
news:013d01c5025b$3b484a40$a601280a@phx.gbl...
> Hi,
> We have just performed (last week) a very similar migration
> for a new client whose existing server went ill but was
> still operable (just). The way we went about the migration
> was as follows:
> Backup all company and user data to USB hard drive
> Run the Exmerge utility to produce pst files for each user.
> Produce a pst file to backup the public folders from Outlook.
> Build the new server with SBS 2K, add all service packs and
> reproduce the same Domain.local, users, group policy, ISA,
> anti-virus etc.
> Restore all company and user data
> De-commission the old server and replace with new server.
> Run ICW to get Internet connection running.
> Run magic disk on each client PC but install NO client apps.
> Import each pst's to each user PC and Public folder pst.
> Set permissions on public folders for those users who
> create and modify public folders.
> Go through the usual procedure for backups etc...
>
> I hav'nt included every detail of every step but this
> procedure has worked well and the new server is now up and
> running and we completed the migration over a weekend.
> Hope this is of some use to you.
> Best wishes
> Ed
>
>
> >-----Original Message-----
> >Hi,
> >
> >This is a popular subject so I will relate what I've
> learned and just ask
> >for comments / criticism re any oversights I have in my plan.
> >
> >Background: I have a new client with a SBS 2000
> installation using ISA,
> >Exchange, OWA, Trend antivirus, file sharing. His business
> has grown to 18
> >users. No second DC, no RAID, backup inconsistent, current
> server is an
> >over-burdened AMD desktop PC with a lot of memory but
> misconfigured hard
> >disks, and is a single point of failure. Running Health
> Monitor actually
> >crashes server (all red marks!)
> >
> >Prior to my coming on-site, they purchased a new "server"
> (actually a P4
> >workstation class machine) to upgrade the facility but the
> previous provider
> >couldn't figure out how to migrate. (Being used as print
> server presently!)
> >At this point I am afraid to try to migrate him to SBS
> 2003 due to license
> >costs, lack of immediate bang-for-buck for problems above.
> Perhaps the next
> >phase after I am established as a consultant to his business.
> >
> >Plan - I will:
> >
> >1. Configure RAID 1 on the new server. (Preformat with
> NTFS using WINPE
> >environment?)
> >2. Install SBS 2000 on the new server. (How far? Use
> "fake" domain name?)
> >Configure volumes like old server, but with appropriate sizes.
> >3. Install compatible backup device on old server. Do a
> full NTbackup of the
> >existing SBS domain including file shares, Exchange &
> sysvol. (Can I backup
> >to new "fake" SBS domain volume instead? Permission
> issues, with no domain
> >trust relationship possible in SBS?)
> >4. Remove backup device from old server and install in new
> server (if
> >network backup not possible.)
> >5. Reboot new server offline (or on isolated subnet?) and
> do Directory
> >Services Restore Mode using backup of old server. New
> server now "thinks" it
> >is DC for existing network. (Which password do I use for
> Restore Mode, old
> >server or new?)
> >6. Configure network IP configurations on new server
> identical to old
> >server. Shutdown.
> >7. Physically replace old server with new, network-wise
> (internal/external
> >connections.) Take old server offline.
> >8. Reboot new server and test. Restore old server if new
> one has issues.
> >9. New server SBS elements work?! Install anti-virus
> server if OK.
> >10. Flush old server, upgrade processor and install new
> Windows 2000 Server
> >Standard.
> >11. Add old server to domain as member server, then run
> DCPromo. Replicate AD.
> >12. Split off anti-virus server duties, add print services
> to second DC.
> >13. DFS for file shares?
> >
> >Thanks in advice for comments, any answers to questions
> you can provide.
> >
> >And Jeff Middleton, TIA for your swing method, but not in
> budget. As a
> >private consultant, I have to spend time unpaid rather
> than buy stuff and
> >charge clients. My time is both invaluable and valueless,
> as long as I still
> >sleep once in a while.
> >.
> >



Re: Server Migration SBS 2000 to New Server Box by Jeff

Jeff
Mon Jan 24 19:20:29 CST 2005

Hello PMC,

It's not my goal to talk you or anyone else into purchasing a Swing It!!
Kit, not at all, not if it doesn't make sense to both of us. The kit forms a
contract that ties me to your success, just as much as it ties you
optimistically to my work plan. It's my goal to see everyone possible stop
going through the shreader you are walking into. But it's my goal to help a
lot more people that just a handful here and there, and that's why I'm using
a business model that requires the kit to cost something reasonable, you get
certainty of skilled help, but you get something substantial: a permanent
resellable skill.

In another 45-60 days....buy Harry's book where the chapter I've written on
Swing Migration will be included. The reason I agreed to publish the
information in a book with no income to me involved is so that someone like
you can afford to get that book, get a great value, even if you can't
justify my support services and tools in the Kit.

So why not give away the Swing Docs if it's going to be in a book I make
nothing from? Because I owe Harry a favor, and he can make a couple bucks
per book, and get the word out. I also owe a lot of favors to a bunch of SBS
MVPs who helped me over the years and with Swing tests, and making that book
a part of their exposure as authors means I bring attention to their
chapters, not just mine. That helps them and Harry, and that help all of us
help the educated community as a whole, and that helps me because I'm part
of the community. We all win.

My goal, my total goal with Swing It!! Kits goes like this:

+ The IT Pro does the job in less time spent, with less confusion involved,
and without causing a problem. He makes more money per hour, too. You get
more time off, and better quality work.
+ The Biz owner gets the job done in less total time, probably less total
cost, with less impact on the business, less frustration to the staff for
needless changes. The business makes more when it runs with less down time
and complication. That pays for upgrades.
+ The staff retains all the things they have set the way they like it at
their workstations. Everything works on the next day, the same way.

If it hasn't become apparent yet, I'm trying to make Swing Migration go big.
Help everyone. IT Pros worldwide, the biz owners, the SBS MVPs, Harry
Brelsford, the SBS Community UGs I now get to speak to by going around the
world, and even my friends in SBS Team (who need more positive experiences
illustrated by us helping them to see how we help ourselves dealing with
things they didn't think mattered to us). The difference in price and
service bundle between the book vs. the Reference Kit vs. the Technician Kit
will all make perfect sense, but attract different people. I really enjoy
thinking about the scale at which that can make my professional contribution
help a lot of people, and it gives me a way to make a living too, at least
for a while.

I won't have to feel guilty telling anyone that the information in Harry's
book is out somewhat out of date the day it ships, primarily because I'm
moving forward with newer, better information. I'll feel really good about
making the Kit documentation better and better, cover more scenarios, better
details in what will be available that same day as a Swing It!! Kit. Harry
realizes the huge audience he has in book sales will still want the book,
and yet extend to people who wouldn't otherwise hear about the option to buy
a Swing It!! Kit, including tools, support and troubleshooting tips. At
least the book will include the correct step order some of us SBS MVPs made
work last summer on SBS 2000 to 2003 upgrades. It will not be the most
efficient way to do a Swing, but it will at least be a good plan, and a damn
good deal.


**********

I think if you and your customer were to make a call to me, I could help you
get that cost covered and make the customer love the idea. I'm not joking. I
would love to help you out, help your customer out.

You are proposing to do what you probably estimate to be about 12 hrs work,
but is really going to be about 18, or more, depending upon your skill. A
Swing Migration could complete that in 10-12 and you would have no
confusion, and you wouldn't be discovering new issues along the way.

The plan you have isn't going to work, not cleanly, not well, not billable,
not reliable. At least, you are going to be about 12 hrs into the project
and find out that you still don't have a working configuration.

You will run in to SFN breaks on the new server as soon as you do the
restore from backup in DSRM mode. I consider bare metal recovery on SBS 2000
to be an embarrassing joke to MS because it's so ugly bad. That's what you
are building into your upgrade.

All the SBS applications will be broken at your Step 5. In Step 6, you
probably have a good chance that you will need to rip out the TCP/IP
services to reconfigure them. At Step 7 you will feel a lot like you are
rally at step 1. You will have to rerun the entire SBS setup, and that's
going to fix those SFN breaks, but you will still need to do all the same
configuration work to fix many things. You will have a really dirty,
probably not much more reliable installation at that point.

If I were your customer, I wouldn't want you doing what you propose to my
server if it was optional. I mean this in the most kind way. What you
outlined there isn't an upgrade, it's a slow crash and demolition followed
by a patched together recovery process that, as yet, I don't think you have
ever done one of these by this method before? If you want to learn a
process, don't waste your time on this approach, it's not going to work.



"PMC" <pmchefalo-spamfree@hotmail.com> wrote in message
news:B5AF2B4D-8A3F-4A20-BA2E-8379421B6015@microsoft.com...
> Hi,
>
> This is a popular subject so I will relate what I've learned and just ask
> for comments / criticism re any oversights I have in my plan.
>
> Background: I have a new client with a SBS 2000 installation using ISA,
> Exchange, OWA, Trend antivirus, file sharing. His business has grown to 18
> users. No second DC, no RAID, backup inconsistent, current server is an
> over-burdened AMD desktop PC with a lot of memory but misconfigured hard
> disks, and is a single point of failure. Running Health Monitor actually
> crashes server (all red marks!)
>
> Prior to my coming on-site, they purchased a new "server" (actually a P4
> workstation class machine) to upgrade the facility but the previous
provider
> couldn't figure out how to migrate. (Being used as print server
presently!)
> At this point I am afraid to try to migrate him to SBS 2003 due to license
> costs, lack of immediate bang-for-buck for problems above. Perhaps the
next
> phase after I am established as a consultant to his business.
>
> Plan - I will:
>
> 1. Configure RAID 1 on the new server. (Preformat with NTFS using WINPE
> environment?)
> 2. Install SBS 2000 on the new server. (How far? Use "fake" domain name?)
> Configure volumes like old server, but with appropriate sizes.
> 3. Install compatible backup device on old server. Do a full NTbackup of
the
> existing SBS domain including file shares, Exchange & sysvol. (Can I
backup
> to new "fake" SBS domain volume instead? Permission issues, with no domain
> trust relationship possible in SBS?)
> 4. Remove backup device from old server and install in new server (if
> network backup not possible.)
> 5. Reboot new server offline (or on isolated subnet?) and do Directory
> Services Restore Mode using backup of old server. New server now "thinks"
it
> is DC for existing network. (Which password do I use for Restore Mode, old
> server or new?)
> 6. Configure network IP configurations on new server identical to old
> server. Shutdown.
> 7. Physically replace old server with new, network-wise (internal/external
> connections.) Take old server offline.
> 8. Reboot new server and test. Restore old server if new one has issues.
> 9. New server SBS elements work?! Install anti-virus server if OK.
> 10. Flush old server, upgrade processor and install new Windows 2000
Server
> Standard.
> 11. Add old server to domain as member server, then run DCPromo. Replicate
AD.
> 12. Split off anti-virus server duties, add print services to second DC.
> 13. DFS for file shares?
>
> Thanks in advice for comments, any answers to questions you can provide.
>
> And Jeff Middleton, TIA for your swing method, but not in budget. As a
> private consultant, I have to spend time unpaid rather than buy stuff and
> charge clients. My time is both invaluable and valueless, as long as I
still
> sleep once in a while.



Re: Server Migration SBS 2000 to New Server Box by pmchefalo-spamfree

pmchefalo-spamfree
Mon Jan 24 22:29:02 CST 2005

Hi, Chris.

The first article is a hard disk migration scenario. The hard disk system is
the problem here. So I don't know whether I would try it.

The second article I've read before. I was hoping that my (apparently dumb
per the FUD swinger) plan (developed by looking at other advice here) would
keep the existing accounts and permissions. I don't know what the "migrate
the workstations to a the network" in step 8 really means.

Thanks,
Pat

"Cris Hanna [SBS-MVP]" wrote:

> You might start by looking here although it deals with 2003
> http://www.smallbizserver.net/Default.aspx?tabid=99
>
> This article should be helpful as well
> http://support.microsoft.com/default.aspx?scid=kb;en-us;278439
> NOTE: Although the exact steps may differ, the same basic concepts apply
> when you migrate a SBS 2000 installation to new hardware.
>
> --
> Cris Hanna [SBS - MVP]
> ---------------------------------------
> Please reply only to the newsgroup and not to me directly so that everyone
> can benefit from the information
> "PMC" <pmchefalo-spamfree@hotmail.com> wrote in message
> news:B5AF2B4D-8A3F-4A20-BA2E-8379421B6015@microsoft.com...
> > Hi,
> >
> > This is a popular subject so I will relate what I've learned and just ask
> > for comments / criticism re any oversights I have in my plan.
> >
> > Background: I have a new client with a SBS 2000 installation using ISA,
> > Exchange, OWA, Trend antivirus, file sharing. His business has grown to 18
> > users. No second DC, no RAID, backup inconsistent, current server is an
> > over-burdened AMD desktop PC with a lot of memory but misconfigured hard
> > disks, and is a single point of failure. Running Health Monitor actually
> > crashes server (all red marks!)
> >
> > Prior to my coming on-site, they purchased a new "server" (actually a P4
> > workstation class machine) to upgrade the facility but the previous
> > provider
> > couldn't figure out how to migrate. (Being used as print server
> > presently!)
> > At this point I am afraid to try to migrate him to SBS 2003 due to license
> > costs, lack of immediate bang-for-buck for problems above. Perhaps the
> > next
> > phase after I am established as a consultant to his business.
> >
> > Plan - I will:
> >
> > 1. Configure RAID 1 on the new server. (Preformat with NTFS using WINPE
> > environment?)
> > 2. Install SBS 2000 on the new server. (How far? Use "fake" domain name?)
> > Configure volumes like old server, but with appropriate sizes.
> > 3. Install compatible backup device on old server. Do a full NTbackup of
> > the
> > existing SBS domain including file shares, Exchange & sysvol. (Can I
> > backup
> > to new "fake" SBS domain volume instead? Permission issues, with no domain
> > trust relationship possible in SBS?)
> > 4. Remove backup device from old server and install in new server (if
> > network backup not possible.)
> > 5. Reboot new server offline (or on isolated subnet?) and do Directory
> > Services Restore Mode using backup of old server. New server now "thinks"
> > it
> > is DC for existing network. (Which password do I use for Restore Mode, old
> > server or new?)
> > 6. Configure network IP configurations on new server identical to old
> > server. Shutdown.
> > 7. Physically replace old server with new, network-wise (internal/external
> > connections.) Take old server offline.
> > 8. Reboot new server and test. Restore old server if new one has issues.
> > 9. New server SBS elements work?! Install anti-virus server if OK.
> > 10. Flush old server, upgrade processor and install new Windows 2000
> > Server
> > Standard.
> > 11. Add old server to domain as member server, then run DCPromo. Replicate
> > AD.
> > 12. Split off anti-virus server duties, add print services to second DC.
> > 13. DFS for file shares?
> >
> > Thanks in advice for comments, any answers to questions you can provide.
> >
> > And Jeff Middleton, TIA for your swing method, but not in budget. As a
> > private consultant, I have to spend time unpaid rather than buy stuff and
> > charge clients. My time is both invaluable and valueless, as long as I
> > still
> > sleep once in a while.
>
>
>

RE: Server Migration SBS 2000 to New Server Box by pmchefalo-spamfree

pmchefalo-spamfree
Mon Jan 24 22:31:02 CST 2005

Ed,

Your plan is similar to the migration plan Chris cites from Microsoft for
SBS 4.5 to SBS 2000.

What is the "magic disk?"

Thanks,
Pat

"Ed Clark" wrote:

> Hi,
> We have just performed (last week) a very similar migration
> for a new client whose existing server went ill but was
> still operable (just). The way we went about the migration
> was as follows:
> Backup all company and user data to USB hard drive
> Run the Exmerge utility to produce pst files for each user.
> Produce a pst file to backup the public folders from Outlook.
> Build the new server with SBS 2K, add all service packs and
> reproduce the same Domain.local, users, group policy, ISA,
> anti-virus etc.
> Restore all company and user data
> De-commission the old server and replace with new server.
> Run ICW to get Internet connection running.
> Run magic disk on each client PC but install NO client apps.
> Import each pst's to each user PC and Public folder pst.
> Set permissions on public folders for those users who
> create and modify public folders.
> Go through the usual procedure for backups etc...
>
> I hav'nt included every detail of every step but this
> procedure has worked well and the new server is now up and
> running and we completed the migration over a weekend.
> Hope this is of some use to you.
> Best wishes
> Ed
>
>
> >-----Original Message-----
> >Hi,
> >
> >This is a popular subject so I will relate what I've
> learned and just ask
> >for comments / criticism re any oversights I have in my plan.
> >
> >Background: I have a new client with a SBS 2000
> installation using ISA,
> >Exchange, OWA, Trend antivirus, file sharing. His business
> has grown to 18
> >users. No second DC, no RAID, backup inconsistent, current
> server is an
> >over-burdened AMD desktop PC with a lot of memory but
> misconfigured hard
> >disks, and is a single point of failure. Running Health
> Monitor actually
> >crashes server (all red marks!)
> >
> >Prior to my coming on-site, they purchased a new "server"
> (actually a P4
> >workstation class machine) to upgrade the facility but the
> previous provider
> >couldn't figure out how to migrate. (Being used as print
> server presently!)
> >At this point I am afraid to try to migrate him to SBS
> 2003 due to license
> >costs, lack of immediate bang-for-buck for problems above.
> Perhaps the next
> >phase after I am established as a consultant to his business.
> >
> >Plan - I will:
> >
> >1. Configure RAID 1 on the new server. (Preformat with
> NTFS using WINPE
> >environment?)
> >2. Install SBS 2000 on the new server. (How far? Use
> "fake" domain name?)
> >Configure volumes like old server, but with appropriate sizes.
> >3. Install compatible backup device on old server. Do a
> full NTbackup of the
> >existing SBS domain including file shares, Exchange &
> sysvol. (Can I backup
> >to new "fake" SBS domain volume instead? Permission
> issues, with no domain
> >trust relationship possible in SBS?)
> >4. Remove backup device from old server and install in new
> server (if
> >network backup not possible.)
> >5. Reboot new server offline (or on isolated subnet?) and
> do Directory
> >Services Restore Mode using backup of old server. New
> server now "thinks" it
> >is DC for existing network. (Which password do I use for
> Restore Mode, old
> >server or new?)
> >6. Configure network IP configurations on new server
> identical to old
> >server. Shutdown.
> >7. Physically replace old server with new, network-wise
> (internal/external
> >connections.) Take old server offline.
> >8. Reboot new server and test. Restore old server if new
> one has issues.
> >9. New server SBS elements work?! Install anti-virus
> server if OK.
> >10. Flush old server, upgrade processor and install new
> Windows 2000 Server
> >Standard.
> >11. Add old server to domain as member server, then run
> DCPromo. Replicate AD.
> >12. Split off anti-virus server duties, add print services
> to second DC.
> >13. DFS for file shares?
> >
> >Thanks in advice for comments, any answers to questions
> you can provide.
> >
> >And Jeff Middleton, TIA for your swing method, but not in
> budget. As a
> >private consultant, I have to spend time unpaid rather
> than buy stuff and
> >charge clients. My time is both invaluable and valueless,
> as long as I still
> >sleep once in a while.
> >.
> >
>

Re: Server Migration SBS 2000 to New Server Box by pmchefalo-spamfree

pmchefalo-spamfree
Mon Jan 24 23:05:03 CST 2005

Ho-hum.

Who's Harry, and why do I care about him? Oh, yeah, he wrote that "chatty
insider" best practices book.

Yes, it is your goal to talk me and every one else into buying a Swing kit.
Why are you denying it? Methinks thou dost protest too much.

I basically consider your response to be FUD. I guess you're saying that
Directory restore doesn't work, so OK, that's the message I getting here. I
saw other advice in the google groups index of this list suggesting it. I
have used the ADMT to successfully migrate a NT domain to a W2K3 domain,
albeit with a name change, so maybe that's what I should explore next.
Supposedly it can be used to reconstruct W2K domains as well as migrate.

And, since I will keep the existing server intact, why do you call the plan
a "slow crash and demolition"? If step five didn't work, I'd re-install the
existing server. See step 8. No harm done, just my time lost.

Perhaps you are addicted to charging per hour spent rather than results
achieved? My customer isn't going to pay me more if it takes longer, 'cause
I'm not going to charge him more. You withholding or giving advice is
somewhat immaterial: you're not going to get the $200, ever. I don't like
your Web site, or your style. I was hoping that you'd get the hint and not
reply to this thread, but ...

Ho-hum.

Hey, here's an idea! I'll do my dumb plan, then things will be broken, and I
can go to the Microsoft Partner break-fix newsgroup and get official help
there ...

Isn't nice to know you can still get flamed on USENET?


"Jeff Middleton [SBS-MVP]" wrote:

> Hello PMC,
>
> It's not my goal to talk you or anyone else into purchasing a Swing It!!
> Kit, not at all, not if it doesn't make sense to both of us. The kit forms a
> contract that ties me to your success, just as much as it ties you
> optimistically to my work plan. It's my goal to see everyone possible stop
> going through the shreader you are walking into. But it's my goal to help a
> lot more people that just a handful here and there, and that's why I'm using
> a business model that requires the kit to cost something reasonable, you get
> certainty of skilled help, but you get something substantial: a permanent
> resellable skill.
>
> In another 45-60 days....buy Harry's book where the chapter I've written on
> Swing Migration will be included. The reason I agreed to publish the
> information in a book with no income to me involved is so that someone like
> you can afford to get that book, get a great value, even if you can't
> justify my support services and tools in the Kit.
>
> So why not give away the Swing Docs if it's going to be in a book I make
> nothing from? Because I owe Harry a favor, and he can make a couple bucks
> per book, and get the word out. I also owe a lot of favors to a bunch of SBS
> MVPs who helped me over the years and with Swing tests, and making that book
> a part of their exposure as authors means I bring attention to their
> chapters, not just mine. That helps them and Harry, and that help all of us
> help the educated community as a whole, and that helps me because I'm part
> of the community. We all win.
>
> My goal, my total goal with Swing It!! Kits goes like this:
>
> + The IT Pro does the job in less time spent, with less confusion involved,
> and without causing a problem. He makes more money per hour, too. You get
> more time off, and better quality work.
> + The Biz owner gets the job done in less total time, probably less total
> cost, with less impact on the business, less frustration to the staff for
> needless changes. The business makes more when it runs with less down time
> and complication. That pays for upgrades.
> + The staff retains all the things they have set the way they like it at
> their workstations. Everything works on the next day, the same way.
>
> If it hasn't become apparent yet, I'm trying to make Swing Migration go big.
> Help everyone. IT Pros worldwide, the biz owners, the SBS MVPs, Harry
> Brelsford, the SBS Community UGs I now get to speak to by going around the
> world, and even my friends in SBS Team (who need more positive experiences
> illustrated by us helping them to see how we help ourselves dealing with
> things they didn't think mattered to us). The difference in price and
> service bundle between the book vs. the Reference Kit vs. the Technician Kit
> will all make perfect sense, but attract different people. I really enjoy
> thinking about the scale at which that can make my professional contribution
> help a lot of people, and it gives me a way to make a living too, at least
> for a while.
>
> I won't have to feel guilty telling anyone that the information in Harry's
> book is out somewhat out of date the day it ships, primarily because I'm
> moving forward with newer, better information. I'll feel really good about
> making the Kit documentation better and better, cover more scenarios, better
> details in what will be available that same day as a Swing It!! Kit. Harry
> realizes the huge audience he has in book sales will still want the book,
> and yet extend to people who wouldn't otherwise hear about the option to buy
> a Swing It!! Kit, including tools, support and troubleshooting tips. At
> least the book will include the correct step order some of us SBS MVPs made
> work last summer on SBS 2000 to 2003 upgrades. It will not be the most
> efficient way to do a Swing, but it will at least be a good plan, and a damn
> good deal.
>
>
> **********
>
> I think if you and your customer were to make a call to me, I could help you
> get that cost covered and make the customer love the idea. I'm not joking. I
> would love to help you out, help your customer out.
>
> You are proposing to do what you probably estimate to be about 12 hrs work,
> but is really going to be about 18, or more, depending upon your skill. A
> Swing Migration could complete that in 10-12 and you would have no
> confusion, and you wouldn't be discovering new issues along the way.
>
> The plan you have isn't going to work, not cleanly, not well, not billable,
> not reliable. At least, you are going to be about 12 hrs into the project
> and find out that you still don't have a working configuration.
>
> You will run in to SFN breaks on the new server as soon as you do the
> restore from backup in DSRM mode. I consider bare metal recovery on SBS 2000
> to be an embarrassing joke to MS because it's so ugly bad. That's what you
> are building into your upgrade.
>
> All the SBS applications will be broken at your Step 5. In Step 6, you
> probably have a good chance that you will need to rip out the TCP/IP
> services to reconfigure them. At Step 7 you will feel a lot like you are
> rally at step 1. You will have to rerun the entire SBS setup, and that's
> going to fix those SFN breaks, but you will still need to do all the same
> configuration work to fix many things. You will have a really dirty,
> probably not much more reliable installation at that point.
>
> If I were your customer, I wouldn't want you doing what you propose to my
> server if it was optional. I mean this in the most kind way. What you
> outlined there isn't an upgrade, it's a slow crash and demolition followed
> by a patched together recovery process that, as yet, I don't think you have
> ever done one of these by this method before? If you want to learn a
> process, don't waste your time on this approach, it's not going to work.
>
>
>
> "PMC" <pmchefalo-spamfree@hotmail.com> wrote in message
> news:B5AF2B4D-8A3F-4A20-BA2E-8379421B6015@microsoft.com...
> > Hi,
> >
> > This is a popular subject so I will relate what I've learned and just ask
> > for comments / criticism re any oversights I have in my plan.
> >
> > Background: I have a new client with a SBS 2000 installation using ISA,
> > Exchange, OWA, Trend antivirus, file sharing. His business has grown to 18
> > users. No second DC, no RAID, backup inconsistent, current server is an
> > over-burdened AMD desktop PC with a lot of memory but misconfigured hard
> > disks, and is a single point of failure. Running Health Monitor actually
> > crashes server (all red marks!)
> >
> > Prior to my coming on-site, they purchased a new "server" (actually a P4
> > workstation class machine) to upgrade the facility but the previous
> provider
> > couldn't figure out how to migrate. (Being used as print server
> presently!)
> > At this point I am afraid to try to migrate him to SBS 2003 due to license
> > costs, lack of immediate bang-for-buck for problems above. Perhaps the
> next
> > phase after I am established as a consultant to his business.
> >
> > Plan - I will:
> >
> > 1. Configure RAID 1 on the new server. (Preformat with NTFS using WINPE
> > environment?)
> > 2. Install SBS 2000 on the new server. (How far? Use "fake" domain name?)
> > Configure volumes like old server, but with appropriate sizes.
> > 3. Install compatible backup device on old server. Do a full NTbackup of
> the
> > existing SBS domain including file shares, Exchange & sysvol. (Can I
> backup
> > to new "fake" SBS domain volume instead? Permission issues, with no domain
> > trust relationship possible in SBS?)
> > 4. Remove backup device from old server and install in new server (if
> > network backup not possible.)
> > 5. Reboot new server offline (or on isolated subnet?) and do Directory
> > Services Restore Mode using backup of old server. New server now "thinks"
> it
> > is DC for existing network. (Which password do I use for Restore Mode, old
> > server or new?)
> > 6. Configure network IP configurations on new server identical to old
> > server. Shutdown.
> > 7. Physically replace old server with new, network-wise (internal/external
> > connections.) Take old server offline.
> > 8. Reboot new server and test. Restore old server if new one has issues.
> > 9. New server SBS elements work?! Install anti-virus server if OK.
> > 10. Flush old server, upgrade processor and install new Windows 2000
> Server
> > Standard.
> > 11. Add old server to domain as member server, then run DCPromo. Replicate
> AD.
> > 12. Split off anti-virus server duties, add print services to second DC.
> > 13. DFS for file shares?
> >
> > Thanks in advice for comments, any answers to questions you can provide.
> >
> > And Jeff Middleton, TIA for your swing method, but not in budget. As a
> > private consultant, I have to spend time unpaid rather than buy stuff and
> > charge clients. My time is both invaluable and valueless, as long as I
> still
> > sleep once in a while.
>
>
>

RE: Server Migration SBS 2000 to New Server Box by Ed

Ed
Tue Jan 25 05:51:13 CST 2005

Hi PMC
When you add users from the "To Do" list in SBS you are
asked if you want to set up a networking disk and what
client apps are to be installed. Leave this until the last
computer has been setup and then agree to create the disk
(magic). This allows you to specify which users can use
which client PC and what client applications (eg. firewall
client, shared modem etc....) are installed on each
client. It really makes the client config a lot easier to
manage. If you plan to do the migration I would recommend
the way we migrated. It does work and it's a very good
learning excecise for the various components of SBS.
What ever you decide I wish you the best of luck
Cheers,
Ed
>-----Original Message-----
>Ed,
>
>Your plan is similar to the migration plan Chris cites
from Microsoft for
>SBS 4.5 to SBS 2000.
>
>What is the "magic disk?"
>
>Thanks,
>Pat
>
>"Ed Clark" wrote:
>
>> Hi,
>> We have just performed (last week) a very similar migration
>> for a new client whose existing server went ill but was
>> still operable (just). The way we went about the migration
>> was as follows:
>> Backup all company and user data to USB hard drive
>> Run the Exmerge utility to produce pst files for each user.
>> Produce a pst file to backup the public folders from
Outlook.
>> Build the new server with SBS 2K, add all service packs and
>> reproduce the same Domain.local, users, group policy, ISA,
>> anti-virus etc.
>> Restore all company and user data
>> De-commission the old server and replace with new server.
>> Run ICW to get Internet connection running.
>> Run magic disk on each client PC but install NO client apps.
>> Import each pst's to each user PC and Public folder pst.
>> Set permissions on public folders for those users who
>> create and modify public folders.
>> Go through the usual procedure for backups etc...
>>
>> I hav'nt included every detail of every step but this
>> procedure has worked well and the new server is now up and
>> running and we completed the migration over a weekend.
>> Hope this is of some use to you.
>> Best wishes
>> Ed
>>
>>
>> >-----Original Message-----
>> >Hi,
>> >
>> >This is a popular subject so I will relate what I've
>> learned and just ask
>> >for comments / criticism re any oversights I have in my
plan.
>> >
>> >Background: I have a new client with a SBS 2000
>> installation using ISA,
>> >Exchange, OWA, Trend antivirus, file sharing. His business
>> has grown to 18
>> >users. No second DC, no RAID, backup inconsistent, current
>> server is an
>> >over-burdened AMD desktop PC with a lot of memory but
>> misconfigured hard
>> >disks, and is a single point of failure. Running Health
>> Monitor actually
>> >crashes server (all red marks!)
>> >
>> >Prior to my coming on-site, they purchased a new "server"
>> (actually a P4
>> >workstation class machine) to upgrade the facility but the
>> previous provider
>> >couldn't figure out how to migrate. (Being used as print
>> server presently!)
>> >At this point I am afraid to try to migrate him to SBS
>> 2003 due to license
>> >costs, lack of immediate bang-for-buck for problems above.
>> Perhaps the next
>> >phase after I am established as a consultant to his
business.
>> >
>> >Plan - I will:
>> >
>> >1. Configure RAID 1 on the new server. (Preformat with
>> NTFS using WINPE
>> >environment?)
>> >2. Install SBS 2000 on the new server. (How far? Use
>> "fake" domain name?)
>> >Configure volumes like old server, but with appropriate
sizes.
>> >3. Install compatible backup device on old server. Do a
>> full NTbackup of the
>> >existing SBS domain including file shares, Exchange &
>> sysvol. (Can I backup
>> >to new "fake" SBS domain volume instead? Permission
>> issues, with no domain
>> >trust relationship possible in SBS?)
>> >4. Remove backup device from old server and install in new
>> server (if
>> >network backup not possible.)
>> >5. Reboot new server offline (or on isolated subnet?) and
>> do Directory
>> >Services Restore Mode using backup of old server. New
>> server now "thinks" it
>> >is DC for existing network. (Which password do I use for
>> Restore Mode, old
>> >server or new?)
>> >6. Configure network IP configurations on new server
>> identical to old
>> >server. Shutdown.
>> >7. Physically replace old server with new, network-wise
>> (internal/external
>> >connections.) Take old server offline.
>> >8. Reboot new server and test. Restore old server if new
>> one has issues.
>> >9. New server SBS elements work?! Install anti-virus
>> server if OK.
>> >10. Flush old server, upgrade processor and install new
>> Windows 2000 Server
>> >Standard.
>> >11. Add old server to domain as member server, then run
>> DCPromo. Replicate AD.
>> >12. Split off anti-virus server duties, add print services
>> to second DC.
>> >13. DFS for file shares?
>> >
>> >Thanks in advice for comments, any answers to questions
>> you can provide.
>> >
>> >And Jeff Middleton, TIA for your swing method, but not in
>> budget. As a
>> >private consultant, I have to spend time unpaid rather
>> than buy stuff and
>> >charge clients. My time is both invaluable and valueless,
>> as long as I still
>> >sleep once in a while.
>> >.
>> >
>>
>.
>

RE: Server Migration SBS 2000 to New Server Box by pmchefalo-spamfree

pmchefalo-spamfree
Tue Jan 25 09:25:02 CST 2005

Hi, Ed.

Thanks for the response. I've set up several SBS 2003 installations (never
2000 before) so this was unfamiliar to me. Of course in 2003, this runs off
the domain login; when you login with the PC it asks if you want to install
the applications, if you accept the default login script. I more often ran
the applications installation command from the "Run" dialogue.

A nicer feature in SBS 2003 I guess.

Thanks,
Pat

"Ed" wrote:

> Hi PMC
> When you add users from the "To Do" list in SBS you are
> asked if you want to set up a networking disk and what
> client apps are to be installed. Leave this until the last
> computer has been setup and then agree to create the disk
> (magic). This allows you to specify which users can use
> which client PC and what client applications (eg. firewall
> client, shared modem etc....) are installed on each
> client. It really makes the client config a lot easier to
> manage. If you plan to do the migration I would recommend
> the way we migrated. It does work and it's a very good
> learning excecise for the various components of SBS.
> What ever you decide I wish you the best of luck
> Cheers,
> Ed
> >-----Original Message-----
> >Ed,
> >
> >Your plan is similar to the migration plan Chris cites
> from Microsoft for
> >SBS 4.5 to SBS 2000.
> >
> >What is the "magic disk?"
> >
> >Thanks,
> >Pat
> >
> >"Ed Clark" wrote:
> >
> >> Hi,
> >> We have just performed (last week) a very similar migration
> >> for a new client whose existing server went ill but was
> >> still operable (just). The way we went about the migration
> >> was as follows:
> >> Backup all company and user data to USB hard drive
> >> Run the Exmerge utility to produce pst files for each user.
> >> Produce a pst file to backup the public folders from
> Outlook.
> >> Build the new server with SBS 2K, add all service packs and
> >> reproduce the same Domain.local, users, group policy, ISA,
> >> anti-virus etc.
> >> Restore all company and user data
> >> De-commission the old server and replace with new server.
> >> Run ICW to get Internet connection running.
> >> Run magic disk on each client PC but install NO client apps.
> >> Import each pst's to each user PC and Public folder pst.
> >> Set permissions on public folders for those users who
> >> create and modify public folders.
> >> Go through the usual procedure for backups etc...
> >>
> >> I hav'nt included every detail of every step but this
> >> procedure has worked well and the new server is now up and
> >> running and we completed the migration over a weekend.
> >> Hope this is of some use to you.
> >> Best wishes
> >> Ed
> >>
> >>
> >> >-----Original Message-----
> >> >Hi,
> >> >
> >> >This is a popular subject so I will relate what I've
> >> learned and just ask
> >> >for comments / criticism re any oversights I have in my
> plan.
> >> >
> >> >Background: I have a new client with a SBS 2000
> >> installation using ISA,
> >> >Exchange, OWA, Trend antivirus, file sharing. His business
> >> has grown to 18
> >> >users. No second DC, no RAID, backup inconsistent, current
> >> server is an
> >> >over-burdened AMD desktop PC with a lot of memory but
> >> misconfigured hard
> >> >disks, and is a single point of failure. Running Health
> >> Monitor actually
> >> >crashes server (all red marks!)
> >> >
> >> >Prior to my coming on-site, they purchased a new "server"
> >> (actually a P4
> >> >workstation class machine) to upgrade the facility but the
> >> previous provider
> >> >couldn't figure out how to migrate. (Being used as print
> >> server presently!)
> >> >At this point I am afraid to try to migrate him to SBS
> >> 2003 due to license
> >> >costs, lack of immediate bang-for-buck for problems above.
> >> Perhaps the next
> >> >phase after I am established as a consultant to his
> business.
> >> >
> >> >Plan - I will:
> >> >
> >> >1. Configure RAID 1 on the new server. (Preformat with
> >> NTFS using WINPE
> >> >environment?)
> >> >2. Install SBS 2000 on the new server. (How far? Use
> >> "fake" domain name?)
> >> >Configure volumes like old server, but with appropriate
> sizes.
> >> >3. Install compatible backup device on old server. Do a
> >> full NTbackup of the
> >> >existing SBS domain including file shares, Exchange &
> >> sysvol. (Can I backup
> >> >to new "fake" SBS domain volume instead? Permission
> >> issues, with no domain
> >> >trust relationship possible in SBS?)
> >> >4. Remove backup device from old server and install in new
> >> server (if
> >> >network backup not possible.)
> >> >5. Reboot new server offline (or on isolated subnet?) and
> >> do Directory
> >> >Services Restore Mode using backup of old server. New
> >> server now "thinks" it
> >> >is DC for existing network. (Which password do I use for
> >> Restore Mode, old
> >> >server or new?)
> >> >6. Configure network IP configurations on new server
> >> identical to old
> >> >server. Shutdown.
> >> >7. Physically replace old server with new, network-wise
> >> (internal/external
> >> >connections.) Take old server offline.
> >> >8. Reboot new server and test. Restore old server if new
> >> one has issues.
> >> >9. New server SBS elements work?! Install anti-virus
> >> server if OK.
> >> >10. Flush old server, upgrade processor and install new
> >> Windows 2000 Server
> >> >Standard.
> >> >11. Add old server to domain as member server, then run
> >> DCPromo. Replicate AD.
> >> >12. Split off anti-virus server duties, add print services
> >> to second DC.
> >> >13. DFS for file shares?
> >> >
> >> >Thanks in advice for comments, any answers to questions
> >> you can provide.
> >> >
> >> >And Jeff Middleton, TIA for your swing method, but not in
> >> budget. As a
> >> >private consultant, I have to spend time unpaid rather
> >> than buy stuff and
> >> >charge clients. My time is both invaluable and valueless,
> >> as long as I still
> >> >sleep once in a while.
> >> >.
> >> >
> >>
> >.
> >
>

Re: Server Migration SBS 2000 to New Server Box by Jeff

Jeff
Tue Jan 25 10:08:04 CST 2005

I tell you what I do like about USENET. We both get to talk.

It doesn't matter if someone asks a great question or a dumb one. As long as
there is someone willing to try to speak to their level of skill, they get
help, somebody tries to help. The universal turn-off for everyone is people
pretending to be smarter than they are, and using flaming to back away.

But better than that, even if the first guy who asked the question decides
that he can't use the