Re: SBS on Virtual PC?
From: attila (gcsokai-nospam_at_yahoo.com)
Date: Sun, 24 Oct 2004 21:26:01 -0400
Thanks for all the tips!
"David Copeland [MSFT]" <firstname.lastname@example.org> wrote in message
> Just realized I forgot.. in case you've not seen it..
> Microsoft Virtual PC 2004 Service Pack 1
> Other related links
> Microsoft Virtual PC 2004
> Microsoft Virtual PC 2004 Free 45-Day Trial Edition
> Microsoft Virtual Server 2005
> Virtual Server 2005 Evaluation Kit
> Hope that helps,
> David Copeland
> Microsoft Small Business Server Support
> This posting is provided "AS IS" with no warranties, and confers no
> SBS Newsgroups:
> SBS v4.x: microsoft.public.backoffice.smallbiz
> SBS 2000: microsoft.public.backoffice.smallbiz2000
> SBS 2003: microsoft.public.windows.server.sbs
> "David Copeland [MSFT]" <email@example.com> wrote in message
>> True, and depending on how fast of a machine/drives and ram and/or
>> of machines you have licensed for Virtual PC/Virtual Server and the guest
>> OS'es you have the ability to create all kinds of environments.
>> Something to keep in mind Virtual Server is the one that SBS would really
>> supported in.. even though it may run fine in VPC. (see below)
>> Attilla, you mentioned that seems like it might be easier with just
>> another machine.. sometimes that may be true.. but depending on what
>> testing/doing.. it sure comes in handy sometimes to be able to simply
>> off the virtual machine and selecting the option to discard the changes..
>> and then simply boot the virtual machine back up for the occassional
>> :) as opposed to manually undoing/re-installing/restoring..
>> You will have to keep in mind that if you do configure a client virtual
>> machine and an SBS server with ISA behind another ISA server that you may
>> need to do additional configurations on the virtualized SBS to do
>> routing through the other ISA server or at least be aware that if
>> isn't working from the virtual pc client that it could be the other ISA
>> server blocking it. (or depending on your networking config you could
>> it connected directly to the external world).. Be sure that you keep any
>> virtual machines up to date with service packs, security updates, and
>> anti-virus updates, etc. as if it were another real machine too.
>> Also, with a real machine can you write a script to configure it.. ;)
>> Script Repository: Virtual Server
>> Sample scripts for managing Microsoft Virtual Server.
>> TechNet Webcast: Virtual Server 2005 COM API: Automating Your Virtual
>> World-Level 300
>> Couple of other tips with virtual machines..
>> 1) Lot cheaper way to learn about things like software mirring, stripe
>> etc.. than having to buy enough actual hardware to do it.
>> 2) Good way to learn/test things like Exchange disaster recoveries
>> 3) Can use virtual floppies for things like a PXE boot floppy for RIS
>> 4) If you are installing SBS into a virtual machine on Virtual Server..
>> sure to turn off VS's DHCP server so that it doesn't conflict with SBS
>> trying to install/configure DHCP.
>> 5) Keep in mind that VPC only support up to a 2g ISO image
>> Q. Does Virtual Server 2005 support non-Microsoft operating systems
>> A. Although Virtual Server 2005 can run virtually all major
>> server operating environments, Microsoft Product Support Services
>> only the following guest operating systems using Virtual Server 2005:
>> . Windows Server 2003, Standard Edition
>> . Windows Server 2003, Enterprise Edition
>> . Windows Server 2003, Web Edition
>> . Windows Small Business Server 2003, Standard Edition
>> . Windows Small Business Server 2003, Premium Edition
>> . Windows 2000 Server
>> . Windows 2000 Advanced Server
>> . Windows NT Server 4.0 with Service Pack 6a
>> Q. Are virtual machine created with Virtual PC compatible with
>> Server and vice versa?
>> A. Yes, virtual machines with either product are compatible, but
>> using Virtual Server and Virtual PC together, there are several points to
>> . Sound cards: Virtual Server does not include an emulated
>> card in its virtual machines, while Virtual PC does. If you will be using
>> virtual machine on both Virtual Server and Virtual PC, you should disable
>> the emulated sound card in Virtual PC. This will prevent the sound card's
>> Plug and Play capability from causing errors on the virtual machine that
>> created with Virtual Server.
>> . SCSI support: Virtual Server provides SCSI support while
>> Virtual PC does not. If you create a virtual machine with virtual SCSI
>> on Virtual Server, the SCSI disks will be ignored if you move the virtual
>> machine to Virtual PC. This can lead to negative consequences in many
>> situations, for example if the virtual machine page file is on the SCSI
>> or if you are trying to use a SCSI disk as the startup disk. If you plan
>> regularly move virtual hard disks between machines created with Virtual
>> and Virtual Server, we recommend that you attach the virtual hard disks
>> to a virtual IDE bus in Virtual Server.
>> . Saved States: Saved-state (.vsv) files between Virtual PC
>> Virtual Server are incompatible. When moving a virtual machine between
>> products, be sure to completely shutdown the guest operating system.
>> . CD-ROM drives: Although Virtual Server allows for virtual
>> machines with multiple CD-ROM drives, Virtual PC supports virtual
>> with only one CD-ROM drive. If you are moving virtual machines between
>> two products, you should configure only a single CD-ROM drive on the
>> machine and attach it to secondary channel 0, which is the default
>> Hope that helps,
>> David Copeland
>> Microsoft Small Business Server Support
>> This posting is provided "AS IS" with no warranties, and confers no
>> SBS Newsgroups:
>> SBS v4.x: microsoft.public.backoffice.smallbiz
>> SBS 2000: microsoft.public.backoffice.smallbiz2000
>> SBS 2003: microsoft.public.windows.server.sbs
>> "SuperGumby [SBS MVP]" <firstname.lastname@example.org> wrote in message
>> > the possibilities are numerous if not infinite.
>> > In my scenario you would also create a VPC client machine for your
>> > The VPC client would have a single NIC 'local only' to talk to the SBS
>> > "Attila" <$email@example.com> wrote in message
>> > news:OzBvZlIuEHA.firstname.lastname@example.org...
>> > > Thanks that is kind of tip I am looking for. What confuses me though
>> > > that if I install it on a worksation that is really connected to my
>> > > production SBS, then how do replicate the configuration of the ISA on
>> > > virtual PC running SBS? I am just trying to visualize it. The way I
>> > > is that the real NIC would be the "outside NIC" on the Virtual PC SBS
>> > > the the second NIC could be its Inside one. So then I could hookup a
>> > > switch to the second VPN NIC? and another worksation to that to
>> > > a real enviornment.
>> > >
>> > > Isn't just easier to buy a cheap Dell PowerEdge SC if the money can
>> > > be
>> > > made available?
>> > > Thanks,
>> > >
>> > > Attila
>> > >
>> > >
>> > > "SuperGumby [SBS MVP]" <email@example.com> wrote in message
>> > > news:O%23f15WIuEHA.3448@TK2MSFTNGP09.phx.gbl...
>> > >> Yes, give the VPC 2 nics. One is 'local only' the other goes to the
>> > >> NIC.
>> > >>
>> > >> I actually suggest installing SBS with just the 'local only'
>> > >> live. Complete the SBS Standard install including major to-do list
>> > >> then shut her down and add the 2nd interface to VPC.
>> > >>
>> > >> "Attila" <$firstname.lastname@example.org> wrote in message
>> > >> news:%23LOc3RIuEHA.2196@TK2MSFTNGP14.phx.gbl...
>> > >>> In a reply to an eariler question on testing SBS settings, Andrew
>> > >>> recommended to perhaps try MS Virtual PC. So I just installed the
>> > >>> version on one of my worksations. My question is, does anybody have
>> > >>> experience in using this with SBS 2003 or 2000? Especially in
>> > >>> using the ISA component, since it needs two NICS, and the
>> > >>> does not. So can realistically test ISA using Virtual PC?
>> > >>> Since I have the eval version, I will give this a try, but I am
>> > >>> just
>> > >>> looking for some feedback /experience.
>> > >>>
>> > >>> Thanks,
>> > >>>
>> > >>> Attila
>> > >>>
>> > >>
>> > >>
>> > >
>> > >