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-->
ApplicationType property must be
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,
- Directory on an FTP server (for example,
- Document file on an FTP server (for example,
- UNC directory path (for example,
file://myServer/myShare or \\\\myServer\\myShare)
- UNC file path (for example,
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
PublishedContentAppshas 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
CommandLineExecutablelocation, and the application name.
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.
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-->
- Open StoreFront and log on as a user who can access applications in the PublishedContentApps delivery group. The display includes the newly created application with the default icon. To learn about customizing the icon, see https://www.citrix.com/blogs/2013/08/21/xd-tipster-changing-delivery-group-icons-revisited-xd7/.
- Click the Citrix Home Page application. The URL launches in a new tab in a locally running instance of your default browser.
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-->
- 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:
- Sign in to Web Studio and select Applications in the left pane.
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.
To change the resource, modify the Path to the executable file field on that page.
To use a published application to open a
PublishedContentapplication (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.
- Turn on maintenance mode for the delivery group.
- Edit the File Type Association property.
- Turn off maintenance mode when you’re done.
- 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.