There are also GPOs for auto-launching applications when users log on. For general application purposes, they’re no use. So if you’re publishing Explorer, they will work – but Explorer isn’t likely to be the only application you’re publishing, unless you’re mental. These don’t work at all – they’re only processed when you launch the shell. o Pulse Secure - Error: Secure App Launcher failed to launch Java applets (Big Sur). In case you’re not familiar, they are generally under \Software\Microsoft\Windows\CurrentVersion\Run. My anyconnect pop up warning Could not connect to server. These exist in both HKLM and HKCU and have entries in the “standard” and “Wow6432Node” trees. Published apps not launching for some users when connecting. What doesn’t workįirst of all, there are the Run keys in the Registry. If you use Citrix Workspace app for Windows and launch the app bar in a vertical position. Let’s get some of them out of the way straight away. Since 2018, ChromiumOS/ChromeOS version 69 onwards also. But like I said, it sounds easy – there are stacks of entry points that you can use to auto-launch something even if you don’t have Ivanti UWM or Citrix WEM to do it. ChromeOS (but not ChromiumOS) from 2016 onwards can also run Android applications from Google Play. I hadn’t given the published applications conundrum much thought after that until Ryan Gallier mentioned it over on World of EUC Slack. In my first deployment to published applications I simply used Ivanti (AppSense) to trigger a process launch so it was pretty straightforward. But with applications, it’s a different matter. On a desktop, this is super easy – CDM itself writes into the Run key in the Registry when it’s installed, so when the user launches a desktop, they connect and everything is good. The applications are normally launched in a seamless window, meaning that users see only the application window and not an additional desktop. But one thing you have to do is make sure the CloudDriveMapper process launches when the user launches their published applications, otherwise they won’t get connected to their OneDrive files and folders. Published applications allow your users to launch applications as if they were installed on their devices when in fact they are hosted remotely. I’m not going to go into the setup of it right now – I have another post in the drafts dealing with that. If you have any workstations with this issue, try deleting the above keys and let me know what kind of results you get.For a lot of my Citrix Virtual Apps deployments (so I’m talking published applications only, not desktops), I sometimes lean on CloudDriveMapper for connecting to OneDrive. Your results may vary, but I have found that deleting the registry keys HKEY_CURRENT_USER\Software\Citrix\ICA Client\Engine\Configuration and HKLM\Software\Citrix\ICA Client\Engine\Configuration (on 64-bit systems: HKLM\Software\Wow6432Node\Citrix\ICA Client\Engine\Configuration) will allow applications to launch consistently, and will cause both the Receiver and PNAgent icons to appear consistently and behave normally. But this manual workaround gets old after a while. But occasionally it will boot with both the Receiver icon and the blue PNAgent icon, and apps will just not launch.Ī typical workaround for this has involved terminating the pnamain.exe process, thus killing the blue PNAgent icon, and allowing apps to launch successfully. Sometimes when the workstation boots, only the Citrix Receiver icon shows up and apps launch fine. This is a very common problem that affects both Windows XP and Windows 7 machines. Do you have a workstation that intermittently boots up with both the black Citrix Receiver icon and the old blue Program Neighborhood Agent/Online Plugin icon? And does it fail to launch published applications?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |