+- Hack Forums (https://hackforums.net)
+-- Forum: Tech (https://hackforums.net/forumdisplay.php?fid=444)
+--- Forum: Computing (https://hackforums.net/forumdisplay.php?fid=88)
+---- Forum: Computing Lounge (https://hackforums.net/forumdisplay.php?fid=8)
+---- Thread: How to manage multiple VMs for infosec training and lab? (/showthread.php?tid=5663533)
How to manage multiple VMs for infosec training and lab? - c2de23 - Jul 6, 2017
Let's say I have the following OSs:
Kali 2017.1
Ubuntu 17.04 Windows 10 Ent. 1607
Windows 7 Ent. SP1 Windows Server 2012 R2
Windows Server 2016
Right now I manage them this way (for Windows guests):
Install it via ISO on Type-2 Hypervisor (VMware Workstation or VirtualBox)
Wait for the automatic reboot after install Shutdown the virtual machine and save a snapshot as "RAW"
Turn on the virtual machine and continue the setup creating a username/password and doing the required initial config Activate the machine offline and turn it off
Save another snapshot as "ACTIVATED"
* Then I turn it on again and do all the updates necessary, turn it off and save a snapshot as "UPDATED"
From this point I do the things I need with the VM. If I need another virtual machine like this one I do a clone using the RAW or UPDATED as source.
-----
This process seems daunting and not reliable, also it's not recommended to use snapshots this way as stated by VMware Knowledge Base. How can I better handle my various VMs?
* - Armada - Jul 6, 2017
(Jul 6, 2017 02:35 PM)c2de23 Wrote: Let's say I have the following OSs:
Kali 2017.1
Ubuntu 17.04 Windows 10 Ent. 1607
Windows 7 Ent. SP1 Windows Server 2012 R2
Windows Server 2016
Right now I manage them this way (for Windows guests):
Install it via ISO on Type-2 Hypervisor (VMware Workstation or VirtualBox)
Wait for the automatic reboot after install Shutdown the virtual machine and save a snapshot as "RAW"
Turn on the virtual machine and continue the setup creating a username/password and doing the required initial config Activate the machine offline and turn it off
Save another snapshot as "ACTIVATED"
* Then I turn it on again and do all the updates necessary, turn it off and save a snapshot as "UPDATED"
From this point I do the things I need with the VM. If I need another virtual machine like this one I do a clone using the RAW or UPDATED as source.
-----
This process seems daunting and not reliable, also it's not recommended to use snapshots this way as stated by VMware Knowledge Base. How can I better handle my various VMs?
Sounds like you got it pretty much figured out.
I assume you want to snapshot the image/ISO/BIN file before config as a fresh install each and every time it is pre-loaded?
Sounds similiar to a Automated RDP deployment system.
But yea, you got it down right, just make sure after you take those initial snap shots (and ensure you do FULL snap shots, not the other linked crap) and backup the OG snaps.
Those you will want to mirror and use the mirrors as import.
Hope that helps.
Regards
* - c2de23 - Jul 7, 2017
(Jul 6, 2017 02:58 PM)Armada Wrote: Sounds like you got it pretty much figured out.
I assume you want to snapshot the image/ISO/BIN file before config as a fresh install each and every time it is pre-loaded?
Sounds similiar to a Automated RDP deployment system.
But yea, you got it down right, just make sure after you take those initial snap shots (and ensure you do FULL snap shots, not the other linked crap) and backup the OG snaps.
Those you will want to mirror and use the mirrors as import.
Hope that helps.
Regards
Yeah, but it's said that it's not recommended to use SP for a long time period. The way I'm doing I'd be using the "ACTIVATED" SP for undetermined time.