If you need to renew the Always On VPN IKEv2 server certificate, here are three lines that will help you. Assuming you have the right certificate and the thumbprint, execute the following commands on the VPN server:

$cert = Get-ChildItem -Path Cert:\LocalMachine\My\ | where { $_.Thumbprint -eq "thumbprint" }

Set-VpnAuthProtocol -CertificateAdvertised $cert

Restart-Service RemoteAccess

If these commands saved your day, leave a comment!

Windows Server 2022 is new and has to be the best Windows Server there is right? Not at all. Microsoft has added a recovery partition (like in Windows Client versions) that prohibits you from expanding the boot disk like you usually would in older Windows Server versions.

Anyway, here are a few diskpart commands that will help you delete the recovery partition and allow you to expand the boot disk:

diskpart

list disk

select disk 0

Make sure partition 4 is the 523MB Recovery partition

select partition 4

delete partition override

References:

https://www.diskpart.com/diskpart/delete-partition-4125.html

If UAC is enabled and Admin Approval Mode is enabled for the built-in Administrator for example, you might have problems accessing network drives from an elevated command prompt. This behavior is expected, since in Admin Approval Mode all apps run as a standard user by default. If a program is elevated, it runs under a different session than the non-elevated user.

Microsoft suggests following fixes or workarounds:

1. Remap network drives via bat file or manually
2. Create this registry key, which creates a link between both sessions:
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System DWORD EnableLinkedConnections 1

References:

https://docs.microsoft.com/en-us/troubleshoot/windows-client/networking/mapped-drives-not-available-from-elevated-command

Have you been having issues with Microsoft Azure AD Sync service after a simple reboot of the Windows Server? These simple steps might help:

Copy model.mdf and modellog.ldf files from

C:\Program Files\Microsoft SQL Server\150\LocalDB\Binn\Templates

to either

C:\Users\ADSyncxxxxx$\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\ADSync2019

or

C:\Windows\ServiceProfiles\ADSync\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\ADSync2019

This issue should not occur starting from version 2.1.1.0 of MS Azure AD Connect. Read the Microsoft doc below to perform a manual in-place upgrade of Azure AD Connect.

References:

https://www.reddit.com/r/sysadmin/comments/rxkd7m/has_your_azure_ad_connect_been_unable_to_start/

https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-upgrade-previous-version#in-place-upgrade

If you have the misfortune of having to troubleshoot and repair boot issues on a virtual machine after a physical host crash, these two commands might help you.

First of all, try to get into the advanced settings on boot (it should be the F11 key), or after a while Windows (Server or 10/11) might automatically go into the menu when it cannot boot from disk. Alternatively a Windows ISO image can be used.

Once in the advanced settings, run the good old checkdisk command:

chkdsk /f C:

After completion, restart the VM and check if you are able to boot. If the issue persists, try restoring the registry database (once again through the advanced settings or a Windows ISO). A scheduled task regularly backs up the registry and puts it the folder C:\Windows\System32\config\Regbak.

copy C:\windows\system32\config\RegBack\* C:\windows\system32\config

Restart the VM and check if you are able to boot into Windows. If you still have issues, you should consider restoring from a backup (it sucks but sometimes it is unavoidable).