This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Wo archive tread sia. Meɖekuku bia biabia yeye ne ehia kpeɖeŋu.

Having trouble running multiple instances of Firefox in XenDesktop 7.1

  • 1 ŋuɖoɖo
  • 1 masɔmasɔ sia le esi
  • 3 views
  • Nuɖoɖo mlɔetɔ John99

albolyard
albolyard
more options

We recently upgraded our Citrix environment to XenDesktop 7.1. We published Firefox, but only one user at a time can have the program open. When we try to run multiple sessions, we get this error message "Firefox is already running, but is not responding. To open a new window, you must first close the existing Firefox process, or restart your system."

We've had it published in previous Citrix environments with no problems. How do we need to configure Firefox in XenDesktop so that multiple users can run the program at the same time? Thanks.

We recently upgraded our Citrix environment to XenDesktop 7.1. We published Firefox, but only one user at a time can have the program open. When we try to run multiple sessions, we get this error message "Firefox is already running, but is not responding. To open a new window, you must first close the existing Firefox process, or restart your system." We've had it published in previous Citrix environments with no problems. How do we need to configure Firefox in XenDesktop so that multiple users can run the program at the same time? Thanks.

All Replies (1)

John99
John99
more options

I do not understand virtualisation.

I can however say that ordinarily Firefox needs each user to have a separate profile and for Firefox to open simultaneous multiple instances with separate profiles the -no-remote argument needs to be used.