# Setup
We will be setting up this machine that sits on two vlans first
## Clone and Startup
1. Clone from template
2. Clone settings
3. Add another NIC so it is accessible on both vlans - 666 and 999
4. Power on and follow setup as usual
5. Accept
6. Create local user and password
7. Same privacy settings as before
8. After we login, we can access cmd and enter `ipconfig` and see that we have indeed been assigned identities in the two vlans by the respective DHCP servers in them (pfSense and DC01)

## Setting a Static IP
For this machine, we will assign it a static ip. For ease, we shall assign it 201 in both /24 vlans. So it will have have the IP Addresses:
- 172.16.66.201
- 192.168.99.201

1. Access Network Connections
2. For ethernet adapter connected to the vlan with the DC
- Disable IPv6
- Set the IP address as desired
- Set the DNS server to the DC
3. For the ethernet adapter on the vlan managed by pfsense
- Similarly, disable IPv6
- Set the static IP address
4. End state might look something like this

## Rename PC
Personally, I genuinely am a fan of having my PC name be something like DESKTOP-TB95UB. Something about that format just gives me a weird mini Dopamine shot - well, that's ADHD for ya!

However, as part of the exercise - and for later (I say "later" - but really, I'm adding this bit into this documentation much after, at the point when I realised I had to, really.) usage.

## Create limited-privilege user




## Additional Settings
1. Disable Screensaver
- If Sleep option is available - set that to never as well
2. I also tried setting the default gateway to the DC, but this made little difference
3. To ensure that they were on the same network, I turned off the firewall so my Kali VM could ping the Windows Client, but then I turned the firwall back on again later

## Joining the Domain



Another way of making sure your computer can find the DC and join the domain






## Enable Autologon as limited-privilege user
***This step was actually done very close to the end during the finishing touches stage***

Double-click executable to begin

Agree, because we all read it that one time

Set it using the local limited-privilege credentials