RE: [ActiveDir] OT: Virtual Server 2005

[Bernard, Aric]

PXE can be leveraged in a number of ways, however keep in mind that the VMs in VS2005 don’t have a BIOS that supports PXE natively.  You can of course mount a bootable floppy disk with a PXE image and drive the VM from there.  You could use RIS or ADS to deploy new images to the VMs.  Microsoft’s VSMT leverages a combination of DHCP, PXE, ADS and VS2005 to migrate physical machines to virtual.   There are no issues when running VS2005 on a machine that is joined to a domain, nor are there any issues when the guest systems (VMs) are joined to the domain.   In terms of the network configuration, if you can clarify exactly what you want and don’t want the VMs to be able to do, I am sure we can specify the proper configuration.   Aric   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Noah Eiger Sent: Friday, November 19, 2004 1:21 PM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] OT: Virtual Server 2005   Thanks all. I will play around with the various methods of duplicating servers (Al, I assume by PXE you mean in combination with RIS? Do you use a virtual RIS server?)   As for the networking portion, I find that when I add a virtual host to a physical card, the virtual machine gets an address from my “real” network.   Also, are there issues with running the host machine on a machine that is joined to a real domain?   From: Mulnick, Al [mailto:[EMAIL PROTECTED] Sent: Friday, November 19, 2004 12:38 PM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] OT: Virtual Server 2005   Networking outside the box is usually done by adding the virtual host to the phys host network card.  The phys NIC acts as a router in this case and everything is NAT'd off to the external network. That's the same for letting the hosted OS access anything off the host server whether internet or internal network.   Copying virtual hosts can be done that way.  I believe there are some tools that make this easier, but that's the way I know of that makes the server supportable.  PXE is another way to provision servers in there. Depends on how you like to use it.  There are instances for copying the virtual servers to another isolated network that can also be done that don't require sysprep that would work well for testing environments.   For newsgroups, you might want to check yahoo newsgroups to see if one exists there yet.    Does that help?   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Noah Eiger Sent: Friday, November 19, 2004 3:24 PM To: [EMAIL PROTECTED] Subject: [ActiveDir] OT: Virtual Server 2005 Hello:   Is anyone using Virtual Server 2005? I am running a TechNet demo copy and had some questions. Documentation and support has been spotty (e.g., the newsgroup is not up and running yet). Here are a few questions. Any thoughts or pointers to web resources appreciated.   -          I can’t seem to figure out how you would set up a virtual network (using a virtual w2k3 server for dns, dhcp, etc.) and then route that out to the Internet. I guess one would need a virtual router/gateway. I think the virtual DHCP server does this. -          Is it possible to setup a virtual network that could also interact with other OS machines (e.g., Linux, MacOS X, etc.). I want to setup a virtual Windows network but also allow other OS machines to access file and directory services and Exchange. -          How would you duplicate virtual machines? It seems that once you have built a single W2k3 server and patched it, you could simply copy it and then sysprep it.   Any thoughts? Thanks.   -- nme