Work with your team to deploy and apply an initial configuration to six virtual servers.
CIT department VMware infrastructure
Agree with your team partner(s) on a naming convention for your servers.
Agree with your team partner(s) on a secure way to share service account passwords with each other. For example, you might want to use a cloud-based password manager that only members of your team can access. (KeePass might be a good option for this, with a shared password database stored in a cloud storage service such as Microsoft OneDrive or Google Drive, and shared to all team members, so that all can access it with their own copy of KeePass software.)
In each of your zones (secure,inside,DMZ) deploy a Windows Server and a Linux server, for a total of six servers. (This is a good starting point, but you may need to deploy additional servers in future assignments)
Choose an appropriate password for the Administrator or root account on each server. (Of course, don’t use a weak easily-guessable password like “password” or “123456.” On the other hand, do not use an overly complicated or lengthy random password either, because sometimes you will not be able to merely copy/paste a password from your team’s shared password manager, but instead you will be forced to carefully type it successfully in order to log in or gain elevated privileges on a server. Find an appropriate balance between security and convenience in your password selections.) Create additional accounts capable of administrator/root privilege on each server: one for each team member, and another for your instructor. (You’ll need to find a secure way to inform your instructor of that account’s initial password.) Make sure every team member can successfully log into and exercise administrator privilege on all six VMs.
Find the private network address ranges assigned to your team’s zones, and configure the virtual network interface of each VM with an appropriate static IP address. (None of these six servers should be configured to obtain an address via DHCP.) Verify that each pair of servers in each zone can ping each other. (Hint: a Windows Server will not respond to ICMP echo request “pings” by default. You will need to enable an inbound rule in Windows Defender Firewall with Advanced Security to let this happen.)
Make sure each server is renamed to match its VM name, according to your team’s machine naming convention. (By default, your Windows Servers are assigned a random hostname such as WIN-A1B2C3D4E5 when they are first deployed, so you’ll want to change that.)
Upload an illustrated tutorial, in which you explain what your team did and how you accomplished it.
Here are some very detailed illustrated “how-to” tutorials that should help you create these servers in vSphere:
Your team’s delivered tutorial should be much shorter than these how-to articles! Nevertheless: