Enabling "super admin" on Windows 10 - SQL Sentry

Enabling "super admin" on Windows 10

Recently, I tried installing SQL Sentry Power Suite on a brand new VM christened with the RTM version of Windows 10. Unfortunately, they've changed something about what Administrator really means. The active account is a local administrator of my VM (which is not connected to a domain), and the service account validation succeeds:

Service account validation

When I click Install, UAC seems happy to let me proceed:

UAC Prompt

Unfortunately, in my case, it later gets hung up on this error message:

Service SQL Sentry Monitoring Service could not be installed. Verify that you have sufficient privileges to install system services.

I learned that Windows 10 (and maybe Windows 8/8.1, I didn't use those long enough to come across this) has a concept of a "super admin" – you enable it and set the password at the command line:

net user Administrator /active:yes
net user Administrator $omeCr@zyPa$$w0rd

Make sure to also add Administrator to the sysadmin role (if you want to select the SQL Sentry database to use using Windows Authentication), and then switch user, and install SQL Sentry from that user account (and set the service to run as that account).

I tried reproducing the problem on another Windows 10 machine, but couldn't, so there is probably some other factor that comes into play (maybe it's not an issue with upgrades from earlier versions of Windows, or the Windows Insider builds). It also seems like it is possible to install the service as a "regular" administrator after the above command line options have been run, but I only tested it on this same machine after uninstalling SQL Sentry, so not sure if that's because of the change or because the service had already been installed successfully once.

We're trying to coerce a reliable repro in the lab, and will address the issue appropriately once we understand the factors that lead to the problem.

Hopefully this is a rare occurrence, but if you come across this issue, please try the workaround. And note that this workaround is likely to pan out for similar issues installing any service.

Comments ( 3 )

    • M McDonald says:

      You don't say whether you did this or not — Use run as administrator when launching the installer?

    • Aaron Bertrand says:

      Yes, I did use Run as Administrator (but with or without that option, I wasn't unable to reproduce this on other, similarly-configured machines, so I'm still not clear why it didn't work in this isolated case).

    • sqlbarbarian says:

      That would totally explain all my recent problems with my home install and permissions on folders etc. I was pretty confused on why I'd be getting more permission requests, when I am already an admin. Maybe this has something to do with it! thanks for the heads up

    Leave A Comment

    Your email address will not be published.