How to install and run mid server with other than the window admin

[sapna_sagar]

How to install and run mid server with other than the window admin means with different user??

[sapna_sagar]

Taken this line from your above comment:

"A Discovery Identifier called SCCM ID & Class Name returns the resource ID of a computer from SCCM and stores it in a table called Source [sys_object_source]."

CAN YOU PLEASE TELL ME , WHICH LINE EXACTLY INSERTING INTO THE Source [sys_object_source] TABLE...???

function(ciData, log, identifier) {

      var sccmID = ciData.getData().correlation_id;

  gs.log('Running....DD..'+ciData.getData().sys_class_name) ;

  //16778287

      var matchable = JSUtil.notNil(sccmID);

  var matching = [];

  if (matchable)

  matching = matchingCIs(sccmID, ciData);

  return new CIIdentifierResult(matching, matchable);

      function matchingCIs(id, ciData) {

              var matches = [];

              findBySourceTable(id, ciData, matches);

              if (matches.length == 0)

                      findByCorrelationIDField(id, ciData, matches);

              return matches;

      }

      function findByCorrelationIDField(id, ciData, matches) {

              var gr = new GlideRecord(identifier.applies_to);

              gr.addQuery('sys_class_name', ciData.getData().sys_class_name);

              gr.addQuery('correlation_id', id);

              gr.query();

              // populate our return value...

              while (gr.next())

                      matches.push('' + gr.getUniqueValue());

      }

      function findBySourceTable(id, ciData, matches) {

              var gr = new GlideRecord("sys_object_source");

              gr.addQuery("name", "SCCM");

              gr.addQuery("id", id);

              gr.addNotNullQuery("target_sys_id");

              gr.addQuery("target_table", ciData.getData().sys_class_name);

              gr.query();

              while (gr.next()) {

                      // Verify it actually exists...

                      var grr = new GlideRecord(ciData.getData().sys_class_name);

                      if (grr.get(gr.target_sys_id))

                              matches.push(gr.target_sys_id + '');

              }

              return matches;

      }

}

[Dave Smith1]

Extracting the ZIP to a set of JAR files and running them as a service does not need privileged access.

However, registering the daemon as a service in Windows service applet (services.msc) requires privileged access. I believe the account needs "Logon as a service" privilege, but I don't know any more than that.

Once the service is up and running, it needs to be changed from a local system account to one with specific Windows credentials. If this is not performed, any credentials added to your Discovery application will fail because the MID server will still try to use the local system account.

Some confusion reigns over the actual privilege needed - it's not really access to the machine it's running on, but credentials to target devices.   The documentation has some information about sudo access to *nix devices and claims Windows Domain Admin rights needed to Windows-based systems, but the upshot is that specific commands are run (shell commands as well as powershell scripts) and if the credentials are for a lower-privileged account then limited information is returned.