If users stop using firefox.1, started using firefox.2, firefox.1 can be removed. If you want to revert to previous version – make package firefox.3, which is assembled from a previous version of the application. If you need another update – make a package called firefox.2 etc.ħ. All users connect to the old firefox, but the new treatment to firefox.exe – redirected to a file firefox.1 – and users use the updated application.Ħ. You create a new package with the help of VMware ThinApp, call it firefox.1ĥ. Users begin to use it – the file is locked firefox.exe.Ĥ.
Create desktop users a shortcut pointing to \ \ \ \ Firefox.exe.ģ. You pack application firefox.exe using VMware ThinApp and put it on the SMB Share.Ģ. 1 – and all new connections will use it!ġ. In fact, there is an interesting mechanism: you can put in a folder with the application of its updated version, but with the extension is not *.
However, when we annex VMware ThinApp runs constantly, and many users use it – then how do we update it (eg a web browser, packed in a file firefox.exe)? In this case, unlike the first method of deployment of virtualized applications (on the local drives of workstations), this method can deliver the application on the workstation in blocks – as demand application of the data. Remember this product Thinstall, through which made pre-installed applications? So ThinApp – this is it is only now under the name VMware.īut there is another way to deliver applications with VMware ThinApp – an opportunity to launch their users with a shared network folder (SMB Share): It is very convenient for mass deployment and maintenance applications. That is, the application is packaged into a single exe-file and deployed on user workstations using msi-installer (see here how it’s done with the VMware View 4.5).
As you know, by means of VMware ThinApp, which is part of the solution for desktop virtualization VMware View 4.5, you can make the delivery of virtualized applications to users.
0 kommentar(er)
