Join Timothy Pintello for an in-depth discussion in this video Creating a snapshot of your virtual machine, part of Windows Server 2012: Installation and Configuration.
…Now, we have gone ahead and created our installation and added our drivers to it.…We want to go ahead and create a snapshot.…Now, the purpose of a snapshot is to make sure that if something goes wrong later,…we can always go back to a previous state that was undamaged.…This will come in very helpful for this course because as we do changes to…our system, we will want to go to the original state of the system and…rather had to re-install everything from scratch,…all we have to do is load a snapshot from a previous version of the virtual machine,…and everything will be sent to where it was originally.…
The way we create a snapshot is click this Snapshots icon here.…And this brings us to the Snapshot Manager screen.…To create a snapshot, we go ahead and click this camera-looking icon.…At this point, we need to go ahead and name our snapshot, and in this case,…we want to go ahead and name our snapshot basic system.…We're choosing basic system because that's descriptive of what the snapshot is.…Once you put your snapshot name in there, you can go ahead and click OK.…
Learn how to choose an edition that's right for your setup, install Windows Server 2012 and the VirtualBox drivers, and then configure the services and roles on your new server. Timothy also shows how to set up local storage and manage Windows Server in one of two ways: through the command line or with the simple admin interface that ships with Windows Server.
- Installing Windows Server 2012
- Installing VirtualBox drivers
- Configuring server roles
- Configuring services
- Configuring disk and file systems
- Using alternative administration methods
Skill Level Beginner
Q: Why can't I get my servers to talk to each other when I attempt to add a standalone computer virtual machine (VM) to my domain VM in VirtualBox?
A: Check the following settings if you are having this problem.
- Are your VMs' network adapters set to host-only?
- Do all your VMs have the correct IP address?
- Do all your VMs have the default gateway set to the same IP address of the host-only adapter in your domain controller VM?
- Is your DHCP server set up to manage the same IP address range of the IP address you are attempting to manually enter into your standalone server's VM?