ThinApp packages are able to support multiple operating systems with one single package. So the general rule is to make sure your environment allows ThinApp to capture all required dependencies of the application. ThinApp will recognize this, investigate which files are related to a component, and mark them as needed to be included in the package. When an installer discovers components already installed, it can register itself to the same components. Snapshotting can be made a little more independent of the capture environment.
The other method, monitoring the installer, will be more independent of the capturing environment but will not support all the installer formats and will not support manual tweaking during capture. This means your package would require Java installed or it will fail to run. Since it was already there when you ran the pre-install snapshot, it will not be a part of the captured differences. If your machine already contains the Java Runtime Environment ( JRE ) and the application you are capturing requires Java, then you will not be able to capture the JRE. But, your starting point will decide the outcome. You can copy files and create registry keys manually and it will all be captured. The alternative would be to try to hook into the installer itself. Many packaging products use snapshotting as a method of capturing changes. This should be all the information you need in order to run the application. The differences between the two snapshots represent the changes made by the installer. After modifying the environment, you create another snapshot, the Post-Installation Snapshot. This means you create a snapshot ( Pre-Installation Snapshot) of the current state of the machine. ThinApp uses a method of snapshotting when capturing an application installation. The environment you use to capture an installation is of great importance. You cannot write a book about a packaging format without discussing the environment used to create the packages. In turn, users can then access a VDI desktop from the relevant icon in Workspace ONE.(For more resources related to this topic, see here.) The capture and build environment By managing the device using VMware Workspace ONE Unified Endpoint Management and establishing Compliance checking, we can define an Access policy that allows access only to users with valid credentials who are using compliant devices to the Workspace ONE catalogue.
By integrating the full VMware Workspace ONE with Horizon, we can fully manage security between a user, a managed endpoint and access to Virtual Desktops.Here are a few ideas of what we could achieve: Subscription licensed The Art of the Possibleįor the purposes of looking at what is possible, let us assume that an Alien Space Bat has deemed it fit to leave an unlimited budget for us to acquire all these tools. VMware Horizon 8 editions can be compared at: To get the full Workspace ONE suite requires purchase of Workspace ONE as a specific product. In the case of Workspace ONE, VMware Horizon Advanced and above includes just Workspace ONE Identity Manager Standard. Some parts are included in the various VMware Horizon editions, while some, notably VMware vSAN and VMware NSX are additional licenses. What parts are available is largely defined by what is purchased. Access provides the user authentication layer into the solution as a whole, while also providing a unified catalogue of applications and services, whether published via VMware Horizon or through single-sign-on to cloud services.Unified Endpoint Management can provide control, configuration and administration to endpoints, be they mobile devices or traditional desktops.VMware Workspace ONE comprises two key elements: These are somewhat integrated topics these days as they do overlap. We then move out into two topics – The Endpoint and The User. With the move from VMware Horizon 7 to 8, the old Linked Clones method of delivering desktops has been retired, so no more Horizon View Composer. For secure access from untrusted or external networks, we deploy Unified Access Gateway appliances to serve as a proxy into the solution. This includes the provisioning of Instant Clone desktop pools (and Remote Desktop Session Hosts). The connection servers provide the brains, managing entitlements and provisioning of desktop and application pools. Secondly, we could deploy VMware NSX to provide enhanced security in the form of micro-segmentation of the network as well as anti-malware protection using Guest Introspection.įor publishing desktops, we have VMware Horizon View. Firstly, we can leverage local storage by implementing VMware vSAN rather than relying on a SAN/NAS based solution. However, we can enhance this further in two ways. For Virtual Desktop delivery, we have the underlying infrastructure of VMware vSphere with vCenter and ESXi.