Tag without

1. Cluster Setup: Ensure that your Proxmox hosts are part of the same cluster. A Proxmox cluster consists of multiple Proxmox VE servers (nodes) combined to offer high availability and load balancing to virtual machines. Nodes in a cluster share resources such as storage and can migrate VMs between each other.
2. Shared Storage: Live migration requires shared storage accessible by both the source and target hosts. This shared storage can be implemented using technologies like NFS, iSCSI, or Ceph. Shared storage allows the VM’s disk images and configuration files to be accessed by any node in the cluster.
3. Migration Prerequisites: Before initiating a live migration, ensure that the target host has enough resources (CPU, memory, storage) to accommodate the migrating VM. Proxmox will check these prerequisites before allowing the migration to proceed.
4. Initiating Migration: In the Proxmox web interface (or using the Proxmox command-line interface), select the VM you want to migrate and choose the “Migrate” option. Proxmox will guide you through the migration process.
5. Migration Process:
   • Pre-Copy Phase: Proxmox starts by copying the memory pages of the VM from the source host to the target host. This is done iteratively, with the majority of memory pages copied in the initial phase.
   • Stopping Point: At a certain point during the migration, Proxmox determines a stopping point. This is the point at which the VM will be paused briefly to perform a final synchronization of memory pages and state information.
   • Pause and Synchronization: The VM is paused on the source host, and any remaining memory pages and state information are transferred to the target host. This pause is usually very brief, minimizing downtime.
   • Completion: Once the final synchronization is complete, the VM is resumed on the target host. From the perspective of the VM and its users, the migration is seamless, and the VM continues to run without interruption on the target host.
6. Post-Migration: After the migration is complete, the VM is running on the target host. You can verify this in the Proxmox web interface or using the command-line tools. The source host frees up resources previously used by the migrated VM.
7. High Availability (HA): In a Proxmox cluster with HA enabled, if a host fails, VMs running on that host can be automatically migrated to other hosts in the cluster, ensuring minimal downtime.

Overall, Proxmox VM live migration is a powerful feature that enables you to move virtual machines between hosts in a Proxmox cluster with minimal downtime, providing flexibility and high availability for your virtualized environment.

Remove the maintainer account (which allowed users to log in through the console after a hard reboot). Users who lose their password must have physical access to the FortiGate and perform a TFTP restore of the firmware in order to regain access to the FortiGate.

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.