How can we help you today? How can we help you today?

Problems installing on a DC

We've got a single server dev environment, and the dev server is also a DC.

The installer fails unless we use a machine admin account as the service account - this is bad!

We'd prefer to use a normal user account as the service account - why are you insisting on a admin account as the service account?
Bernard Sheppard
0

Comments

3 comments

Sort by
  • Nigel Morse
    This is beacuse the service account is the default account used to connect to the monitored servers both via SQL and WMI. Beacuse of what we monitor we need this to be an admin account on those servers.

    Although you can specify a different windows account for each servers WMI connection and a SQL Authentication account for the SQL connection it is far far easier to have one admin account for all the connections. If you didn't choose an admin account up front at install time you'd need to reinstall, so to avoid that we thought it easier to require an admin account at install.
    Nigel Morse
    0
  • Bernard Sheppard
    Fair enough for the WMI access.

    However, ideally, I'd like two default accounts - one for WMI, and one for SQL - it allows finer grained control over the rights assigned to each account. I guess it is too late given this is an RC.
    Bernard Sheppard
    0
  • Nigel Morse
    It's been a a... thorny issue shall we say :)

    The main issue is which the SQL account in the SQL connections use the "logged in" user (like connecting via SSMS - it trys to connect as you) - so that's the one it's best to get correct.

    WMI allows you to specify an account on the remote machine to use which is why that can be changed per-computer. Having a default is a good idea, but also complicates things even more.
    Nigel Morse
    0

Add comment

Please sign in to leave a comment.