Forum Discussion

Michael_Dieter's avatar
28 days ago

Non-Admin Collector install

After trying to navigate through all the ramifications of Collector Least Privilege, I considered the option of simply getting new VM servers and installing new collectors with a "least privilege" user account.  I'm fortunate enough that we have sufficient compute and storage resources that my request for new VMs can be delivered, and then I can remove the old collectors from service and our server virtualization team can delete them (returning those compute and storage resources to the available pool; net impact is 0).  This seems like it will be less overall headache and effort than running the LM-supplied scripts.

So I'm just going to throw this screen shot out there, for public consumption, of the install ---being done with the intent of moving to "Least Privilege"---recommending Domain Admin/Local Admin. 

Sure, maybe this is just an artifact in the installer presentation? 

 

  • I have been struggling with the non-admin migration as well. I am curious, where were you able to find instructions to install collector with a non-admin user?

    • Joe_Williams's avatar
      Joe_Williams
      Icon for Professor rankProfessor

      Install as SYSTEM then use the PowerShell script found in the support documents. This was the easiest way to do it.

  • Running the collector install, you get prompted for user credentials (an account that is local admin) with privilege to install software.   One should use this account to run the collector installer but supply a different (non-admin) user account at the prompt during installation?

    This answer may be self-evident to some, but I find the instructions not clear and seem to rely on implicit assumption by the reader instead of explicit intent by the technical content team.