APPDATAFOLDER
Greetings,
I am trying to modify the MSI installation for AT&T Communications Manager. There are a few settings, like disabling the app from being the default WI-FI utility, configure VPN settings within the app, as well as disabling the auto-update. I have found these settings are stored in RC4 encypted files, in <current user>\Application Data\AT&T. My attempt has been to modify the original MSI, by creating a new feature and a new component containing the files and installing them to [APPDATAFOLDER]\AT&T\Com Manager\. This has successfully installed on a few different corporate images, but does not work on a few older Windows XP builds. Would anyone know what the APPDATAFOLDER variable looks for on the target machine to know who the current logged in user is?
As I mentioned, this works well for the majority of our workstation builds, but not all. It is the same exact packages working on some, but not all.
Any help would be much appreciated.
Cheers
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
nheim
16 years ago
Hi Vjt,
are you trying to install this to just the actual profile or to each user on a machine?
Did you log the failing install?
Regards, Nick
are you trying to install this to just the actual profile or to each user on a machine?
Did you log the failing install?
Regards, Nick
Posted by:
vjt914
16 years ago
[font="trebuchet ms"]I would at least like to be able to install to just the current logged in user, though it would be nice for all users. However, I can't use the all users app data variable, since the app is writing data to the all users\application data folder, but not the data that stores the app settings for each user.
[font="trebuchet ms"]
[font="trebuchet ms"]It actually will not produce an error, installs successfully, just doesn't add that folder. We have a similar problem with our distribution tool, Marimba, using the macro SYS.PROFILE which is supposed to do the same thing. The problem only exits on a few of our older builds, and I was just seeing if anyone knew if there was something I could configure on the target system to pickup the variable.
[font="trebuchet ms"]
[font="trebuchet ms"]Thanks for your help, Nick.
[font="trebuchet ms"]
[font="trebuchet ms"]It actually will not produce an error, installs successfully, just doesn't add that folder. We have a similar problem with our distribution tool, Marimba, using the macro SYS.PROFILE which is supposed to do the same thing. The problem only exits on a few of our older builds, and I was just seeing if anyone knew if there was something I could configure on the target system to pickup the variable.
[font="trebuchet ms"]
[font="trebuchet ms"]Thanks for your help, Nick.
Posted by:
nheim
16 years ago
Hi Vjt,
take the logfile and search for the folder in question. There are a lot of "smaller" errors, which are not terminating the installation.
Regards, Nick
take the logfile and search for the folder in question. There are a lot of "smaller" errors, which are not terminating the installation.
Regards, Nick
Posted by:
vjt914
16 years ago
I found that there seems to be two separate issues. The larger issue is that I am trying to install this app that requires administrative rights, with a system account via our distribution tool. It thinks the current user is system, since it is taking control of the install. I thought I was installed as a standard user when I was testing. I know the issue still exists with our distributuon tool, not picking up the variable which I was I automatically assumed the same issue here.
My apologies, I will have to figure out a workaround. Thanks for your help, Nick.
My apologies, I will have to figure out a workaround. Thanks for your help, Nick.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.