Application Data
I have an application that I deploy (miktex). Now I have a need to deploy a folder to All Users\application data. Any package that I make will not create directories into all users\application data. Can someone fill me in as to why?
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
Coriolus
16 years ago
Posted by:
pisanom
16 years ago
Posted by:
Coriolus
16 years ago
Do you test your packages prior to deployment? If not, do so from this day forward.
When you send your package do you specify ALLUSERS=1? That could solve your problem.
Test the 'ALLUSERS=1' option on a test machine and see if that solves it, if it does, remotely uninstall the application from the machines and then reinstall it. If it doesn't maybe a registry hack or something may be what you need.
TEST! TEST! TEST! :)
When you send your package do you specify ALLUSERS=1? That could solve your problem.
Test the 'ALLUSERS=1' option on a test machine and see if that solves it, if it does, remotely uninstall the application from the machines and then reinstall it. If it doesn't maybe a registry hack or something may be what you need.
TEST! TEST! TEST! :)
Posted by:
aogilmor
16 years ago
Posted by:
anonymous_9363
16 years ago
The ALLUSERS property is irrelevant here.You are almost certainly falling over the (well-known to experienced packagers) "feature" in WPS where it completely ignores the All Users profile location. Heaven only knows when they'll fix this nonsense.I reported it in 5.6 and we're at 7.1 so I for one am not holding my breath.
If you have an InstallShield MSI handy, you can rip the relevant Custom Actions straight out and patse them into your project. Make sure you add them to the UI and EI sequences, to ensure that silent installs (which don't run the UI) install correctly. The CAs you're interested in look like this:
If VersionNT then
Set Property USERPROFILE to [%USERPROFILE]\
End
If VersionNT =400 then
Set Property ALLUSERSPROFILE to [%SystemRoot]\Profiles\All Users\
End
If VersionNT >= 500 then
Set Property ALLUSERSPROFILE to [%ALLUSERSPROFILE]\
End
Of course, if you don't have a handy MSI, you can use the above as a clue as to what you need to do. As I say, just make sure you add these to both sequences.
Lastly, add them to your Windows Application template because this *will* bite you again. It's one of the first things I do when I go to a new client.
If you have an InstallShield MSI handy, you can rip the relevant Custom Actions straight out and patse them into your project. Make sure you add them to the UI and EI sequences, to ensure that silent installs (which don't run the UI) install correctly. The CAs you're interested in look like this:
If VersionNT then
Set Property USERPROFILE to [%USERPROFILE]\
End
If VersionNT =400 then
Set Property ALLUSERSPROFILE to [%SystemRoot]\Profiles\All Users\
End
If VersionNT >= 500 then
Set Property ALLUSERSPROFILE to [%ALLUSERSPROFILE]\
End
Of course, if you don't have a handy MSI, you can use the above as a clue as to what you need to do. As I say, just make sure you add these to both sequences.
Lastly, add them to your Windows Application template because this *will* bite you again. It's one of the first things I do when I go to a new client.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.