A good backup tool uses VSS Writers to achieve application consistent backups, which also truncates transaction log files. You can also achieve that without having to do a backup. Here are the few commands:

diskshadow

You can add multiple volumes, if database and log files are located on different disk drives:

add volume D:

add volume E:

begin backup

create

end backup

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

In Microsoft 365 / Exchange Online, to connect a soft deleted mailbox, you have need to use the cmdlet New-MailboxRestoreRequest to restore the mailbox to another user.

Get-Mailbox -SoftDeletedMailbox | select guid

Get-Mailbox <NewMailbox> | select guid

New-MailboxRestoreRequest -SourceMailbox <GUID> -TargetMailbox <GUID of new mailbox> -AllowLegacyDNMismatch

To check the status of the restore:

Get-MailboxRestoreRequest | Get-MailboxRestoreStatistics

References:

Reddit

If you are noticing seemingly random RDS session freezing on Windows 10/11 clients, this registry key might help. It disables the UDP protocol for RDP connections, which Microsoft enabled by default since Windows 10 1809/1909. I have had this issue occur on Windows 10 21H2.

HKLM\Software\Policies\Microsoft\Windows NT\Terminal Services\Client

DWORD fClientDisableUDP 1

A reboot of the machine was not needed, after closing the RDP session and reconnecting, TCP was being used. You can check which protocol is being used by clicking the symbol at the top:

References:

https://www.michaelmaw.com/how-to-fix-remote-desktop-freezing/

https://community.spiceworks.com/topic/2269433-remote-desktop-randomly-freezes-up

When trying to install the Teams system-wide on an RDS, you might get this error stating that no VDI environment was detected:

msiexec /i “Teams_windows_x64.msi” ALLUSER=1

This is because the installer checks if these registry entries are present on the system (Citrix or VMware):

HKLM\Software\Citrix\PortICA DWORD ALLUSER 1

So the solution is easy: just manually add the Citrix key you are good to go. Teams should work just fine on a RDS that is not provisioned by Citrix or VMware Horizon (why shouldn’t it?).

References:

https://www.masterpackager.com/blog/mst-to-install-microsoft-teams-msi-vdi-to-regular-windows-10