1.) Not supported. Full stop.
2.) Certainly works, many of us have done it. But see #1.
3.) I'd want at least one additional NIC on the hyper-v parent. You should
always have a dedicated management NIC that isn't used by Hyper-V or any of
the guests.
4.) What other VMs are you planning on using on that box? SBS will only see
4GB of the RAM.
5.) Do not install any other roles on your parent partition (host).
Especially since your firewall is running on a guest.
6.) You should not join the parent to the domain.
7.) Reminder. See #1.

--
Charlie.
http://msmvps.com/blogs/russel






"Daniel Jewel" <cyberdudeiq@newsgroup> wrote in message
news:uKYpkRmeKHA.1652@newsgroup

> Hi all,
>
> I am flirting with the idea to put to test the following virtualization:
>
> Server 2008 R2 + Hyper-V as host and ( HW = Xeon Quad; 8 GBs RAM; RAID 5;
> 2 NICs)
> SBS 2003 R3 as guest VM
>
> I need some ideas, gotchas and tips on how to make it workable
>
> Thanks,
>
> Dan
>
>

Thanks guys...

I do not plan on using FAX and USB Backup can be re-routed to member server
(USB) so no issues there.
I plan on 4 partitions for the host. Parent partition with Core Server and
Hyper-V services only if possible!?
SBS on a dedicated a 300GBs partition
Will ISA work with 2 NICs and provide security to the LAN?

Dan

"Charlie Russel - MVP" <Charlie@newsgroup> wrote in message
news:eyJmx6neKHA.2780@newsgroup

> 1.) Not supported. Full stop.
> 2.) Certainly works, many of us have done it. But see #1.
> 3.) I'd want at least one additional NIC on the hyper-v parent. You should
> always have a dedicated management NIC that isn't used by Hyper-V or any
> of the guests.
> 4.) What other VMs are you planning on using on that box? SBS will only
> see 4GB of the RAM.
> 5.) Do not install any other roles on your parent partition (host).
> Especially since your firewall is running on a guest.
> 6.) You should not join the parent to the domain.
> 7.) Reminder. See #1.
>
> --
> Charlie.
> http://msmvps.com/blogs/russel
>
>
>
>
> "Daniel Jewel" <cyberdudeiq@newsgroup> wrote in message
> news:uKYpkRmeKHA.1652@newsgroup

>> Hi all,
>>
>> I am flirting with the idea to put to test the following virtualization:
>>
>> Server 2008 R2 + Hyper-V as host and ( HW = Xeon Quad; 8 GBs RAM; RAID 5;
>> 2 NICs)
>> SBS 2003 R3 as guest VM
>>
>> I need some ideas, gotchas and tips on how to make it workable
>>
>> Thanks,
>>
>> Dan
>>
>>

>

Daniel Jewel wrote:

> Thanks guys...
>
> I do not plan on using FAX and USB Backup can be re-routed to member
> server (USB) so no issues there.
> I plan on 4 partitions for the host. Parent partition with Core
> Server and Hyper-V services only if possible!?
> SBS on a dedicated a 300GBs partition
> Will ISA work with 2 NICs and provide security to the LAN?
>
> Dan

again, Charlies #1 ( &#7).

Hyper-V R2 or Server Core R2 with Hyper-v alone would be best.

Not only seperate partitions and seperate NICs, but seperate spindles should
be considered for performance.

Will ISA work, Will ISA provide security to the LAN? Yes, but.... ISA can
not *fully* protect the Hyper-V Physical NIC that you will configure as a
Virtual NIC. ISA will function and appear to be providing full capabiliites,
but effectivly it is running on an virtualized Network device. If the
physical network device can be compromised underneath ISA, then your Hyper-V
host and all that is connected to it *could* be at risk. I'm not aware of
anyone having done this, but theoretically, it is possible.

>
> "Charlie Russel - MVP" <Charlie@newsgroup> wrote in
> message news:eyJmx6neKHA.2780@newsgroup

>> 1.) Not supported. Full stop.
>> 2.) Certainly works, many of us have done it. But see #1.
>> 3.) I'd want at least one additional NIC on the hyper-v parent. You
>> should always have a dedicated management NIC that isn't used by
>> Hyper-V or any of the guests.
>> 4.) What other VMs are you planning on using on that box? SBS will
>> only see 4GB of the RAM.
>> 5.) Do not install any other roles on your parent partition (host).
>> Especially since your firewall is running on a guest.
>> 6.) You should not join the parent to the domain.
>> 7.) Reminder. See #1.
>>
>> --
>> Charlie.
>> http://msmvps.com/blogs/russel
>>
>>
>>
>>
>> "Daniel Jewel" <cyberdudeiq@newsgroup> wrote in message
>> news:uKYpkRmeKHA.1652@newsgroup

>>> Hi all,
>>>
>>> I am flirting with the idea to put to test the following
>>> virtualization: Server 2008 R2 + Hyper-V as host and ( HW = Xeon Quad; 8
>>> GBs RAM;
>>> RAID 5; 2 NICs)
>>> SBS 2003 R3 as guest VM
>>>
>>> I need some ideas, gotchas and tips on how to make it workable
>>>
>>> Thanks,
>>>
>>> Dan

--
/kj

So...if I follow Charlie's advice (getting an additional NIC for management
only) I should be good to go...right ?
Dan

"kj [SBS MVP]" <KevinJ.SBS@newsgroup> wrote in message
news:#SRqnMoeKHA.5808@newsgroup

> Daniel Jewel wrote:

>> Thanks guys...
>>
>> I do not plan on using FAX and USB Backup can be re-routed to member
>> server (USB) so no issues there.
>> I plan on 4 partitions for the host. Parent partition with Core
>> Server and Hyper-V services only if possible!?
>> SBS on a dedicated a 300GBs partition
>> Will ISA work with 2 NICs and provide security to the LAN?
>>
>> Dan

>
> again, Charlies #1 ( &#7).
>
> Hyper-V R2 or Server Core R2 with Hyper-v alone would be best.
>
> Not only seperate partitions and seperate NICs, but seperate spindles
> should be considered for performance.
>
> Will ISA work, Will ISA provide security to the LAN? Yes, but.... ISA can
> not *fully* protect the Hyper-V Physical NIC that you will configure as a
> Virtual NIC. ISA will function and appear to be providing full
> capabiliites, but effectivly it is running on an virtualized Network
> device. If the physical network device can be compromised underneath ISA,
> then your Hyper-V host and all that is connected to it *could* be at risk.
> I'm not aware of anyone having done this, but theoretically, it is
> possible.
>

>>
>> "Charlie Russel - MVP" <Charlie@newsgroup> wrote in
>> message news:eyJmx6neKHA.2780@newsgroup

>>> 1.) Not supported. Full stop.
>>> 2.) Certainly works, many of us have done it. But see #1.
>>> 3.) I'd want at least one additional NIC on the hyper-v parent. You
>>> should always have a dedicated management NIC that isn't used by
>>> Hyper-V or any of the guests.
>>> 4.) What other VMs are you planning on using on that box? SBS will
>>> only see 4GB of the RAM.
>>> 5.) Do not install any other roles on your parent partition (host).
>>> Especially since your firewall is running on a guest.
>>> 6.) You should not join the parent to the domain.
>>> 7.) Reminder. See #1.
>>>
>>> --
>>> Charlie.
>>> http://msmvps.com/blogs/russel
>>>
>>>
>>>
>>>
>>> "Daniel Jewel" <cyberdudeiq@newsgroup> wrote in message
>>> news:uKYpkRmeKHA.1652@newsgroup
>>>> Hi all,
>>>>
>>>> I am flirting with the idea to put to test the following
>>>> virtualization: Server 2008 R2 + Hyper-V as host and ( HW = Xeon Quad;
>>>> 8 GBs RAM;
>>>> RAID 5; 2 NICs)
>>>> SBS 2003 R3 as guest VM
>>>>
>>>> I need some ideas, gotchas and tips on how to make it workable
>>>>
>>>> Thanks,
>>>>
>>>> Dan

>
> --
> /kj
>

I think what your missing here is once you go down this route, you lose MS Support.
I've said it once, Charlie's said it twice.

As Charlie also points out, it can be done, but you do so at your own risk

--
Cris Hanna [SBS - MVP] (since 1997)
Co-Contributor, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...7269967&sr=8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Daniel Jewel" <cyberdudeiq@newsgroup> wrote in message news:e00yoioeKHA.3960@newsgroup
So...if I follow Charlie's advice (getting an additional NIC for management
only) I should be good to go...right ?
Dan

"kj [SBS MVP]" <KevinJ.SBS@newsgroup> wrote in message
news:#SRqnMoeKHA.5808@newsgroup

> Daniel Jewel wrote:

>> Thanks guys...
>>
>> I do not plan on using FAX and USB Backup can be re-routed to member
>> server (USB) so no issues there.
>> I plan on 4 partitions for the host. Parent partition with Core
>> Server and Hyper-V services only if possible!?
>> SBS on a dedicated a 300GBs partition
>> Will ISA work with 2 NICs and provide security to the LAN?
>>
>> Dan

>
> again, Charlies #1 ( &#7).
>
> Hyper-V R2 or Server Core R2 with Hyper-v alone would be best.
>
> Not only seperate partitions and seperate NICs, but seperate spindles
> should be considered for performance.
>
> Will ISA work, Will ISA provide security to the LAN? Yes, but.... ISA can
> not *fully* protect the Hyper-V Physical NIC that you will configure as a
> Virtual NIC. ISA will function and appear to be providing full
> capabiliites, but effectivly it is running on an virtualized Network
> device. If the physical network device can be compromised underneath ISA,
> then your Hyper-V host and all that is connected to it *could* be at risk.
> I'm not aware of anyone having done this, but theoretically, it is
> possible.
>

>>
>> "Charlie Russel - MVP" <Charlie@newsgroup> wrote in
>> message news:eyJmx6neKHA.2780@newsgroup

>>> 1.) Not supported. Full stop.
>>> 2.) Certainly works, many of us have done it. But see #1.
>>> 3.) I'd want at least one additional NIC on the hyper-v parent. You
>>> should always have a dedicated management NIC that isn't used by
>>> Hyper-V or any of the guests.
>>> 4.) What other VMs are you planning on using on that box? SBS will
>>> only see 4GB of the RAM.
>>> 5.) Do not install any other roles on your parent partition (host).
>>> Especially since your firewall is running on a guest.
>>> 6.) You should not join the parent to the domain.
>>> 7.) Reminder. See #1.
>>>
>>> --
>>> Charlie.
>>> http://msmvps.com/blogs/russel
>>>
>>>
>>>
>>>
>>> "Daniel Jewel" <cyberdudeiq@newsgroup> wrote in message
>>> news:uKYpkRmeKHA.1652@newsgroup
>>>> Hi all,
>>>>
>>>> I am flirting with the idea to put to test the following
>>>> virtualization: Server 2008 R2 + Hyper-V as host and ( HW = Xeon Quad;
>>>> 8 GBs RAM;
>>>> RAID 5; 2 NICs)
>>>> SBS 2003 R3 as guest VM
>>>>
>>>> I need some ideas, gotchas and tips on how to make it workable
>>>>
>>>> Thanks,
>>>>
>>>> Dan

>
> --
> /kj
>

Daniel Jewel wrote:

> So...if I follow Charlie's advice (getting an additional NIC for
> management only) I should be good to go...right ?
> Dan

Considering the limitations and restrictions and following Charlie's advice
( + others including mine) you would be embarking with knowledge on a
"workable" virtualization project.

>
> "kj [SBS MVP]" <KevinJ.SBS@newsgroup> wrote in message
> news:#SRqnMoeKHA.5808@newsgroup

>> Daniel Jewel wrote:

>>> Thanks guys...
>>>
>>> I do not plan on using FAX and USB Backup can be re-routed to member
>>> server (USB) so no issues there.
>>> I plan on 4 partitions for the host. Parent partition with Core
>>> Server and Hyper-V services only if possible!?
>>> SBS on a dedicated a 300GBs partition
>>> Will ISA work with 2 NICs and provide security to the LAN?
>>>
>>> Dan

>>
>> again, Charlies #1 ( &#7).
>>
>> Hyper-V R2 or Server Core R2 with Hyper-v alone would be best.
>>
>> Not only seperate partitions and seperate NICs, but seperate spindles
>> should be considered for performance.
>>
>> Will ISA work, Will ISA provide security to the LAN? Yes, but....
>> ISA can not *fully* protect the Hyper-V Physical NIC that you will
>> configure as a Virtual NIC. ISA will function and appear to be
>> providing full capabiliites, but effectivly it is running on an
>> virtualized Network device. If the physical network device can be
>> compromised underneath ISA, then your Hyper-V host and all that is
>> connected to it *could* be at risk. I'm not aware of anyone having
>> done this, but theoretically, it is possible.
>>

>>>
>>> "Charlie Russel - MVP" <Charlie@newsgroup> wrote in
>>> message news:eyJmx6neKHA.2780@newsgroup
>>>> 1.) Not supported. Full stop.
>>>> 2.) Certainly works, many of us have done it. But see #1.
>>>> 3.) I'd want at least one additional NIC on the hyper-v parent. You
>>>> should always have a dedicated management NIC that isn't used by
>>>> Hyper-V or any of the guests.
>>>> 4.) What other VMs are you planning on using on that box? SBS will
>>>> only see 4GB of the RAM.
>>>> 5.) Do not install any other roles on your parent partition (host).
>>>> Especially since your firewall is running on a guest.
>>>> 6.) You should not join the parent to the domain.
>>>> 7.) Reminder. See #1.
>>>>
>>>> --
>>>> Charlie.
>>>> http://msmvps.com/blogs/russel
>>>>
>>>>
>>>>
>>>>
>>>> "Daniel Jewel" <cyberdudeiq@newsgroup> wrote in message
>>>> news:uKYpkRmeKHA.1652@newsgroup
>>>>> Hi all,
>>>>>
>>>>> I am flirting with the idea to put to test the following
>>>>> virtualization: Server 2008 R2 + Hyper-V as host and ( HW = Xeon
>>>>> Quad; 8 GBs RAM;
>>>>> RAID 5; 2 NICs)
>>>>> SBS 2003 R3 as guest VM
>>>>>
>>>>> I need some ideas, gotchas and tips on how to make it workable
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Dan

>>
>> --
>> /kj

--
/kj

I'm fully aware it will not be supported by Microsoft... but, as I said
before, this is project for me to get my feet wet with Hyper-V and other VM
servers
Thanks to all for the helping hand ! Really appreciate it...
Dan

"kj [SBS MVP]" <KevinJ.SBS@newsgroup> wrote in message
news:ufUXmApeKHA.5808@newsgroup

> Daniel Jewel wrote:

>> So...if I follow Charlie's advice (getting an additional NIC for
>> management only) I should be good to go...right ?
>> Dan

>
>
> Considering the limitations and restrictions and following Charlie's
> advice ( + others including mine) you would be embarking with knowledge on
> a "workable" virtualization project.
>
>

>>
>> "kj [SBS MVP]" <KevinJ.SBS@newsgroup> wrote in message
>> news:#SRqnMoeKHA.5808@newsgroup

>>> Daniel Jewel wrote:
>>>> Thanks guys...
>>>>
>>>> I do not plan on using FAX and USB Backup can be re-routed to member
>>>> server (USB) so no issues there.
>>>> I plan on 4 partitions for the host. Parent partition with Core
>>>> Server and Hyper-V services only if possible!?
>>>> SBS on a dedicated a 300GBs partition
>>>> Will ISA work with 2 NICs and provide security to the LAN?
>>>>
>>>> Dan
>>>
>>> again, Charlies #1 ( &#7).
>>>
>>> Hyper-V R2 or Server Core R2 with Hyper-v alone would be best.
>>>
>>> Not only seperate partitions and seperate NICs, but seperate spindles
>>> should be considered for performance.
>>>
>>> Will ISA work, Will ISA provide security to the LAN? Yes, but....
>>> ISA can not *fully* protect the Hyper-V Physical NIC that you will
>>> configure as a Virtual NIC. ISA will function and appear to be
>>> providing full capabiliites, but effectivly it is running on an
>>> virtualized Network device. If the physical network device can be
>>> compromised underneath ISA, then your Hyper-V host and all that is
>>> connected to it *could* be at risk. I'm not aware of anyone having
>>> done this, but theoretically, it is possible.
>>>
>>>>
>>>> "Charlie Russel - MVP" <Charlie@newsgroup> wrote in
>>>> message news:eyJmx6neKHA.2780@newsgroup
>>>>> 1.) Not supported. Full stop.
>>>>> 2.) Certainly works, many of us have done it. But see #1.
>>>>> 3.) I'd want at least one additional NIC on the hyper-v parent. You
>>>>> should always have a dedicated management NIC that isn't used by
>>>>> Hyper-V or any of the guests.
>>>>> 4.) What other VMs are you planning on using on that box? SBS will
>>>>> only see 4GB of the RAM.
>>>>> 5.) Do not install any other roles on your parent partition (host).
>>>>> Especially since your firewall is running on a guest.
>>>>> 6.) You should not join the parent to the domain.
>>>>> 7.) Reminder. See #1.
>>>>>
>>>>> --
>>>>> Charlie.
>>>>> http://msmvps.com/blogs/russel
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> "Daniel Jewel" <cyberdudeiq@newsgroup> wrote in message
>>>>> news:uKYpkRmeKHA.1652@newsgroup
>>>>>> Hi all,
>>>>>>
>>>>>> I am flirting with the idea to put to test the following
>>>>>> virtualization: Server 2008 R2 + Hyper-V as host and ( HW = Xeon
>>>>>> Quad; 8 GBs RAM;
>>>>>> RAID 5; 2 NICs)
>>>>>> SBS 2003 R3 as guest VM
>>>>>>
>>>>>> I need some ideas, gotchas and tips on how to make it workable
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Dan
>>>
>>> --
>>> /kj

>
> --
> /kj
>

Daniel Jewel wrote:

> I'm fully aware it will not be supported by Microsoft... but, as I
> said before, this is project for me to get my feet wet with Hyper-V
> and other VM servers
> Thanks to all for the helping hand ! Really appreciate it...
> Dan

Don't think the 'get my feet wet with...' was understood. For that purpose
it will serve you well. For an end customer production environment, then
serious considerations should be given to supportability and limitations.

Have fun, there are several here that have successfully done what you are
proposing.

>
> "kj [SBS MVP]" <KevinJ.SBS@newsgroup> wrote in message
> news:ufUXmApeKHA.5808@newsgroup

>> Daniel Jewel wrote:

>>> So...if I follow Charlie's advice (getting an additional NIC for
>>> management only) I should be good to go...right ?
>>> Dan

>>
>>
>> Considering the limitations and restrictions and following Charlie's
>> advice ( + others including mine) you would be embarking with
>> knowledge on a "workable" virtualization project.
>>
>>

>>>
>>> "kj [SBS MVP]" <KevinJ.SBS@newsgroup> wrote in message
>>> news:#SRqnMoeKHA.5808@newsgroup
>>>> Daniel Jewel wrote:
>>>>> Thanks guys...
>>>>>
>>>>> I do not plan on using FAX and USB Backup can be re-routed to
>>>>> member server (USB) so no issues there.
>>>>> I plan on 4 partitions for the host. Parent partition with Core
>>>>> Server and Hyper-V services only if possible!?
>>>>> SBS on a dedicated a 300GBs partition
>>>>> Will ISA work with 2 NICs and provide security to the LAN?
>>>>>
>>>>> Dan
>>>>
>>>> again, Charlies #1 ( &#7).
>>>>
>>>> Hyper-V R2 or Server Core R2 with Hyper-v alone would be best.
>>>>
>>>> Not only seperate partitions and seperate NICs, but seperate
>>>> spindles should be considered for performance.
>>>>
>>>> Will ISA work, Will ISA provide security to the LAN? Yes, but....
>>>> ISA can not *fully* protect the Hyper-V Physical NIC that you will
>>>> configure as a Virtual NIC. ISA will function and appear to be
>>>> providing full capabiliites, but effectivly it is running on an
>>>> virtualized Network device. If the physical network device can be
>>>> compromised underneath ISA, then your Hyper-V host and all that is
>>>> connected to it *could* be at risk. I'm not aware of anyone having
>>>> done this, but theoretically, it is possible.
>>>>
>>>>>
>>>>> "Charlie Russel - MVP" <Charlie@newsgroup> wrote in
>>>>> message news:eyJmx6neKHA.2780@newsgroup
>>>>>> 1.) Not supported. Full stop.
>>>>>> 2.) Certainly works, many of us have done it. But see #1.
>>>>>> 3.) I'd want at least one additional NIC on the hyper-v parent.
>>>>>> You should always have a dedicated management NIC that isn't
>>>>>> used by Hyper-V or any of the guests.
>>>>>> 4.) What other VMs are you planning on using on that box? SBS
>>>>>> will only see 4GB of the RAM.
>>>>>> 5.) Do not install any other roles on your parent partition
>>>>>> (host). Especially since your firewall is running on a guest.
>>>>>> 6.) You should not join the parent to the domain.
>>>>>> 7.) Reminder. See #1.
>>>>>>
>>>>>> --
>>>>>> Charlie.
>>>>>> http://msmvps.com/blogs/russel
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> "Daniel Jewel" <cyberdudeiq@newsgroup> wrote in message
>>>>>> news:uKYpkRmeKHA.1652@newsgroup
>>>>>>> Hi all,
>>>>>>>
>>>>>>> I am flirting with the idea to put to test the following
>>>>>>> virtualization: Server 2008 R2 + Hyper-V as host and ( HW = Xeon
>>>>>>> Quad; 8 GBs RAM;
>>>>>>> RAID 5; 2 NICs)
>>>>>>> SBS 2003 R3 as guest VM
>>>>>>>
>>>>>>> I need some ideas, gotchas and tips on how to make it workable
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Dan
>>>>
>>>> --
>>>> /kj

>>
>> --
>> /kj

--
/kj

Agree. It was not clear that this was a lab project and not a customers environment you were planning to move.

--
Cris Hanna [SBS - MVP] (since 1997)
Co-Contributor, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...7269967&sr=8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Daniel Jewel" <cyberdudeiq@newsgroup> wrote in message news:usCvfXpeKHA.3752@newsgroup
I'm fully aware it will not be supported by Microsoft... but, as I said
before, this is project for me to get my feet wet with Hyper-V and other VM
servers
Thanks to all for the helping hand ! Really appreciate it...
Dan

"kj [SBS MVP]" <KevinJ.SBS@newsgroup> wrote in message
news:ufUXmApeKHA.5808@newsgroup

> Daniel Jewel wrote:

>> So...if I follow Charlie's advice (getting an additional NIC for
>> management only) I should be good to go...right ?
>> Dan

>
>
> Considering the limitations and restrictions and following Charlie's
> advice ( + others including mine) you would be embarking with knowledge on
> a "workable" virtualization project.
>
>

>>
>> "kj [SBS MVP]" <KevinJ.SBS@newsgroup> wrote in message
>> news:#SRqnMoeKHA.5808@newsgroup

>>> Daniel Jewel wrote:
>>>> Thanks guys...
>>>>
>>>> I do not plan on using FAX and USB Backup can be re-routed to member
>>>> server (USB) so no issues there.
>>>> I plan on 4 partitions for the host. Parent partition with Core
>>>> Server and Hyper-V services only if possible!?
>>>> SBS on a dedicated a 300GBs partition
>>>> Will ISA work with 2 NICs and provide security to the LAN?
>>>>
>>>> Dan
>>>
>>> again, Charlies #1 ( &#7).
>>>
>>> Hyper-V R2 or Server Core R2 with Hyper-v alone would be best.
>>>
>>> Not only seperate partitions and seperate NICs, but seperate spindles
>>> should be considered for performance.
>>>
>>> Will ISA work, Will ISA provide security to the LAN? Yes, but....
>>> ISA can not *fully* protect the Hyper-V Physical NIC that you will
>>> configure as a Virtual NIC. ISA will function and appear to be
>>> providing full capabiliites, but effectivly it is running on an
>>> virtualized Network device. If the physical network device can be
>>> compromised underneath ISA, then your Hyper-V host and all that is
>>> connected to it *could* be at risk. I'm not aware of anyone having
>>> done this, but theoretically, it is possible.
>>>
>>>>
>>>> "Charlie Russel - MVP" <Charlie@newsgroup> wrote in
>>>> message news:eyJmx6neKHA.2780@newsgroup
>>>>> 1.) Not supported. Full stop.
>>>>> 2.) Certainly works, many of us have done it. But see #1.
>>>>> 3.) I'd want at least one additional NIC on the hyper-v parent. You
>>>>> should always have a dedicated management NIC that isn't used by
>>>>> Hyper-V or any of the guests.
>>>>> 4.) What other VMs are you planning on using on that box? SBS will
>>>>> only see 4GB of the RAM.
>>>>> 5.) Do not install any other roles on your parent partition (host).
>>>>> Especially since your firewall is running on a guest.
>>>>> 6.) You should not join the parent to the domain.
>>>>> 7.) Reminder. See #1.
>>>>>
>>>>> --
>>>>> Charlie.
>>>>> http://msmvps.com/blogs/russel
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> "Daniel Jewel" <cyberdudeiq@newsgroup> wrote in message
>>>>> news:uKYpkRmeKHA.1652@newsgroup
>>>>>> Hi all,
>>>>>>
>>>>>> I am flirting with the idea to put to test the following
>>>>>> virtualization: Server 2008 R2 + Hyper-V as host and ( HW = Xeon
>>>>>> Quad; 8 GBs RAM;
>>>>>> RAID 5; 2 NICs)
>>>>>> SBS 2003 R3 as guest VM
>>>>>>
>>>>>> I need some ideas, gotchas and tips on how to make it workable
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Dan
>>>
>>> --
>>> /kj

>
> --
> /kj
>

One further suggestion. The NIC that you physically connect to the Internet
(and that gets virtualized the ISA external NIC should have no MS Networking
services (either client or server) enabled. It's ONLY function should be to
pass through the ISA external NIC. And if it were my box, I'd go a step
further and protect the entire box with AuthAnvil to further protect me from
something happening before the packets could get to ISA. (No direct
connection to AuthAnvil, except that he's a friend and fellow MVP and I
really like the product. www.scorpionsoft.com)
--
Charlie.
http://msmvps.com/blogs/russel




"Daniel Jewel" <cyberdudeiq@newsgroup> wrote in message
news:e00yoioeKHA.3960@newsgroup

> So...if I follow Charlie's advice (getting an additional NIC for
> management only) I should be good to go...right ?
> Dan
>
> "kj [SBS MVP]" <KevinJ.SBS@newsgroup> wrote in message
> news:#SRqnMoeKHA.5808@newsgroup

>> Daniel Jewel wrote:

>>> Thanks guys...
>>>
>>> I do not plan on using FAX and USB Backup can be re-routed to member
>>> server (USB) so no issues there.
>>> I plan on 4 partitions for the host. Parent partition with Core
>>> Server and Hyper-V services only if possible!?
>>> SBS on a dedicated a 300GBs partition
>>> Will ISA work with 2 NICs and provide security to the LAN?
>>>
>>> Dan

>>
>> again, Charlies #1 ( &#7).
>>
>> Hyper-V R2 or Server Core R2 with Hyper-v alone would be best.
>>
>> Not only seperate partitions and seperate NICs, but seperate spindles
>> should be considered for performance.
>>
>> Will ISA work, Will ISA provide security to the LAN? Yes, but.... ISA can
>> not *fully* protect the Hyper-V Physical NIC that you will configure as a
>> Virtual NIC. ISA will function and appear to be providing full
>> capabiliites, but effectivly it is running on an virtualized Network
>> device. If the physical network device can be compromised underneath ISA,
>> then your Hyper-V host and all that is connected to it *could* be at
>> risk. I'm not aware of anyone having done this, but theoretically, it is
>> possible.
>>

>>>
>>> "Charlie Russel - MVP" <Charlie@newsgroup> wrote in
>>> message news:eyJmx6neKHA.2780@newsgroup
>>>> 1.) Not supported. Full stop.
>>>> 2.) Certainly works, many of us have done it. But see #1.
>>>> 3.) I'd want at least one additional NIC on the hyper-v parent. You
>>>> should always have a dedicated management NIC that isn't used by
>>>> Hyper-V or any of the guests.
>>>> 4.) What other VMs are you planning on using on that box? SBS will
>>>> only see 4GB of the RAM.
>>>> 5.) Do not install any other roles on your parent partition (host).
>>>> Especially since your firewall is running on a guest.
>>>> 6.) You should not join the parent to the domain.
>>>> 7.) Reminder. See #1.
>>>>
>>>> --
>>>> Charlie.
>>>> http://msmvps.com/blogs/russel
>>>>
>>>>
>>>>
>>>>
>>>> "Daniel Jewel" <cyberdudeiq@newsgroup> wrote in message
>>>> news:uKYpkRmeKHA.1652@newsgroup
>>>>> Hi all,
>>>>>
>>>>> I am flirting with the idea to put to test the following
>>>>> virtualization: Server 2008 R2 + Hyper-V as host and ( HW = Xeon Quad;
>>>>> 8 GBs RAM;
>>>>> RAID 5; 2 NICs)
>>>>> SBS 2003 R3 as guest VM
>>>>>
>>>>> I need some ideas, gotchas and tips on how to make it workable
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Dan

>>
>> --
>> /kj
>>