How to deploy a software when current logged in user doesn't have admin rights?
This is a very common problem with organization they don't provide admin right to end users.
Dell KACE manage Installation uses current logged in user so when I am deploying Dhruva desktop backup agent using kace it is getting failed.
Do any one suggest the alternative way to push the software installation to bulk machines and the current logged in user doesn't have admin right.
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
Pressanykey
8 years ago
Hi,
First off, I'm not sure that the statement regarding KACE is correct, most deployment tools use a "system" account to deply software normally, and some allow actions to be carried out in the context of the currently logged on user, but only actions that he has the permissions to execute.
I take it that this application requires you to put resources on the machine that are user specific... If this is the case, and the package is in a "MSI" format, then adding an ActiveSetup call to perform a "self-repair" should fix this, however the user (if logged on) would be required to logoff and back on again.
If the application is not in a MSI format, then I suggest you repackage it (Raypack for KACE), and use the self-repair mechanism to install the user specific resources.
First off, I'm not sure that the statement regarding KACE is correct, most deployment tools use a "system" account to deply software normally, and some allow actions to be carried out in the context of the currently logged on user, but only actions that he has the permissions to execute.
I take it that this application requires you to put resources on the machine that are user specific... If this is the case, and the package is in a "MSI" format, then adding an ActiveSetup call to perform a "self-repair" should fix this, however the user (if logged on) would be required to logoff and back on again.
If the application is not in a MSI format, then I suggest you repackage it (Raypack for KACE), and use the self-repair mechanism to install the user specific resources.
Posted by:
anonymous_9363
8 years ago
>admin rights to end users
That isn't a problem, it's Best Practice. Your experience should tell you that users are dangerous, prone to doing stupid things.
From what I know of KBoxes, an MI can be set to use the local System account. Don't forget, though, that that account has no network access so the package will need to be copied locally first.
That isn't a problem, it's Best Practice. Your experience should tell you that users are dangerous, prone to doing stupid things.
From what I know of KBoxes, an MI can be set to use the local System account. Don't forget, though, that that account has no network access so the package will need to be copied locally first.
Posted by:
chucksteel
8 years ago
As Pressanykey said, KACE runs managed installs as SYSTEM and not as the currently logged in user. We use Druva also and have been deploying it to end users as a managed install. What kind of problems are you seeing?
