Justin Corbin Portfolio Labs
- 1. Master Switch Switch Switch Switch Root DC Domain1.biz DNS DC SubDomain1.biz DNS DHCP Root DC Domain2.biz DNS DC SubDomain2.biz DNS DHCP Root DC Domain3.biz DNS DC SubDomain3.biz DNS DHCP Member Server VPN Member Server VPN Member Server VPN Windows Network Infrastructure Lab Scenario Multiple Domains and VPNs Notes 1. Each domain has a different IP address and subnet — each is a Forest/Site 2. Only two workstations can be connected via VPN. 3. Note that Router Switches can also be used to create VPN connection. 4. Create 5 users with profiles on each Root DC. 5. Master switch is the classroom switch — use uplink on assigned row. Workstation Connects to Domain1.biz via VPN Workstation Connects to Domain2.biz via VPN Workstation Connects to Domain3.biz via VPN
- 2. Creating a Windows 2012 Domain Controller with PowerShell Note : Complete this Hands-on Lab using a Virtual Machine that is hosted on either your ESXi host or Hyper-V host. In either case, be sure that you are on an Internal Connector. (your virtual server needs to be isolated from the network.). To create the domain controller use the ADDSDeployment module. You’ll only find this on servers where you’ve installed the AD Domain Services feature which you do like this: Install-WindowsFeature -Name AD-Domain-Services -Confirm:$false Import the module Import-Module ADDSDeployment Get-Command -Module ADDSDeployment Create the Domain Controller. This is the equivalent of running DCPROMO in earlier versions. Even better you don’t need the answer file. Everything is a parameter on the cmdlet. Install-ADDSDomain Controller -DomainName "manticore.org" -InstallDns -Credential (Get-Credential manticorerichard) -ApplicationPartitionsToReplicate * Thats it! Just wait for replication to happen. You can also demote a domain controller $cred = Get-Credential Uninstall-ADDSDomainController -Credential $cred -RemoveApplicationPartitions -Confirm:$false Restart the machine and uninstall AD & DNS Uninstall-WindowsFeature -Name AD-Domain-Services, DNS -Confirm:$false Restart-Computer -ComputerName dc02 Leave the domain $cred = Get-Credential manticorerichard Remove-Computer -UnjoinDomainCredential $cred -Workgroup Test Trash the VM. And best of all it works over remoting. You will need to recreate the session for restarts & changes but it is really easy. Server Core is now a much friendlier option. Windows Server 2012 R2 Server Core Virtual Machine CNT 253 hands-on Lab Domain Controller via PowerShell Note: This lab is posted in Canvas also. You must turn in this diagram with your notes and name for credit.
- 3. InternalConn Switch Virtual Machine Windows Server 2012 R2 AD and DNS Server Enterprise Edition (GUI) Static IP Address CN = ServerXYZ Scope for 50 hosts Exclusion Range for 1st 10 Ips Reservation for 2 Clients CNT 251 SP 14 – Hands-on Lab Virtual DC, DNS and DHCP Member Servers Virtual Workstation (2 of these!) Windows 7 or Windows 8 installed Gets DHCP IP Address from DHCP Server Gets DNS address from DHCP Server Virtual Machine Windows Server 2012 R2 Member Server Server Enterprise Edition (GUI) Static IP Address CN = ServerXYZ DHCP Server Scope for 50 hosts Exclusion Range for 1st 10 Ips Virtual Machine Windows Server 2012 R2 Member Server DNS Server Server Enterprise Edition (GUI) Static IP Address CN = ServerXYZ Has Zone for your Domain!!