I'm packaging in an environment that is pushing applications via SMS 2003 and I'm trying to get a better grasp on how these packages are being installed. The packages are being pushed so that the user does NOT need to be logged in to the machine so all installs are running as local system. We may have instances where there are multiple users on one machine so I would like for any HKCU entries or any files that get copied to user profiles to get copied to all users who currently have profiles on the machine as well as any future users. I know that future users get their profiles from "Default User" so that's not really an issue, my concern is more for users who already have a profile on the machine....my question is whether it would be beneficial to write a custom action that enumerates all user profiles on the machine and copy user specific settings for all users at one time, or to use ActiveSetup so that it happens when the user logs in themselves.

Based on some advice of the SMS admin here, the current solution is to create an MSI that has the Local Machine settings and launch that via SMS as local system...then have a second setup that only has user specific settings and have that setup pushed via SMS as the logged on user. I really do not like the idea of having two setups for each application and I'm sure there is a better way to do this.....I will take any suggestions.
0 Comments   [ + ] Show comments


There are no answers at this time

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.