Console Apps Are Just Way Too Common I've worked at a few different companies that for one reason or another have had console applications that were critical to the business. Unfortunately, all too often these mission-critical command line applications would end up being closed or paused. A critical patch would be installed on the Windows OS, causing the server to reboot, and the person installing the patch would forget to log back into the server's console. Or someone would remote desktop into the server and start up a second copy of the applications, causing all sorts of problems. When you have command line applications running, something as simple as a mouse click can completely stop the command line application. By clicking within a DOS window that is running an application, the command line application can be stopped in its tracks as the command window has gone from an interactive mode to selecting text to be copied. If these applications were configured to run as a Windows service, then these problems would have been avoided, thereby escaping production outages. Story Time Default Sysadmin Rights When installing a new SQL Server, special attention needs to