Introduction
The Citrix Connector 7.5 for System Center 2012 Configuration Manager, also known simply as Citrix known Connector, XenApp and XenDesktop 7 integrated with Configuration Manager 2012 (CM). The Connector simplifies the use of Configuration Manager deployment technology Citrix server and desktop image management to automate. The connector uses the new application / deployment type (App / DT) feature in Configuration Manager 2012 to orchestrate provisioning on the right images at the right time. Administrators can optionally use the app / DT model to the actual application publications.
Many of our customers are to provide still early in the migration to the app / DT model. They are the use nor its extensive library of packages and programs developed with great care over many years. These Citrix customers want to know how we use with these packages and programs all the goodness of the Connector. So if you are interested with the Citrix Connector packages and programs on the Citrix server and desktop provide, this post is for you.
In many cases, packages and programs with the Citrix Connector designed to provide a straight forward process is familiar to every CM administrator. However, there are two scenarios in which specific measures are necessary to prevent unintended consequences when deploy packages and programs with the Citrix Connector
Scenario 1 -. Providing image Managed (MCS or PVS) Citrix hosts
The first scenario, which require special attention to packages and programs for VMs created with Citrix XenDesktop Machine Creation Services (MCS) or Citrix Provisioning Services (PVS) sends. As an administrator, you want software on the master image of a machine catalog and rely on XenDesktop / XenApp deploy to clone VMs workers. VM clones waste compute, storage and network resources, since each clone to reject providing directly the changes when restarting.
Thus, the Citrix Connector is optimized only install applications on the master image of a machine catalog while completely skipping installation of the application on the cloning of the master image. The key factor that can selectively install our applications is a CM client policy that a 3 rd party such as the Citrix Connector jurisdiction if the application or updates to install brings.
Here is the problem. unstoppable CM client policy the installation packages, programs or task sequences; it applies only to the app / DT model and Windows updates. This means that the Citrix Connector can not prevent the installation of packages and programs on MCS or PVS clones, resulting in unnecessary resource utilization.
created solution
to create a device collection, only the update module contains and delivering packages and programs to this device collection instead of the collection device from Citrix Connector
Scenario 2 -. App Publishing of the CM Console
The second scenario game comes when the CM to publish console, the package / program as XenApp hosted application. The Citrix Connector uses CM application detection logic to ensure that the application is installed to Citrix Receiver before publication. This is a symbol appear in the receiver before all servers in a delivery group, the installed applications have to prevent.
Unfortunately implementations package / program have no reliable, continuous application detection logic. Consequently, these orchestration function of the Citrix Connector can not be supported if the Citrix Application Publishing Wizard to publish apps from the Configuration Manager console.
solution 1
use Citrix Studio to use, publish, instead of the Citrix Application Publishing Wizard in the CM console.
solution 2
If you want to use CM application catalog and that the Citrix version of the installed program hosted there to appear, you have a new application with a script deployment type and a Citrix deployment type create. The script DT provides the application of the detection logic of looking for the executable, while the Citrix DT created publishing application in XenDesktop.
solution Details
The rest of this post is divided into two sections and specific examples of how to implement the solutions discussed above. The first focuses on the image management and accurate implementation of the program in the update device for Citrix device collection targeting. The second section focuses hosted on the publication of the installed CM program as Citrix App.
solution for image management and resource utilization
As already mentioned, the Citrix Connector can not prevent the installation of packages and programs on pooled Citrix Session hosts created using Machine Creation Services (MCS) or provisioning service (PVS). To avoid this potential inefficiency, a new device collection needs to be created that contains only the update module. There are four steps to achieve this:
- create the new device collection
- are running the program on the new device collection
- for providing success Update on the monitor device and
- to update the pooled Citrix session host with the updated image.
are described in detail in the following these steps.
to see background information on the master image management with the Citrix Connector and the role of the update module, the master image management Video http://www.citrix.com/tv/#videos/ 11534 on CitrixTV.
Before starting, you use the machine catalog ensure properties that there is provided an update device, the Update method property value "Update Device" and the Update Device contains property value a hostname. This is a very important step. If an update device is managed not defined for a Citrix Imagers collection, the steps described below will have zero members in a new device collection result.
Step 1: the Configuration Manager console, use one device collection
- in the Assets and Compliance Section of the Configuration Manager console, click on the " create collecting device" to create action. toolbar band
- on the General page of the Create device collection Wizard
- give the collection a name on the parent collection (eg "XDsite1 MCS based Win7 desktop - MasterImage ")
- for limiting search collection, this is the parent collection created by the Citrix Connector that represents your XD Catalogue (eg XDsite1 MCS Win7 desktops)
- on the Membership rules page on the Add rule button and query rule from the drop-down menu
select 
- Name the query rule " IsMasterImage "
- then click the Edit query statement key
- in the general click the create "star" icon
- Select can Citrix_VirtualDesktopInfo attribute class and IsMasterImage attribute
- be the result properties
- on the criteria tab, click the create "star" icon
- on the Criterion properties page, the following values:
- Criterion type = Simple value
- Where: Citrix_VirtualDesktopInfo - IsMasterImage
- operator: is equal to
- value: 1 (true)
- Click OK to proceed.
- Click OK to continue
- Click OK to proceed.
- Click Next to proceed to the Summary page
- on the Summary page Next to apply the settings to the new device collection.
- with Update Membership discount on the new collection created device the query, and fill in the device collection with the update device Apply computer. When you are done you will have a device collection with a single element, the update module (see example below)
Step 2 -. Ask the program
make Next, the package / program to the collection device in the previous step have. Program delivery is common practice for experienced administrators Configuration Manager and is well-documented on TechNet here. automates order to make the process as possible, we recommend that the provisioning action on "Install" and the purpose is "required" on the Provisioning Settings page of the Deploy Software Wizard.
Step 3 - Monitor Deployment for completion
After providing the software, monitor the deployment to ensure that it successfully installed on the update device in the targeted collection. In the following TechNet article explains how to monitor software installations http://technet.microsoft.com/en-us/library/gg682201.aspx.
For a successful deployment is shown in the figure below , If the program is successful deployment to 100%, go to step 4 and using Citrix tools to propagate the changes to the entire pool of Citrix Session Host.
step 4 -. Update virtual machine instances with New Image
After the software is successfully triggered on the update module, use the appropriate Citrix administration console to propagate the changes to all machine instances in the Catalogue
machine Creation services
use Citrix Studio the master image with the update module to update that the package / program providing received. The following links provide the information necessary for this step.
- MCS image management (eDocs) http://support.citrix.com/proddocs/topic/xenapp-xendesktop-75/cn-plan- mcs.html
- an update Master Image (eDocs) http://support.citrix.com/proddocs/topic/xenapp-xendesktop-75/cds-update-master-vm-rho.html
Provisioning Services
to use to promote the Provisioning Services Console maintenance version of the vDisk that the package / program provision in the get production version. The following links provide the information necessary for this step.
- PVS Image Management (eDocs) http://support.citrix.com/proddocs/topic/xenapp-xendesktop-75/cn-plan- pvs.html
- Promotion updated vDisk versions (eDocs) http://support.citrix.com/proddocs/topic/provisioning-7/pvs-vdisks-update-promotion.html
solution for Application Publishing
the first section of this paper included the installation of packages and programs Citrix machines Configuration Manager manages. This section focuses on the application by the program installs the publication as a virtual Citrix app hosted. There are two ways to publish applications:
- using Citrix or Studio
- use to the CM console, Citrix Connection console installed extension
Using Citrix. posting Studio to storefront / receiver only
The first and simplest solution is easy to use Citrix Studio to publish the application. Here are the details of how to create a delivery group application http://support.citrix.com/proddocs/topic/xenapp-xendesktop-75/cds-create-deliv-grp-application.html#cds-create-deliv-grp-application.
Use posting CM console with the CM App Catalog and storefront / Receiver
If the Configuration Manager Application Catalog to use applications to users to deliver and want the Citrix version of the program hosted there to appear, you must perform the following 5 steps to create a script-based application.
More information (including a how-to-video) via script-based application, use the following resources.
- publish existing applications http://www.citrix.com/tv/#videos/11562
- create script-based application (eDocs) http: // support. citrix.com/proddocs/ Thread / xenapp-XenDesktop 75 / cn-create script app.html
step 1 - Create a new application
to create a new application with the same name as the package and add a script DT, this application is the package in the new CM 2012 app / DT model that supports the Citrix Connector
step 2 questions -. With this solution you use in a script DT application
script DT to create the detection logic with the Citrix Connector required to ensure that the program is installed prior to the publication in XenDesktop ,
in the preparation of the script DT, however the package / program have an installer on the content page of the wizard, in this scenario, enter install the content. Simply enter "zero" for the installation program and move to the detection method page.
The detection rule of the script-DT is used to detect the presence of the application installed by the package / program. In the example below the detection usually indicates the presence of C: Program Files (x86) Citrix Dev Test APP10 App10.exe in the file system. It is important to use the file system detection method to reference the executable file that will eventually be published in XenDesktop, as you will see later is in. Use the Registry or Windows Installer product code (adjustment type) as an application detection method is not
Step 3 -. Ask, must the app / script DT to the instrument collection of Citrix Session Hosts
as opposed to the package / program that deliberately in a device collection was targeted, that contains only the update module that application with script DT on the device collection by to be deployed Citrix connector that contains all pooled Citrix session hosts. The use of evaluation delivers success if the file, registry key, or from the package / program installed product code is detected, the Citrix Connector tells the application is ready
Step 4 for publication in XenDesktop -. Add the Citrix XenApp and XenDesktop 7.5 DT apply
The App / Script DT at the Citrix device collection target, the next step is to add the Citrix DT apply. This will launch the Citrix Publishing Wizard. As you can see in the example below, the Publishing Wizard is the executable defined detection method in the script-DT as the command line of the published application.
Step 5 - Set the app / Citrix DT Connector Created User Collection
, the last step in the Citrix hosted version of contained package / program in the CM application catalog is to provide the application with both the script and DT Citrix DT to a user collection. The Citrix Connector creates user collections in CM, corresponding to the delivery groups defined in XenDesktop. Make sure that you deploy the app to the user collection, which coincides with the selected delivery group if the app posting.
Done!
Other Resources
An alternative approach to the methods discussed in this paper is to use the System Center 2012 SP1 Configuration Manager Package Conversion Manager 2.0. This is a tool from Microsoft that supports the conversion of packages and programs in the new app / DT model.
http://technet.microsoft.com/en-us/library/hh531519.aspx
https://www.microsoft.com/en-us/download/details.aspx ? id = 34605
0 Komentar