Hi experts.. looking for some best practices here..
I would like to use the same account for remote Windows servers as the SiteScope service account (a domain user). I assume that you must deploy a remote for various monitors, which I have been doing for some time (but using a different account).
My question is, in two parts: 1) are remotes required in a template if you are using the same account as the SiteScope service (domain account), and 2) if so, how can you just tell SiteScope to use that instead of having to maintain the login information in the remote's properties.
And then, a follow up question - the global setting of 'optionalSetupConnection' - how does that affect things if you only need it for a small amount of machines (I had never used it before, and SiS always seemed to work with the local account in a remote's properties, however i have noticed SiteScope will attempt to log in with the service's account first, then the remote's credentials without that global parameter set).
After a recent local account password change, a lot of strange things started to happen (see my other post), so I want to avoid that when the password is changed on the service accounts. If SiS will just ignore the remote properties (or if i can skip remote deployment) it will be less of an issue.