Does anyone know if BS 2003 is supported on Hyper-V?



It supports windows server 2003 R2 so i'd expect it to support SBS 2003 R2
Premium.

If it is supported: Do I need to install firewall and antivirus on Hyper-V
itself or is it safe. (I think this is a stupid question, but can't find
anything on that so want confirmation that I need to install)

Thanks

Bas

Look for a similar thread on 09-04-2009 in this group.

--
Larry
Please post the resolution to your
issue so that others may benefit.

Get a Health Check for SBS at:
www.sbsbpa.com


"Bas" <Bas@newsgroup> wrote in message
news:61768BCF-1F4A-4801-92B7-F7C72BE2F4CB@newsgroup

> Does anyone know if BS 2003 is supported on Hyper-V?
>
> It supports windows server 2003 R2 so i'd expect it to support SBS 2003 R2
> Premium.
>
> If it is supported: Do I need to install firewall and antivirus on Hyper-V
> itself or is it safe. (I think this is a stupid question, but can't find
> anything on that so want confirmation that I need to install)
>
> Thanks
>
> Bas
>
>

Ok thanks!

So it isn't supported by MS but it should work.

What I didn't understand is: can SBS be the DC while vitualised?

We are planning a clean install of the SBS 2003 and might are looking at
doing this directly under Hyper-V if pratical...

Also my questions about the security of the Hyper-V server were not answered.

Could you please answer those for me?

Thanks

"Larry Struckmeyer [SBS-MVP]" wrote:

> Look for a similar thread on 09-04-2009 in this group.
>
> --
> Larry
> Please post the resolution to your
> issue so that others may benefit.
>
> Get a Health Check for SBS at:
> www.sbsbpa.com
>
>
> "Bas" <Bas@newsgroup> wrote in message
> news:61768BCF-1F4A-4801-92B7-F7C72BE2F4CB@newsgroup

> > Does anyone know if BS 2003 is supported on Hyper-V?
> >
> > It supports windows server 2003 R2 so i'd expect it to support SBS 2003 R2
> > Premium.
> >
> > If it is supported: Do I need to install firewall and antivirus on Hyper-V
> > itself or is it safe. (I think this is a stupid question, but can't find
> > anything on that so want confirmation that I need to install)
> >
> > Thanks
> >
> > Bas
> >
> >

>
>

The answer to the q about SBS being the DC is self evident. SBS can *only*
be a DC. There can be other DCs in the domain, but SBS *must* be a DC and
hold all of the FSMO roles.

The q about an edge device/firewall and AV is mostly to do with your comfort
level. What is "safe" when the bad guys of the world work 24x7 to penetrate
remote computers is anyones guess really. It also depends on what you have
to lose. If you are guarding the recipie for Coke, then you probably don't
want it in electronic form anywhere. If you are guarding Joes Plumbing (no
offense to Joe) it may be a different matter.

But, if you go unprotected on the internet, call the server "Honey Pot" becuase
it will surely be one.

-
Larry
Please post the resolution to your
issue so others may benefit
-
Get Your SBS Health Check at
www.sbsbpa.com

> Ok thanks!
>
> So it isn't supported by MS but it should work.
>
> What I didn't understand is: can SBS be the DC while vitualised?
>
> We are planning a clean install of the SBS 2003 and might are looking
> at doing this directly under Hyper-V if pratical...
>
> Also my questions about the security of the Hyper-V server were not
> answered.
>
> Could you please answer those for me?
>
> Thanks
>
> "Larry Struckmeyer [SBS-MVP]" wrote:
>

>> Look for a similar thread on 09-04-2009 in this group.
>>
>> --
>> Larry
>> Please post the resolution to your
>> issue so that others may benefit.
>> Get a Health Check for SBS at:
>> www.sbsbpa.com
>> "Bas" <Bas@newsgroup> wrote in message
>> news:61768BCF-1F4A-4801-92B7-F7C72BE2F4CB@newsgroup
>>

>>> Does anyone know if BS 2003 is supported on Hyper-V?
>>>
>>> It supports windows server 2003 R2 so i'd expect it to support SBS
>>> 2003 R2 Premium.
>>>
>>> If it is supported: Do I need to install firewall and antivirus on
>>> Hyper-V itself or is it safe. (I think this is a stupid question,
>>> but can't find anything on that so want confirmation that I need to
>>> install)
>>>
>>> Thanks
>>>
>>> Bas
>>>

Right, thanks larry

You confirmed for me what I expected: that I need two protection packages
then. One for the HYper-V and one for the SBS VM.

Thanks Again

Bas

"Larry Struckmeyer[SBS-MVP]" wrote:

> The answer to the q about SBS being the DC is self evident. SBS can *only*
> be a DC. There can be other DCs in the domain, but SBS *must* be a DC and
> hold all of the FSMO roles.
>
> The q about an edge device/firewall and AV is mostly to do with your comfort
> level. What is "safe" when the bad guys of the world work 24x7 to penetrate
> remote computers is anyones guess really. It also depends on what you have
> to lose. If you are guarding the recipie for Coke, then you probably don't
> want it in electronic form anywhere. If you are guarding Joes Plumbing (no
> offense to Joe) it may be a different matter.
>
> But, if you go unprotected on the internet, call the server "Honey Pot" becuase
> it will surely be one.
>
> -
> Larry
> Please post the resolution to your
> issue so others may benefit
> -
> Get Your SBS Health Check at
> www.sbsbpa.com
>
>

> > Ok thanks!
> >
> > So it isn't supported by MS but it should work.
> >
> > What I didn't understand is: can SBS be the DC while vitualised?
> >
> > We are planning a clean install of the SBS 2003 and might are looking
> > at doing this directly under Hyper-V if pratical...
> >
> > Also my questions about the security of the Hyper-V server were not
> > answered.
> >
> > Could you please answer those for me?
> >
> > Thanks
> >
> > "Larry Struckmeyer [SBS-MVP]" wrote:
> >

> >> Look for a similar thread on 09-04-2009 in this group.
> >>
> >> --
> >> Larry
> >> Please post the resolution to your
> >> issue so that others may benefit.
> >> Get a Health Check for SBS at:
> >> www.sbsbpa.com
> >> "Bas" <Bas@newsgroup> wrote in message
> >> news:61768BCF-1F4A-4801-92B7-F7C72BE2F4CB@newsgroup
> >>
> >>> Does anyone know if BS 2003 is supported on Hyper-V?
> >>>
> >>> It supports windows server 2003 R2 so i'd expect it to support SBS
> >>> 2003 R2 Premium.
> >>>
> >>> If it is supported: Do I need to install firewall and antivirus on
> >>> Hyper-V itself or is it safe. (I think this is a stupid question,
> >>> but can't find anything on that so want confirmation that I need to
> >>> install)
> >>>
> >>> Thanks
> >>>
> >>> Bas
> >>>

>
>
>

Well, I'll offer a different answer wrt Hyper-V. If you use hyper-v as it
should be, with NO additional roles or features installed that aren't
directly related to managing Hyper-V, and you don't use it as a workstation
or web surfer or other reason to connect to the Internet, then why worry
about it? A-V software imposes a fair amount of overhead on file access, and
it's not something I want on my virtualization parent. So, I run the
absolute minimum on my Hyper-V host, I don't join it to the domain (since
the domain is virtualized as a child on it), and I have it set to not even
have an IP address on the SBS network's subnet. My Hyper-V host has two NICs
that it can see: the iSCSI subnet, and the management subnet. Both of which
run on segregated subnets from my domain network.

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


"Bas" <Bas@newsgroup> wrote in message
news:9F99F40F-52FF-47C1-8D14-C431161299CB@newsgroup

> Right, thanks larry
>
> You confirmed for me what I expected: that I need two protection packages
> then. One for the HYper-V and one for the SBS VM.
>
> Thanks Again
>
> Bas
>
> "Larry Struckmeyer[SBS-MVP]" wrote:
>

>> The answer to the q about SBS being the DC is self evident. SBS can
>> *only*
>> be a DC. There can be other DCs in the domain, but SBS *must* be a DC
>> and
>> hold all of the FSMO roles.
>>
>> The q about an edge device/firewall and AV is mostly to do with your
>> comfort
>> level. What is "safe" when the bad guys of the world work 24x7 to
>> penetrate
>> remote computers is anyones guess really. It also depends on what you
>> have
>> to lose. If you are guarding the recipie for Coke, then you probably
>> don't
>> want it in electronic form anywhere. If you are guarding Joes Plumbing
>> (no
>> offense to Joe) it may be a different matter.
>>
>> But, if you go unprotected on the internet, call the server "Honey Pot"
>> becuase
>> it will surely be one.
>>
>> -
>> Larry
>> Please post the resolution to your
>> issue so others may benefit
>> -
>> Get Your SBS Health Check at
>> www.sbsbpa.com
>>
>>

>> > Ok thanks!
>> >
>> > So it isn't supported by MS but it should work.
>> >
>> > What I didn't understand is: can SBS be the DC while vitualised?
>> >
>> > We are planning a clean install of the SBS 2003 and might are looking
>> > at doing this directly under Hyper-V if pratical...
>> >
>> > Also my questions about the security of the Hyper-V server were not
>> > answered.
>> >
>> > Could you please answer those for me?
>> >
>> > Thanks
>> >
>> > "Larry Struckmeyer [SBS-MVP]" wrote:
>> >
>> >> Look for a similar thread on 09-04-2009 in this group.
>> >>
>> >> --
>> >> Larry
>> >> Please post the resolution to your
>> >> issue so that others may benefit.
>> >> Get a Health Check for SBS at:
>> >> www.sbsbpa.com
>> >> "Bas" <Bas@newsgroup> wrote in message
>> >> news:61768BCF-1F4A-4801-92B7-F7C72BE2F4CB@newsgroup
>> >>
>> >>> Does anyone know if BS 2003 is supported on Hyper-V?
>> >>>
>> >>> It supports windows server 2003 R2 so i'd expect it to support SBS
>> >>> 2003 R2 Premium.
>> >>>
>> >>> If it is supported: Do I need to install firewall and antivirus on
>> >>> Hyper-V itself or is it safe. (I think this is a stupid question,
>> >>> but can't find anything on that so want confirmation that I need to
>> >>> install)
>> >>>
>> >>> Thanks
>> >>>
>> >>> Bas
>> >>>

>>
>>
>>

Thanks, Charlie.

I was hoping you would check in here.

Can you clarify exactly what version of Server/Hyper-V you are discussing
here, or if it matters?

--
Larry
Please post the resolution to your
issue so that others may benefit.

Get a Health Check for SBS at:
www.sbsbpa.com


"Charlie Russel - MVP" <Charlie@newsgroup> wrote in message
news:%23p7cICgOKHA.5128@newsgroup

> Well, I'll offer a different answer wrt Hyper-V. If you use hyper-v as it
> should be, with NO additional roles or features installed that aren't
> directly related to managing Hyper-V, and you don't use it as a
> workstation or web surfer or other reason to connect to the Internet, then
> why worry about it? A-V software imposes a fair amount of overhead on file
> access, and it's not something I want on my virtualization parent. So, I
> run the absolute minimum on my Hyper-V host, I don't join it to the domain
> (since the domain is virtualized as a child on it), and I have it set to
> not even have an IP address on the SBS network's subnet. My Hyper-V host
> has two NICs that it can see: the iSCSI subnet, and the management subnet.
> Both of which run on segregated subnets from my domain network.
>
> --
> Charlie.
> http:/msmvps.com/blogs/xperts64
>
>
> "Bas" <Bas@newsgroup> wrote in message
> news:9F99F40F-52FF-47C1-8D14-C431161299CB@newsgroup

>> Right, thanks larry
>>
>> You confirmed for me what I expected: that I need two protection packages
>> then. One for the HYper-V and one for the SBS VM.
>>
>> Thanks Again
>>
>> Bas
>>
>> "Larry Struckmeyer[SBS-MVP]" wrote:
>>

>>> The answer to the q about SBS being the DC is self evident. SBS can
>>> *only*
>>> be a DC. There can be other DCs in the domain, but SBS *must* be a DC
>>> and
>>> hold all of the FSMO roles.
>>>
>>> The q about an edge device/firewall and AV is mostly to do with your
>>> comfort
>>> level. What is "safe" when the bad guys of the world work 24x7 to
>>> penetrate
>>> remote computers is anyones guess really. It also depends on what you
>>> have
>>> to lose. If you are guarding the recipie for Coke, then you probably
>>> don't
>>> want it in electronic form anywhere. If you are guarding Joes Plumbing
>>> (no
>>> offense to Joe) it may be a different matter.
>>>
>>> But, if you go unprotected on the internet, call the server "Honey Pot"
>>> becuase
>>> it will surely be one.
>>>
>>> -
>>> Larry
>>> Please post the resolution to your
>>> issue so others may benefit
>>> -
>>> Get Your SBS Health Check at
>>> www.sbsbpa.com
>>>
>>>
>>> > Ok thanks!
>>> >
>>> > So it isn't supported by MS but it should work.
>>> >
>>> > What I didn't understand is: can SBS be the DC while vitualised?
>>> >
>>> > We are planning a clean install of the SBS 2003 and might are looking
>>> > at doing this directly under Hyper-V if pratical...
>>> >
>>> > Also my questions about the security of the Hyper-V server were not
>>> > answered.
>>> >
>>> > Could you please answer those for me?
>>> >
>>> > Thanks
>>> >
>>> > "Larry Struckmeyer [SBS-MVP]" wrote:
>>> >
>>> >> Look for a similar thread on 09-04-2009 in this group.
>>> >>
>>> >> --
>>> >> Larry
>>> >> Please post the resolution to your
>>> >> issue so that others may benefit.
>>> >> Get a Health Check for SBS at:
>>> >> www.sbsbpa.com
>>> >> "Bas" <Bas@newsgroup> wrote in message
>>> >> news:61768BCF-1F4A-4801-92B7-F7C72BE2F4CB@newsgroup
>>> >>
>>> >>> Does anyone know if BS 2003 is supported on Hyper-V?
>>> >>>
>>> >>> It supports windows server 2003 R2 so i'd expect it to support SBS
>>> >>> 2003 R2 Premium.
>>> >>>
>>> >>> If it is supported: Do I need to install firewall and antivirus on
>>> >>> Hyper-V itself or is it safe. (I think this is a stupid question,
>>> >>> but can't find anything on that so want confirmation that I need to
>>> >>> install)
>>> >>>
>>> >>> Thanks
>>> >>>
>>> >>> Bas
>>> >>>
>>>
>>>
>>>

>

Doesn't matter. If all you're doing with Hyper-V is running the
virtualization, then I honestly don't see a need to run the overhead of AV.
Don't read your email, don't surf, don't connect to the internet at all,
really, with the possible exception of getting updates. (and you could
manage to do that all manually, if desired, using local .MSU files.)

Now if you really want to cut down the footprint, use the Hyper-V Server, or
Windows Server running a Core install. Plus, if you opt for Hyper-V Server,
you can run the R2 version that gives you hot add/remove of VHDs. (Plus it's
a lot faster with dynamic disks than v1 was.)

--
Charlie.
http://msmvps.com/blogs/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel


"Larry Struckmeyer [SBS-MVP]" <lstruckmeyer@newsgroup-wizards.com> wrote in
message news:ex9%23mZgOKHA.4028@newsgroup

> Thanks, Charlie.
>
> I was hoping you would check in here.
>
> Can you clarify exactly what version of Server/Hyper-V you are discussing
> here, or if it matters?
>
> --
> Larry
> Please post the resolution to your
> issue so that others may benefit.
>
> Get a Health Check for SBS at:
> www.sbsbpa.com
>
>
> "Charlie Russel - MVP" <Charlie@newsgroup> wrote in message
> news:%23p7cICgOKHA.5128@newsgroup

>> Well, I'll offer a different answer wrt Hyper-V. If you use hyper-v as it
>> should be, with NO additional roles or features installed that aren't
>> directly related to managing Hyper-V, and you don't use it as a
>> workstation or web surfer or other reason to connect to the Internet,
>> then why worry about it? A-V software imposes a fair amount of overhead
>> on file access, and it's not something I want on my virtualization
>> parent. So, I run the absolute minimum on my Hyper-V host, I don't join
>> it to the domain (since the domain is virtualized as a child on it), and
>> I have it set to not even have an IP address on the SBS network's subnet.
>> My Hyper-V host has two NICs that it can see: the iSCSI subnet, and the
>> management subnet. Both of which run on segregated subnets from my domain
>> network.
>>
>> --
>> Charlie.
>> http:/msmvps.com/blogs/xperts64
>>
>>
>> "Bas" <Bas@newsgroup> wrote in message
>> news:9F99F40F-52FF-47C1-8D14-C431161299CB@newsgroup

>>> Right, thanks larry
>>>
>>> You confirmed for me what I expected: that I need two protection
>>> packages
>>> then. One for the HYper-V and one for the SBS VM.
>>>
>>> Thanks Again
>>>
>>> Bas
>>>
>>> "Larry Struckmeyer[SBS-MVP]" wrote:
>>>
>>>> The answer to the q about SBS being the DC is self evident. SBS can
>>>> *only*
>>>> be a DC. There can be other DCs in the domain, but SBS *must* be a DC
>>>> and
>>>> hold all of the FSMO roles.
>>>>
>>>> The q about an edge device/firewall and AV is mostly to do with your
>>>> comfort
>>>> level. What is "safe" when the bad guys of the world work 24x7 to
>>>> penetrate
>>>> remote computers is anyones guess really. It also depends on what you
>>>> have
>>>> to lose. If you are guarding the recipie for Coke, then you probably
>>>> don't
>>>> want it in electronic form anywhere. If you are guarding Joes Plumbing
>>>> (no
>>>> offense to Joe) it may be a different matter.
>>>>
>>>> But, if you go unprotected on the internet, call the server "Honey Pot"
>>>> becuase
>>>> it will surely be one.
>>>>
>>>> -
>>>> Larry
>>>> Please post the resolution to your
>>>> issue so others may benefit
>>>> -
>>>> Get Your SBS Health Check at
>>>> www.sbsbpa.com
>>>>
>>>>
>>>> > Ok thanks!
>>>> >
>>>> > So it isn't supported by MS but it should work.
>>>> >
>>>> > What I didn't understand is: can SBS be the DC while vitualised?
>>>> >
>>>> > We are planning a clean install of the SBS 2003 and might are looking
>>>> > at doing this directly under Hyper-V if pratical...
>>>> >
>>>> > Also my questions about the security of the Hyper-V server were not
>>>> > answered.
>>>> >
>>>> > Could you please answer those for me?
>>>> >
>>>> > Thanks
>>>> >
>>>> > "Larry Struckmeyer [SBS-MVP]" wrote:
>>>> >
>>>> >> Look for a similar thread on 09-04-2009 in this group.
>>>> >>
>>>> >> --
>>>> >> Larry
>>>> >> Please post the resolution to your
>>>> >> issue so that others may benefit.
>>>> >> Get a Health Check for SBS at:
>>>> >> www.sbsbpa.com
>>>> >> "Bas" <Bas@newsgroup> wrote in message
>>>> >> news:61768BCF-1F4A-4801-92B7-F7C72BE2F4CB@newsgroup
>>>> >>
>>>> >>> Does anyone know if BS 2003 is supported on Hyper-V?
>>>> >>>
>>>> >>> It supports windows server 2003 R2 so i'd expect it to support SBS
>>>> >>> 2003 R2 Premium.
>>>> >>>
>>>> >>> If it is supported: Do I need to install firewall and antivirus on
>>>> >>> Hyper-V itself or is it safe. (I think this is a stupid question,
>>>> >>> but can't find anything on that so want confirmation that I need to
>>>> >>> install)
>>>> >>>
>>>> >>> Thanks
>>>> >>>
>>>> >>> Bas
>>>> >>>
>>>>
>>>>
>>>>

>>

>

Thanks for all the help, Charlie and Larry!

I am pretty new to VM so I'd like to confirm that I understand you correctly.

Here is what I udnerstand:

1. Install Hyper-V core to the host machine
2. Assign Hyper-V a static IP address that will be outside the SBS IP-range
3. Install SBS 2003 R2 Premium with all paraferalia to a VM (with AV and ISA
etc)
4. Don't join the Hyper-V to the SBS domain.

Please realise that the host machine will directly connected to the router
that connects the network to the internet. All port numbers for internet
traffic such as 110, 25, 80 etc will be either closed or directed to the SBS
server's IP number.

Questions:
Won't SBS see the Hyper-V machine as a machine on the network and
automatically try to join it?
If I do the above things I should be OK with the hyper-V?

Thanks again!

Bas

"Charlie Russel - MVP" wrote:

> Doesn't matter. If all you're doing with Hyper-V is running the
> virtualization, then I honestly don't see a need to run the overhead of AV.
> Don't read your email, don't surf, don't connect to the internet at all,
> really, with the possible exception of getting updates. (and you could
> manage to do that all manually, if desired, using local .MSU files.)
>
> Now if you really want to cut down the footprint, use the Hyper-V Server, or
> Windows Server running a Core install. Plus, if you opt for Hyper-V Server,
> you can run the R2 version that gives you hot add/remove of VHDs. (Plus it's
> a lot faster with dynamic disks than v1 was.)
>
> --
> Charlie.
> http://msmvps.com/blogs/xperts64
> http://mvp.support.microsoft.com/profile/charlie.russel
>
>
> "Larry Struckmeyer [SBS-MVP]" <lstruckmeyer@newsgroup-wizards.com> wrote in
> message news:ex9%23mZgOKHA.4028@newsgroup

> > Thanks, Charlie.
> >
> > I was hoping you would check in here.
> >
> > Can you clarify exactly what version of Server/Hyper-V you are discussing
> > here, or if it matters?
> >
> > --
> > Larry
> > Please post the resolution to your
> > issue so that others may benefit.
> >
> > Get a Health Check for SBS at:
> > www.sbsbpa.com
> >
> >
> > "Charlie Russel - MVP" <Charlie@newsgroup> wrote in message
> > news:%23p7cICgOKHA.5128@newsgroup

> >> Well, I'll offer a different answer wrt Hyper-V. If you use hyper-v as it
> >> should be, with NO additional roles or features installed that aren't
> >> directly related to managing Hyper-V, and you don't use it as a
> >> workstation or web surfer or other reason to connect to the Internet,
> >> then why worry about it? A-V software imposes a fair amount of overhead
> >> on file access, and it's not something I want on my virtualization
> >> parent. So, I run the absolute minimum on my Hyper-V host, I don't join
> >> it to the domain (since the domain is virtualized as a child on it), and
> >> I have it set to not even have an IP address on the SBS network's subnet.
> >> My Hyper-V host has two NICs that it can see: the iSCSI subnet, and the
> >> management subnet. Both of which run on segregated subnets from my domain
> >> network.
> >>
> >> --
> >> Charlie.
> >> http:/msmvps.com/blogs/xperts64
> >>
> >>
> >> "Bas" <Bas@newsgroup> wrote in message
> >> news:9F99F40F-52FF-47C1-8D14-C431161299CB@newsgroup
> >>> Right, thanks larry
> >>>
> >>> You confirmed for me what I expected: that I need two protection
> >>> packages
> >>> then. One for the HYper-V and one for the SBS VM.
> >>>
> >>> Thanks Again
> >>>
> >>> Bas
> >>>
> >>> "Larry Struckmeyer[SBS-MVP]" wrote:
> >>>
> >>>> The answer to the q about SBS being the DC is self evident. SBS can
> >>>> *only*
> >>>> be a DC. There can be other DCs in the domain, but SBS *must* be a DC
> >>>> and
> >>>> hold all of the FSMO roles.
> >>>>
> >>>> The q about an edge device/firewall and AV is mostly to do with your
> >>>> comfort
> >>>> level. What is "safe" when the bad guys of the world work 24x7 to
> >>>> penetrate
> >>>> remote computers is anyones guess really. It also depends on what you
> >>>> have
> >>>> to lose. If you are guarding the recipie for Coke, then you probably
> >>>> don't
> >>>> want it in electronic form anywhere. If you are guarding Joes Plumbing
> >>>> (no
> >>>> offense to Joe) it may be a different matter.
> >>>>
> >>>> But, if you go unprotected on the internet, call the server "Honey Pot"
> >>>> becuase
> >>>> it will surely be one.
> >>>>
> >>>> -
> >>>> Larry
> >>>> Please post the resolution to your
> >>>> issue so others may benefit
> >>>> -
> >>>> Get Your SBS Health Check at
> >>>> www.sbsbpa.com
> >>>>
> >>>>
> >>>> > Ok thanks!
> >>>> >
> >>>> > So it isn't supported by MS but it should work.
> >>>> >
> >>>> > What I didn't understand is: can SBS be the DC while vitualised?
> >>>> >
> >>>> > We are planning a clean install of the SBS 2003 and might are looking
> >>>> > at doing this directly under Hyper-V if pratical...
> >>>> >
> >>>> > Also my questions about the security of the Hyper-V server were not
> >>>> > answered.
> >>>> >
> >>>> > Could you please answer those for me?
> >>>> >
> >>>> > Thanks
> >>>> >
> >>>> > "Larry Struckmeyer [SBS-MVP]" wrote:
> >>>> >
> >>>> >> Look for a similar thread on 09-04-2009 in this group.
> >>>> >>
> >>>> >> --
> >>>> >> Larry
> >>>> >> Please post the resolution to your
> >>>> >> issue so that others may benefit.
> >>>> >> Get a Health Check for SBS at:
> >>>> >> www.sbsbpa.com
> >>>> >> "Bas" <Bas@newsgroup> wrote in message
> >>>> >> news:61768BCF-1F4A-4801-92B7-F7C72BE2F4CB@newsgroup
> >>>> >>
> >>>> >>> Does anyone know if BS 2003 is supported on Hyper-V?
> >>>> >>>
> >>>> >>> It supports windows server 2003 R2 so i'd expect it to support SBS
> >>>> >>> 2003 R2 Premium.
> >>>> >>>
> >>>> >>> If it is supported: Do I need to install firewall and antivirus on
> >>>> >>> Hyper-V itself or is it safe. (I think this is a stupid question,
> >>>> >>> but can't find anything on that so want confirmation that I need to
> >>>> >>> install)
> >>>> >>>
> >>>> >>> Thanks
> >>>> >>>
> >>>> >>> Bas
> >>>> >>>
> >>>>
> >>>>
> >>>>
> >>

> >

>
>