SBS 2003 Physical to Virtual

I would like to convert an existing SBS 2003 system to Hyper-V. I have Server
2008 on a new server with Hyper-V role installed. I have several other
virtual machines set up and working without problems. I've not seen any
decent write-ups on the conversion steps. I've researched the subject but
haven't come up with any good information. Based on what I've read, this is
not a trivial task. The VMware converter utilities don't appear to work well
for SBS.
Do I need to install the OS in a new virtual machine, update it to all the
latest patches and service packs, then do an NTbackup restore? If I do that
what other issues will I face.
I would prefer to avoid the expense of a swing migration as this is just a
small development network with only 10 users.
Can someone point me to a good source for info on this subject please?

Thanks in advance,
Steve

I don't do anything virtualized except when I am doing swing
migrations. I have installed a new server on new hardware and done a
restore from myold server's NTBackup and it worked fine. Why not try
that. It should only take a few hours in your VM system. I just had a
few minor cleanup items like getting nics to work but that was only a
few minutes to clean that up.

On Sat, 14 Mar 2009 05:50:01 -0700, Steve Schwab
<SteveSchwab@discussions.microsoft.com> wrote:

>I would like to convert an existing SBS 2003 system to Hyper-V. I have Server
>2008 on a new server with Hyper-V role installed. I have several other
>virtual machines set up and working without problems. I've not seen any
>decent write-ups on the conversion steps. I've researched the subject but
>haven't come up with any good information. Based on what I've read, this is
>not a trivial task. The VMware converter utilities don't appear to work well
>for SBS.
>Do I need to install the OS in a new virtual machine, update it to all the
>latest patches and service packs, then do an NTbackup restore? If I do that
>what other issues will I face.
>I would prefer to avoid the expense of a swing migration as this is just a
>small development network with only 10 users.
>Can someone point me to a good source for info on this subject please?
>
>Thanks in advance,
>Steve
See what SBS support is working on
http://blogs.technet.com/sbs/default.aspx
Check your SBS with the SBS Best Practices Analyzer
http://blogs.technet.com/sbs/archive...A/default.aspx

yeah, treat is as a standard 'restore to new hardware'. The fact the new
hardware is actually being provided by a virtualisation system simply means
you get to play a few times if things go wrong.

NOTE: For the restore you only need the base Windows OS and your current
Windows Service Pack, you do not need to fully install/configure/update SBS.

A search of the group for 'new hardware' should bring up related discussion,
including one commented to today about success. The comment today includes a
mention about networking and it seems we forgot to offer a piece of advice
on this. If you don't mind losing network connectivity on your OriginalSBS
you can change it's NIC(s) to use the MS Loopback Adapter and perform a
backup (just not across the network :-). This means that when you restore
you also restore networking to the loopback adapter(s), so a) the system
doesn't try to jump on your network immediately and b) initial start of the
restored system can properly see AD. You then adjust the restored system to
use your actual (or in this case virtual) NIC(s).

After performing the backup of OriginalSBS with the Loopback Adapters in
place you can rejig it back to using your real network cards so that
operation can continue until you are ready commit to the new system.

--
SBS remote support services. (Fees apply)
mickm at mickmalloy dot dyndns dot org

"Jim Behning SBS MVP" <jimbehning@doesthisblockpork.mindspring.com> wrote in
message news:ceenr4pmsh4fo9181u61er9knu518h9ld3@4ax.com...
>I don't do anything virtualized except when I am doing swing
> migrations. I have installed a new server on new hardware and done a
> restore from myold server's NTBackup and it worked fine. Why not try
> that. It should only take a few hours in your VM system. I just had a
> few minor cleanup items like getting nics to work but that was only a
> few minutes to clean that up.
>
> On Sat, 14 Mar 2009 05:50:01 -0700, Steve Schwab
> <SteveSchwab@discussions.microsoft.com> wrote:
>
>>I would like to convert an existing SBS 2003 system to Hyper-V. I have
>>Server
>>2008 on a new server with Hyper-V role installed. I have several other
>>virtual machines set up and working without problems. I've not seen any
>>decent write-ups on the conversion steps. I've researched the subject but
>>haven't come up with any good information. Based on what I've read, this
>>is
>>not a trivial task. The VMware converter utilities don't appear to work
>>well
>>for SBS.
>>Do I need to install the OS in a new virtual machine, update it to all the
>>latest patches and service packs, then do an NTbackup restore? If I do
>>that
>>what other issues will I face.
>>I would prefer to avoid the expense of a swing migration as this is just a
>>small development network with only 10 users.
>>Can someone point me to a good source for info on this subject please?
>>
>>Thanks in advance,
>>Steve
> See what SBS support is working on
> http://blogs.technet.com/sbs/default.aspx
> Check your SBS with the SBS Best Practices Analyzer
> http://blogs.technet.com/sbs/archive...A/default.aspx

Thanks Jim and SuperGumby,
I figured the NTbackup routine would be the approach to take. SuperGumby,
you're right about just starting over if things don't go well. Since I've
never done a restore to new hardware it will be a good experience for me. I
didn't know that all you needed was to be up to date on Service Pack Level. I
assume that holds true for Exchange as well?
I think I'll try the Loopback Adapter trick as well.
Thanks for the help

"SuperGumby [SBS MVP]" wrote:

> yeah, treat is as a standard 'restore to new hardware'. The fact the new
> hardware is actually being provided by a virtualisation system simply means
> you get to play a few times if things go wrong.
>
> NOTE: For the restore you only need the base Windows OS and your current
> Windows Service Pack, you do not need to fully install/configure/update SBS.
>
> A search of the group for 'new hardware' should bring up related discussion,
> including one commented to today about success. The comment today includes a
> mention about networking and it seems we forgot to offer a piece of advice
> on this. If you don't mind losing network connectivity on your OriginalSBS
> you can change it's NIC(s) to use the MS Loopback Adapter and perform a
> backup (just not across the network :-). This means that when you restore
> you also restore networking to the loopback adapter(s), so a) the system
> doesn't try to jump on your network immediately and b) initial start of the
> restored system can properly see AD. You then adjust the restored system to
> use your actual (or in this case virtual) NIC(s).
>
> After performing the backup of OriginalSBS with the Loopback Adapters in
> place you can rejig it back to using your real network cards so that
> operation can continue until you are ready commit to the new system.
>
> --
> SBS remote support services. (Fees apply)
> mickm at mickmalloy dot dyndns dot org
>
> "Jim Behning SBS MVP" <jimbehning@doesthisblockpork.mindspring.com> wrote in
> message news:ceenr4pmsh4fo9181u61er9knu518h9ld3@4ax.com...
> >I don't do anything virtualized except when I am doing swing
> > migrations. I have installed a new server on new hardware and done a
> > restore from myold server's NTBackup and it worked fine. Why not try
> > that. It should only take a few hours in your VM system. I just had a
> > few minor cleanup items like getting nics to work but that was only a
> > few minutes to clean that up.
> >
> > On Sat, 14 Mar 2009 05:50:01 -0700, Steve Schwab
> > <SteveSchwab@discussions.microsoft.com> wrote:
> >
> >>I would like to convert an existing SBS 2003 system to Hyper-V. I have
> >>Server
> >>2008 on a new server with Hyper-V role installed. I have several other
> >>virtual machines set up and working without problems. I've not seen any
> >>decent write-ups on the conversion steps. I've researched the subject but
> >>haven't come up with any good information. Based on what I've read, this
> >>is
> >>not a trivial task. The VMware converter utilities don't appear to work
> >>well
> >>for SBS.
> >>Do I need to install the OS in a new virtual machine, update it to all the
> >>latest patches and service packs, then do an NTbackup restore? If I do
> >>that
> >>what other issues will I face.
> >>I would prefer to avoid the expense of a swing migration as this is just a
> >>small development network with only 10 users.
> >>Can someone point me to a good source for info on this subject please?
> >>
> >>Thanks in advance,
> >>Steve
> > See what SBS support is working on
> > http://blogs.technet.com/sbs/default.aspx
> > Check your SBS with the SBS Best Practices Analyzer
> > http://blogs.technet.com/sbs/archive...A/default.aspx
>
>

I poked around and answered my own question about the backup.
Thanks again,
Steve

"Steve Schwab" wrote:

> Thanks Jim and SuperGumby,
> I figured the NTbackup routine would be the approach to take. SuperGumby,
> you're right about just starting over if things don't go well. Since I've
> never done a restore to new hardware it will be a good experience for me. I
> didn't know that all you needed was to be up to date on Service Pack Level. I
> assume that holds true for Exchange as well?
> I think I'll try the Loopback Adapter trick as well.
> Thanks for the help
>
> "SuperGumby [SBS MVP]" wrote:
>
> > yeah, treat is as a standard 'restore to new hardware'. The fact the new
> > hardware is actually being provided by a virtualisation system simply means
> > you get to play a few times if things go wrong.
> >
> > NOTE: For the restore you only need the base Windows OS and your current
> > Windows Service Pack, you do not need to fully install/configure/update SBS.
> >
> > A search of the group for 'new hardware' should bring up related discussion,
> > including one commented to today about success. The comment today includes a
> > mention about networking and it seems we forgot to offer a piece of advice
> > on this. If you don't mind losing network connectivity on your OriginalSBS
> > you can change it's NIC(s) to use the MS Loopback Adapter and perform a
> > backup (just not across the network :-). This means that when you restore
> > you also restore networking to the loopback adapter(s), so a) the system
> > doesn't try to jump on your network immediately and b) initial start of the
> > restored system can properly see AD. You then adjust the restored system to
> > use your actual (or in this case virtual) NIC(s).
> >
> > After performing the backup of OriginalSBS with the Loopback Adapters in
> > place you can rejig it back to using your real network cards so that
> > operation can continue until you are ready commit to the new system.
> >
> > --
> > SBS remote support services. (Fees apply)
> > mickm at mickmalloy dot dyndns dot org
> >
> > "Jim Behning SBS MVP" <jimbehning@doesthisblockpork.mindspring.com> wrote in
> > message news:ceenr4pmsh4fo9181u61er9knu518h9ld3@4ax.com...
> > >I don't do anything virtualized except when I am doing swing
> > > migrations. I have installed a new server on new hardware and done a
> > > restore from myold server's NTBackup and it worked fine. Why not try
> > > that. It should only take a few hours in your VM system. I just had a
> > > few minor cleanup items like getting nics to work but that was only a
> > > few minutes to clean that up.
> > >
> > > On Sat, 14 Mar 2009 05:50:01 -0700, Steve Schwab
> > > <SteveSchwab@discussions.microsoft.com> wrote:
> > >
> > >>I would like to convert an existing SBS 2003 system to Hyper-V. I have
> > >>Server
> > >>2008 on a new server with Hyper-V role installed. I have several other
> > >>virtual machines set up and working without problems. I've not seen any
> > >>decent write-ups on the conversion steps. I've researched the subject but
> > >>haven't come up with any good information. Based on what I've read, this
> > >>is
> > >>not a trivial task. The VMware converter utilities don't appear to work
> > >>well
> > >>for SBS.
> > >>Do I need to install the OS in a new virtual machine, update it to all the
> > >>latest patches and service packs, then do an NTbackup restore? If I do
> > >>that
> > >>what other issues will I face.
> > >>I would prefer to avoid the expense of a swing migration as this is just a
> > >>small development network with only 10 users.
> > >>Can someone point me to a good source for info on this subject please?
> > >>
> > >>Thanks in advance,
> > >>Steve
> > > See what SBS support is working on
> > > http://blogs.technet.com/sbs/default.aspx
> > > Check your SBS with the SBS Best Practices Analyzer
> > > http://blogs.technet.com/sbs/archive...A/default.aspx
> >
> >

You don't need to worry about Exchange, at the time of restore Exchange
should not be on the box.

Again, you install just the base OS from SBS media and apply the same level
Service Pack to Windows as exists on the backup. Everything else (Exchange,
sharepoint, SBS customisations) gets restored to the system from the backup.
Interrupt/cancel the 'SBS' installation process after the basic windows
install is complete. No Exchange, not a DC, just Windows.

and yes, I suggest that this is a great opportunity to test your Disaster
Recovery Strategy. Starting with the last known backup, your installation
CD/DVD, and very little else but the grey matter between your ears, can you
restore the system?

--
SBS remote support services. (Fees apply)
mickm at mickmalloy dot dyndns dot org

"Steve Schwab" <SteveSchwab@discussions.microsoft.com> wrote in message
news:F77039CF-20D4-415A-870A-4122E9E2A12F@microsoft.com...
> Thanks Jim and SuperGumby,
> I figured the NTbackup routine would be the approach to take. SuperGumby,
> you're right about just starting over if things don't go well. Since I've
> never done a restore to new hardware it will be a good experience for me.
> I
> didn't know that all you needed was to be up to date on Service Pack
> Level. I
> assume that holds true for Exchange as well?
> I think I'll try the Loopback Adapter trick as well.
> Thanks for the help
>
> "SuperGumby [SBS MVP]" wrote:
>
>> yeah, treat is as a standard 'restore to new hardware'. The fact the new
>> hardware is actually being provided by a virtualisation system simply
>> means
>> you get to play a few times if things go wrong.
>>
>> NOTE: For the restore you only need the base Windows OS and your current
>> Windows Service Pack, you do not need to fully install/configure/update
>> SBS.
>>
>> A search of the group for 'new hardware' should bring up related
>> discussion,
>> including one commented to today about success. The comment today
>> includes a
>> mention about networking and it seems we forgot to offer a piece of
>> advice
>> on this. If you don't mind losing network connectivity on your
>> OriginalSBS
>> you can change it's NIC(s) to use the MS Loopback Adapter and perform a
>> backup (just not across the network :-). This means that when you restore
>> you also restore networking to the loopback adapter(s), so a) the system
>> doesn't try to jump on your network immediately and b) initial start of
>> the
>> restored system can properly see AD. You then adjust the restored system
>> to
>> use your actual (or in this case virtual) NIC(s).
>>
>> After performing the backup of OriginalSBS with the Loopback Adapters in
>> place you can rejig it back to using your real network cards so that
>> operation can continue until you are ready commit to the new system.
>>
>> --
>> SBS remote support services. (Fees apply)
>> mickm at mickmalloy dot dyndns dot org
>>
>> "Jim Behning SBS MVP" <jimbehning@doesthisblockpork.mindspring.com> wrote
>> in
>> message news:ceenr4pmsh4fo9181u61er9knu518h9ld3@4ax.com...
>> >I don't do anything virtualized except when I am doing swing
>> > migrations. I have installed a new server on new hardware and done a
>> > restore from myold server's NTBackup and it worked fine. Why not try
>> > that. It should only take a few hours in your VM system. I just had a
>> > few minor cleanup items like getting nics to work but that was only a
>> > few minutes to clean that up.
>> >
>> > On Sat, 14 Mar 2009 05:50:01 -0700, Steve Schwab
>> > <SteveSchwab@discussions.microsoft.com> wrote:
>> >
>> >>I would like to convert an existing SBS 2003 system to Hyper-V. I have
>> >>Server
>> >>2008 on a new server with Hyper-V role installed. I have several other
>> >>virtual machines set up and working without problems. I've not seen any
>> >>decent write-ups on the conversion steps. I've researched the subject
>> >>but
>> >>haven't come up with any good information. Based on what I've read,
>> >>this
>> >>is
>> >>not a trivial task. The VMware converter utilities don't appear to work
>> >>well
>> >>for SBS.
>> >>Do I need to install the OS in a new virtual machine, update it to all
>> >>the
>> >>latest patches and service packs, then do an NTbackup restore? If I do
>> >>that
>> >>what other issues will I face.
>> >>I would prefer to avoid the expense of a swing migration as this is
>> >>just a
>> >>small development network with only 10 users.
>> >>Can someone point me to a good source for info on this subject please?
>> >>
>> >>Thanks in advance,
>> >>Steve
>> > See what SBS support is working on
>> > http://blogs.technet.com/sbs/default.aspx
>> > Check your SBS with the SBS Best Practices Analyzer
>> > http://blogs.technet.com/sbs/archive...A/default.aspx
>>
>>

All you should need to do is get the operating system at the correct
service pack. Get your partitions set up. Let the restore go. Maybe
you already had that figured out.

On Sat, 14 Mar 2009 16:41:00 -0700, Steve Schwab
<SteveSchwab@discussions.microsoft.com> wrote:

>I poked around and answered my own question about the backup.
>Thanks again,
>Steve
>
>"Steve Schwab" wrote:
>
>> Thanks Jim and SuperGumby,
>> I figured the NTbackup routine would be the approach to take. SuperGumby,
>> you're right about just starting over if things don't go well. Since I've
>> never done a restore to new hardware it will be a good experience for me. I
>> didn't know that all you needed was to be up to date on Service Pack Level. I
>> assume that holds true for Exchange as well?
>> I think I'll try the Loopback Adapter trick as well.
>> Thanks for the help
>>
>> "SuperGumby [SBS MVP]" wrote:
>>
>> > yeah, treat is as a standard 'restore to new hardware'. The fact the new
>> > hardware is actually being provided by a virtualisation system simply means
>> > you get to play a few times if things go wrong.
>> >
>> > NOTE: For the restore you only need the base Windows OS and your current
>> > Windows Service Pack, you do not need to fully install/configure/update SBS.
>> >
>> > A search of the group for 'new hardware' should bring up related discussion,
>> > including one commented to today about success. The comment today includes a
>> > mention about networking and it seems we forgot to offer a piece of advice
>> > on this. If you don't mind losing network connectivity on your OriginalSBS
>> > you can change it's NIC(s) to use the MS Loopback Adapter and perform a
>> > backup (just not across the network :-). This means that when you restore
>> > you also restore networking to the loopback adapter(s), so a) the system
>> > doesn't try to jump on your network immediately and b) initial start of the
>> > restored system can properly see AD. You then adjust the restored system to
>> > use your actual (or in this case virtual) NIC(s).
>> >
>> > After performing the backup of OriginalSBS with the Loopback Adapters in
>> > place you can rejig it back to using your real network cards so that
>> > operation can continue until you are ready commit to the new system.
>> >
>> > --
>> > SBS remote support services. (Fees apply)
>> > mickm at mickmalloy dot dyndns dot org
>> >
>> > "Jim Behning SBS MVP" <jimbehning@doesthisblockpork.mindspring.com> wrote in
>> > message news:ceenr4pmsh4fo9181u61er9knu518h9ld3@4ax.com...
>> > >I don't do anything virtualized except when I am doing swing
>> > > migrations. I have installed a new server on new hardware and done a
>> > > restore from myold server's NTBackup and it worked fine. Why not try
>> > > that. It should only take a few hours in your VM system. I just had a
>> > > few minor cleanup items like getting nics to work but that was only a
>> > > few minutes to clean that up.
>> > >
>> > > On Sat, 14 Mar 2009 05:50:01 -0700, Steve Schwab
>> > > <SteveSchwab@discussions.microsoft.com> wrote:
>> > >
>> > >>I would like to convert an existing SBS 2003 system to Hyper-V. I have
>> > >>Server
>> > >>2008 on a new server with Hyper-V role installed. I have several other
>> > >>virtual machines set up and working without problems. I've not seen any
>> > >>decent write-ups on the conversion steps. I've researched the subject but
>> > >>haven't come up with any good information. Based on what I've read, this
>> > >>is
>> > >>not a trivial task. The VMware converter utilities don't appear to work
>> > >>well
>> > >>for SBS.
>> > >>Do I need to install the OS in a new virtual machine, update it to all the
>> > >>latest patches and service packs, then do an NTbackup restore? If I do
>> > >>that
>> > >>what other issues will I face.
>> > >>I would prefer to avoid the expense of a swing migration as this is just a
>> > >>small development network with only 10 users.
>> > >>Can someone point me to a good source for info on this subject please?
>> > >>
>> > >>Thanks in advance,
>> > >>Steve
>> > > See what SBS support is working on
>> > > http://blogs.technet.com/sbs/default.aspx
>> > > Check your SBS with the SBS Best Practices Analyzer
>> > > http://blogs.technet.com/sbs/archive...A/default.aspx
>> >
>> >
See what SBS support is working on
http://blogs.technet.com/sbs/default.aspx
Check your SBS with the SBS Best Practices Analyzer
http://blogs.technet.com/sbs/archive...A/default.aspx