• Date
  • Date 7 Mar 2019 22:05
  • Replies 5 replies
  • Subscribers 128 subscribers
  • Views 511 views

Impact of changing from Local Account to Active Directory Domain ID to run LiveCompare?

Hello Everyone,

We have been running LiveCompare for quite a few years and it is currently running under a local Windows account with administrator rights, as the installation guide calls for. However, a recent audit has prompted the question of whether we can change LiveCompare to run with an Active Directory Domain ID. 

What would the impact of changing to an AD ID be? Does anyone else run with an AD ID?

Thanks for your comments,
Chris Ryan

  • We have always run under a domain account in the local admin group. No issues. -Ray
  • You can use a domain account so long as it is added to the local administrators group. Many customers run LiveCompare with this type of account.

    We recommend a local account because the domain account may have network privileges that even indirectly you don't want to expose through LiveCompare. In short, a local account makes very clear that the LiveCompare service account can't be used to do anything outside of the LiveCompare server.

    The soon-to-be-released LiveCompare 3.9 makes switching accounts much simpler. There is a special variant of the configuration wizard that you can use to change account. We expect to release LiveCompare 3.9 in the coming days (some chance of change).
  • In reply to rberry:

    Thanks Ray!
  • In reply to Chris Trueman:

    Thanks for the explanation Chris. I'll be looking forward to 3.9 and will load that up in our Dev server once available and give the change to Domain a try there.

    We are currently version 3.8, if I cannot get our team to do the upgrade to 3.9 quickly, is there a recommended way to change to Domain account in version 3.8 we should follow?
  • In reply to chrisryanmn:

    In 3.8 use the configuration wizard to first deconfigure LiveCompare and then again to configure it using the new account. You should probably check first to see if you have any scheduled tasks (PHD collection, workflows, etc.) and make sure that they are still scheduled once re-configured.