Need help on our own deployed application

[ramachandrankes]

Hi Team,

Please let me know your thoughts on how to resolve one issue which I am facing.

Description:

1. I have my own software for our company and this has been published in the principle of ClickOnce deployment manifest. If user click on an icon then application will reach out the server and install automatically and then a respective shortcut will get created.

2. If user logged off the VDI and login again, then it is asking to install the application again if they click on the shortcut created on the step 1. This time again another shortcut created as a copy of the same application. This continues for each time logoff and login.

3. We cannot deploy this via App stack / pushing image from parent host as we have frequent release on the versions.

Kindly suggest one good idea to resolve the same. So that when I click on my icon first time, it will get install and from second time it should not install instead it should open application directly.

If you need more clarifications please let me know.

Thanks,
Ram

[RoderikdeBlock]

You could use writable volumes (AppVolumes).

Using Writable Volumes with Non-Persistent Virtual Desktops

On a non-persistent virtual desktop environment, all applications that the user installs are removed after the user logs out of the desktop. Writable Volumes store the applications and settings of users and make user-specific data persistent and portable across non-persistent virtual desktops. This way, you can address use cases, such as providing development and test machines for users to install custom applications on non-persistent virtual desktops. You must reboot the desktop after you remove a Writable Volume.

[ramachandrankes]

During the initial setup we have not created a writable volume source template whereas we created only app stack source template. It is difficult for us to create a writable volume source template.

Please let me know if any other recommendations from your end if possiible.

Thanks,

Ram

[jonathanjabez]

Hi Ram,

As you have raised this template upload issue in one another community discussion, per the discussion, you can safely upload both Appstack and Writable Volume templates to the respective datastore you have chosen for Appstack and Writable Volumes. These templates do not affect the production appstacks or writable volumes as they get uploaded to a different folder.

All production appstacks reside in [Datastore]\CloudVolumes\apps\ directoy and all production writable volume disks reside in [Datastore]\CloudVolume\writable directory. However, the templates get apploaded to [Datastore]\CloudVolume\writable_tempates directory (for creating new writable volume) and [Datastore]\CloudVolume\app_tempates (for creating new appstacks).

In the "Upload Prepackaged Volumes" select the datastore you have configured for Writable Volumes, select "Use vCenter"and under Volumes choose one or more checkmarks  to upload the templates.

template_profile_only_workstaion - For User Profile settings only

template_uia_only_workstaion - For User Installed Applications only

template_uia_plus_profile_workstaion - For retaining both User Profile settings and User Installed Applications

/Jon

[ramachandrankes]

OK thanks. Let me try to create the writable volumes template.

Regards,

Ram

[jonathanjabez]

If you found this or any other post helpful please consider the use of the Helpful/Correct buttons to award points. Thank you