![citrix receiver mojave citrix receiver mojave](https://support.cloudnetworks.com.au/hc/article_attachments/360001474775/mceclip2.png)
You have to add : launchctl unload –w /Library/LaunchAgents/_Mac.plist For the time being - and as mere principle - I choose the hard way myself.įor further reference about launchctl, this AskDifferent answer is quite helpful.Ĭreating an app in Automator with shell script works fine to unload at startup without removing the plist files.
![citrix receiver mojave citrix receiver mojave](https://i1.wp.com/martijnhs.com/wp-content/uploads/2014/09/screenshot4.png)
There is actually a discussion on their forum about this, but it appears dead and without response. But I've made it simple as an Automator task, which runs the mentioned commands to start the service and immediately after start the Citrix Receiver.Īctually, I have no doubt that it is relatively easy for Citrix to make this configurable as a preference. Especially to repeat it every now and then. Unfortunately, this is a bit of a cumbersome process.
![citrix receiver mojave citrix receiver mojave](http://www.intellischool.org/wp-content/uploads/citrix-on-mac-3.png)
Launchctl load /Library/LaunchAgents/_Mac.plist To fix this, you manually need to start the services again: launchctl load /Library/LaunchAgents/ Unable to connect to the citrix AuthManager service The only issue now is that when you open the Citrix Receiver application, you may get something like the following error: In order to remove them completely from starting up automatically, I use the following commands: launchctl remove The process below allows you to stop autostart at boot.įirst, I fetched a list of all "citrix" processes that run on startup: launchctl list | grep citrix Like mentions, starting and stopping is done through launchctl. Considering that one can just delete the above. I did notice these services are unneeded if using the the companies web app. It is irrelevant because the Citrix Receiver App will not start those services when it starts and will therefore not work if they were stopped or disabled. However I am currently unable to prevent launchd from autoloading these services through launchctl. You can use launchctl to stop the processes like so launchctl stop _Mac The following services are are started at login by launchd /Library/LaunchAgents/_Mac.plist