Lab00‐Routing&Windows - ConnorEast/Tech-Journal GitHub Wiki
                
<< Previous Page 
              
           | Steps | Purpose | 
|---|---|
| Step 1: Confirm the firewall has access to both WAN & LAN Network Adapters | Allows for communication between networks | 
| Step 2: Launch the Web Console | Allows access to VM via Web Based Interface | 
| Step 3: go through the Wan interface setup and restart the box | Allows data to transfer from my WAN ip: 10.0.17.107 to the upstream gateway 10.0.17.2 | 
| Step 4: Select "Ping Host" and ping google | Confirms network connectivity | 
| Steps | Purpose | 
|---|---|
| Step 1: "open lusmgr.msc" | This is where users are stored and the area in which one would go to create a new super user account. | 
| Step 2: "under users, right click and select new user" | Once the new user is made you can log in with it | 
| Step 3: "right click on the new user, select properties, select add group, select administrators" | This gives the account administartive level privileges. | 
| Step 4: Set wks01 with a static IP | This is done to give basic network access to the Week VM | 
| Step 5: change the device host name | Changes the name for better AD controls | 
| Step 6: Go to the PFSense Firewall IP and complete the setup | This is done to finalize the network setup of the LAN. | 
| Steps | Purpose | 
|---|---|
| Step 1: Confirm the VM is on the LAN adapter | Allows internal network communication | 
| Step 2: use the command "sconfig" and go through the setup of section 8 | This allows for you to specify the Ip address, default gateway, and dns servers neccessary for proper network functionality. | 
Step 3:Install AD on Server Core 
  | 
The first command invokes powershell. The second command installs Active directory domain tools which allows for powershell compatability. The final command creates a new forest called "east.local" | 
| Steps | Purpose | 
|---|---|
  | 
Opens a command prompt and disables automatic windows updates as new updates may break AD services. | 
| Step 2: Manually set ip [10.0.5.10], gateway [10.0.5.2] & DNS [10.0.5.5] | The IP gives an address for data to be routed to. The gateway gives the next jump for data leaving your network. DNS gives access to AD configurations & name resolution. | 
| Step 3: go to "System/About/RenamePC" and connect to Domain | Allows the AD device to manage the VM. | 
| Step 4: Open Server Manager, Select Manage > Add Rules and Features, and select "Remote Server Administration Tools", "Role Administration Tools", "AD DS and AD LDS Tools", "DHCP Server Tools", "File Services Tools" | |
| Step 5: Select "Manage" > "add servers" > "[Name of Core]" | This adds the core server to the list of managable devices. | 
| Server Core: | A CLI based server focusing on improved speed via the removal of UI. Typically it used powershell for any and all changes which need to be made. | 
| Powershell: -Name | This commandlet specifies which host you are looking for information from. See Deliverable 5 for an active example | 
| Powershell: -DomainName | Specifies the tree which is to be looked at. Its importance increases based on how many forests exist. | 
| Powershell: |