ActiveSync 4.5.5096 - AdminStudio 7.5
HI All,
I am packaging the above application and am hitting an issue with it repairing for a user the first time it logs in. The application comes as an msi and after doing an admin install to extract the files I apply a response transform and add just client specific properties. I have tried adding "AND (NOT REINSTALL)" as suggested in a post here on Appdeploy however this has not stopped the problem. Has anyone else had/overcame this issue?
I install as an admin, reboot, log in as a user and start up for first time and it repairs. This is an issue because it is being delivered via CA UniCenter which creates a virtual drive, installs and then deletes the drive => no path back to the source.
Thanks in advance..
I am packaging the above application and am hitting an issue with it repairing for a user the first time it logs in. The application comes as an msi and after doing an admin install to extract the files I apply a response transform and add just client specific properties. I have tried adding "AND (NOT REINSTALL)" as suggested in a post here on Appdeploy however this has not stopped the problem. Has anyone else had/overcame this issue?
I install as an admin, reboot, log in as a user and start up for first time and it repairs. This is an issue because it is being delivered via CA UniCenter which creates a virtual drive, installs and then deletes the drive => no path back to the source.
Thanks in advance..
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
Tone
17 years ago
Is the source available if you use SOURCELIST property?
SOURCELIST=\\Server1\Share\Package;\\Server2\Share\Package
SOURCELIST=\\Server1\Share\Package;\\Server2\Share\Package
Posted by:
oreillyr
17 years ago
Unfortunately not! The drive is deleted after installation and as such the path back to the source is not available.
Posted by:
Tone
17 years ago
sorry was a bit unclear, is it possible to copy source to secondary location where it can be accessed..
Posted by:
oreillyr
17 years ago
We could copy the package locally and install from there however I would prefer to avoid this option.
There are no user files in the application so it should not need to revert to source during a repair. I think there is something in the application forcing a reinstall when a new user logs in or something to that effect.
There are no user files in the application so it should not need to revert to source during a repair. I think there is something in the application forcing a reinstall when a new user logs in or something to that effect.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.