Tag how to

Hello everyone, in this video I am going to install mikrotik router os on hyper-v and after that I will be configure routerOS to provide internet access for clients by configuring dhcp server , create a nat rule , setup pptp vpn server. Ok lets start

1. Hardware Requirements:
   • MikroTik router device (such as a MikroTik RouterBOARD)
   • Ethernet cables
   • Computer with an Ethernet port
   • Power source for the router
2. Initial Setup:
   • Connect the MikroTik router to a power source and to your computer using an Ethernet cable. The router usually has a default IP address for the initial configuration, such as 192.168.88.1. Ensure that your computer is set to obtain an IP address automatically through DHCP.
3. Access the Router:
   • Open a web browser on your computer and enter the default IP address of the MikroTik router in the address bar (e.g., http://192.168.88.1).
   • You should see the MikroTik login page. The default username is “admin,” and there is no password by default. It is crucial to change the default password during the initial setup for security reasons.
4. Basic Configuration:
   • Once logged in, you can start configuring the router. Here are some basic configurations:
     • Set a strong password for the “admin” user.
     • Set the router’s hostname.
     • Configure the time zone.
     • Set the DNS servers.
5. LAN Configuration:
   • Configure the LAN (Local Area Network) settings, including the IP address and subnet mask for the router’s LAN interface.
   • You can create DHCP server pools to assign IP addresses to devices on your local network automatically.
6. WAN Configuration:
   • Configure the WAN (Wide Area Network) interface, which could be connected to your internet service provider (ISP). This often involves configuring the IP address, subnet mask, gateway, and DNS servers provided by your ISP.
   • Set up NAT (Network Address Translation) if you have multiple devices on your LAN and want them to share a single public IP address.
7. Firewall Configuration:
   • Create firewall rules to control incoming and outgoing traffic. MikroTik routers have a powerful firewall system that allows you to filter and control traffic based on various criteria.
8. Security and Access Control:
   • Configure access control lists (ACLs) to restrict or allow specific traffic.
   • Enable SSH or secure Winbox access for remote management and disable insecure services like Telnet.
9. Additional Features:
   • Depending on your needs, you can configure various additional features such as VPNs, VLANs, QoS (Quality of Service), routing protocols, and more.
10. Save and Backup Configuration:
    • After configuring your MikroTik router, make sure to save your configuration settings and create regular backups. This can be done through the router’s web interface.
11. Testing:
    • Test your network to ensure everything is working as expected. Check internet connectivity, LAN connectivity, and any specific services or features you’ve configured.
12. Documentation:
    • Keep thorough documentation of your MikroTik router’s configuration, including any changes you make over time. This will be helpful for troubleshooting and future reference.

bash
sysprep.exe /generalize /oobe /shutdown /unattend:unattend.xml

• /generalize: Prepares the Windows installation to be imaged.
• /oobe: Configures the computer to boot to Windows Welcome upon the next restart.
• /shutdown: Shuts down the computer after Sysprep completes.
• /unattend:unattend.xml: Specifies an unattend.xml file to automate the Sysprep process. This file is optional but recommended for consistency.

Step 3: Boot the Reference Computer into Windows PE

• Insert a bootable media (USB drive or DVD) containing Windows PE.
• Boot the reference computer from the bootable media.

Step 4: Capture the Image

• In Windows PE, open a command prompt.
• Use the WDSUTIL command to capture the image. For example:

mathematica
WDSUTIL /Verbose /Progress /Capture-Image /Image:”CustomImage” /Name:”Custom Image” /Description:”Customized Windows Image” /CaptureDir:”D:\Captures”

• /Image:"CustomImage": Specifies the name for the captured image.
• /Name:"Custom Image": Specifies a friendly name for the captured image.
• /Description:"Customized Windows Image": Provides a description for the captured image.
• /CaptureDir:"D:\Captures": Specifies the directory to store the captured image.

Step 5: Upload the Captured Image to WDS Server

• After capturing the image, navigate to the WDS server.
• Use the WDS MMC snap-in or the WDSUTIL command to upload the captured image to the server.

Step 6: Create an Install Image

• In the WDS MMC snap-in, right-click on “Install Images” and select “Add Install Image.”
• Specify the location of the captured image file and follow the wizard to create the install image.

Step 7: Deploy the Image

• Boot a client computer from the network using PXE boot.
• Select the customized image from the WDS server for deployment.
• Follow the on-screen instructions to deploy the image to the client computer.

Make sure to test the deployment thoroughly before deploying to production environments.

1. Install Windows Deployment Services Role:

• Open Server Manager on a Windows Server machine.
• Click on “Add roles and features.”
• Select “Windows Deployment Services” as the role to install.
• Follow the wizard to complete the installation.

2. Configure Windows Deployment Services:

• After installing the role, open the Windows Deployment Services console from the Server Manager.
• Right-click on the server name and select “Configure Server.”
• Follow the wizard to configure the server.
• Choose the location to store the images (you can use the default location).
• Select “Integrated with Active Directory” if you want to use Active Directory Domain Services (AD DS) to authorize clients and manage computer accounts.
• Specify the DHCP server settings. You can choose to configure DHCP options 60, 66, and 67, or you can manually configure DHCP options if you’re using a separate DHCP server.

3. Add Boot and Install Images:

• In the Windows Deployment Services console, expand the server name.
• Right-click on “Boot Images” and select “Add Boot Image.”
• Browse to the location of the Windows installation files and select the boot image (boot.wim) file.
• Repeat the process to add the install image (install.wim) file for the Windows version you want to deploy.

4. Configure DHCP Options (if not done in step 2):

• If you didn’t configure DHCP options during the WDS configuration, you’ll need to do it manually on your DHCP server.
• Configure option 60 to PXEClient.
• Configure option 66 to the IP address of the WDS server.
• Configure option 67 to boot\x64\pxeboot.n12 for BIOS-based systems or boot\x64\wdsmgfw.efi for UEFI-based systems.

5. PXE Boot and Install Windows:

• Boot the client computer from the network (PXE boot). This usually involves pressing a key (e.g., F12) during startup to access the boot menu and selecting the network boot option.
• The client will contact the WDS server and load the boot image.
• Follow the on-screen instructions to select the install image and complete the Windows installation.

6. Monitor Deployment:

• Use the Windows Deployment Services console to monitor the deployment process and view the status of client installations.

By following these steps, you can set up Windows Deployment Services to deploy Windows operating systems over the network, making it easier to manage and deploy Windows installations across multiple computers.

1. Preparing the Environment:

• Ensure that both servers meet the hardware and software requirements for Windows Server and DHCP.
• Assign static IP addresses to each server.
• Ensure that DNS is properly configured and that both servers can resolve each other’s names.

2. Installing the DHCP Server Role:

• Open Server Manager on both servers.
• Select “Add roles and features” and proceed with the installation wizard.
• Select “DHCP Server” as the role to install.
• Complete the DHCP Server installation wizard.

3. Configuring DHCP Failover:

• Open DHCP Manager on one of the servers.
• Right-click on the DHCP server name and select “Configure Failover.”
• Follow the wizard to configure DHCP failover.
• Choose the partner server, configure the shared secret, and set the mode (Load Balance or Hot Standby) and relationship (Primary or Secondary).

4. Installing the Failover Clustering Feature:

• Open Server Manager on both servers.
• Select “Add roles and features” and proceed with the installation wizard.
• Select “Failover Clustering” as the feature to install.

5. Creating the Cluster:

• Open Failover Cluster Manager on one of the servers.
• Click on “Create Cluster” and follow the wizard.
• Add both servers to the cluster.
• Configure cluster settings such as the cluster name and IP address.

6. Configuring DHCP Server Role in the Cluster:

• In Failover Cluster Manager, right-click on “Services and Applications” and select “Configure a Service or Application.”
• Select “DHCP Server” as the service to configure.
• Follow the wizard to add the DHCP server role to the cluster.

7. Testing Failover:

• Perform a failover test to ensure that the DHCP server cluster functions correctly.
• Use the Failover Cluster Manager to initiate a failover and verify that DHCP services remain available during the failover process.

8. Monitoring and Maintenance:

• Regularly monitor the DHCP server cluster using Failover Cluster Manager to ensure it remains healthy.
• Perform regular maintenance tasks, such as applying updates and patches, to keep the cluster secure and up-to-date.

Note: Ensure that you have sufficient IP address ranges and leases configured to handle the increased demand that comes with clustering. Additionally, testing failover in a controlled environment is crucial to ensure proper functioning in a production environment.

1. Prepare the Windows ISO: Obtain a Windows installation ISO file. You can download these from the Microsoft website or use an existing ISO file you have.
2. Upload the ISO to EVE-NG: Log in to the EVE-NG web interface. In the top menu, go to “Images” and then click on “Browse” to select the Windows ISO file from your local machine. Click on “Upload” to upload the ISO file to EVE-NG.
3. Create a QEMU VM: In the EVE-NG web interface, go to the “Node” section and click on “Add Node.” Select the type as “QEMU” and configure the settings for the VM. You can specify the number of CPUs, amount of RAM, and the size of the hard disk.
4. Map the Windows ISO: In the QEMU VM settings, go to the “Console” tab. Under the “CD/DVD” section, select the Windows ISO file you uploaded earlier as the CD/DVD image.
5. Start the VM: After configuring the VM settings, click on “Add Node” to create the QEMU VM. Start the VM by clicking on the play button in the EVE-NG interface.
6. Install Windows: Access the VM console by right-clicking on the VM in the EVE-NG interface and selecting “Console.” The VM will boot from the Windows ISO. Follow the on-screen instructions to install Windows. You may need to format the virtual hard disk and select the installation partition during the process.
7. Complete the Installation: After Windows is installed, the VM will restart. You can then log in to Windows and configure it as needed.
8. Optional: Install VirtIO Drivers: For better performance, you can install VirtIO drivers in Windows. These drivers are included in the EVE-NG installation and can be found in the /opt/unetlab/addons/qemu/virtio-win directory. To install the drivers, mount the VirtIO ISO in Windows and run the installer.
9. Access Windows from EVE-NG: Once Windows is installed and running, you can access it from EVE-NG by right-clicking on the VM in the EVE-NG interface and selecting “Console.”
10. Activate Windows: After installation, you’ll need to activate Windows using a valid product key. You can do this by going to “Settings” > “Update & Security” > “Activation” in Windows.

Remember to comply with Microsoft’s licensing terms and ensure that you have a valid license for Windows when using it on EVE-NG or any other virtualization platform.