virtualbox.org

I am trying to gather information before attempting to build a network inside of a virtual machine. There are two considerations which must be satisfied before attempting to build the network:

• The budget is very strained; so I must use available resources and only free software to enable the virtual network.
• I prefer to avoid starting the build only to find out that it cannot be done using VirtualBox. My main concern here is Microsoft activation at a later date if it is not possible for VirtualBox to run a network in a virtual environment.

With that said, here is the basic architecture I wish to create inside a VM.

1. The physical host is Windows 7 HP SP1x64.
2. The virtual guest will be the network I wish to build.
3. The network will run Windows Server 2008R2 x64 with two clients (Win 7 Pro SP1 x64 and Win 8 Pro x64.)

What do I wish to accomplish?
This will serve as my personal classroom/lab to learn Server 2008 and apply classroom curriculum to get a feel for something simulating real world environments. (for example: configuring a network, implementing group policies, deploying apps or utilities to clients, etc.) I wish to establish communication inside the virtual network and/or the host and Internet as I choose for various learning purposes. The ability to restore any broken OSes or reset to default configurations for experimenting with new configurations is a real bonus.

I have read the VirtualBox User Manual, and to the level of my understanding, it sounds like this is possible. I realize that this is a technically challenging task with a steep learning curve.

So here are the specific questions I have before attempting the build.
Will VirtualBox allow me to run three virtual OSes (server and two clients) simultaneously in a single instance of VirtualBox?
If the answer to the above is yes, does the virtual server have to be launched before the virtual clients to enable full features?
If the answer to running the virtual OSes simultaneously is no, can multiple instances of VirtualBox run at the same time and be integrated to simulate a network? If so, do you have recommended reading or specific guidance?

All helpful answers and guidance will be appreciated.

You can run as many guest simultaneous as you have memory to support them.

You should also look at the below link to make you life easier while learning how to manage Windows domains and not interfere with your local LAN.

The easiest and for most the best way to use and test Windows domains in VirtualBox
Setup Windows Domain in VirtualBox

PerryG,

To the best of my understanding I satisfy minimum system requirements for running the full network. (i3-2330M @2.2GHZ, hyperthreading and virtualization enabled and 8GB memory and plenty of HDD free space -- I think this is cutting it pretty tight.)

Thanks for the link. Some of the jargon in the link is unfamiliar to me. I researched the terms included in the linked article and have a few questions about the terms and instructions:
1) In the diagram: Is the domain controller the same thing as the NOS (Server 2008) I wish to use, and are the clients Win7 and Win8? The best description I found through research was In a Microsoft article. Well Phooey! I have not satisfied minimum requirements to include urls yet. ... anyway ... The definition I found seems to qualify the client/server as a domain. Is that correct?
2) From the article, "The easiest way to setup a Windows Domain for testing and learning is to set it up in its own network outside of the local network." If my understanding is correct, my file and printer sharing via Windows Network and Sharing Center (three computers, two printers) is not the same as a client/server network. so... Would the virtual client/server in VirtualBox running in my Windows7 host be considered "in its own network outside of the local network" or "in the local network"?
3) Can Server 2008 act as the guest performing the routing for Internet access?

Thanks again.

1) Yes and the clients can be anything, even Linux guests.

2) Files within the domain network will be able to be shared and printers that are connected to the domain network will as well but not the ones in the local LAN.
If you are wanting to use resources within the local LAN you would not use the Internal network, but this is going to make your life harder. Keep in mind that configuration and set up of guests are outside the scope of this forum. You would need to use your study material and MS forums for that.

3) Yes but the cost of using it will drop your ability to add at least one other guest. The router ( PC ) would be a stand alone and is the gateway for the test domain.

1) understood

2) referring to the diagram again ... I have discovered that it is possible (in VMware Player ... don't know about VirtualBox) to create the individual VMs and then move them to an external drive. (This satisfies my requirement for using existing resources. Adding an additional standalone computer is in the far future.)The various virtual OSes are run by pointing to the file on the external drive containing the OS from the virtualization program on the host machine. In this scenario, does the host qualify as the standalone computer? I can draw it that way, but I don't think it will be that way from an operational standpoint.

I understand that this is a complex project because I am combining multiple topics into one. I am currently assembling my informational resources and intend to attempt to get one component running properly at a time before beginning the next where possible.

3)Because the host memory is maxed out at 8GB, I did not intend to increase the number of guests running at a given time. If I am interpreting the system requirements and the operation of VirtualBox properly, the memory allocation will be 2GB for host + 2GB for server guest + 2GB each for the client guests. Any guests not running do not borrow memory from the host. Do I have the correct read on that?

While I usually start with 2048MB to install the guest (makes install faster) I then reduce the memory to 512MB when finished. The guest will operate at that level unless you are really hammering it hard, but for most this will allow you to operate the server and at least 3 guests, maybe more, for testing. Of course if this is to be a live, real environment even 2GB is not adequate.

good deal .. I was not aware that I could decrease memory after installation and still have a reasonably functional OS.

This will be for testing/learning purposes. I will run from one host only; so I don't foresee scenarios where I will be able to hammer it hard. The real environment of multiple users pushing the limits of system requirements is not in my game plan. I just want to gain functional basic client/server understanding in my controlled environment before being introduced to it in the real world. My classes are too fast paced to allow adequate lab time and Q&A beyond the scope of the curriculum defined for the classes. Thirty lab minutes/week and five Q&A minutes/lecture don't adequately address my thirst for understanding. The only solution I see to expand my understanding is independent study and experimentation.

I believe I am ready to begin the build in my spare time.

I really appreciate the knowledge and experience you have shared with me.

regards,
mrdp