Sometimes you need to change user settings when deploying packages and it would be nice to have a function for this. The dream scenario would be if the function could handle these things.
- Add HKCU registry keys for users.
- Copy custom files/scripts to a folder on the client and then run this from the users context.
- Run the above file/script for the current logged in user.
The first two things is possible with scripts and Active Setup but the last one is a bit more complex which I'm not sure how to solve. I have seen other Client Management systems handle this but I don't know if it's possible with scripting only. If it isn't possible then the two first things would be nice anyway.
Comments: In our wrappers we do run the Active Setup for the profile of the installer on the spot. We also know that's a bad idea if the Installer is System/SCCM because it just pollutes the profile for nothing. Actually we have create a few: * One to generate Version stamps based on date and time (needed for re-installs to re-trigger Active setups) * One to check the folder and create the ActiveSetup in the HKLM hive. * One to remove the Active-setup in the HKLM hive for uninstalls. As for the file copy, we have something for that already which makes it moot. We create custom ARP entries for each packages so that we get uninstall logs for everything. To do that we copy all the files needed to an UNINSTALL folder. In that UNINSTALL folder is where we store the files triggered by ActiveSetup. Like I said, we have a lot of work ahead: Rolling logs, Pre/Post inventory, sanity checks, custom ARP entries with parent-child support, etc. Most of it is overkill but it's what we have in the CMD wrappers so to get buy-in we need to re-create it all in PowerShell. And I'll release what I can as extensions to this project.
- Add HKCU registry keys for users.
- Copy custom files/scripts to a folder on the client and then run this from the users context.
- Run the above file/script for the current logged in user.
The first two things is possible with scripts and Active Setup but the last one is a bit more complex which I'm not sure how to solve. I have seen other Client Management systems handle this but I don't know if it's possible with scripting only. If it isn't possible then the two first things would be nice anyway.
Comments: In our wrappers we do run the Active Setup for the profile of the installer on the spot. We also know that's a bad idea if the Installer is System/SCCM because it just pollutes the profile for nothing. Actually we have create a few: * One to generate Version stamps based on date and time (needed for re-installs to re-trigger Active setups) * One to check the folder and create the ActiveSetup in the HKLM hive. * One to remove the Active-setup in the HKLM hive for uninstalls. As for the file copy, we have something for that already which makes it moot. We create custom ARP entries for each packages so that we get uninstall logs for everything. To do that we copy all the files needed to an UNINSTALL folder. In that UNINSTALL folder is where we store the files triggered by ActiveSetup. Like I said, we have a lot of work ahead: Rolling logs, Pre/Post inventory, sanity checks, custom ARP entries with parent-child support, etc. Most of it is overkill but it's what we have in the CMD wrappers so to get buy-in we need to re-create it all in PowerShell. And I'll release what I can as extensions to this project.