B
Brad
We are deploying a java web start application that has been programmed
and delivered to us by an outside vendor onto several machines that
are shared by different users.
All of the users log onto our network and authenticate to a windows
domain.
We would like all of the icons and java items to be deployed into the
All Users profile so that other people that use these PCs don't have
to keep reinstalling the applications and the icons.
We have changed some of the jnlp files and the temporary files section
of the javaws preferences to point to the all users profile section
and have told javaws not to create icons and generally have
accomplished our goal, BUT...
When a new jar file is deployed, (which happens automatically at app
launch to keep weveryone in sync with the correct versions), javaws
deletes the all users icon and creates a new one on the users personal
desktop.
When the next user logs in, they will not see any icons.
Are we missing something? We have tried this with several versions of
javaws including the most current and all seem to behave identically.
....or is there something the app vendor must specify to make this
work?
Thanks,
Brad
and delivered to us by an outside vendor onto several machines that
are shared by different users.
All of the users log onto our network and authenticate to a windows
domain.
We would like all of the icons and java items to be deployed into the
All Users profile so that other people that use these PCs don't have
to keep reinstalling the applications and the icons.
We have changed some of the jnlp files and the temporary files section
of the javaws preferences to point to the all users profile section
and have told javaws not to create icons and generally have
accomplished our goal, BUT...
When a new jar file is deployed, (which happens automatically at app
launch to keep weveryone in sync with the correct versions), javaws
deletes the all users icon and creates a new one on the users personal
desktop.
When the next user logs in, they will not see any icons.
Are we missing something? We have tried this with several versions of
javaws including the most current and all seem to behave identically.
....or is there something the app vendor must specify to make this
work?
Thanks,
Brad