Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 2 subscribers
  • Views 3961 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Push install bug during protect computers wizard?

ShunzeLee

Dear Sir,

When I push install the endpoint on client with SEC protect computers wizard,

it need user to input the credentials during the procedure.

 

MY SEC's administrator account (administrator) is different with client administrator account (shunze).

When I input the client's administrator account in the credential, the wizard return error.

Only the SEC's administrator can pass the verification.

Since the administrator account is different with the client admin account,

the push install failed on client finally...


It needs to add the client's admin account (shunze) on SEC, and give the administrator privilege to the account,

the push install succeeded.

 

It should be a bug, isn't it?

Then credential on wizard should be client's admin not SEC's admin.

Thanks~



This thread was automatically locked due to age.
Parents
  • 0

    The account you specify in the wizard needs to be able to logon to the management server.  This way the mgntsvc.exe process, which is connecting to the remote computer to create the scheduled task to run setup.exe can impersonate the account you entered.

    Typically in a domain environment you would use a domain admin account.  E.g. dom\admin.

    This way, the account can authenticate locally on the management server, and the account, by virtue of being a member of domain admins, which is a member of the local administrators group on the client has permissions.

    In a workgroup environment, if the endpoint has the local account computername\bob, then on the management server there would need to be an account called bob (with the same password) also that you could specify in the protect wizard.  Therefore in a workgroup environment, ideally there is a common administrative account on all computers with the same password.

    Regards,

    Jak

Reply
  • 0

    The account you specify in the wizard needs to be able to logon to the management server.  This way the mgntsvc.exe process, which is connecting to the remote computer to create the scheduled task to run setup.exe can impersonate the account you entered.

    Typically in a domain environment you would use a domain admin account.  E.g. dom\admin.

    This way, the account can authenticate locally on the management server, and the account, by virtue of being a member of domain admins, which is a member of the local administrators group on the client has permissions.

    In a workgroup environment, if the endpoint has the local account computername\bob, then on the management server there would need to be an account called bob (with the same password) also that you could specify in the protect wizard.  Therefore in a workgroup environment, ideally there is a common administrative account on all computers with the same password.

    Regards,

    Jak

Children
No Data
Unfiltered HTML