Post

Day-5 Windows Server Installation

Posted Updated
By Cyberpengunine__
1 min read

day-5

Today, we’ll focus on creating our Windows server as a target machine. This server will play a crucial role in our simulated attack scenarios, following the logic diagram we established on Day 1.

Let’s get started:

  1. Launch a New Vultr Server:
    • Log in to your Vultr account and go to compute option.

    • Click on “Deploy New Server”.

      new-server.png

    • Choose “Cloud Compute - Shared CPU” as the server type.

      select-type.png

    • Select the same location as your VPC and ELK instance for optimal network connectivity.

      choose-location.png

    • For the image, select “Windows Standard 2022 Server”.

      win-image.png

    • Choose a suitable plan, such as the “Regular Cloud Compute” with 1 vCPU, 2GB RAM, and 55GB SSD storage.

      select-plan.png

    • Do not choose any Additional Features for Win-server. We will not add it to VPC as per our modification in logical diagram below.

      no-additional-features.png

  2. Isolate the Windows Server:
    • Let’s adjust our logic diagram from Day 1. We’ll place the Windows server and Ubuntu server outside the VPC. This means they’ll be accessible from the internet but won’t have access to the private network used by other servers within the VPC. This isolation will help prevent any potential compromise of the Windows server from affecting the rest of our setup.

    Modified-Logic-Diagram.drawio.png

  3. Deploy and Access the Server:

    • Give your server a meaningful name and deploy it.

      server-hostname.png

      deployed-win-server.png

    • Once deployed, open the server and click “Show Extra Keys”(with symbol ‘A’).

      clt-alt-del-key.png

    • Then click on option Send Ctrl+Alt+Del (Three dots) to send a keyboard interrupt and log in using the provided credentials.

      put-win-pass.png

      running-windows.png

  4. Expose RDP:
    • Ensure that Remote Desktop Protocol (RDP) is exposed to the internet. This will allow you to access the server remotely.

    • To verify, copy the server’s public IP address and try connecting to it using RDP on your system.

      rdp-exposed.png

That’s it for today! We’ve successfully deployed the Windows server. In the next blog post, we’ll focus on configuring it for its role in our simulated attacks.

MYDFIR 30Day SOC_Challenge
soc_challenge soc cybersecurity day5of30
This post is licensed under CC BY 4.0 by the author.