Citrix workspace msi installer


  • Working towards a solution
  • Citrix Receiver Per-User Install Cleanup
  • Microsoft Teams on Citrix Virtual Apps and Desktops, part #1 – installing the damned thing
  • Download and Install Latest Citrix Workspace App
  • Known Citrix Workspace Bug Open to New Attack Vector
  • Search Site
  • Silent install Citrix Receiver not working!
  • Working towards a solution

    In XenApp 6. Login to the PC as an administrator. If installing Workspace app or Receiver for Windows 4. Then finish the installation. If installing an older version of Receiver: Go to the downloaded Citrix Receiver. Shift-right-click CitrixReceiver.

    Open a command prompt. Click Install when prompted. Install the receiver. On the right, double-click Local user name and password. Select Enabled and then check the box next to Allow pass-through authentication for all ICA connections. Click OK. You can use a GPO to configure this on the client side.

    Local Intranet zone should have Automatic logon only in Intranet zone enabled. Logoff Windows and log back on. In Task Manager you should now see ssonsvr. In Receiver 4. Click Configuration Checker. The lines with red x will indicate the issue and corrective action. Select Enabled, and then click Show. Enter a store path based on the example shown in the Help box.

    Workspace app and Receiver 4. Then click OK. This only works if the app is a Favorite, or if Favorites are disabled, or Mandatory Store. Some of the settings only apply if SelfServiceMode is set to False.

    More details in Configuring application delivery at Citrix Docs. StartMenuDir — If there is potentially a conflict between local apps and remote apps, then you should place the Start Menu shortcuts in a folder. If you import the receiver. Enable the Manage App shortcut setting to control placement of shortcuts. Enable the setting Control when Citrix Workspace attempts to reconnect to existing sessions and configure it as desired.

    Prelaunch Staring with Receiver 4. Otherwise, set registry values to enable prelaunch. Receiver 4. For example, to enable scheduled pre-launch on Monday, Wednesday, and Friday at p. The session actually launches between p. Note: there is a bug fixed in Receiver 4. Copy the. Edit a GPO that applies to the endpoint devices that are running Receiver. Then expand the regions, and configure the permission settings as desired. Enter a descriptive name for the StoreFront server.

    Add the path to your store e. Now when users launch the published desktop, Workspace app or Receiver will be automatically configured with this URL. This is an alternative to using a User Experience Management product to control shortcut placement.

    Note: Workspace app or Receiver tends to be slow to create Start Menu shortcuts, so make sure you perform a Proof of Concept to determine how this functionality impacts logon times.

    Configuration of Workspace app or Receiver inside a published desktop is simplified if you have the following minimum versions: Workspace app or Receiver 4. This feature is called vPrefer. Enable the Group Policy setting Remove common program groups from Start Menu and apply it to non-administrators. Workspace app or Receiver will re-add the shortcuts based on user group membership. On the VDA, configure the following Workspace app or Receiver Registry keys or corresponding settings in the receiver.

    Otherwise, only subscribed favorited icons would be placed on the Start Menu and Desktop. Note: Windows Server and Windows 10 and newer only supports a single level of Start Menu folders, so setting this effectively turns off published app categories. Check the box next to Allow pass-through authentication for all ICA connections. Make sure it is not in the Trusted Sites zone, or enable Automatic logon with current user name and password for the Trusted Sites zone. Make sure ssonsvr.

    If not, troubleshoot it. When configuring Citrix Profile Management, make sure! Assign users to the delivery group, and the individual published applications if visibility is limited. In Citrix Studio, edit each published application, and on the Delivery tab, specify a category.

    This will become the Start Menu folder name. Only subscribed or Favorite apps are displayed in the Start Menu and Desktop. Also replace the path to the store with your store path. By default, Workspace app and Receiver only support https. Your StoreFront store probably delivers both application and desktop icons. If you want to filter out the desktop icons, then create a new StoreFront store, and configure the Workspace app or Receiver on the VDA to connect to the new Store.

    On the Advanced Settings page, in the Filter resources by type row, choose Citrix. For vPrefer in Workspace app or Receiver 4. Edit the setting vPrefer.

    Set it to Allow all apps. Configure your client devices to connect to the published desktop. When users connect to the published desktop, Workspace app or Receiver will auto-launch and hopefully auto-login. Users can open the systray icon to subscribe to more applications. Users can copy icons from the Start Menu to the desktop. Users can then launch applications directly from the Start Menu, from the Desktop, or from the Workspace app or Receiver if the Self-Service interface is enabled.

    If Workspace app or Receiver 4. When launching an app icon that came from Workspace app or Receiver, Workspace app or Receiver checks the local VDA machine to see if the application can be launched on the local VDA instead of by creating a new Citrix double-hop session. If the application is installed locally on the VDA then the local application shortcut should launch quickly.

    If the user deletes Workspace app or Receiver shortcuts from the Start Menu, you can get them back by going to the systray icon and refreshing the applications. Or sometimes you have to reset Workspace app or Receiver. If you are running components older than Receiver 4. For applications that are installed on the same VDA that is publishing the desktop, configure Group Policy Preferences to recreate the application shortcuts based on Active Directory group membership.

    Applications on other delivery groups are handled by Receiver. Or use the prefer keyword to copy shortcuts from the PreferTemplateDirectory. On the VDA, configure the following Receiver Registry keys or corresponding settings in the receiver.

    Assign users to the Delivery Group and the applications if visibility is limited. Notice the lower case p. With the prefer keyword, if you publish an application that is also created using Group Policy Preferences, the Group Policy Preferences icon will take precedence.

    This is good. Otherwise the Receiver published application icon would result in a new Citrix double-hop session.

    When users connect to the published desktop, Group Policy Preferences will create shortcuts to local applications. Receiver will auto-launch and hopefully auto-login. See below for considerations. Users can then launch applications directly from the Start Menu, from the Desktop, or from the Receiver if Self-Service interface is enabled. If a local shortcut e. Group Policy Preferences shortcut, or copied from template directory matches a published application with KEYWORDS:prefer then the local shortcut will override the published application icon.

    If the user deletes Receiver shortcuts from the Start Menu, you can get them back by going to the systray icon and refreshing the applications.

    Or sometimes you have to reset Receiver. The shortcuts copied from the Prefer Template Directory are renamed to match the published app name. For prefer local apps, any command line parameters specified in the published app are ignored. If you need these command line parameters, add them to the shortcut in the Prefer Template Directory.

    Citrix Receiver Per-User Install Cleanup

    Thus when a user signs in the Teams. This is what keeps Teams up to date for the user and also launches it. Notice the program is actually called Update. This takes about MB of space per user.

    Teams always launches automatically. Do this for Citrix and other VDI see a few bullet points below. With per-machine automatic updates is disabled. This is if you want to install on a non-VDA machine of course, not something Microsoft recommends. Should have gone with better option names really. You can also install Teams as part of Microsoft This blog post too has info on Teams and OneDrive installation as part of Microsoft Loads of useful info, including an uninstall of per-user so we can switch to per-machine.

    For per user installs it automatically updates. No place to signup for Teams update notifications either. If you have Orca installed you can right click the MSI and see the version there below screenshot is from the MSI I downloaded today; but Teams on my machine which is a per-user install and thus auto-updates is on a newer version 1.

    But it looks like there may be more locations than just that. No additional download needed. However, Teams does not load it automatically the first time around. Quit both, open Teams, open Outlook. You can turn off calling and meeting features for users via policies. The VDA needs to be The client needs to be Workspace app or higher. Currently only Windows clients are supported. Linux too seems to be supported and above also x64 distros only.

    This also needs a Citrix policy setting which is on by default. This needs to be allowed, and the Workspace version supported, before optimizations are turned on. In this case a registry key is set to indicate Teams is running optimized.

    Screenshots here. This is a live article from Citrix with latest updates CTX Citrix persistent vs non-persistent: Non-persistent means you have a master image and the actual VDA server is reset upon a reboot and so all user profiles etc. That comes under non-persistent. Use that along with the updates at this blog post which is a great read for general Teams info too.

    For persistent you can do both per-machine or per-user install. For non-persistent you must do per-machine install.

    With HDX optimization, incoming screen sharing is treated as a video stream. Therefore, if you are in the middle of a video call and the other peer starts to share the desktop, that original camera video feed is paused. Instead, the screen sharing video feed displays. The peer must then manually resume the camera sharing.

    Good stuff: If you are publishing Teams as a stand-alone seamless application, screen sharing captures the local desktop of your physical endpoint in Citrix Workspace app minimum version In fallback mode, the peripherals are mapped to the VDA. The peripherals appear to the Microsoft Teams app as if they were locally attached to the virtual desktop.

    To enable audio only, set the value to 2. This feature requires Teams version 1. So in fallback mode you will have poor performance and increased CPU usage of the Citrix servers. Hence it is better to disable it by setting the value to 0, or at least 1 if you want to allow just audio.

    Instead, HDX technologies use server-side rendering. Real time audio performance might not be optimal. Known Issues Teams does not do well with 4k displays. I curse Teams every day coz of this and today I came across this doc that states it as a known issue. Workaround available. Only the primary monitor can be shared in Citrix.

    Microsoft Teams on Citrix Virtual Apps and Desktops, part #1 – installing the damned thing

    As described by Citrix in the article Windows 10 Fall Creators Update v — Citrix Known Issuesthe network provider has a bug which is fixed in Windows 10 version and higher.

    This bug causes the error "failed to get network providers" when you try to display the network provider order graphically. Please be aware that the actual functionality of the network provider still works. With Windows 10, this is no longer the case. The item with the lowest number is executed first and the item with the highest number last. I recommend to use a different number, for example or The reason for this is simple; you may have another third-party product that already occupies the number This is for example the case when you install a product such as Lotus Notes including the Notes Single logon service.

    The main goal is that the PnSson value is listed as the fourth item, after the three default Microsoft ones. The third Microsoft entry has the value ofso the value PnSson needs to have a higher value at least or higher. In the complete installation script below, the missing network provider registry item is created in lines tobut only for Windows 10 version Performance optimizations There seem to be a couple of registry values that may improve the performance of Workspace app.

    I did not add these to the complete installation script. Complete installation script I packed the complete Citrix Workspace app installation in my installation template. Users can copy icons from the Start Menu to the desktop. Users can then launch applications directly from the Start Menu, from the Desktop, or from the Workspace app or Receiver if the Self-Service interface is enabled.

    If Workspace app or Receiver 4. When launching an app icon that came from Workspace app or Receiver, Workspace app or Receiver checks the local VDA machine to see if the application can be launched on the local VDA instead of by creating a new Citrix double-hop session. If the application is installed locally on the VDA then the local application shortcut should launch quickly.

    If the user deletes Workspace app or Receiver shortcuts from the Start Menu, you can get them back by going to the systray icon and refreshing the applications. Or sometimes you have to reset Workspace app or Receiver. If you are running components older than Receiver 4. For applications that are installed on the same VDA that is publishing the desktop, configure Group Policy Preferences to recreate the application shortcuts based on Active Directory group membership.

    Download and Install Latest Citrix Workspace App

    Applications on other delivery groups are handled by Receiver. Or use the prefer keyword to copy shortcuts from the PreferTemplateDirectory. On the VDA, configure the following Receiver Registry keys or corresponding settings in the receiver. Assign users to the Delivery Group and the applications if visibility is limited.

    Notice the lower case p. With the prefer keyword, if you publish an application that is also created using Group Policy Preferences, the Group Policy Preferences icon will take precedence.

    Known Citrix Workspace Bug Open to New Attack Vector

    This is good. Otherwise the Receiver published application icon would result in a new Citrix double-hop session. When users connect to the published desktop, Group Policy Preferences will create shortcuts to local applications. Receiver will auto-launch and hopefully auto-login. See below for considerations.

    Users can then launch applications directly from the Start Menu, from the Desktop, or from the Receiver if Self-Service interface is enabled. If a local shortcut e.

    Group Policy Preferences shortcut, or copied from template directory matches a published application with KEYWORDS:prefer then the local shortcut will override the published application icon. If the user deletes Receiver shortcuts from the Start Menu, you can get them back by going to the systray icon and refreshing the applications.

    Or sometimes you have to reset Receiver. The shortcuts copied from the Prefer Template Directory are renamed to match the published app name. For prefer local apps, any command line parameters specified in the published app are ignored.

    Search Site

    If you need these command line parameters, add them to the shortcut in the Prefer Template Directory. If you have multiple published apps pointing to the same prefer local shortcut, then only one copy will be made, and it will have the name of only one of the published apps.

    To workaround this, in the Prefer Template Directory, create separate shortcuts for each published app, and adjust the published app prefer keyword accordingly. These shortcuts can then be copied to your Prefer Template Directory.

    However, SSP exposes sufficient information for its activities to be scripted. Running these. Note: Workspace app and Receiver 4. If you want to drive SSP directly for launch instead of through an. There will be keys in there named farm-name server-farm-name. These parameters are user-independent and can therefore be cloned from a reference user to a general case. System account The last option is to install the Citrix Receiver with the system account.

    Login AM uses its own service account that is comparable with a normal account that is dedicated to Login AM. However, the system account has more rights and is comparable to a Linux root account. PsExec First, it is needed to run the installer under the system account. That can be done with PsExec. PsExec is part of the PsTools package.

    Silent install Citrix Receiver not working!

    For more information and a download link, click here. The PowerShell script is starting PsExec with all the arguments needed to run it in the background. PsExec will, in return, start the command under system account to install the Citrix Receiver.


    thoughts on “Citrix workspace msi installer

    1. It is a pity, that now I can not express - it is very occupied. I will return - I will necessarily express the opinion on this question.

    Leave a Reply

    Your email address will not be published. Required fields are marked *