Several more per user/machine questions
Still trying to educate myself a bit more on this.
I'm reading about per user and per machine installations. I should first specify that all apps will be assigned, so the user will never initiate the install on their own. The majority of the GPO's created for the previously packaged apps are per user, with a few per machines here and there. The group that did this packaging and assigning was in and out before my time so I'm trying to piece it togather.
I understand availablity of apps depending on whether they are assigned per user or per machine, and the install permissions that go with each, but I still have these questions:
- What takes place when I have a package that drops reg keys into HKCU, yet the packaged is assigned per machine? Are they ignored or moved to HKLM?
- What are the possible problems I could experience when I change a package from being assigned per user to per machine? (Clarification: Assume I'm creating a new GPO for the per machine assignment, and moving users over. Yes, they will uninstall and reinstall, but asside from that, are there risks involved?)
- When the Installelevated policy is set for both HKLM and HKCU, does that mean assigned packages will install with elevated privledges when assign both per machine and per user?
Thanks for accomodating a GPO newbie.
I'm reading about per user and per machine installations. I should first specify that all apps will be assigned, so the user will never initiate the install on their own. The majority of the GPO's created for the previously packaged apps are per user, with a few per machines here and there. The group that did this packaging and assigning was in and out before my time so I'm trying to piece it togather.
I understand availablity of apps depending on whether they are assigned per user or per machine, and the install permissions that go with each, but I still have these questions:
- What takes place when I have a package that drops reg keys into HKCU, yet the packaged is assigned per machine? Are they ignored or moved to HKLM?
- What are the possible problems I could experience when I change a package from being assigned per user to per machine? (Clarification: Assume I'm creating a new GPO for the per machine assignment, and moving users over. Yes, they will uninstall and reinstall, but asside from that, are there risks involved?)
- When the Installelevated policy is set for both HKLM and HKCU, does that mean assigned packages will install with elevated privledges when assign both per machine and per user?
Thanks for accomodating a GPO newbie.
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
clewster
19 years ago
What takes place when I have a package that drops reg keys into HKCU, yet the packaged is assigned per machine? Are they ignored or moved to HKLM?
no they are put in the users profile aswell. i believe they go into the dafault profile aswell so all users will have the settings
- What are the possible problems I could experience when I change a package from being assigned per user to per machine? (Clarification: Assume I'm creating a new GPO for the per machine assignment, and moving users over. Yes, they will uninstall and reinstall, but asside from that, are there risks involved?)
we have just done this at work. its painfull but well worth it. just makesure you keep the user install policy so you can uninstall because user policies always overide machine installs, this can mess things up in the user profile. theres not really much risk as long as you ensure the user install is removed when you move it over to a machine install.
- When the Installelevated policy is set for both HKLM and HKCU, does that mean assigned packages will install with elevated privledges when assign both per machine and per user?
I though all assigned software installed with elevated privledges. but please dont hold me to that
Posted by:
Sweede
19 years ago
Hi Blade
no USER registry settings should not be in package for adding as computer package they will only apply if MSI installer self repare mostly
it is no problem to dele them.
IF you ned usersettings put them in separate MSI and add as userpackage install at logon
Computerpackages applies for group off computer names
User package applies for group off usernames
About moving from USER to COMPUTER You are not just moving users over to Computer packages
Test a few users by giving them a deny on the user package to get it uninstalled
and then add the computer name to your new GPO.
some programs could be difficult to remove
If you dont know how to make a deny on one single user just say so and I will show you
Sweede ;-)
no USER registry settings should not be in package for adding as computer package they will only apply if MSI installer self repare mostly
it is no problem to dele them.
IF you ned usersettings put them in separate MSI and add as userpackage install at logon
Computerpackages applies for group off computer names
User package applies for group off usernames
About moving from USER to COMPUTER You are not just moving users over to Computer packages
Test a few users by giving them a deny on the user package to get it uninstalled
and then add the computer name to your new GPO.
some programs could be difficult to remove
If you dont know how to make a deny on one single user just say so and I will show you
Sweede ;-)
Posted by:
clewster
19 years ago
I seem to be following you round sweede.
From my understanding and what we have deployed all user settings will still get configured when you deploy to machine level when the user first opens the program. A bit like publishing to the user except it only installs the user settings when they open the program.
With the experience I have had with user level installs of any kind I would recommend that you don’t use em at all!!! They cause nothing but problems and I think you will find a lot of people who will agree with me.
no USER registry settings should not be in package for adding as computer package they will only apply if MSI installer self repare mostly
From my understanding and what we have deployed all user settings will still get configured when you deploy to machine level when the user first opens the program. A bit like publishing to the user except it only installs the user settings when they open the program.
With the experience I have had with user level installs of any kind I would recommend that you don’t use em at all!!! They cause nothing but problems and I think you will find a lot of people who will agree with me.
Posted by:
Sweede
19 years ago
Hi Clewster
True I think but same result will happen without usersettings inside the MSI Computer package.
Missing user settings are self repaired on first logon mostly.
I use always Computer packages for all my installations and I always remove all user registry settings from the MSI.
Sweede :-)
True I think but same result will happen without usersettings inside the MSI Computer package.
Missing user settings are self repaired on first logon mostly.
I use always Computer packages for all my installations and I always remove all user registry settings from the MSI.
Sweede :-)
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
