Most of the work of running a Windows server happens inside an RDP session: checking that overnight backups completed, applying the monthly cumulative update, clearing a stuck print spooler, and reading the security log to see who logged on at 03:00. None of it is glamorous, and all of it is easy to do inconsistently. This article describes a repeatable daily routine built entirely from built-in tools, designed for a Windows VPS that you administer remotely and may not visit physically for months.
The routine assumes Windows Server 2019 or 2022, an account with local administrator rights, and a habit of starting the session by opening an elevated PowerShell window rather than clicking through Server Manager. Everything below can be scripted once you are satisfied with the manual version.
Understand Where Your RDP Sessions Actually Live
RDP sessions are not processes you can see in Task Manager alone. query user lists interactive sessions with their IDs, states, and logon times; query session includes listener and console sessions. Disconnecting an RDP client does not end the session — it moves to Disc state and keeps every process, open file handle, and locked registry hive alive. That is why a disconnected session holds a file lock that blocks a backup, and why the server appears to have memory pressure while no user is logged on.
Decide a policy and enforce it. For administration, log off rather than disconnect at the end of the session: logoff 3 /server:localhost cleans up properly. If you need long-running unattended work, run it as a scheduled task under a service account instead of leaving an interactive session open. Terminal Services settings live under HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services; the value MaxDisconnectionTime (in minutes) will terminate disconnected sessions automatically, and fEnableRemoteFXAdvancedRemoteApp is not a substitute for a session policy.
Clipboard, Drive Mapping, and Their Risks
Clipboard redirection and drive redirection are convenience features that quietly punch a hole in your isolation boundary. A shared clipboard lets you paste a password reset script as easily as a marketing document, and drive redirection exposes your local C: drive to the server as \\tsclient\C, so a compromised session can read workstation files.
Control this both client-side and server-side. In gpedit.msc or Group Policy Management, navigate to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Session Host > Device and Resource Redirection. Set Do not allow drive redirection to Enabled for production hosts, and set Do not allow clipboard redirection to Enabled where policy requires it. The corresponding registry values are fDisableCdm and fDisableClip under the Terminal Services key. For file transfer, use SMB over a private network or Copy-Item -ToSession with PowerShell remoting instead.
Applying Windows Updates on a Remote Server
Check the update state before doing anything cosmetic. Get-WindowsUpdate from PSWindowsUpdate is not built in; inbox-only alternatives involve the Microsoft.Update.Session COM object. The practical shortcut is to let the Windows Update service work and monitor it: Get-WinEvent -LogName "System" -MaxEvents 100 | Where-Object {$_.ProviderName -eq "Microsoft-Windows-WindowsUpdateClient"}.
Two event IDs matter most: 19 (installation succeeded) and 20 (installation failed). A cluster of 20s followed by a reboot is the classic signature of a partly applied cumulative update. Configure a maintenance window with the registry key HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU\NoAutoRebootWithLoggedOnUsers set to 1 so a rebooting update does not strand your session mid-task, and always confirm the host comes back with Test-NetConnection host -Port 3389 from outside before you close your laptop.
Verifying Backups Instead of Trusting Them
A backup job that reports success is not a backup. Windows Server Backup writes to the event log under Microsoft-Windows-Backup, and Get-WinEvent -LogName "Microsoft-Windows-Backup/Operational" -MaxEvents 20 will show completed, failed, and missed runs with byte counts. Compare the reported bytes against the size of your data set from the previous run; a job that “completes” in four minutes for a 200 GB volume is copying nothing useful.
Once a week, restore something. Pick a small file from the latest recovery point, restore it to an alternate location with wbadmin get versions and wbadmin start recovery, and confirm the content is valid before deleting the test copy. Record the recovery point time in your runbook. An image-level restore test to a throwaway VM is the only way to know the boot volume is recoverable on this provider’s storage.
A Daily Logon and Security Review
Two minutes of log review each morning catches most surprises early. Event ID 4624 with logon type 10 records RDP logons; type 3 records network logons, which is how a compromised credential being used from elsewhere usually looks. Failures are 4625, and a burst of 4625s against the Administrator account from a single source address is either a misconfigured service or a brute-force attempt against an exposed port.
Query the log directly rather than scrolling: Get-WinEvent -FilterHashtable @{LogName='Security'; Id=4624,4625; StartTime=(Get-Date).AddHours(-24)}. Note the IpAddress and TargetUserName fields in each record. Also check 4648 (logon with explicit credentials) and 4672 (special privileges assigned), which together tell you whether anything is running with elevated rights that you did not schedule. Keep security log size at least 256 MB or you will lose the previous day’s records before you look at them.
Housekeeping That Prevents Slow Degradation
Three checks keep a server from degrading quietly. First, disk free space per volume with Get-Volume | Select DriveLetter,SizeRemaining,Size — under 10 percent free on the system volume makes update installation fail with misleading errors. Second, the Windows event log sizes and the C:\Windows\Temp footprint. Third, the status of the services you depend on: Get-Service | Where-Object {$_.StartType -eq 'Automatic' -and $_.Status -ne 'Running'} should return nothing on a healthy host.
Recycle IIS application pools during this window if you run web workloads; Get-IISAppPool | Restart-WebAppPool does it in one line, and doing it on a schedule beats discovering a memory leak at peak traffic. For .NET applications, also check Get-Process w3wp | Select Id,WorkingSet64,StartTime — a worker process that has grown steadily for weeks and never recycled is telling you something about your application code.
Writing the Routine Down
The value of a daily routine is that it is boring and repeatable. Collect the commands above into a single read-only audit script, run it at the start of each session, and save the output to a dated file. You then have a rolling record of disk usage, failed updates, and logon anomalies that makes “the server has been slow for a while” a diagnosable statement rather than a vague complaint.
If you are still choosing a host, review the management and console options in a Windows VPS plan comparison before you commit — out-of-band console access is what saves you when an update breaks networking and RDP never comes back. Routine administration is mostly the discipline of looking at the same things in the same order, every day.


