As part of our commitment to continuous innovation Agile, we expand and improve the experience of publishing applications and desktops in each quarterly release of XenApp and XenDesktop. As I mentioned in my previous blog post, that the guiding principles we follow are:
- Application Publishing concretes while maintaining desktop publishing essentially as today [1945004ist] Simplify by new functions to the right place
- to reduce the amount of unnecessary change Minimize
What are application groups?
application groups are a new concept, which we introduced in the 7.9 version of XenApp and XenDesktop.
 | An Application group consists of three things:
|
application groups can be used to categorize applications in collections and some settings allow for all applications in an administered group. You may have noticed that there are now three places where you can define users: applications, delivery groups and application groups. We recommend that users are defined on only one level and a general Active Directory Users group is used elsewhere. If you use to start the application groups, it makes sense to use it for all applications.
application groups can be linked to one or more delivery groups. This means that an application in an application group changing contain or setting on the application group itself, affect all of the delivery groups. The user list on an application group provides a further restriction on the users that are defined on each of the linked delivery groups.
When an application group links to several groups Delivery as app Group 2 in the above figure can be a priority 0, 1, ... defined on the link for each delivery group, with 0 being the highest priority. Delivery Group priority for an application group can be used:
- Prioritize access to delivery groups by machines criteria (eg performance or age)
- load balancing applications between machines in delivery groups
priority controls the order in which the machinery should be evaluated for the delivery of an application in the group in each delivery group. Delivery groups with the same priority for an application group are load balancing.
Note that applications may also be intended for applications several delivery groups and delivery group priorities are added.
When would I use application groups?
The first thing to notice about application groups, that they are completely optional. Microscale implementations will work well without application groups, but what you should scale your deployment to a greater number of applications and delivery groups check if the application sets launch would simplify management of your deployment.
let the search in a specific application, for application groups.
consider an application set of Microsoft Office. Before, would upgrade all users to the latest version of Office, like its release and collect feedback from beta testers to stage. This could be achieved by the creation of "beta user" and "Prod users' Active Directory user groups are reached, said beta user is a subset of Prod user, and then with Citrix Studio Office applications for both user groups as in the picture posting below.
users who are not beta testers always consumed Office applications from any of the production machines. If a beta tester connects to an Office application, the use of beta-machine will be started if there is one, otherwise it will be launched from a production machine. So are the beta testers should avoid downtime. The beta-delivery group, once the applications have moved into the production office will be disabled.
This model can easily be extended with more application groups to support the development, testing, acceptance and production lifecycle.
New Application Group Workflows
In this blog post we are going to see the application set workflows from the perspective of Citrix Studio. As with all types of objects in the FMA architecture (7.x), includes all functions to application groups, is also from the PowerShell SDK.
from the node applications in Citrix Studio, select the application Create Group Wizard to create an application group. You can create an application group to provide either before or after delivery groups.
After creating an application group, are the details of the node applications. The Group Details tab shows all application and delivery groups that contain the selected application. It also shows the relationship between the application, delivery groups and machines, such as the top of the entity-relationship diagram.
counts the delivery groups and machines are hyperlinks. Clicking on a hyperlink takes you to the Delivery Group Delivery Group at the delivery nodes groups and click on a machine number hyperlink will take you to the list of machines on the Web node.
Select an application group and click Edit Application Group can be found on the page take down. From here you can edit the user, delivery groups and settings for the application group.
The delivery groups page to manage the delivery groups, the link for the application group and its priorities. On the Settings page, you can disable sharing sessions with other application groups that are linked to the same delivery group.
Summary
- application groups are optional.
- application groups can be used to categorize applications in collections.
- users and settings are specific to an application group to all applications in the group.
- Use as application groups, we recommend that you use for all applications and define only the user's application set.
- application set priorities can be used to several delivery groups and delivery group, to link failover and load balancing for control.
further information, refer to the product documentation about application groups.
If you have any questions about application groups, to ask in the comments below, feel free.
0 Komentar