Thibble Wiki - User contributions [en]

Nginx Reverse Proxy + SSL

2025-04-14T14:59:13Z

T20A02: Created page with "= Nginx Reverse Proxy = In this guide I will be outlining the necessary steps to setup and configure a Nginx Reverse Proxy instance using docker, and configuring SSL using Lets Encrypt and Cloudflare. This will allow the use of subdomains and a safe way to expose services to the internet, which providing SSL based security for these services outside of the local network. == Setup == In this guide we will be using docker, and assuming that a basic installation of dock..."

= Nginx Reverse Proxy =

In this guide I will be outlining the necessary steps to setup and configure a Nginx Reverse Proxy instance using docker, and configuring SSL using Lets Encrypt and Cloudflare. This will allow the use of subdomains and a safe way to expose services to the internet, which providing SSL based security for these services outside of the local network.

== Setup ==

In this guide we will be using docker, and assuming that a basic installation of docker is installed on the host system. In additon do this for ease of configuration and scalability a docker file was used.

This will also assume that you have a docker macvlan network configured, to allow the container its own IP address for easy of port management with further containers.

First Create the directory to house your docker file and create a file named "docker-compose.yml" with the following content:

<pre>
services:
app:
container_name: reverse-proxy
image: 'docker.io/jc21/nginx-proxy-manager:latest'
restart: unless-stopped
networks:
service:
ipv4_address: 192.168.1.20
ports:
- '80:80'
- '81:81'
- '443:443'
volumes:
- ./data:/data
- ./letsencrypt:/etc/letsencrypt
healthcheck:
test: ["CMD", "/usr/bin/check-health"]
interval: 10s
timeout: 3s

networks:
service:
external: true
</pre>

If you are not using macvlan networking some edits can be made to yeild the following:

<pre>
services:
app:
container_name: reverse-proxy
image: 'docker.io/jc21/nginx-proxy-manager:latest'
restart: unless-stopped
ports:
- '80:80'
- '81:81'
- '443:443'
volumes:
- ./data:/data
- ./letsencrypt:/etc/letsencrypt
healthcheck:
test: ["CMD", "/usr/bin/check-health"]
interval: 10s
timeout: 3s
</pre>

Once this is saved, from that directory run <pre>docker compose up -d</pre>. This will pull and start the container. Now from the IP specified in the macvlan, or from the host address, you should be able to access the web UI with the following:

https://192.168.0.X:81/

Now you have spun a fresh install of Nginx proxy manager.

== SSL Configuration ==

In this half of the guide we will be going over the setup, and pulling of a "wildcard" or edge certificate from Cloudflare to validate the SSL of all of the subdomains you will be using from your domain.

Main Page

2025-04-14T14:47:25Z

T20A02:

Welcome to the Goomba Cloud Wiki!.

This guide includes a culmination of projects written by yours truly, the site administrator! You will find anything from Proxmox stack configuration, all the way to software manual install guides (Including a guide to setting up this wiki) and much more!

== Pages ==

=== Reference ===

[[Key Based SSH from Windows to Linux]]

[[Windows 11 Enterprise .iso creation]]

[[Windows 11 Network Bypass]]

=== Services ===

[[Forgejo Install from Binary]]

[[Vaultwarden Docker Container Setup]]

[[Wireguard VPN Setup (Regular and Site to Site)]]

[[Project Send Setup and Configuration]]

[[Configuring Headscale]]

[[Nginx Reverse Proxy + SSL]]

=== Projects ===

[[RPI CUPS server for mini print server]]

[[Dell Optiplex NVME BIOS mod]]

[[Windows AD with linux Clients]]

[[Apt Repository Cache]]
=== Virtualization ===

[[Ceph & Proxmox installation]]

[[vCenter Installation and SSO]]

[[Adding Networks in PFSense]]

[[Proxmox High Avilability (HA)]]

[[Proxmox NFS Configuration]]

[[Proxmox VM Passthrough]]

[[ESXI Settup]]

[[Hyper‐V Creating New, and Linked VM's]]

Dell Optiplex NVME BIOS mod

2025-02-02T04:37:41Z

T20A02:

=== Install and boot from an NVMe SSD on a Dell OptiPlex 9020, 7020 or 3020 ===

December 25, 2021 by Paulie

In this post I will show you how you can modify the BIOS of your Dell OptiPlex 9020, 7020 or 3020 so that they can support an NVMe SSD drive as a boot device. These machines have a UEFI BIOS, but they do not contain an NVMe driver. By adding the driver into the BIOS you can boot from a PCIe NVMe SSD.

Required Hardware

In order to carry out this upgrade, you will need a few things:

An NVMe SSD. I used a 512Gb Samsung 970 EVOPlus
An NVMe to PCIe Adapter, I used this one from Amazon.
A Dell OptiPlex 9020, 7020 or 3020 to upgrade.
I have personally tried this procedure on the 3020 and 7020 Small Form Factor and a 9020 Minitower. It works for every variant of the machine. There are slight variations in the procedure for each machine.

Procedure Overview

This process involves five steps:

Upgrade your current BIOS if required.
A18 for the OptiPlex 7020.
A20 for the OptiPlex 3020.
A25 for the OptiPlex 9020.
Backup your current BIOS.
Add NVMe driver support into the BIOS backup.
Writing the modified BIOS back to the system.
Install the PCIe NVMe SSD and Adapter.
Optimise BIOS settings.
Machine Preparation

Before starting the the physical installation of the NVMe SSD you can do all of the required preparation while the machine is running on your existing drive.

== Upgrade your BIOS ==

The first step, is to upgrade your current BIOS:

A18 for the OptiPlex 7020.
A20 for the OptiPlex 3020.
A25 for the OptiPlex 9020.
Just download the BIOS update from the Dell website and run the update. Before the update runs it will show your current version and the version that you will be updated to:

[[File:Dell-Optiplex-BIOS-Update-Prompt.png|400px]]

Dell BIOS Update Utility for Dell Optiplex

Install Intel Management Engine Components

Next install the Intel Management Engine Components from Dell. These management components will allow you to access the BIOS in order to back it up. Reboot once after installation of the management tools.

Download Intel Management Engine Tools

Now download Intel ME System Tools and extract the Zip file to your machine. For the purposes of this blog post I will assume that it has been extracted to: C:\Intel ME System Tools v9.1 r7.

The Intel ME System Tools will be used to backup the BIOS and write the modified image back to the machine.

== Backup your current BIOS ==

Parts of the BIOS are protected and cannot be read to or written from. In order to get a complete backup the machine must be put into service mode.

Switch the machine off completely.
Disconnect it from the mains Power.
Move the jumper from the two pin PSWD connector, to the two PIN SERVICE_MODE connector. It is located between the Power Supply and the PCI Slot closest to it:
Note: If you have a spare jumper you could leave the password jumper in place.

[[File:Dell-Optiplex-7020-Service-Mode.jpg|700px]]

Image of Dell Optiplex 7020 Motherboard Service mode pins.

[[File:OptiPlex-3020-Service-Mode.jpg|700px]]

Service Mode pins for Dell OptiPlex 7020 SFF

[[File:Dell-Optiplex-7020-9020-Service-Mode.jpg|700px]]

Image of Dell Optiplex 3020 Motherboard Service mode pins.

Service Mode Pins for Dell OptiPlex 3020 SFF

Service Mode Pins for Dell OptiPlex 7020/9020 Mini Tower

Once the machine is in service mode, turn it back on, you will receive some warning notifications:

First a warning informing you that the password has been disabled. Don’t worry about this as you will be putting the password jumper back where it should be soon. It will show this message:

[[File:Dell-Security-Manager.png|400px]]

Image of Dell Security Manager warning when the password reset jumper has been removed from Dell OptiPlex

Next, you will also receive a message notifying you that service mode is enabled:

[[File:Optiplex-7020-Service-Mode-alert.png|400px]]

Warning from Dell OptiPlex when the service mode jumpers have been set.

Press F1 to continue and continue to boot normally

When your machine is booted up again you can take a backup of your existing firmware. Open a command prompt as administrator:

[[File:Run-Command-Prompt-Administrator.png|600px]]

Showing how to run a command prompt as an administrator

Run the following commands:

cd "\Intel ME System Tools v9.1 r7\Flash Programming Tool\WIN64" fptw64.exe -d backup.bin

[[File:Optiplex-7020-3020-Backup-BIOS-Intel-FPT.png|700px]]

Image of output from Intel Flash Programming Tool when taking a backup of a Dell OptiPlex BIOS

The example above is from an OptiPlex 7020, the output from the 3020 will look slightly different as it only has a single flash device and will give output such as:

Platform: Intel(R) H81 Express Chipset Reading HSFSTS register... Flash Descriptor: Valid

--- Flash Devices Found ---
MX25L6405D ID:0xc22017 Size: 8192KB (65535Kb)
Reading Flash [0x800000] 8192KB of 8192KB - 100% complete. Writing flash contents to file "backup.bin"...
Memory Dump Complete FPT Operation Passed

You will now have a file named backup.bin which contains a full backup of your BIOS. Leave the command prompt open as we are going to use it again to write the modified BIOS back.

== Modify the BIOS Image ==

Download and open UEFITool 0.28.0 to modify your BIOS (Direct link to version I used).

Open the backup.bin from the previous step in UEFI Tool and expand it like so:

Image of UEFI Tool with a Dell BIOS Image loaded.

[[File:Optiplex-7020-UEFITool.png|700px]]

Scroll to the bottom of this section and you should see an area that looks like this:

[[File:Insert-NVME-DXE-Location.png|700px]]

Image of correct location to insert NVMe driver in Dell OptiPlex BIOS

Now, download this NVMe Express Driver and save it to your machine. Next, right click on the final DXE Driver before the Freeform entries. Specifically these is IDs:

D95D6B4F-92FA-4E78-9C48-C68C0813688E for the OptiPlex 7020 or 9020
6C58FC74-64DA-4D83-8BCD-9FD574C97316 for the OptiPlex 3020
Right click the item and choose Insert After:

[[File:Insert-NVME-DXE-InsertAfter.png|700px]]

Choose the file NvmExpressDxe_Small.ffs that you just downloaded and you will see it appear right after the item that you selected:

[[File:Insert-NVME-DXE-Inserted.png|700px]]

Image of NVMe Driver being inserted into Dell Optiplex BIOS

Now go to File -> Save Image File and save the file as nvme.bin.

== Write the new BIOS to the machine ==

You are now ready to write the new file back to the machine. Go back to the command prompt session. Type the following command:

fptw64.exe -bios -f nvme.bin

You should get output like this:

[[File:Optiplex-7020-Write-NVMe-BIOS-1.png|500px]]

Shut down the machine and take the jumper off the service pins and move it back to the password reset pins if you took it from there.

== Install the PCI NVMe SSD ==

If you have not yet installed your SSD into the machine, you can do it now. For the 7020 use the blue PCI slot, it is approximately twice as fast as the smaller black one.

For the 3020 you need to install it into the PCI Slot closest to the Power Supply.

== Optimise BIOS Settings ==

Now that you have written the new BIOS, restart the machine.

You should be able to see the adapter in the BIOS:

[[File:Dell-Optiplex-7020-NVMe-Bios-System-Information-1024x576.png|600px]]

Image of System Information screen from a Dell Optiplex 7020 BIOS.

If you are not going to have any SATA drives connected you need to disable them in the BIOS, here you can see I have disabled all of the ports that do not have a drive connected:

[[File:Dell-Optiplex-7020-NVMe-Bios-SATA-Options-1024x576.png|600px]]

Disabling the un-used ports prevents an error on startup.

Finally, if you want the maximum possible speed from your new drive, consider disabling C-States in the BIOS. This makes it marginally faster, but I doubt you would notice much difference:

[[File:Dell-Optiplex-7020-Disable-C-States-1024x576.png|600px]]

Now you should be bale to boot from an NVMe Drive natively using a PCIe adapter!

Dell Optiplex NVME BIOS mod

2025-02-02T04:37:20Z

T20A02:

Install and boot from an NVMe SSD on a Dell OptiPlex 9020, 7020 or 3020

December 25, 2021 by Paulie

In this post I will show you how you can modify the BIOS of your Dell OptiPlex 9020, 7020 or 3020 so that they can support an NVMe SSD drive as a boot device. These machines have a UEFI BIOS, but they do not contain an NVMe driver. By adding the driver into the BIOS you can boot from a PCIe NVMe SSD.

Required Hardware

In order to carry out this upgrade, you will need a few things:

An NVMe SSD. I used a 512Gb Samsung 970 EVOPlus
An NVMe to PCIe Adapter, I used this one from Amazon.
A Dell OptiPlex 9020, 7020 or 3020 to upgrade.
I have personally tried this procedure on the 3020 and 7020 Small Form Factor and a 9020 Minitower. It works for every variant of the machine. There are slight variations in the procedure for each machine.

Procedure Overview

This process involves five steps:

Upgrade your current BIOS if required.
A18 for the OptiPlex 7020.
A20 for the OptiPlex 3020.
A25 for the OptiPlex 9020.
Backup your current BIOS.
Add NVMe driver support into the BIOS backup.
Writing the modified BIOS back to the system.
Install the PCIe NVMe SSD and Adapter.
Optimise BIOS settings.
Machine Preparation

Before starting the the physical installation of the NVMe SSD you can do all of the required preparation while the machine is running on your existing drive.

== Upgrade your BIOS ==

The first step, is to upgrade your current BIOS:

A18 for the OptiPlex 7020.
A20 for the OptiPlex 3020.
A25 for the OptiPlex 9020.
Just download the BIOS update from the Dell website and run the update. Before the update runs it will show your current version and the version that you will be updated to:

[[File:Dell-Optiplex-BIOS-Update-Prompt.png|400px]]

Dell BIOS Update Utility for Dell Optiplex

Install Intel Management Engine Components

Next install the Intel Management Engine Components from Dell. These management components will allow you to access the BIOS in order to back it up. Reboot once after installation of the management tools.

Download Intel Management Engine Tools

Now download Intel ME System Tools and extract the Zip file to your machine. For the purposes of this blog post I will assume that it has been extracted to: C:\Intel ME System Tools v9.1 r7.

The Intel ME System Tools will be used to backup the BIOS and write the modified image back to the machine.

== Backup your current BIOS ==

Parts of the BIOS are protected and cannot be read to or written from. In order to get a complete backup the machine must be put into service mode.

Switch the machine off completely.
Disconnect it from the mains Power.
Move the jumper from the two pin PSWD connector, to the two PIN SERVICE_MODE connector. It is located between the Power Supply and the PCI Slot closest to it:
Note: If you have a spare jumper you could leave the password jumper in place.

[[File:Dell-Optiplex-7020-Service-Mode.jpg|700px]]

Image of Dell Optiplex 7020 Motherboard Service mode pins.

[[File:OptiPlex-3020-Service-Mode.jpg|700px]]

Service Mode pins for Dell OptiPlex 7020 SFF

[[File:Dell-Optiplex-7020-9020-Service-Mode.jpg|700px]]

Image of Dell Optiplex 3020 Motherboard Service mode pins.

Service Mode Pins for Dell OptiPlex 3020 SFF

Service Mode Pins for Dell OptiPlex 7020/9020 Mini Tower

Once the machine is in service mode, turn it back on, you will receive some warning notifications:

First a warning informing you that the password has been disabled. Don’t worry about this as you will be putting the password jumper back where it should be soon. It will show this message:

[[File:Dell-Security-Manager.png|400px]]

Image of Dell Security Manager warning when the password reset jumper has been removed from Dell OptiPlex

Next, you will also receive a message notifying you that service mode is enabled:

[[File:Optiplex-7020-Service-Mode-alert.png|400px]]

Warning from Dell OptiPlex when the service mode jumpers have been set.

Press F1 to continue and continue to boot normally

When your machine is booted up again you can take a backup of your existing firmware. Open a command prompt as administrator:

[[File:Run-Command-Prompt-Administrator.png|600px]]

Showing how to run a command prompt as an administrator

Run the following commands:

cd "\Intel ME System Tools v9.1 r7\Flash Programming Tool\WIN64" fptw64.exe -d backup.bin

[[File:Optiplex-7020-3020-Backup-BIOS-Intel-FPT.png|700px]]

Image of output from Intel Flash Programming Tool when taking a backup of a Dell OptiPlex BIOS

The example above is from an OptiPlex 7020, the output from the 3020 will look slightly different as it only has a single flash device and will give output such as:

Platform: Intel(R) H81 Express Chipset Reading HSFSTS register... Flash Descriptor: Valid

--- Flash Devices Found ---
MX25L6405D ID:0xc22017 Size: 8192KB (65535Kb)
Reading Flash [0x800000] 8192KB of 8192KB - 100% complete. Writing flash contents to file "backup.bin"...
Memory Dump Complete FPT Operation Passed

You will now have a file named backup.bin which contains a full backup of your BIOS. Leave the command prompt open as we are going to use it again to write the modified BIOS back.

== Modify the BIOS Image ==

Download and open UEFITool 0.28.0 to modify your BIOS (Direct link to version I used).

Open the backup.bin from the previous step in UEFI Tool and expand it like so:

Image of UEFI Tool with a Dell BIOS Image loaded.

[[File:Optiplex-7020-UEFITool.png|700px]]

Scroll to the bottom of this section and you should see an area that looks like this:

[[File:Insert-NVME-DXE-Location.png|700px]]

Image of correct location to insert NVMe driver in Dell OptiPlex BIOS

Now, download this NVMe Express Driver and save it to your machine. Next, right click on the final DXE Driver before the Freeform entries. Specifically these is IDs:

D95D6B4F-92FA-4E78-9C48-C68C0813688E for the OptiPlex 7020 or 9020
6C58FC74-64DA-4D83-8BCD-9FD574C97316 for the OptiPlex 3020
Right click the item and choose Insert After:

[[File:Insert-NVME-DXE-InsertAfter.png|700px]]

Choose the file NvmExpressDxe_Small.ffs that you just downloaded and you will see it appear right after the item that you selected:

[[File:Insert-NVME-DXE-Inserted.png|700px]]

Image of NVMe Driver being inserted into Dell Optiplex BIOS

Now go to File -> Save Image File and save the file as nvme.bin.

== Write the new BIOS to the machine ==

You are now ready to write the new file back to the machine. Go back to the command prompt session. Type the following command:

fptw64.exe -bios -f nvme.bin

You should get output like this:

[[File:Optiplex-7020-Write-NVMe-BIOS-1.png|500px]]

Shut down the machine and take the jumper off the service pins and move it back to the password reset pins if you took it from there.

== Install the PCI NVMe SSD ==

If you have not yet installed your SSD into the machine, you can do it now. For the 7020 use the blue PCI slot, it is approximately twice as fast as the smaller black one.

For the 3020 you need to install it into the PCI Slot closest to the Power Supply.

== Optimise BIOS Settings ==

Now that you have written the new BIOS, restart the machine.

You should be able to see the adapter in the BIOS:

[[File:Dell-Optiplex-7020-NVMe-Bios-System-Information-1024x576.png|600px]]

Image of System Information screen from a Dell Optiplex 7020 BIOS.

If you are not going to have any SATA drives connected you need to disable them in the BIOS, here you can see I have disabled all of the ports that do not have a drive connected:

[[File:Dell-Optiplex-7020-NVMe-Bios-SATA-Options-1024x576.png|600px]]

Disabling the un-used ports prevents an error on startup.

Finally, if you want the maximum possible speed from your new drive, consider disabling C-States in the BIOS. This makes it marginally faster, but I doubt you would notice much difference:

[[File:Dell-Optiplex-7020-Disable-C-States-1024x576.png|600px]]

Now you should be bale to boot from an NVMe Drive natively using a PCIe adapter!

Windows 11 Network Bypass

2025-02-02T03:43:43Z

T20A02: Created page with "=== Windows 11 network Bypass === As of windows 11 build 25120.1010 Microsoft removed the ability to bypass the need for a Microsoft account using the "OOBE/BYPASSNRO" Command which would present the user with the "I Don't have Internet" Option at the network screen. Now when running that command the machine will restart, but the option will not appear. Now that method is obsolete, the following new method allows the same outcome, though with more work. Press Shift +..."

=== Windows 11 network Bypass ===

As of windows 11 build 25120.1010 Microsoft removed the ability to bypass the need for a Microsoft account using the "OOBE/BYPASSNRO" Command which would present the user with the "I Don't have Internet" Option at the network screen. Now when running that command the machine will restart, but the option will not appear.

Now that method is obsolete, the following new method allows the same outcome, though with more work.

Press Shift + F10. The command prompt opens

<pre>
net.exe user "User Name" /add

net.exe localgroup "Administrators" "User Name" /add

cd OOBE

msoobe.exe && shutdown.exe -r
</pre>

The Machine will now reboot, and present a "Password incorrect" error, and by pressing OK, you will be brought to the login screen, where you can switch to the new user we created in the bottom right, and continue as normal.

Main Page

2025-02-02T03:39:20Z

T20A02:

Welcome to the Goomba Cloud Wiki!.

This guide includes a culmination of projects written by yours truly, the site administrator! You will find anything from Proxmox stack configuration, all the way to software manual install guides (Including a guide to setting up this wiki) and much more!

== Pages ==

=== Reference ===

[[Key Based SSH from Windows to Linux]]

[[Windows 11 Enterprise .iso creation]]

[[Windows 11 Network Bypass]]

=== Services ===

[[Forgejo Install from Binary]]

[[Vaultwarden Docker Container Setup]]

[[Wireguard VPN Setup (Regular and Site to Site)]]

[[Project Send Setup and Configuration]]

[[Configuring Headscale]]

=== Projects ===

[[RPI CUPS server for mini print server]]

[[Dell Optiplex NVME BIOS mod]]

[[Windows AD with linux Clients]]

[[Apt Repository Cache]]
=== Virtualization ===

[[Ceph & Proxmox installation]]

[[vCenter Installation and SSO]]

[[Adding Networks in PFSense]]

[[Proxmox High Avilability (HA)]]

[[Proxmox NFS Configuration]]

[[Proxmox VM Passthrough]]

[[ESXI Settup]]

[[Hyper‐V Creating New, and Linked VM's]]

Configuring Headscale

2025-01-24T03:03:09Z

T20A02: /* Client Connection */

== Headscale Setup and Usage ==

==== Summary ====

Tailscale is a free to use VPN service which is build upon Wireguard, is a fast HTTPS based VPN service which removes the server role in a traditional Wireguard setup, and replaces it with a Peer 2 Peer protocol, and a Authentication server. This allows you to connect multiple devices directly, providing device to device connection, via IP and dynamic/magic DNS. Headscale is a open source port of the service, which allows you to host your own authentication server removing limits on speeds, and improving reliability.

In this setup I will be outlining the configuration of the Client and server for Headscale, as well as configuring a client as a "Exit Node" allowing it to forward traffic to local Subnets to other nodes connected to it, for remote network access without the need of a static public address, allowing the traversal of Carrier grade NAT, and port forwarding.

=== Headscale server Installation ===

First we are going to set up our server and install Headscale. The server is recommend by Headscale to be a Apt based Distro, in this example I used Debian 12 Latest. After initial setup I installed firewalld as a firewall appliance which I recommend especially if you are using a VPS that has a public address assigned. Once that is done make sure the following ports are open on the server:

80/tcp required for initial request
443/tcp used for traffic
8080/tcp used by the authentication server

41641/udp used for the relay functionality
3478/udp used for the relay functionality

If using Firewalld like i was these can be opened with:

<pre>
sudo firewall-cmd --permanent --allow-port=80/tcp \
sudo firewall-cmd --permanent --allow-port=443/tcp \
sudo firewall-cmd --permanent --allow-port=8080/tcp \
sudo firewall-cmd --permanent --allow-port=41641/udp \
sudo firewall-cmd --permanent --allow-port=3478/udp
</pre>

Once those ports are open the following link to get the latest release of headscale's .deb file for amd64.

[https://github.com/juanfont/headscale/releases/latest Latest Headscale Release]

Copy the URL of the .deb file and use wget to download it to the server:

<pre>
wget https://github.com/juanfont/headscale/releases/download/v0.24.1/headscale_0.24.1_linux_amd64.deb
</pre>

Once this is downloaded install it with dpkg:

<pre>
sudo dpkg -i headscale_0.24.1_linux_amd64.deb
</pre>

Now we need to update the IP address of the server in the config before we start it.

Edit the config with the following:

<pre>
sudo nano /etc/headscale/config.yaml
</pre>

In the section Highlighted change the blacked out part to the your public address, also change the "Listen Addr" Section to be 0.0.0.0:8080 to allow authentication requests from any IP.

[[File:Headscale Server Config.png|1000px]]

After this save and close the config file, and then enable and start the headscale service.

<pre>
sudo systemctl enable headscale.service
sudo systemctl start headscale.service
</pre>

Then check that is is running with

<pre>
sudo systemctl status headscale.service
</pre>

You should see a active and started service, without errors or warnings in the dmesg output:

[[File:Headscale Running.png|800px]]

Finally we need to create a user to tie out devices together:

<pre>
headscale users create <USER>
</pre>

Now we have configured and started our Headscale server, which is ready for authentication requests. Keep a session open with the server, as we will need access to accept and import the keys for out clients, and have created a use for our devices.

=== Client Configuration ===

Now we will outline the configuration of the clients, as they are going to be using the standard Railscale client to access our own server, giving us the advantaged of cross compatibility.

In my example i will be connecting two Linux devices one as the client and one as the "Exit Node". Additonal documentation for other platforms and OS's can be found here:

[https://tailscale.com/kb/1017/install Tailscale Documentation Page ]

First we are going to download and run the installser script on our two clients

<pre>
curl -fsSL https://tailscale.com/install.sh | sh
</pre>

It will prompt for sudo password, and then install. Once installed enable and start the service like we did with Headscale:

<pre>
sudo systemctl enable tailscaled.service
sudo systemctl start tailscaled.service
</pre>

Now we need to connect our new Client device to the Headscale server, so it can authenticate the device, and direct it to the other nodes on the Headscale network:

<pre>
sudo tailscale ip --login-server=http://xxx.xxx.xxx.xxx:8080
</pre>

When you do this you will be prompted with a URL. We arent going click the URL but we need the key generated, this is the section at the end starting with "mkey:" Including all of the numbers and letters which is the key for authentication. Copy this key and then on the headscale server run the following command to register and accept the client:

<pre>
sudo headscale nodes register --user <USER> --key <KEY>
</pre>

Example Screenshot:

[[File:Tailscale Client Key.png|800px]]

Once this is run the device will be accepted and connected. Confirm this my running <pre> sudo tailscale status </pre> on the client. This should return the new node, and its status in the TTY:

[[File:Tailscale Status.png|800px]]

On the server we can confirm the connected device with <pre> sudo headscale nodes list</pre> Which gives good status info of all nodes:

[[File:Headscale Node Status.png|800px]]

We can see the nodes on my server are "Online" and no expired.

==== Exit Node ====

Up until this point the setup for a exit node, or regular client is the same, but we need to do a few more things to setup a node as a exit node to allow other clients to access the node and its local subnets.

Now that we have the node authenticated we are going to reconnect it to the headscale server, with a few flags to advertise as an exit node, and to advertise the subnets that are allowed locally:

<pre>
sudo tailscale set --advertise-exit-node --advertise- routes=10.0.1.0/24
</pre>

In the "Advertise Routes" Flag make sure to update to the Subnet you want to share.

Now we need to run the following to allow routing to work correctly on the exit node.

<pre>
echo 'net.ipv4.ip_forward = 1' | sudo tee -a /etc/sysctl.d/99-tailscale.conf
echo 'net.ipv6.conf.all.forwarding = 1' | sudo tee -a /etc/sysctl.d/99-tailscale.conf
sudo sysctl -p /etc/sysctl.d/99-tailscale.conf
</pre>

Now the node is advertising this subnet. Now we need to go "Approve" the advertisement on the headscale server. From the server run the following:

<pre>
sudo headscale routes list
</pre>

This will list all the routes available on the server, in my case the 10.0.1.0/24 route got the "ID" of 3. Now we run the Following to accept the route "3":

<pre>
sudo headscale routes enable -r 3
</pre>

Now if we run the list command from above we should see that the "Enabled" and "Primary" field should be "true":

[[File:Route Status.png|800px]]

==== Client Connection ====

Finally we just have to go to our mobile client, and configure it to connect to the exit node. To do this simply reconnect to the headscale server with the following command:

<pre>
sudo tailscale up --login-server=http://xxx.xxx.xxx.xxx:8080 --accept-routes --exit-node=<EXIT NODE NAME>
</pre>

Now you should be connected, and able to ping devices and access services on that subnet.

==== Conclusion ====

Headscale takes a powerful free to use tool and drops control into you own hands, allowing the creation and use of a powerful networking system. All of the client configuration for this setup uses the same syntax and commands as tail-scale clients, and can be changed, tweaked, and modified using the information found in tail-scales official documentation.

[https://tailscale.com/kb/1017/install Offical Tailscale Documents]

Also thanks to "europecafe" on Reddit for their post providing some clarification of the process, and Lemmy Bean

Configuring Headscale

2025-01-24T03:00:38Z

T20A02:

== Headscale Setup and Usage ==

==== Summary ====

Tailscale is a free to use VPN service which is build upon Wireguard, is a fast HTTPS based VPN service which removes the server role in a traditional Wireguard setup, and replaces it with a Peer 2 Peer protocol, and a Authentication server. This allows you to connect multiple devices directly, providing device to device connection, via IP and dynamic/magic DNS. Headscale is a open source port of the service, which allows you to host your own authentication server removing limits on speeds, and improving reliability.

In this setup I will be outlining the configuration of the Client and server for Headscale, as well as configuring a client as a "Exit Node" allowing it to forward traffic to local Subnets to other nodes connected to it, for remote network access without the need of a static public address, allowing the traversal of Carrier grade NAT, and port forwarding.

=== Headscale server Installation ===

First we are going to set up our server and install Headscale. The server is recommend by Headscale to be a Apt based Distro, in this example I used Debian 12 Latest. After initial setup I installed firewalld as a firewall appliance which I recommend especially if you are using a VPS that has a public address assigned. Once that is done make sure the following ports are open on the server:

80/tcp required for initial request
443/tcp used for traffic
8080/tcp used by the authentication server

41641/udp used for the relay functionality
3478/udp used for the relay functionality

If using Firewalld like i was these can be opened with:

<pre>
sudo firewall-cmd --permanent --allow-port=80/tcp \
sudo firewall-cmd --permanent --allow-port=443/tcp \
sudo firewall-cmd --permanent --allow-port=8080/tcp \
sudo firewall-cmd --permanent --allow-port=41641/udp \
sudo firewall-cmd --permanent --allow-port=3478/udp
</pre>

Once those ports are open the following link to get the latest release of headscale's .deb file for amd64.

[https://github.com/juanfont/headscale/releases/latest Latest Headscale Release]

Copy the URL of the .deb file and use wget to download it to the server:

<pre>
wget https://github.com/juanfont/headscale/releases/download/v0.24.1/headscale_0.24.1_linux_amd64.deb
</pre>

Once this is downloaded install it with dpkg:

<pre>
sudo dpkg -i headscale_0.24.1_linux_amd64.deb
</pre>

Now we need to update the IP address of the server in the config before we start it.

Edit the config with the following:

<pre>
sudo nano /etc/headscale/config.yaml
</pre>

In the section Highlighted change the blacked out part to the your public address, also change the "Listen Addr" Section to be 0.0.0.0:8080 to allow authentication requests from any IP.

[[File:Headscale Server Config.png|1000px]]

After this save and close the config file, and then enable and start the headscale service.

<pre>
sudo systemctl enable headscale.service
sudo systemctl start headscale.service
</pre>

Then check that is is running with

<pre>
sudo systemctl status headscale.service
</pre>

You should see a active and started service, without errors or warnings in the dmesg output:

[[File:Headscale Running.png|800px]]

Finally we need to create a user to tie out devices together:

<pre>
headscale users create <USER>
</pre>

Now we have configured and started our Headscale server, which is ready for authentication requests. Keep a session open with the server, as we will need access to accept and import the keys for out clients, and have created a use for our devices.

=== Client Configuration ===

Now we will outline the configuration of the clients, as they are going to be using the standard Railscale client to access our own server, giving us the advantaged of cross compatibility.

In my example i will be connecting two Linux devices one as the client and one as the "Exit Node". Additonal documentation for other platforms and OS's can be found here:

[https://tailscale.com/kb/1017/install Tailscale Documentation Page ]

First we are going to download and run the installser script on our two clients

<pre>
curl -fsSL https://tailscale.com/install.sh | sh
</pre>

It will prompt for sudo password, and then install. Once installed enable and start the service like we did with Headscale:

<pre>
sudo systemctl enable tailscaled.service
sudo systemctl start tailscaled.service
</pre>

Now we need to connect our new Client device to the Headscale server, so it can authenticate the device, and direct it to the other nodes on the Headscale network:

<pre>
sudo tailscale ip --login-server=http://xxx.xxx.xxx.xxx:8080
</pre>

When you do this you will be prompted with a URL. We arent going click the URL but we need the key generated, this is the section at the end starting with "mkey:" Including all of the numbers and letters which is the key for authentication. Copy this key and then on the headscale server run the following command to register and accept the client:

<pre>
sudo headscale nodes register --user <USER> --key <KEY>
</pre>

Example Screenshot:

[[File:Tailscale Client Key.png|800px]]

Once this is run the device will be accepted and connected. Confirm this my running <pre> sudo tailscale status </pre> on the client. This should return the new node, and its status in the TTY:

[[File:Tailscale Status.png|800px]]

On the server we can confirm the connected device with <pre> sudo headscale nodes list</pre> Which gives good status info of all nodes:

[[File:Headscale Node Status.png|800px]]

We can see the nodes on my server are "Online" and no expired.

==== Exit Node ====

Up until this point the setup for a exit node, or regular client is the same, but we need to do a few more things to setup a node as a exit node to allow other clients to access the node and its local subnets.

Now that we have the node authenticated we are going to reconnect it to the headscale server, with a few flags to advertise as an exit node, and to advertise the subnets that are allowed locally:

<pre>
sudo tailscale set --advertise-exit-node --advertise- routes=10.0.1.0/24
</pre>

In the "Advertise Routes" Flag make sure to update to the Subnet you want to share.

Now we need to run the following to allow routing to work correctly on the exit node.

<pre>
echo 'net.ipv4.ip_forward = 1' | sudo tee -a /etc/sysctl.d/99-tailscale.conf
echo 'net.ipv6.conf.all.forwarding = 1' | sudo tee -a /etc/sysctl.d/99-tailscale.conf
sudo sysctl -p /etc/sysctl.d/99-tailscale.conf
</pre>

Now the node is advertising this subnet. Now we need to go "Approve" the advertisement on the headscale server. From the server run the following:

<pre>
sudo headscale routes list
</pre>

This will list all the routes available on the server, in my case the 10.0.1.0/24 route got the "ID" of 3. Now we run the Following to accept the route "3":

<pre>
sudo headscale routes enable -r 3
</pre>

Now if we run the list command from above we should see that the "Enabled" and "Primary" field should be "true":

[[File:Route Status.png|800px]]

==== Client Connection ====

Finally we just have to go to our mobile client, and configure it to connect to the exit node. To do this simply reconnect to the headscale server with the following command:

<pre>
sudo tasilscale up --login-server=http://xxx.xxx.xxx.xxx:8080 --accept-routes --exit-node=<EXIT NODE NAME>
</pre>

Now you should be connected, and able to ping devices and access services on that subnet.

==== Conclusion ====

Headscale takes a powerful free to use tool and drops control into you own hands, allowing the creation and use of a powerful networking system. All of the client configuration for this setup uses the same syntax and commands as tail-scale clients, and can be changed, tweaked, and modified using the information found in tail-scales official documentation.

[https://tailscale.com/kb/1017/install Offical Tailscale Documents]

Also thanks to "europecafe" on Reddit for their post providing some clarification of the process, and Lemmy Bean

Configuring Headscale

2025-01-24T02:59:17Z

T20A02:

== Headscale Settup and Usage ==

==== Summary ====

Tailscale is a free to use VPN service which is build upon Wireguard, is a fast HTTPS based VPN service which removes the server role in a traditional Wireguard setup, and replaces it with a Peer 2 Peer protocol, and a Authentication server. This allows you to connect multiple devices directly, providing device to device connection, via IP and dynamic/magic DNS. Headscale is a open source port of the service, which allows you to host your own authentication server removing limits on speeds, and improving reliability.

In this setup I will be outlining the configuration of the Client and server for Headscale, as well as configuring a client as a "Exit Node" allowing it to forward traffic to local Subnets to other nodes connected to it, for remote network access without the need of a static public address, allowing the traversal of Carrier grade NAT, and port forwarding.

=== Headscale server Installation ===

First we are going to set up our server and install Headscale. The server is recommend by Headscale to be a Apt based Distro, in this example I used Debian 12 Latest. After initial setup I installed firewalld as a firewall appliance which I recommend especially if you are using a VPS that has a public address assigned. Once that is done make sure the following ports are open on the server:

80/tcp required for initial request
443/tcp used for traffic
8080/tcp used by the authentication server

41641/udp used for the relay functionality
3478/udp used for the relay functionality

If using Firewalld like i was these can be opened with:

<pre>
sudo firewall-cmd --permanent --allow-port=80/tcp \
sudo firewall-cmd --permanent --allow-port=443/tcp \
sudo firewall-cmd --permanent --allow-port=8080/tcp \
sudo firewall-cmd --permanent --allow-port=41641/udp \
sudo firewall-cmd --permanent --allow-port=3478/udp
</pre>

Once those ports are open the following link to get the latest release of headscale's .deb file for amd64.

[https://github.com/juanfont/headscale/releases/latest Latest Headscale Release]

Copy the URL of the .deb file and use wget to download it to the server:

<pre>
wget https://github.com/juanfont/headscale/releases/download/v0.24.1/headscale_0.24.1_linux_amd64.deb
</pre>

Once this is downloaded install it with dpkg:

<pre>
sudo dpkg -i headscale_0.24.1_linux_amd64.deb
</pre>

Now we need to update the IP address of the server in the config before we start it.

Edit the config with the following:

<pre>
sudo nano /etc/headscale/config.yaml
</pre>

In the section Highlighted change the blacked out part to the your public address, also change the "Listen Addr" Section to be 0.0.0.0:8080 to allow authentication requests from any IP.

[[File:Headscale Server Config.png|1000px]]

After this save and close the config file, and then enable and start the headscale service.

<pre>
sudo systemctl enable headscale.service
sudo systemctl start headscale.service
</pre>

Then check that is is running with

<pre>
sudo systemctl status headscale.service
</pre>

You should see a active and started service, without errors or warnings in the dmesg output:

[[File:Headscale Running.png|800px]]

Finally we need to create a user to tie out devices together:

<pre>
headscale users create <USER>
</pre>

Now we have configured and started our Headscale server, which is ready for authentication requests. Keep a session open with the server, as we will need access to accept and import the keys for out clients, and have created a use for our devices.

=== Client Configuration ===

Now we will outline the configuration of the clients, as they are going to be using the standard Railscale client to access our own server, giving us the advantaged of cross compatibility.

In my example i will be connecting two Linux devices one as the client and one as the "Exit Node". Additonal documentation for other platforms and OS's can be found here:

[https://tailscale.com/kb/1017/install Tailscale Documentation Page ]

First we are going to download and run the installser script on our two clients

<pre>
curl -fsSL https://tailscale.com/install.sh | sh
</pre>

It will prompt for sudo password, and then install. Once installed enable and start the service like we did with Headscale:

<pre>
sudo systemctl enable tailscaled.service
sudo systemctl start tailscaled.service
</pre>

Now we need to connect our new Client device to the Headscale server, so it can authenticate the device, and direct it to the other nodes on the Headscale network:

<pre>
sudo tailscale ip --login-server=http://xxx.xxx.xxx.xxx:8080
</pre>

When you do this you will be prompted with a URL. We arent going click the URL but we need the key generated, this is the section at the end starting with "mkey:" Including all of the numbers and letters which is the key for authentication. Copy this key and then on the headscale server run the following command to register and accept the client:

<pre>
sudo headscale nodes register --user <USER> --key <KEY>
</pre>

Example Screenshot:

[[File:Tailscale Client Key.png|800px]]

Once this is run the device will be accepted and connected. Confirm this my running <pre> sudo tailscale status </pre> on the client. This should return the new node, and its status in the TTY:

[[File:Tailscale Status.png|800px]]

On the server we can confirm the connected device with <pre> sudo headscale nodes list</pre> Which gives good status info of all nodes:

[[File:Headscale Node Status.png|800px]]

We can see the nodes on my server are "Online" and no expired.

==== Exit Node ====

Up until this point the setup for a exit node, or regular client is the same, but we need to do a few more things to setup a node as a exit node to allow other clients to access the node and its local subnets.

Now that we have the node authenticated we are going to reconnect it to the headscale server, with a few flags to advertise as an exit node, and to advertise the subnets that are allowed locally:

<pre>
sudo tailscale set --advertise-exit-node --advertise- routes=10.0.1.0/24
</pre>

In the "Advertise Routes" Flag make sure to update to the Subnet you want to share.

Now we need to run the following to allow routing to work correctly on the exit node.

<pre>
echo 'net.ipv4.ip_forward = 1' | sudo tee -a /etc/sysctl.d/99-tailscale.conf
echo 'net.ipv6.conf.all.forwarding = 1' | sudo tee -a /etc/sysctl.d/99-tailscale.conf
sudo sysctl -p /etc/sysctl.d/99-tailscale.conf
</pre>

Now the node is advertising this subnet. Now we need to go "Approve" the advertisement on the headscale server. From the server run the following:

<pre>
sudo headscale routes list
</pre>

This will list all the routes available on the server, in my case the 10.0.1.0/24 route got the "ID" of 3. Now we run the Following to accept the route "3":

<pre>
sudo headscale routes enable -r 3
</pre>

Now if we run the list command from above we should see that the "Enabled" and "Primary" field should be "true":

[[File:Route Status.png|800px]]

==== Client Connection ====

Finally we just have to go to our mobile client, and configure it to connect to the exit node. To do this simply reconnect to the headscale server with the following command:

<pre>
sudo tasilscale up --login-server=http://xxx.xxx.xxx.xxx:8080 --accept-routes --exit-node=<EXIT NODE NAME>
</pre>

Now you should be connected, and able to ping devices and access services on that subnet.

==== Conclusion ====

Headscale takes a powerful free to use tool and drops control into you own hands, allowing the creation and use of a powerful networking system. All of the client configuration for this setup uses the same syntax and commands as tail-scale clients, and can be changed, tweaked, and modified using the information found in tail-scales official documentation.

[https://tailscale.com/kb/1017/install Offical Tailscale Documents]

Also thanks to "europecafe" on Reddit for their post providing some clarification of the process, and Lemmy Bean

Configuring Headscale

2025-01-24T02:56:00Z

T20A02:

File:Route Status.png

2025-01-24T02:49:22Z

T20A02: File uploaded with MsUpload

File uploaded with MsUpload

File:Headscale Node Status.png

2025-01-24T02:37:00Z

T20A02: File uploaded with MsUpload

File uploaded with MsUpload

File:Tailscale Status.png

2025-01-24T02:35:21Z

T20A02: File uploaded with MsUpload

File uploaded with MsUpload

File:Tailscale Client Key.png

2025-01-24T02:33:30Z

T20A02: File uploaded with MsUpload

File uploaded with MsUpload

Configuring Headscale

2025-01-24T02:26:13Z

T20A02: Created page with "== Headscale Settup and Usage == ==== Summary ==== Tailscale is a free to use VPN service which is build upon Wireguard, is a fast HTTPS based VPN service which removes the server role in a traditional Wireguard setup, and replaces it with a Peer 2 Peer protocol, and a Authentication server. This allows you to connect multiple devices directly, providing device to device connection, via IP and dynamic/magic DNS. Headscale is a open source port of the service, which all..."

File:Headscale Running.png

2025-01-24T02:23:33Z

T20A02: File uploaded with MsUpload

File uploaded with MsUpload

File:Headscale Server Config.png

2025-01-24T02:19:19Z

T20A02: File uploaded with MsUpload

File uploaded with MsUpload

Main Page

2025-01-24T01:57:36Z

T20A02:

Welcome to the Goomba Cloud Wiki!.

This guide includes a culmination of projects written by yours truly, the site administrator! You will find anything from Proxmox stack configuration, all the way to software manual install guides (Including a guide to setting up this wiki) and much more!

== Pages ==

=== Reference ===

[[Key Based SSH from Windows to Linux]]

[[Windows 11 Enterprise .iso creation]]

=== Services ===

[[Forgejo Install from Binary]]

[[Vaultwarden Docker Container Setup]]

[[Wireguard VPN Setup (Regular and Site to Site)]]

[[Project Send Setup and Configuration]]

[[Configuring Headscale]]

=== Projects ===

[[RPI CUPS server for mini print server]]

[[Dell Optiplex NVME BIOS mod]]

[[Windows AD with linux Clients]]

[[Apt Repository Cache]]
=== Virtualization ===

[[Ceph & Proxmox installation]]

[[vCenter Installation and SSO]]

[[Adding Networks in PFSense]]

[[Proxmox High Avilability (HA)]]

[[Proxmox NFS Configuration]]

[[Proxmox VM Passthrough]]

[[ESXI Settup]]

[[Hyper‐V Creating New, and Linked VM's]]

Apt Repository Cache

2024-11-27T16:17:04Z

T20A02: Created page with "==Apt Repository Cache== "apt-cache-ng" is a apt repository package which allows the configuration of a apt repository cache server, acting much like a windows update cache server but for Linux distributions such as Debian or Ubuntu. This service will log and cache package files as well as provide a web interface for monitoring usage and other statistics. ===Setup=== First start with a fresh installation for your server, and a static IP address. In my case I used Deb..."

==Apt Repository Cache==

"apt-cache-ng" is a apt repository package which allows the configuration of a apt repository cache server, acting much like a windows update cache server but for Linux distributions such as Debian or Ubuntu. This service will log and cache package files as well as provide a web interface for monitoring usage and other statistics.

===Setup===

First start with a fresh installation for your server, and a static IP address. In my case I used Debian 12.

1. Start with a fresh update
<pre>
sudo apt update && apt install upgrade
</pre>

2. Next install the package
<pre>
sudo apt install apt-cacher-ng
</pre>

3. Now alow the required ports through your machine firewall. The service runs on port 3142.

Example for ufw:
<pre>
sudo ufw allow 3142/tcp
</pre>

4. Now you have a basic installation. You should be able to navigate to the servers IP, using port 3142, and see the web interface including usage.

[[File:Apt-Cacher-NG-WEB.png|400px]]

===Client Configuration===

Now that we have the server configured and running, and we verified it with the presence of the web UI, we can configure the Client side. This is done simply by adding one like to a file, in your Clients apt DConf folder.

1. Run the following command, to generate a file called "00cacher" and populate it with the config line. make sure to update the IP address to match that of your caching server
<pre>
echo 'Acquire::http::Proxy "http://cacheserver:3142";' \
> /etc/apt/apt.conf.d/00cacher
</pre>

Now you are done! Running an apt update, make sure you do not see any errors, if you do there is likely a misconfiguration in the client config file.

Going back over to the server you should find activity in the cacher log located at
<pre>
/var/log/apt-cacher-ng/apt-cacher.log
</pre>
and you should also now see content stored in
<pre>
/var/cache/apt-cacher-ng/
</pre>

File:Apt-Cacher-NG-WEB.png

2024-11-27T16:09:16Z

T20A02: File uploaded with MsUpload

File uploaded with MsUpload

Main Page

2024-11-27T16:00:47Z

T20A02:

Welcome to the Goomba Cloud Wiki!.

This guide includes a culmination of projects written by yours truly, the site administrator! You will find anything from Proxmox stack configuration, all the way to software manual install guides (Including a guide to setting up this wiki) and much more!

== Pages ==

=== Reference ===

[[Key Based SSH from Windows to Linux]]

[[Windows 11 Enterprise .iso creation]]

=== Services ===

[[Forgejo Install from Binary]]

[[Vaultwarden Docker Container Setup]]

[[Wireguard VPN Setup (Regular and Site to Site)]]

[[Project Send Setup and Configuration]]

=== Projects ===

[[RPI CUPS server for mini print server]]

[[Dell Optiplex NVME BIOS mod]]

[[Windows AD with linux Clients]]

[[Apt Repository Cache]]
=== Virtualization ===

[[Ceph & Proxmox installation]]

[[vCenter Installation and SSO]]

[[Adding Networks in PFSense]]

[[Proxmox High Avilability (HA)]]

[[Proxmox NFS Configuration]]

[[Proxmox VM Passthrough]]

[[ESXI Settup]]

[[Hyper‐V Creating New, and Linked VM's]]

Main Page

2024-11-14T06:28:37Z

T20A02:

Welcome to the Goomba Cloud Wiki!.

This guide includes a culmination of projects written by yours truly, the site administrator! You will find anything from Proxmox stack configuration, all the way to software manual install guides (Including a guide to setting up this wiki) and much more!

== Pages ==

=== Reference ===

[[Key Based SSH from Windows to Linux]]

[[Windows 11 Enterprise .iso creation]]

=== Services ===

[[Forgejo Install from Binary]]

[[Vaultwarden Docker Container Setup]]

[[Wireguard VPN Setup (Regular and Site to Site)]]

[[Project Send Setup and Configuration]]

=== Projects ===

[[RPI CUPS server for mini print server]]

[[Dell Optiplex NVME BIOS mod]]

[[Windows AD with linux Clients]]
=== Virtualization ===

[[Ceph & Proxmox installation]]

[[vCenter Installation and SSO]]

[[Adding Networks in PFSense]]

[[Proxmox High Avilability (HA)]]

[[Proxmox NFS Configuration]]

[[Proxmox VM Passthrough]]

[[ESXI Settup]]

[[Hyper‐V Creating New, and Linked VM's]]

Hyper‐V Creating New, and Linked VM's

2024-11-02T02:22:15Z

T20A02: Created page with "== Creating a Base VM in Hyper-V with Windows Server 2019 == === Creating the Base VM === ==== PowerShell Commands: ==== These are the commands used in order top create a new base VM via powershell <pre> $VMName = "BaseVM" $VMPath = "C:\Hyper-V\VMs" $ISOPath = "C:\Path\to\WindowsServer2019.iso" New-VM -Name $VMName -Path $VMPath -MemoryStartupBytes 4GB -NewVHDPath "$VMPath\$VMName.vhdx" -NewVHDSizeBytes 60GB Set-VMBios -VMName $VMName -BootOrder "CD" Add-VMDvdDrive..."

== Creating a Base VM in Hyper-V with Windows Server 2019 ==

=== Creating the Base VM ===

==== PowerShell Commands: ====

These are the commands used in order top create a new base VM via powershell

<pre>
$VMName = "BaseVM"
$VMPath = "C:\Hyper-V\VMs"
$ISOPath = "C:\Path\to\WindowsServer2019.iso"

New-VM -Name $VMName -Path $VMPath -MemoryStartupBytes 4GB -NewVHDPath "$VMPath\$VMName.vhdx" -NewVHDSizeBytes 60GB
Set-VMBios -VMName $VMName -BootOrder "CD"
Add-VMDvdDrive -VMName $VMName -Path $ISOPath
Start-VM -Name $VMName
</pre>

These are the commands used in order, to make a linked clone of a VM

<pre>
$LinkedVMName = "LinkedCloneVM"

New-VHD -Path "C:\Hyper-V\VMs\$LinkedVMName.vhdx" -ParentPath "C:\Hyper-V\VMs\BaseVM.vhdx" -Differencing
New-VM -Name $LinkedVMName -Path "C:\Hyper-V\VMs" -MemoryStartupBytes 4GB -VHDPath "C:\Hyper-V\VMs\$LinkedVMName.vhdx"
Start-VM -Name $LinkedVMName
</pre>

==== Other General Commands: ====

# Interacting with PowerShell Commands

To stop a virtual machine using PowerShell, you can execute the following command:

<pre>
Stop-Service -Name YourVMName
# OR
Stop-Process -Name YourVMName

Checkpoint-VM -Name YourVMName -SnapshotName snapshot1
# OR
Checkpoint-Computer -Name YourVMName -SnapshotName snapshot1

Start-Service -Name YourVMName
# OR
Start-Process -Name YourVMName

# Change the network profile for 'YourVMName' to another network by name
Set-NetConnectionProfile -InterfaceAlias YourVMName -NetworkCategory "Private"

# OR

# Change the IP address of 'YourVMName' to another network
Set-NetIPAddress -InterfaceAlias YourVMName -IPAddress NewIPAddress -PrefixLength SubnetMask -DefaultGateway NewGateway

</pre>

Written in part with ChatGPT

Main Page

2024-11-02T02:17:53Z

T20A02:

Welcome to the Goomba Cloud Wiki!.

This guide includes a culmination of projects written by yours truly, the site administrator! You will find anything from Proxmox stack configuration, all the way to software manual install guides (Including a guide to setting up this wiki) and much more!

== Pages ==

=== Reference ===

[[Key Based SSH from Windows to Linux]]

[[Windows 11 Enterprise .iso creation]]

=== Services ===

[[Forgejo Install from Binary]]

[[Vaultwarden Docker Container Setup]]

[[Wireguard VPN Setup (Regular and Site to Site)]]

[[Project Send Setup and Configuration]]

=== Projects ===

[[RPI CUPS server for mini print server]]

[[Dell Optiplex NVME BIOS mod]]

=== Virtualization ===

[[Ceph & Proxmox installation]]

[[vCenter Installation and SSO]]

[[Adding Networks in PFSense]]

[[Proxmox High Avilability (HA)]]

[[Proxmox NFS Configuration]]

[[Proxmox VM Passthrough]]

[[ESXI Settup]]

[[Hyper‐V Creating New, and Linked VM's]]

ESXI Settup

2024-11-02T02:12:12Z

T20A02: Created page with "=== ESXI Configuration === This is a quick install guide written for ESXI 8.0. 1) First install ESXI using a bootable media, following the standard install prompts, and configure a custom password, which will be used for web access. 2) Install ESXI on the smaller of the two drives, as we are going to be using the larger as the datastore for VM Disk's, and the smaller for ESXI itself and ISO files. 3) After ESXI is installed, and started up to the main screen, Press..."

=== ESXI Configuration ===

This is a quick install guide written for ESXI 8.0.

1) First install ESXI using a bootable media, following the standard install prompts, and configure a custom password, which will be used for web access.

2) Install ESXI on the smaller of the two drives, as we are going to be using the larger as the datastore for VM Disk's, and the smaller for ESXI itself and ISO files.

3) After ESXI is installed, and started up to the main screen, Press "F2" to access basic systems settings, this will require you to input your password, you set at install. Then select management network settings and configure them as following:

Device IP: 192.168.7.14
Subnet Address: 255.255.255.0
Gateway: 192.168.7.250
DNS Servers: 192.168.4.4, 192.168.4.5
Hostname: System4.cyber.local

4) After this you should be able to access the ESXI web interface, via the devices IP "192.168.7.14" or system4.cyber.local

5) Next Select the "Storage" tab on on the dashboard. Now you can rename the first datastore, and also can mount and format other drives as datastores. We configured two datastores:

<code>
datastore1-super4

datastore2-super4
</code>

Datastore 2 holds the ESXI install, and we have added a directory for holding out ISO files for VM's

6) Now we are configuring out Internal virtual network switch "350-Internal".

First enter the network tab, from the left side of the screen just below the datastore tab.

Next click the "vswitch" section on the top of the menu

Now create a new switch from the options right below, and create a new switch named 350-Internal

Next go to the tool bar above, and select port-groups, select new port-group, and then associate it with the new internal network

Now out ESXI environment is configured.

=== PFSense Configuration ===

First Create a new VM from the VM tab in ESXI with the following specs:

2 network ports, one on <code>VM-Network</code>, on on <code>350-Internal</code> network

1 CPU

2 GB of RAM

8GB Thin Provision Disk

Mounted PFSense .iso file from datastore. (Don't forget this as I could not get the VM to boot, when mounting this later)

2) Install PFSense and use the default settings for the install

3) Once rebooted, access the CLI from the VM Console window and select 2 to configure IP's on the Interface

4) wxc0 is out WAN network Interface, and should be configured with the following:

<code>
No DHCP

IP: 192.168.7.75/24

Upstream Gateway: 192.168.7.250

No IPV6 Address

Do Not revert web interface
</code>

5) For the LAN network select wxc1

<code>
IP: 10.0.7.2/24

No Upstream gateway

No IPV6

No DHCP

Do Not Revert Web Interface
</code>

=== MGMT1 Install ===

In this section we are installing our MGMT box, I used the default xubuntu for the task, as it is reliable, and easy to work with.

1) Create a second VM with the following specs:

<code>
2 CPU Cores

5GB of RAM

30GB Thin provisioned Drive

Network adapter on the 350-Internal network

Xubuntu ISO, mounted in the CD ROM (again don't forget)
</code>

2) Boot up the machine, set username to "Super" hostname to "mgmt1", and Password to whatever you would like.

3) After install, reboot the machine and right click on the network status icon in the top right, and select "network settings"

Configure the settings as follows:
<code>
STATIC:

IP: 10.0.17.100

Subnet: 255.255.255.0

Gateway: 10.0.17.2

DNS Server: 1.1.1.1
</code>

Finally Install Chrome remote desktop for easy access, by downloading the Google Chrome .deb file, and installing with

<code>sudo dpkg -i "File Name"</code>

Main Page

2024-11-02T01:54:58Z

T20A02: /* Virtualization */

Welcome to the Goomba Cloud Wiki!.

This guide includes a culmination of projects written by yours truly, the site administrator! You will find anything from Proxmox stack configuration, all the way to software manual install guides (Including a guide to setting up this wiki) and much more!

== Pages ==

=== Reference ===

[[Key Based SSH from Windows to Linux]]

[[Windows 11 Enterprise .iso creation]]

=== Services ===

[[Forgejo Install from Binary]]

[[Vaultwarden Docker Container Setup]]

[[Wireguard VPN Setup (Regular and Site to Site)]]

[[Project Send Setup and Configuration]]

=== Projects ===

[[RPI CUPS server for mini print server]]

[[Dell Optiplex NVME BIOS mod]]

=== Virtualization ===

[[Ceph & Proxmox installation]]

[[vCenter Installation and SSO]]

[[Adding Networks in PFSense]]

[[Proxmox High Avilability (HA)]]

[[Proxmox NFS Configuration]]

[[Proxmox VM Passthrough]]

[[ESXI Settup]]

Main Page

2024-11-02T01:53:50Z

T20A02:

Welcome to the Goomba Cloud Wiki!.

This guide includes a culmination of projects written by yours truly, the site administrator! You will find anything from Proxmox stack configuration, all the way to software manual install guides (Including a guide to setting up this wiki) and much more!

== Pages ==

=== Reference ===

[[Key Based SSH from Windows to Linux]]

[[Windows 11 Enterprise .iso creation]]

=== Services ===

[[Forgejo Install from Binary]]

[[Vaultwarden Docker Container Setup]]

[[Wireguard VPN Setup (Regular and Site to Site)]]

[[Project Send Setup and Configuration]]

=== Projects ===

[[RPI CUPS server for mini print server]]

[[Dell Optiplex NVME BIOS mod]]

=== Virtualization ===

[[Ceph & Proxmox installation]]

[[vCenter Installation and SSO]]

[[Adding Networks in PFSense]]

[[Proxmox High Avilability (HA)]]

[[Proxmox NFS Configuration]]

[[Proxmox VM Passthrough]]

VCenter Installation and SSO

2024-11-02T01:50:11Z

T20A02:

=== vCenter Installation ===

==== vCenter Stage 1 ====

vCenter is a powerfull tool, and is critical in its role of clustering ESXi hosts, from VMware into one group allowing central management, SSO, permissions control, backups, and migrations along with much more functionality from a single web portal.

Before installing vCenter you will need to have your vCenter .iso file, or disk mounted to the system you use for management, on the same network as the device. Additionally you will want to make any DNS records you plan on using.

1) First Verify connection, and resolution to your AD controller, by pining it by name, and IP to verify it is working properly.

2) Now open the VSCA .iso directory, via cli, from your management device, and enter the /media/vsca-ui-installer/ directory, then move to the folder based on your guest OS.

[[File:1.png|600px]]

3) Now run the "Installer" file in that directory, to launch the Ui vCenter installer, where you will be greeted with this window.

[[File:2.png|600px]]

4) Click Install, Then next, Then accept the the EULA

[[File:3.png|600px]]

5) Once you reach the following page, enter the FQDN or IP of the ESXI server, then the login credentials for it, and click "Next", and Accept the Certificate warning. This is warning the user that the ESXI host selected is using a self signed cert. This is not an issue in most environments, but should be addressed for large production environments.

[[File:4.png|600px]]

[[File:5.png|600px]]

5) Once those settings are validated, and the ESXI system has been connected to the installer, then you must configure a VM name, and root password for the vCenter "Vm", as it will act on the ESXI host.

[[File:6.png|600px]]

6) Next Pick the size of the deployment, this is entirely up to the size of the environment, and the resources available. Here I picked "Small".

[[File:7.png|600px]]

7) Then you must pick the datastore, on the host esxi server, that will hold the vCenter VM

[[File:8.png|600px]]

8) Finally configure the network settings to be used by the vCenter instance. Here I used a reserved address for the server, the gateway was my PFSense router IP, and the DNS server was my Domain Controller.

[[File:9.png|600px]]

9) Click next, to review your settings, and then finish to install vCenter, and complete Stage 1. This will take some time

==== Stage 2, ESXI Configuration ====

Now that the server has been provisioned we must complete setup.

1) First we will be greeted by that original start page for the UI. Stage 2 will no longer be greyed out, and Stage one should have a green check indicating completion. Click Next

[[File:10.png|600px]]

2) Configure the NTP server settings to be used for the vCenter server. I recommend configuring a server, and not using system time, to prevent desync issues between ESXI Host's, vCenter, and the AD Controller once SSO is enabled. I used pool.ntp.org

3) Next use "Create a new SSO domain" for now to create a local domain, so that we can have multiple accounts, even if SSO stops working.

[[File:11.png|600px]]

4) Finally decline the CEIP setup, and make sure to uncheck the CEIP box;

[[File:12.png|600px]]

5) Finally Verify your settings, and hit finish, again this will take some time.

==== Stage 3, Adding Licensing, and Hosts ====

Here we now have a completed vCenter install, and we are going to add our ESXI host, and add our licensing information

1) Connect the the vcenter server using the IP set in Stage 1, or a FQDN set on the AD server, and click Launch Vsphere Client.

[[File:13.png|600px]]

2) Sign in with the "administrator@vsphere.local" account created in stage 2 of the vCenter installation. After that you will be greeted with the dashboard.

[[File:14.png|600px]]

3) Now add your license by going to the 3 bars at the top left, Then click "administration"

[[File:15.png|600px]]

4) Now on the left, click "Licenses"

[[File:16.png|600px]]

5) Now click add, and enter each license key, one per line, then click next, set names, and then apply them.

[[File:17.png|600px]]

6) Finally go to the assets tab, and apply the vCenter license.

7) Now we are going to add out host. To do this first we must go to our menu in the top left, then right click the vCenter domain, the New data center, and name it. Here i used SYS350

[[File:18.png|600px]]

8) Once the data-center is created, now we will right click it and select "add Host"

[[File:19.png|600px]]

9) Now enter the IP or FQDN of the device. *Note: This IP/Name will dictate the name of the host in the inventory tab, and cannot be changed without orphaning and rejoining the host*

[[File:20.png|600px]]

10) Click next, and enter the login information for the host, and click next

[[File:21.png|600px]]

11) Now accept the Security alert, and click next, then next again for host settings.

12) Then assign a ESXI License, and click Next

13) Leave lock down disabled, then select your new cluster for the location, and then click Complete.\

[[File:22.png|600px]]

14) Now your host is joined to vCenter, and you should see it, and any VM's it was hosting on the left panel, under the data center.

=== SSO Configuration ===

Here we will connect our domain, to the vCenter server, to allow Domain admins to access the vCenter environment accordingly.

1) First go to the menu at the top left again, and then click administration, then under "Single Sign On" select configuration

[[File:23.png|600px]]

2) Then select "Active Directory Domain"

[[File:24.png|600px]]

3) Then click "join AD" and enter your domains information, including the credentials of a domain admin. once this in completed you must reboot vCenter

4) To reboot vCenter, login to the vCenter management page via "https://domainname.local:5480" Then enter your administrator@vsphere.local credentials. After login you will be greeted with the vCenter dash panel

[[File:25.png|600px]]

5) Next at the top right, click "Actions" and then reboot. This will take some time, and this dash will recover before the main login will.

6) After the reboot, login to the VSphere client page, not the dashboard, and go to the SSO Users and Groups page

[[File:26.png|600px]]

7) Now navigate to "Groups", then click "Administrators"

[[File:27.png|600px]]

8) Now click "Add Members", switch the domain to your newly joined domain, and search "Domain Admins" adding it to the box below. Then click Save.

[[File:28.png|600px]]

9) Finally to make the domain you selected the default choice, click on "Identity Sources" then your domain entry, and click "Set as Default". This will make you only have to use the domain user's logon name, not the full domain string.

[[File:29.png|600px]]

Now we are complete, you can logout of your administrator@vsphere.local user and log in using your domain admin account.

VCenter Installation and SSO

2024-11-02T01:42:30Z

T20A02:

=== vCenter Installation ===

==== vCenter Stage 1 ====

vCenter is a powerfull tool, and is critical in its role of clustering ESXi hosts, from VMware into one group allowing central management, SSO, permissions control, backups, and migrations along with much more functionality from a single web portal.

Before installing vCenter you will need to have your vCenter .iso file, or disk mounted to the system you use for management, on the same network as the device. Additionally you will want to make any DNS records you plan on using.

1) First Verify connection, and resolution to your AD controller, by pining it by name, and IP to verify it is working properly.

2) Now open the VSCA .iso directory, via cli, from your management device, and enter the /media/vsca-ui-installer/ directory, then move to the folder based on your guest OS.

3) Now run the "Installer" file in that directory, to launch the Ui vCenter installer, where you will be greeted with this window.

[[:File:1.png]]

4) Click Install, Then next, Then accept the the EULA

![image](https://github.com/T20A026/SYS-350-Enterprise-Virtualization/assets/70958837/2884ebbb-899a-404e-95f0-0cc0afecfd82)

5) Once you reach the following page, enter the FQDN or IP of the ESXI server, then the login credentials for it, and click "Next", and Accept the Certificate warning. This is warning the user that the ESXI host selected is using a self signed cert. This is not an issue in most environments, but should be addressed for large production environments.

![image](https://github.com/T20A026/SYS-350-Enterprise-Virtualization/assets/70958837/03431db8-39f0-4406-aa8f-295d688a2f38)

![image](https://github.com/T20A026/SYS-350-Enterprise-Virtualization/assets/70958837/b33629a6-42fd-451c-9ca3-251ae30d42fe)

5) Once those settings are validated, and the ESXI system has been connected to the installer, then you must configure a VM name, and root password for the vCenter "Vm", as it will act on the ESXI host.

![image](https://github.com/T20A026/SYS-350-Enterprise-Virtualization/assets/70958837/7d3e661e-d189-4052-8923-962ed08802f8)

6) Next Pick the size of the deployment, this is entirely up to the size of the environment, and the resources available. Here I picked "Small".

![image](https://github.com/T20A026/SYS-350-Enterprise-Virtualization/assets/70958837/608d7500-501c-4ac7-9079-0de924e01888)

7) Then you must pick the datastore, on the host esxi server, that will hold the vCenter VM

![image](https://github.com/T20A026/SYS-350-Enterprise-Virtualization/assets/70958837/0f91bc22-1f33-40ff-a226-16a1976628fc)

8) Finally configure the network settings to be used by the vCenter instance. Here I used a reserved address for the server, the gateway was my PFSense router IP, and the DNS server was my Domain Controller.

![image](https://github.com/T20A026/SYS-350-Enterprise-Virtualization/assets/70958837/85dbb624-1449-4244-ab62-d7f5288ba7f2)

9) Click next, to review your settings, and then finish to install vCenter, and complete Stage 1. This will take some time

==== Stage 2, ESXI Configuration ====

Now that the server has been provisioned we must complete setup.

1) First we will be greeted by that original start page for the UI. Stage 2 will no longer be greyed out, and Stage one should have a green check indicating completion. Click Next

![image](https://github.com/T20A026/SYS-350-Enterprise-Virtualization/assets/70958837/b70056e1-c2bb-4168-aab6-f1c5b0355adf)

2) Configure the NTP server settings to be used for the vCenter server. I recommend configuring a server, and not using system time, to prevent desync issues between ESXI Host's, vCenter, and the AD Controller once SSO is enabled. I used pool.ntp.org

3) Next use "Create a new SSO domain" for now to create a local domain, so that we can have multiple accounts, even if SSO stops working.

![image](https://github.com/T20A026/SYS-350-Enterprise-Virtualization/assets/70958837/c80d9d99-a89a-4381-9d50-5651e0914934)

4) Finally decline the CEIP setup, and make sure to uncheck the CEIP box;

![image](https://github.com/T20A026/SYS-350-Enterprise-Virtualization/assets/70958837/630ae572-da5a-4552-aaca-f23d32c50e79)

5) Finally Verify your settings, and hit finish, again this will take some time.

==== Stage 3, Adding Licensing, and Hosts ====

Here we now have a completed vCenter install, and we are going to add our ESXI host, and add our licensing information

1) Connect the the vcenter server using the IP set in Stage 1, or a FQDN set on the AD server, and click Launch Vsphere Client.

![image](https://github.com/T20A026/SYS-350-Enterprise-Virtualization/assets/70958837/1e765081-030d-4d26-a7bb-34d56c0b20d8)

2) Sign in with the "administrator@vsphere.local" account created in stage 2 of the vCenter installation. After that you will be greeted with the dashboard.

![image](https://github.com/T20A026/SYS-350-Enterprise-Virtualization/assets/70958837/3291bc04-fd1c-4c29-ba5d-3540e7de12c1)

3) Now add your license by going to the 3 bars at the top left, Then click "administration"

![image](https://github.com/T20A026/SYS-350-Enterprise-Virtualization/assets/70958837/4f664eb0-8fae-4f01-b6d7-b331301acd33)

4) Now on the left, click "Licenses"

![image](https://github.com/T20A026/SYS-350-Enterprise-Virtualization/assets/70958837/c48cd0a8-9921-46a5-8ef9-3d5138e8e9fa)

5) Now click add, and enter each license key, one per line, then click next, set names, and then apply them.

![image](https://github.com/T20A026/SYS-350-Enterprise-Virtualization/assets/70958837/8aef5039-25ac-4b08-81b7-711f69187638)

6) Finally go to the assets tab, and apply the vCenter license.

7) Now we are going to add out host. To do this first we must go to our menu in the top left, then right click the vCenter domain, the New data center, and name it. Here i used SYS350

![image](https://github.com/T20A026/SYS-350-Enterprise-Virtualization/assets/70958837/5d1823d8-3185-4f80-a351-0224b2cfc463)

8) Once the data-center is created, now we will right click it and select "add Host"

![image](https://github.com/T20A026/SYS-350-Enterprise-Virtualization/assets/70958837/4224fef8-744d-4937-b057-ae8730bccc98)

9) Now enter the IP or FQDN of the device. *Note: This IP/Name will dictate the name of the host in the inventory tab, and cannot be changed without orphaning and rejoining the host*

![image](https://github.com/T20A026/SYS-350-Enterprise-Virtualization/assets/70958837/fe5f3021-45b4-4897-9d94-790fa72bab9e)

10) Click next, and enter the login information for the host, and click next

![image](https://github.com/T20A026/SYS-350-Enterprise-Virtualization/assets/70958837/415050eb-5882-462f-8709-9c6294a65d72)

11) Now accept the Security alert, and click next, then next again for host settings.

12) Then assign a ESXI License, and click Next

13) Leave lock down disabled, then select your new cluster for the location, and then click Complete.\

![image](https://github.com/T20A026/SYS-350-Enterprise-Virtualization/assets/70958837/4208cec0-2c75-430e-8991-71ef11bfd940)

14) Now your host is joined to vCenter, and you should see it, and any VM's it was hosting on the left panel, under the data center.

=== SSO Configuration ===

Here we will connect our domain, to the vCenter server, to allow Domain admins to access the vCenter environment accordingly.

1) First go to the menu at the top left again, and then click administration, then under "Single Sign On" select configuration

![image](https://github.com/T20A026/SYS-350-Enterprise-Virtualization/assets/70958837/91c6c59c-f4f7-490a-9d14-5959ef7a59d2)

2) Then select "Active Directory Domain"

![ima![image](https://github.com/T20A026/SYS-350-Enterprise-Virtualization/assets/70958837/65ba7513-99a9-43c9-9382-7d997a49eaba)

3) Then click "join AD" and enter your domains information, including the credentials of a domain admin. once this in completed you must reboot vCenter

4) To reboot vCenter, login to the vCenter management page via "https://domainname.local:5480" Then enter your administrator@vsphere.local credentials. After login you will be greeted with the vCenter dash panel

![image](https://github.com/T20A026/SYS-350-Enterprise-Virtualization/assets/70958837/3c5ef6b7-36f9-4ee7-9213-924d4a2ab914)

5) Next at the top right, click "Actions" and then reboot. This will take some time, and this dash will recover before the main login will.

6) After the reboot, login to the VSphere client page, not the dashboard, and go to the SSO Users and Groups page

![image](https://github.com/T20A026/SYS-350-Enterprise-Virtualization/assets/70958837/ab7a5c70-c996-412d-94ce-73a745973257)

7) Now navigate to "Groups", then click "Administrators"

![image](https://github.com/T20A026/SYS-350-Enterprise-Virtualization/assets/70958837/be989d25-e5d7-41e0-bede-7f18326059fb)

8) Now click "Add Members", switch the domain to your newly joined domain, and search "Domain Admins" adding it to the box below. Then click Save.

![image](https://github.com/T20A026/SYS-350-Enterprise-Virtualization/assets/70958837/e66b53d2-cde2-45c6-bf47-110d459d1167)

9) Finally to make the domain you selected the default choice, click on "Identity Sources" then your domain entry, and click "Set as Default". This will make you only have to use the domain user's logon name, not the full domain string.

![image](https://github.com/T20A026/SYS-350-Enterprise-Virtualization/assets/70958837/ffc208e2-dcab-4937-8878-bd0bc212df3f)

Now we are complete, you can logout of your administrator@vsphere.local user and log in using your domain admin account.

File:29.png

2024-11-02T01:41:18Z

T20A02: File uploaded with MsUpload

File uploaded with MsUpload

File:28.png

2024-11-02T01:41:17Z

T20A02: File uploaded with MsUpload

File uploaded with MsUpload

File:27.png

2024-11-02T01:41:17Z

T20A02: File uploaded with MsUpload

File uploaded with MsUpload

File:26.png

2024-11-02T01:41:17Z

T20A02: File uploaded with MsUpload

File uploaded with MsUpload

File:25.png

2024-11-02T01:41:17Z

T20A02: File uploaded with MsUpload

File uploaded with MsUpload

File:24.png

2024-11-02T01:41:16Z

T20A02: File uploaded with MsUpload

File uploaded with MsUpload

File:23.png

2024-11-02T01:41:16Z

T20A02: File uploaded with MsUpload

File uploaded with MsUpload

File:22.png

2024-11-02T01:41:16Z

T20A02: File uploaded with MsUpload

File uploaded with MsUpload

File:21.png

2024-11-02T01:41:15Z

T20A02: File uploaded with MsUpload

File uploaded with MsUpload

File:20.png

2024-11-02T01:41:15Z

T20A02: File uploaded with MsUpload

File uploaded with MsUpload

File:19.png

2024-11-02T01:41:15Z

T20A02: File uploaded with MsUpload

File uploaded with MsUpload

File:18.png

2024-11-02T01:41:15Z

T20A02: File uploaded with MsUpload

File uploaded with MsUpload

File:17.png

2024-11-02T01:41:14Z

T20A02: File uploaded with MsUpload

File uploaded with MsUpload

File:16.png

2024-11-02T01:41:14Z

T20A02: File uploaded with MsUpload

File uploaded with MsUpload

File:15.png

2024-11-02T01:41:14Z

T20A02: File uploaded with MsUpload

File uploaded with MsUpload

File:14.png

2024-11-02T01:41:14Z

T20A02: File uploaded with MsUpload

File uploaded with MsUpload

File:13.png

2024-11-02T01:41:13Z

T20A02: File uploaded with MsUpload

File uploaded with MsUpload

File:12.png

2024-11-02T01:41:13Z

T20A02: File uploaded with MsUpload

File uploaded with MsUpload

File:11.png

2024-11-02T01:41:13Z

T20A02: File uploaded with MsUpload

File uploaded with MsUpload

File:10.png

2024-11-02T01:41:12Z

T20A02: File uploaded with MsUpload

File uploaded with MsUpload

File:9.png

2024-11-02T01:41:12Z

T20A02: File uploaded with MsUpload

File uploaded with MsUpload