My first post will describe a solution that can help service providers to use Citrix CloudPortal Service Manager (CPSM) together with Citrix App studio to manage the visibility and use of applications installed within Desktop released.
for those of you who have worked with Citrix App Studio and integration with CloudPortal Manager service before probably know that the current integration of these great products has a limitation that they can "only" allow automation and the creation of jobs published or published applications. What if your map as a service provider is to offer only Windows Desktop as a Service and any use of the application and it will run in the published desktop? How do you manage the access and visibility or even billing for applications installed inside the office? There are many excellent third-party tools like AppSense that can do this or another option is to use the basic functionality of Citrix App Studio and CPSM a little more creatively ...
If you need to know more about how to configure Citrix App studio I encourage to have a look at a great fast deployment guide written by Thomas Hammond describes how to make a basic configuration of Citrix App studio (/ blogs / -quick-deployment Guide citrix-app-studio-2012/03/29 / /).
the integration between service Manager and Citrix CloudPortal App studio is done through the installation of new services (hosted applications and Desktop) in service Manager CloudPortal. There is a good Citrix TV video that shows how to achieve integration (http://www.citrix.com/tv/#videos/5401).
When using hosted applications and services CloudPortal Service Manager Office in the provision of advertising created Citrix App studio for the first customer, a domain local group for the ad is created under CortexSystem / services / OR HostedAppsandDesktops active in the Directory field. CPSM default uses a group of naming HostedAppsandDesktops UserPlanName during the creation of these groups. CPSM uses this group to control which client the availability of the announcement. When a customer subscribes to advertising available with CPSM, a comprehensive new customer specific domain group is created and added to be a member of the local group of the domain availability check of the announcement. The default naming convention CPSM is used for this group is HostedAppsandDesktops CustomerShortCode UserPlanName . So basically the idea is that we will use the system CPSM large domain local group that controls the availability of advertising to manage access to applications within the published desktop. Theintegration between CPA and App Studio (hosted applications and desktop services) will handle the tenant of the creative process in App Studio, and the creation of the subscription filtered tenant with global domain specific customer group established by CPSM and add the newly created subscription to advertising in App studio. And yes, we'll let App Studio to leverage it built in automated workflows to take care of the creation of published applications to XenApp farm based on the configurations made in App Studio, although we will not use published applications in this case.
So let say a new application called SAP will be installed at dedicated customer session host XenApp. After the process of installing Citrix App Studio is used to automatically fill the newly installed SAP application and create an advertising it. After the creation of advertising, a new user plan must be created in CPSM (in our case, the name will just SAP) and user plane will be mapped to the newly created advertising. When the new advertising CPSM is on and planned for the first customer, the broad domain local group of the CPA system is created under CortexSystem / OR HostedAppsandDesktops services in addition to the domain global group of specified client. At this stage, we will use the local group created domain (in this case HostedAppsandDesktops SAP) for reading and permission to run NTFS rights shortcut to SAP and application executables boot menu XenApp host application session and remove these default user group rights. When users are provisioned with the user CPSM plan, the tenant will be created in App Studio, subscription to this tenant will be created and thus the creation of published applications in XenApp farm is automated by App Studio workflows. This is nothing new right? The user will be provisioned member of the global group of related customer field (in this case HostedAppsandDesktops SAP CCS) is a member of the largest domain local group of CPSM system that controls the availability of the ad and this right with the NTFS rights required. This is just the interweaving of the core group, right? At the end user will get the required group memberships and rights that enable the visibility and use of the application within the office. As our service provider does not offer or even show applications published to the user when logging in via the web interface or Cloud Gateway, published applications created by App Studio can be disabled and hidden to users. Instead of doing according to the published application in AppCenter, we can use App Studio to edit these properties in the overall ad created for each published application. Whenever a new customer administration provisions, a user plane corresponding to advertise to users in CPSM, App Studio automatically creates the necessary applications published and he will inherit advertising settings so that new applications published will be created with properties to be hidden and disabled.
If the service provider for any reason will offer opportunity to access the published application in the future, it is only necessary to change the properties of existiting publisheed applications or settings advertising to get there .
and here you have a solution for managing access to applications within a published desktop to the use of built-in Citrix CloudPortal Services Manager and Citrix App Studio.
0 Komentar