Product documentation
Citrix Virtual Apps and Desktops
Service Current Release 2407 2402 LTSR 2311 2308 2305 2303 2212 2209 2206 2203 LTSR 1912 LTSR
View PDF

Publish content

November 28, 2023
Contributed by: 
C

Note:

You can manage your Citrix Virtual Apps and Desktops deployment using two management consoles: Web Studio (web-based) and Citrix Studio (Windows-based). This article covers only Web Studio. For information about Citrix Studio, see the equivalent article in Citrix Virtual Apps and Desktops 7 2212 or earlier.

You can publish an application that is simply a URL or UNC path to a resource, such as a Microsoft Word document or a web link. This feature is known as published content. The ability to publish content adds flexibility to how you deliver content to users. You benefit from the existing access control and management of applications. You can also specify whether to use local or published applications to open the content.

The published content appears just like other applications in StoreFront and Citrix Workspace app. Users access it in the same way they access applications. On the client, the resource opens as usual.

  • If a locally installed application is appropriate, it is launched to open the resource.
  • If a File Type Association has been defined, a published application launches to open the resource.

You publish content using the PowerShell SDK. You cannot use Web Studio to publish content. However, you can use Web Studio to edit application properties later, after they are published.

Configuration overview and preparation

Publishing content uses the New-BrokerApplication cmdlet with the following key properties. (See the cmdlet help for descriptions of all cmdlet properties.)

New-BrokerApplication –ApplicationType PublishedContent -CommandLineExecutable location -Name app-name -DesktopGroup delivery-group-name
<!--NeedCopy-->

The ApplicationType property must be PublishedContent.

The CommandLineExecutable property specifies the location of the published content. The following formats are supported, with a limit of 255 characters.

  • HTML website address (for example, http://www.citrix.com)
  • Document file on a web server (for example, https://www.citrix.com/press/pressrelease.doc)
  • Directory on an FTP server (for example, ftp://ftp.citrix.com/code)
  • Document file on an FTP server (for example, ftp://ftp.citrix.com/code/Readme.txt>)
  • UNC directory path (for example, file://myServer/myShare or \\\\myServer\\myShare)
  • UNC file path (for example, file://myServer/myShare/myFile.asf or \\myServer\myShare\myFile.asf)

Ensure that you have the correct SDK.

  • For Citrix DaaS (formerly Citrix Virtual Apps and Desktops service) deployments, download and install the Citrix Virtual Apps and Desktops Remote PowerShell SDK.
  • For on-premises Citrix Virtual Apps and Desktops deployments, use the PowerShell SDK that is installed with the Delivery Controller. Adding a published content application requires a minimum version 7.11 Delivery Controller.

The following procedures use examples. In the examples:

  • A machine catalog has been created.
  • A delivery group named PublishedContentApps has been created. The group uses a multi-session OS machine from the catalog. The WordPad application has been added to the group.
  • Assignments are made for the delivery group name, the CommandLineExecutable location, and the application name.

Get started

On the machine containing the PowerShell SDK, open PowerShell.

The following cmdlet adds the appropriate PowerShell SDK snap-in, and assigns the returned delivery group record.

Add-PsSnapin Citrix\* $dg = Get-BrokerDesktopGroup –Name PublishedContentApps

If you are using Citrix DaaS, authenticate by entering your Citrix Cloud credentials. If there is more than one customer, choose one.

Publish a URL

After assigning the location and application name, the following cmdlet publishes the Citrix home page as an application.

$citrixUrl = "https://www.citrix.com/"
$appName = "Citrix Home Page"

New-BrokerApplication –ApplicationType PublishedContent –CommandLineExecutable $citrixURL –Name $appName –DesktopGroup $dg.Uid
<!--NeedCopy-->

Verify success:

Publish resources located at UNC paths

In this example, the administrator has already created a share named PublishedResources. After assigning the locations and application names, the following cmdlets publish an RTF and a DOCX file in that share as a resource.

$rtfUNC = "\\GMSXJ-EDGE0.xd.local\\PublishedResources\\PublishedRTF.rtf"
$rtfAppName = "PublishedRTF"

New-BrokerApplication –ApplicationType PublishedContent
–CommandLineExecutable $rtfUNC -Name $rtfAppName
-DesktopGroup $dg.Uid

$docxUNC = "\\GMSXJ-EDGE0.xd.local\PublishedResources\PublishedDOCX.docx"
$docxAppName = "PublishedDOCX"

New-BrokerApplication –ApplicationType PublishedContent
–CommandLineExecutable $docxUNC -Name $docxAppName
-DesktopGroup $dg.Uid
<!--NeedCopy-->

Verify success:

  • Refresh your StoreFront window to see the newly published documents.
  • Click the PublishedRTF and PublishedDOCX applications. Each document opens in a locally running WordPad.

View and edit PublishedContent applications

You manage published content using the same methods that you use for other application types.

To view and edit PublishedContent applications, follow these steps:

  1. Sign in to Web Studio and select Applications in the left pane.

  2. On the Applications tab, select a PublishedContent application, and then select Properties.

    Application properties (such as user visibility, group association, and shortcut) apply to the published content. However, you cannot change the command-line argument or working directory properties on the Location page.

  3. To change the resource, modify the Path to the executable file field on that page.

    Path to executable file setting in Application Settings

  4. To use a published application to open a PublishedContent application (rather than a local application), follow these steps:

    In this example, the published WordPad application is edited to create a File Type Association for .rtf files.

    1. Turn on maintenance mode for the delivery group.
    2. Edit the File Type Association property.
    3. Turn off maintenance mode when you’re done.
    4. Refresh StoreFront to load the File Type Association changes, and then click the PublishedRTF and PublishedDOCX applications. Notice the difference. PublishedDOCX still opens in the local WordPad. However, PublishedRTF now opens in the published WordPad due to the file type association.

    Examples of where applications open

For more information

Publish content
November 28, 2023
Contributed by: 
C
November 28, 2023
Contributed by: 
C

In this article

Site feedback | Your privacy choices footer linkYour Privacy Choices | Privacy and legal terms | Cookie preferences | Consent settings | docs.cloud.com
© 1999- Cloud Software Group, Inc. All rights reserved.