Production-tested. Partner links.
🛸 Proton VPN – Encrypted tunnel
🔐 Proton Pass – Zero-knowledge vault
🦑 GitKraken Pro – Visual Git client
🐧 Linux Foundation – Code: VALDEMAR
Disable Server Manager Autostart in Windows Server 2019
By Vladimir Mikhalev · Solutions Architect · Docker Captain · IBM Champion
This article is for those looking for a detailed and clear guide on how to disable Server Manager autostart in Windows Server 2019.
NOTEFor instructions on disabling Server Manager autostart in Windows Server 2012 R2, see: Disable Server Manager Autostart in Windows Server 2012 R2.
We go into the system under an account with administrator rights.
Open Server Manager, click on the “Manage” button in the upper right corner of the screen, and select “Server Manager Properties”.
Check the box “Do not start Server Manager automatically at logon” and click on the “OK” button.
Server Manager will no longer start automatically.
You can also disable the automatic start of “Server Manager” through the task scheduler. To do this, you must disable the task that is responsible for the automatic start of “Server Manager”.
In Server Manager, click on the “Tools” button in the upper right corner of the screen and select “Task Scheduler”.
In the “Task Scheduler Library” go to the “Microsoft” section, then to “Windows”, and in the “Server Manager” subsection, select the “Server Manager” task.
In the “Actions” menu, click on the “Disable” button.
Server Manager will no longer start automatically.
In addition, you can disable the task that is responsible for automatically starting Server Manager using the command line.
Press “Start”, specify “cmd” in the search bar, and select “Command Prompt”.
Disable Server Manager autostart using the command:
schtasks /Change /TN "Microsoft\Windows\Server Manager\ServerManager" /Disable
Server Manager will no longer start automatically.
You can also disable the task that is responsible for automatically starting Server Manager using Windows PowerShell.
On the keyboard, press the key combination “Win” and “x” and in the menu that opens, select “Windows PowerShell (Admin)”.
Disable Server Manager autostart using the command:
Get-ScheduledTask -TaskName ServerManager | Disable-ScheduledTask
Server Manager will no longer start automatically.
Related Posts
- 1Recovering a Corrupt Exchange Database with Stellar Repair — Real-World Lab TestSysAdmin & IT Pro · We deliberately broke an Exchange 2019 server to see if Stellar Repair for Exchange could recover a dirty-shutdown EDB file. Step-by-step recovery process, lab setup, and lessons learned.
- 2Distinctions Between Terminal, Command Line, Shell, and PromptSysAdmin & IT Pro · Learn the differences between terminal, command line, shell, and prompt in Linux. A beginner-friendly guide to essential CLI concepts and tools.
- 3Install Ubuntu Server 22.04 LTSSysAdmin & IT Pro · Step-by-step guide to install Ubuntu Server 22.04 LTS. Covers language, disk setup, OpenSSH, user creation, and system configuration for beginners.
- 4Install OTRS on Ubuntu ServerSysAdmin & IT Pro · Comprehensive guide to installing OTRS Community Edition on Ubuntu Server. Learn to configure PostgreSQL, Apache, SSL with Let's Encrypt, and launch OTRS securely.
Random Posts
- 1Configure Exchange Server 2016SysAdmin & IT Pro · Step-by-step guide to configure Exchange Server 2019. Learn how to set up mailbox databases, public folders, DNS, certificates, send/receive connectors, and more.
- 2Install Active Directory Domain Services on Windows Server 2008 R2SysAdmin & IT Pro · Step-by-step guide to install Active Directory Domain Services (AD DS) on Windows Server 2008 R2. Configure DNS, static IP, and promote to domain controller.
- 3Essential Commands for Listing Docker ContainersDevOps & Cloud · Master Docker with essential commands for listing containers. This guide covers all you need to manage container states efficiently.
- 4Install Wiki.js with Docker ComposeSelf-Hosting · Step-by-step guide to install Wiki.js with Docker Compose on Ubuntu using Traefik, Let's Encrypt, and PostgreSQL. Secure setup with SSH and HTTPS.