Citrix

How to Create Custom Delivery Services Console with Windows Administration Components on XenApp

  • CTX126752
  • Created onMar 26, 2014
  • Updated onSep 06, 2014
Article Topic Configuration

Objective

This article describes how to create only one customized management console with all the Windows and Citrix consoles so the administrator can publish only one Microsoft Management Console (MMC).

Since the Delivery Services Console for XenApp is not registered by default as a snap-in on the Windows server, the users cannot create a customized MMC with the Delivery Services Console or Web Interface Console. If the user tries to create a custom MMC and look for the desired snap-ins, the Citrix consoles are not listed. Attempting to do a File > Open and Browse to C:\Program Files (x86)\Citrix\Citrix Delivery Services Console\Framework\Cmi60.msc displays the following error message:

“MMC could not create the snap-in.”

User-added image

There are also issues following CTX112473 – How to Publish the Access Management Console on Presentation Server 4.5 and UAC (User Access Control) in Windows 2008 and non-administrative users.

Non-administrative users who launch cmilaunch.exe are always challenged with an administrative account and password.
Note: For non-Administrator Add read permissions to the MMC and add user to the distributed com user group on the XML server.

Publishing an application C:\windows\system32\mmc.exe “C:\Program Files (x86)\Citrix\Citrix Delivery Services Console\Framework\Cmi60.msc” bypasses the UAC issue and then, after the first configuration, subsequent launches reuse the .msc created in the users \appdata\roaming\microsoft\mmc folder.

This article helps the administrators to have one console to access all the desired components and at the same time publish the MMC so it can be accessed from anywhere by the administrator.

Instructions

Complete the following steps to create the custom Microsoft Management Console:

  1. Log on to the XenApp server and create a folder on the root driver of the server. For example, C:\CustomConsoles\.

  2. Locate the Delivery Services Console *.msc file. Copy the file to the recently created folder C:\CustomConsoles.

    Citrix XenApp 6.0 Windows 2008 Server R2

    Cmi60.msc

    C:\Program Files (x86)\Citrix\Citrix Delivery Services Console\Framework\

  3. Right-click on the file and select Author mode; the console opens with all the author options that can be customized.User-added image

  4. The first time the console is opened the server discovery starts. Follow the normal process for the discovery and ensure to select the required options so that the discovery wizard runs automatically the next time you open the console. That way, the user only has to configure discovery the first time the console is opened.User-added image

    Ensure to select the desired options for the console when the discovery process is executed.

  5. Go to File > Add/Remove Snap-In. The snap-ins to be changed are listed. If you add the new snap-ins to the console you only see the Delivery Services Console in the tree. The configuration of the pre-existing Delivery Services Console snap-in does not allow showing others. The newly added snap-ins are hidden. To fix this, clear the configuration, remove the Delivery Services Console snap-ins and add them back again. This causes a new configuration of the snap-ins and you can add others snap-ins and see them. If desired, you can save the .msc file to record the changes. You can Save as and change the name of the file, for example, CustomDSC.msc.

    User-added image

    User-added image

  6. The following screen shot contains a list of recommended snap-ins that you must add to the console.User-added image

    • Citrix Web Interface: Only if the web Interface is installed on the same server where it is going to be published.

    • Group Policy Management: Required to work with Active Directory, GPO, or Citrix GPOs.

    • Event Viewer: View event logs of the server. The user can use the Connect To option to change servers inside the console.

    • Services: View services of the desired server. The user can use the Connect To option to change servers inside the console.

    • Local Users and Groups: View local users, groups, and the permissions. The user can use the Connect To option to change servers inside the console.

  7. Close the console and open it normally. Do not use Author mode. When it opens, ensure all the desired settings are as expected. If a discovery is requested, run it again, save, and close the console.User-added image

  8. Open the console in Author mode again. Go to File>Options, make the following changes.

    • Title description of the console

    • Console icon

    • Change console mode to User mode – limited access, single windows. This setting blocks users from making changes to the console settings and views.

    • Select Do not save changes to this console. If the user is able to make changes, any changes to the setting are not saved. This is the reason that discovery must be tested before enabling these options. If the discovery is not configured beforehand, every time the user opens the console, the discovery wizard opens.

    • Clear Allow the user to customize views option. This allows the user to customize the view of the console.

      User-added image

  9. Publish the custom console. Open the Delivery Services Console of the server and add a new published application. Write the application name and description of the console.

    User-added image

    User-added image

  10. Configure the applications to access the applications installed on the server. On the next page, browse for mmc.exe inside the System32 folder of Windows and add the path of the custom *.msc file as a parameter. Ensure the working directory matches the locations of mmc.exe. Because you are using a custom console, you must name it with the mmc.exe to launch it.User-added image

    User-added image

  11. Add the servers or workgroup to handle the console. Because it is an administration console for the farm, it is recommended that you add all the servers, and all the servers must have the custom console copied to the same locations.
    User-added image

  12. Add the administrators that have permissions to access the components of the console.User-added image

  13. Change the icon to match the Delivery Services Console (this is optional). Click Next and click Finish to complete the configuration.User-added image

Now there is a custom access-to-all administration console for the administrators of the farm. When giving permissions for the administration of XenApp, be cautious not to give excessive access to non-administrators.

Additional Resources

This procedure has been tested with Citrix XenApp 6.5 console Citrix AppCenter, the same procedure works with no issue.

CTX127619 – Hotfix XA600W2K8R2X64019 - For Citrix XenApp 6.0 for Windows Server 2008 R2 - Spanish resolved an issue in which an administrator level account was unable to launch the application, the published application name may not show in the Discovery Services Console, CTX128945 – Hotfix XA600W2K8R2X64056 - For Citrix XenApp 6.0 for Windows Server 2008 R2 - English.

The Elder Geek - Microsoft Management Console Basics - This is a third party article of other customization concepts for Microsoft Management Console.

Automatic translation

Important: Non-English versions of this article are translated by an automatic translation system (also referred to as Machine Translation, or MT) and have not been translated or reviewed by a person. Citrix offers a machine translated version of this article to allow for greater access to the support content. However, automatic translation is not always perfect and may contain vocabulary, syntax or grammar errors. Citrix is not responsible for inconsistencies, errors or damage incurred as a result of the use of machine translated articles. Thank you.

Traduction automatique

Important : cet article a été traduit par un système de traduction automatique (également appelé Traduction automatique ou TA) et n'a pas été vérifié par des spécialistes. Citrix propose une traduction automatique de cet article afin de permettre à toute personne ne maîtrisant pas l'anglais d'accéder au contenu de l'assistance. Toutefois, la traduction automatique n'étant pas parfaite, elle peut contenir des erreurs de terminologie, de syntaxe ou de grammaire. Citrix n'est pas responsable des incohérences, erreurs ou dommages pouvant résulter de l'utilisation par nos clients d'articles TA.

Automatische vertaling

Belangrijk: Dit artikel is vertaald door een automatisch vertalingssysteem (ook Machine Translation of MT genoemd) en is niet vertaald of beoordeeld door mensen. Citrix biedt een machine-vertaalde versie van dit artikel aan om een betere toegang mogelijk te maken tot de support-inhoud. Automatisch vertalen werkt echter niet altijd perfect en het resultaat kan fouten bevatten in de woordkeuze, syntaxis of grammatica. Citrix is niet verantwoordelijk voor inconsistenties, fouten of schade als gevolg van het gebruik van MT-artikelen door onze klanten.

Maschinelle Übersetzung

Wichtig: Dieser Artikel wurde mit einem maschinellen Übersetzungssystem und ohne jegliche Bearbeitung durch Personen übersetzt. Citrix bietet maschinelle Übersetzungen von Artikeln an, damit Benutzer umfassenden Zugriff auf Support-Inhalte haben. Maschinelle Übersetzungen enthalten jedoch möglicherweise Fehler in Bezug auf Terminologie, Syntax und Grammatik. Citrix übernimmt keine Verantwortung für Inkonsistenzen, Fehler oder Schäden, die aus der Verwendung von maschinell übersetzten Artikeln durch Kunden resultieren.

自动翻译

重要提示:本文是由自动翻译系统翻译完成的(也称为“机器翻译”或 MT),未经人工翻译或审查。Citrix 提供本文的机器翻译版本是为了方便更多人访问支持内容。然而,自动翻译的文章并不总是完美的,可能存在词汇、语法或文法方面的错误。对于因客户使用机器翻译文章导致出现的不一致、错误或损害,Citrix 不承担任何责任。

機械翻訳

重要:この技術情報資料は機械翻訳システム(自動翻訳あるいはMTとも呼ぶ)により翻訳され、翻訳者により翻訳またはレビューされたものではありません。サポート用資料をより参照しやすくするため、Citrixはこの技術文書の機械翻訳バージョンを提供しています。しかしながら、機械翻訳の品質は翻訳者による翻訳ほど十分ではありません。誤訳や、文法、言葉使い、そのほか、たとえば日本語を母国語としない方が日本語を話すときに間違えるようなミスを含んでいる可能性があります。機械翻訳の品質、および技術情報資料の内容の誤訳やお客様が技術情報資料を利用されたことによって生じた直接または間接的な問題や損害については、いかなる責任も負わないものとします。

Tradução automática

Importante: este artigo foi traduzido por um sistema de tradução automática (também conhecido por Machine Translation ou MT) e não foi traduzido nem revisado por pessoas. A Citrix oferece uma versão traduzida por máquina deste artigo para permitir maior acesso ao conteúdo de suporte. No entanto, a tradução automática não é sempre perfeita, podendo conter erros de vocabulário, sintaxe ou gramática. A Citrix não se responsabiliza por inconsistências, erros ou danos incorridos como resultado do uso de artigos de MT de nossos clientes.

Traducción automática

Importante: Este artículo ha sido traducido por un sistema de Traducción automática (también llamada MT o Machine Translation) sin intervención de un traductor humano. Citrix ofrece la traducción automática de este artículo para ampliar el acceso a la información de asistencia técnica. No obstante, la traducción automática no es perfecta y puede contener errores de vocabulario, sintaxis y gramática. Citrix no se hace responsable de cualquier imprecisión, error o daño ocasionados por el uso que hagan nuestros clientes de los artículos traducidos automáticamente.
Languages
Was this helpful?
Thank you for your feedback

Share your comments or find out more about this topic

Citrix Forums