Officially, not supported. Realistically, works fine, with the usual
limitations of Hyper-V VMs. (No USB, no tape, and no FAX). If you expect
that second domain to actually connect to the internet, you'll need to have
a dedicated NIC for that subnet. Otherwise, if it's only to maintain a
running SBS 2k3, with no real connection, then you can use an internal
network that only other virtualized machines and the host can see.
--
Charlie.
http://msmvps.com/blogs/russel
"Guzzifrank" <> wrote in message
news:8CA4E2CC-6B3C-4CFF-8736-...
> We want to reduce equipment in the lab. We have a well functioning SBS2008
> Standard domain running with one sbs2008 (8 GB) server and a second
> win2008 (8 GB system mem) server running our AVG service and Hyper-v.
> Under Hyper-v we have two guests, an XP Pro running old version of
> Quickbooks for company accounting and a Win2003R2 server running
> BlackBerry Enterprise Server running 4 blackberry phones. We have 10 real
> Vista Business workstations which will go Windows 7 Pro over the next two
> weeks. This all runs on 192.168.8.x and uses one public static IP address.
>
> We also have a second domain running SBS2003 R2 (4 GB) that we keep up to
> help support four SBS2003 client sites. We do all contract work for them
> and need to keep a working domain. We have one XP Pro and one Vista
> Business workstation running just to test changes before implementation.
>
> We have just received a Dell T605 with 32 GB and four 1.5 TB drives so we
> want to add it to the sbs2008 domain and make the whole sbs2003 completely
> virtual.
>
> do you have comment on Hyper-v and SBS2003? I do want to end up with a
> 'one nic' sbs2003 domain on a public static IP address.
Linear Mode
