Allow user account to install software in Win7 without installing it in other accounts
I currently have an administrator account and a regular user account I created through the adminsitrator account.
I'd like to give make it possible for my other user account to install software in its account in such a way that my administrator account is not littered up with that software that's being installed.
How to do it? I am using Win 7.
windows-7 windows user-accounts
add a comment |
I currently have an administrator account and a regular user account I created through the adminsitrator account.
I'd like to give make it possible for my other user account to install software in its account in such a way that my administrator account is not littered up with that software that's being installed.
How to do it? I am using Win 7.
windows-7 windows user-accounts
add a comment |
I currently have an administrator account and a regular user account I created through the adminsitrator account.
I'd like to give make it possible for my other user account to install software in its account in such a way that my administrator account is not littered up with that software that's being installed.
How to do it? I am using Win 7.
windows-7 windows user-accounts
I currently have an administrator account and a regular user account I created through the adminsitrator account.
I'd like to give make it possible for my other user account to install software in its account in such a way that my administrator account is not littered up with that software that's being installed.
How to do it? I am using Win 7.
windows-7 windows user-accounts
windows-7 windows user-accounts
asked Feb 20 '11 at 2:32
devoured elysiumdevoured elysium
54251227
54251227
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
If the installer is an MSI installer and it was written to allow per-user installation, then it should "just work". When your non-admin user runs the installer, it will install in its per-user mode. If your admin account ran the installer, it would usually have a choice to install for everyone or just that user.
The trouble is not all installers are MSI's. And not all MSI's are written to allow per-user installation. Depending on the software, it may not even be possible to do a per-user install regardless of the type of installer.
So ultimately, the set of apps this will work with is pretty small. Most developers assume the user will have administrative privileges on the machine at install time and that they will want all users on the machine to have access.
I thought regular user (non-admin) accounts couldn't install any software, even for themselves only.
– martineau
Feb 20 '11 at 8:01
They can by default on a non-domain joined machine as long as the installer doesn't want to write anywhere they don't normally have write access to. There are additional ways installers can be locked down with Group Policy in a domain environment.
– Ryan Bolger
Feb 20 '11 at 17:17
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f247990%2fallow-user-account-to-install-software-in-win7-without-installing-it-in-other-ac%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
If the installer is an MSI installer and it was written to allow per-user installation, then it should "just work". When your non-admin user runs the installer, it will install in its per-user mode. If your admin account ran the installer, it would usually have a choice to install for everyone or just that user.
The trouble is not all installers are MSI's. And not all MSI's are written to allow per-user installation. Depending on the software, it may not even be possible to do a per-user install regardless of the type of installer.
So ultimately, the set of apps this will work with is pretty small. Most developers assume the user will have administrative privileges on the machine at install time and that they will want all users on the machine to have access.
I thought regular user (non-admin) accounts couldn't install any software, even for themselves only.
– martineau
Feb 20 '11 at 8:01
They can by default on a non-domain joined machine as long as the installer doesn't want to write anywhere they don't normally have write access to. There are additional ways installers can be locked down with Group Policy in a domain environment.
– Ryan Bolger
Feb 20 '11 at 17:17
add a comment |
If the installer is an MSI installer and it was written to allow per-user installation, then it should "just work". When your non-admin user runs the installer, it will install in its per-user mode. If your admin account ran the installer, it would usually have a choice to install for everyone or just that user.
The trouble is not all installers are MSI's. And not all MSI's are written to allow per-user installation. Depending on the software, it may not even be possible to do a per-user install regardless of the type of installer.
So ultimately, the set of apps this will work with is pretty small. Most developers assume the user will have administrative privileges on the machine at install time and that they will want all users on the machine to have access.
I thought regular user (non-admin) accounts couldn't install any software, even for themselves only.
– martineau
Feb 20 '11 at 8:01
They can by default on a non-domain joined machine as long as the installer doesn't want to write anywhere they don't normally have write access to. There are additional ways installers can be locked down with Group Policy in a domain environment.
– Ryan Bolger
Feb 20 '11 at 17:17
add a comment |
If the installer is an MSI installer and it was written to allow per-user installation, then it should "just work". When your non-admin user runs the installer, it will install in its per-user mode. If your admin account ran the installer, it would usually have a choice to install for everyone or just that user.
The trouble is not all installers are MSI's. And not all MSI's are written to allow per-user installation. Depending on the software, it may not even be possible to do a per-user install regardless of the type of installer.
So ultimately, the set of apps this will work with is pretty small. Most developers assume the user will have administrative privileges on the machine at install time and that they will want all users on the machine to have access.
If the installer is an MSI installer and it was written to allow per-user installation, then it should "just work". When your non-admin user runs the installer, it will install in its per-user mode. If your admin account ran the installer, it would usually have a choice to install for everyone or just that user.
The trouble is not all installers are MSI's. And not all MSI's are written to allow per-user installation. Depending on the software, it may not even be possible to do a per-user install regardless of the type of installer.
So ultimately, the set of apps this will work with is pretty small. Most developers assume the user will have administrative privileges on the machine at install time and that they will want all users on the machine to have access.
answered Feb 20 '11 at 6:12
Ryan BolgerRyan Bolger
3,1811518
3,1811518
I thought regular user (non-admin) accounts couldn't install any software, even for themselves only.
– martineau
Feb 20 '11 at 8:01
They can by default on a non-domain joined machine as long as the installer doesn't want to write anywhere they don't normally have write access to. There are additional ways installers can be locked down with Group Policy in a domain environment.
– Ryan Bolger
Feb 20 '11 at 17:17
add a comment |
I thought regular user (non-admin) accounts couldn't install any software, even for themselves only.
– martineau
Feb 20 '11 at 8:01
They can by default on a non-domain joined machine as long as the installer doesn't want to write anywhere they don't normally have write access to. There are additional ways installers can be locked down with Group Policy in a domain environment.
– Ryan Bolger
Feb 20 '11 at 17:17
I thought regular user (non-admin) accounts couldn't install any software, even for themselves only.
– martineau
Feb 20 '11 at 8:01
I thought regular user (non-admin) accounts couldn't install any software, even for themselves only.
– martineau
Feb 20 '11 at 8:01
They can by default on a non-domain joined machine as long as the installer doesn't want to write anywhere they don't normally have write access to. There are additional ways installers can be locked down with Group Policy in a domain environment.
– Ryan Bolger
Feb 20 '11 at 17:17
They can by default on a non-domain joined machine as long as the installer doesn't want to write anywhere they don't normally have write access to. There are additional ways installers can be locked down with Group Policy in a domain environment.
– Ryan Bolger
Feb 20 '11 at 17:17
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f247990%2fallow-user-account-to-install-software-in-win7-without-installing-it-in-other-ac%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown