We started in 2016 with the introduction of our new AppDisk technology that allows administrators to package and manage applications, regardless of its master OS image, thereby alleviating the complexity of managing multiple, departmental-based images.
AppDisk makes it easy to update or applications to install, without affecting the golden desktop or server image.
AppDisks-one application layering solution was included in XenApp / XenDesktop 7.8, the end of February 2016. was published at this time, I sketched the basics of layering application or image-management as a whole in a blog post. now my goal is to cover the administration of the split application with Citrix AppDisks. Ready? Let's dig right in!
Creating a AppDisk
There are several approaches to create a AppDisk. The first method is to manually create at the level hypervisor and then import it within Studio. The second approach is to create and assign the AppDisk directly from the studio. You can read more about both approaches here
To a AppDisk from Studio create .:
Click the AppDisks node in Studio, then select "Create AppDisk" from the Actions menu.
On the next screen, select the size of the hard drive. There are predefined options of 3, 20 or 100 GB or you could choose a custom size. This is also where you could also import an existing AppDisk that you created manually. Note that on a 3GB AppDisk, a good deal of space has been used up, and you would probably get less than 1GB for all new applications you are looking to install in this layer.
Next, choose the machine catalog, use would be used for the VM to install applications in this AppDisk. Only the compatible options are made available.
For example in the figure below, the only two options available to NonPersistentVDI catalog available and the Win 7 Pool. Reasons are provided why the other machine catalogs are not provided. It is also worth mentioning that AppDisks only random pool catalogs are assigned. The machine catalog should work at least an available VM for AppDisk creation.
Next, give a name AppDisk and AppDisk build begins. In my lab, I have seen anywhere from 10 minutes for a 3 GB hard drive and less than 20 minutes for a 20GB AppDisk (SATA storage). Creation of these plates on SSD storage was about 30% faster.
Once the AppDisk is created, you can install the necessary applications.
Installing applications within a AppDisk
in the studio, click on the newly created AppDisk. It should say "Ready to Install Applications". Under the section details for AppDisk is preparing machine provided information. Within the hypervisor management console, log on to the preparation machine, and install the necessary applications.
Once you have the application installed in the studio, select the AppDisk and under Action, select "Seal AppDisk." Thereby, the sealing process, and once this is complete, you can AppDNA compatibility analysis for this AppDisk.
note that AppDisk Layering can not be used for applications that have file system drivers and services. AppDisk contains no application isolation. App-V or Turbo.net provides this functionality.
configuration AppDNA and AppDisk for compatibility issues analyze
is the main differentiator between AppDisk and other layering technologies, is integration with AppDNA for compatibility analysis delivery group. For example, if we create a AppDisk we test compatibility against multiple XenApp image or a pooled Windows 10 delivery group as examples. This gives the administrator the security that comes with this AppDisk delivery group to work without going through extensive regression testing.
If you have assigned several AppDisks to a delivery group, the AppDNA compatibility analysis ensures that all AppDisks play well together and assigns the AppDisk assignment on the analysis as needed based. AppDNA integration is a XenApp / XenDesktop Platinum-only function.
Before you can perform a compatibility analysis, AppDNA must be configured within Studio. Click the AppDNA section under Configuration and enter the AppDNA connection settings. Make sure that the connection test passes.
Coming back to where we were in the AppDisk creation, we had the sealing process only just begun. Once this process is complete, the compatibility analysis AppDNA occur are automatically configured when AppDNA connection settings in. The compatibility analysis will be carried out against the Catalogue that the preparation machine belongs.
If you assign a AppDisk to a delivery group is, the compatibility analysis carried out automatically against this delivery group. If multiple AppDisks are assigned, then the AppDisks be as needed based on the analysis rearranged. There is an option the AppDisks to "Auto Order" when you are assigned a AppDisk to a delivery group.
to see the report, click "View Report" next to the AppDisk, you just sealed.
You can view the reports also, from the AppDNA Console under the Reports section. Here you have different views, including problems with the application, application actions, Issue View and Action View.
Assigning a AppDisk to a delivery group / Groups
to assign an application to a delivery group, click Delivery groups within Studio, select the delivery group you want to assign AppDisk. Under the Actions pane, select "Manage AppDisks".
The next screen shows you the currently assigned AppDisks and gives you the ability AppDisks add. Once you assign your AppDisk, select order car.
You can then select the roll-out strategy. , you can either restart all machines within that delivery group immediately or you can assign the AppDisk the next restart of the machine. You can then check the configuration and then click Finish. This triggers an analysis AppDNA compatibility if you XenApp or XenDesktop Platinum feature and configure your server within AppDNA Studio authorization.
You can AppDisk with an operating system for delivery groups running other operating systems as well as long as the created assign application is compatible with the target operating system. In my lab, I tested two AppDisks a Win2k12 preparation allocates VM to a Win 7 random pool.
assign a AppDisk to a delivery group that delivery group must use the same storage. To assign a AppDisk to a delivery group to different memory, you would create a new VM tied at the hypervisor level to the target storage, must create clone and associate AppDisk to the new VM and the re-import within Studio. I hope that this process will be simplified in the next versions of the product.
Updating a AppDisk
Currently, there is no management is built in version AppDisk. This means that every time you need to make an update, you are basically the existing AppDisk cloning so that changes to it and then the new AppDisk to the delivery groups reassignment. It is also worth noting that you can not change a AppDisk size when a new version to create.
To a AppDisk Update, click the AppDisk nodes within Studio, highlight the AppDisk you want to update, and select "Create New Version" from the Actions pane.
on the next screen, select the pooled random machine catalog that you want to use VM for preparation. Again, a VM must be available within this machine catalog to perform the update.
then to designate the AppDisk with version information and "Create New Version" button. This is reflected from the AppDisk creation process as described above. be performed AppDNA compatibility analysis against preparing VM machine catalog, as soon as the new version of AppDisk is created.
Once the new version is ready, you can assign the AppDisk on the required delivery groups and raise the allocation of the old version. This will kick off again the compatibility analysis AppDNA.
Resize a AppDisk
There are no options to change a AppDisk from Studio today. You would need at the hypervisor level, and then import the size and again and reassign the AppDisk. Some hope that we encounter in the near future.
Deleting a AppDisk
to delete a AppDisk in Studio, click AppDisks, highlight the AppDisk you want to delete and select "Delete AppDisk" the action area.
Final Thoughts
As I described in my previous blog post on image management, image management AppDisk us one step further in simplifying leads. However App Layering is no one-size-fits-all solution and should in conjunction with other solutions such as application isolation, and the like.
I am very impressed with AppDisks be used as a v1 product. The performance was very good considering that I performed most of my tests in my lab using SATA storage.
Follow @gkuruvilla
0 Komentar