Suggest a new feature or enhancement...

Support auto-upgrading instances of Deployment Manager which run as domain user

In order to provide the Deployment Manager with the permissions required to deploy to SQL Database using Windows authentication, the Windows service hosting it needs to use the logon credentials of a Windows domain user. Currently updates fail unless the server is running as Local System.

26 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Paul ZahPaul Zah shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    1 comment

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Iain ElderIain Elder commented  ·   ·  Flag as inappropriate

        Our database security policy forbids us from granting logins for specific machines. Each login must be mapped to a service account in an Active Directory domain.

        RGDM needs a sysadmin login to perform SQL Server deployments, so we run RGDM under an account like CORP\svc_rgdm and grant sysadmin to that service account.

        In that scenario, here's what we do to upgrade RGDM.

        1. Change the service account to LocalSystem.
        2. Restart the service.
        3. Upgrade.
        4. Change the service account back to CORP\svc_rgdm.
        5. Restart the service again.

        It makes upgrades disruptive for our release engineering team.

      Feedback and Knowledge Base