Powershell Module for Citrix WEM – Part 4 – Import Published applications

Recently James Kindon (@james_kindon) asked me if I could assist in importing published applications to WEM.

This resulted in a new function in the Citrix WEM PowerShell module.

You can read up on this module in Powershell Module for Citrix WEM – Part 1 – Application actions, Powershell Module for Citrix WEM – Part 2 – GPO Import and more, and Powershell Module for Citrix WEM – Part 3 – EnvironmentalSettings and MicrosoftUsvSettings from GPO and much, much more.

The new function is called Import-VUEMActionsFromBrokerApplicationCSV.

Import-VUEMActionsFromBrokerApplicationCSV01 citrix wem part 4


Imports an exported BrokerApplication CSV and converts this to WEM Applications Actions.


-CSVFile <String>
This is the full path including the filename to an exported BrokerApplications CSV file.
-OutputPath <String>
Location where the output xml file will be written to. Defaults to current folder if omitted.
-OutputFileName <String>
The default filename is VUEMApplications.xml. Use this parameter to override this if needed.
-Prefix <String>
Provide a prefix string used to generate Action names (as displayed in the WEM console).
-SelfHealingEnabled [<SwitchParameter>]
This will enable the SelfHealing option.
-OverrideEmptyDescription [<SwitchParameter>]
If used will generate a description based on the Action name, but only if a description is not found during processing.
-OverrideDisplayName <String>
Use this parameter to select a different column in the CSV to provide the DisplayName in the Application Action.
Possible values here are “Name”, “BrowserName” or “ApplicationName”. Will use “PublishedName” if omitted.
-IgnoreStartMenuFolder [<SwitchParameter>]
Use this parameter if you wish to ignore the StartMenuFolder in the CSV file.
This will create all Application Actions in the default location, which is in the root of the StartMenu.
-Disable [<SwitchParameter>]
If used will create disabled Actions. Defaults to $False if omitted (uses Enabled status from the imported CSV).


The CSV input for this function needs to be generated using a Citrix powershell command:

Get-BrokerApplication | Export-CSV -Path <path to output csv file>

This command will not extract icons for your Published Applications and use them in the WEM actions.
To provide Icons for your actions, place them in the same folder als the CSV file that you are importing and name them according to the Published Application’s target (e.g. if the target is ‘outlook.exe’, extract or find an icon, name it ‘outlook.ico’, and place it in the folder where the CSV file is).
If you don’t provide an icon, a default icon will be generated.
If the target binary for the Published Application is available in the same path on the machine where you run the import function, the function will extract the icon from that binary.

If the CSV contains published content (URLs), this function will create them in WEM accordingly.

A big thank you again to James Kindon (@james_kindon) for helping me out during development and for testing the module!

You can download the module on Github: https://github.com/msfreaks/Citrix.WEM

If there’s any other functionality you’d like to see in this module, don’t hesitate to contact me!

Until next time,

Arjan Mensch

25+ years experience in Microsoft powered environments. Enjoy automating stuff using powershell. In my free time (hah! as if there is any) I used to hunt achievements and gamerscore on anything Xbox Live enabled (Windows Mobile, Windows 8, Windows 10, Xbox 360 and Xbox One). Recently I picked up my Lego addiction again.

Tagged with: , , ,
Posted in Citrix, Powershell
4 comments on “Powershell Module for Citrix WEM – Part 4 – Import Published applications
  1. […] The solution? Workspace Environment Management (again). WEM is more than capable of delivering a robust and dynamic Modern Start Menu without any of the logon impact overhead or multiple touch points. I have written on how to control the Start Menu with WEM so won’t double tap into how this is done, however we had a nice challenge in moving a few hundred applications out of the Citrix Studio and into WEM. Currently there is no functionality to delivery this via native tools, and it’s a manual process. Or at least was a manual process until my good friend Arjan Mensch stepped in once again to save the day with another awesome addition to his WEM PowerShell Module. […]

  2. nickclarkson says:

    Hi Arjan – somehow missed part 4 of the module. I came here via James’ article. I’ll be looking at this on Monday as it might help speed up the Start Menu creation. I still have some ‘backline’ apps that will be run from silos, but the Receiver should pull them into the Start Menu as normal. Thanks again for your script.

  3. […] Part 4: Convert Studio to WEM Apps […]

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

Blog Authors

Enter your email address to follow this blog and receive notifications of new posts by email.

Join 446 other followers

Blog Stats
  • 3,603,294 hits
  • An error has occurred; the feed is probably down. Try again later.
  • An error has occurred; the feed is probably down. Try again later.
%d bloggers like this: