Update Readme with troubleshooting section for citrix #2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Emastermind
commented
Feb 21, 2025
|
Thank you for the PR! I proposed to complete a bit by adding the fact that these commands must be run with administrator privileges. Is this okay for you? |
af-airbus
force-pushed
the
citrix-troubleshooting
branch
from
2a0205f to
e4f542b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
As discussed in #1, one more step is needed on newer citrix to start and get a working soxy.exe backend.
This pull request just add a new troubleshooting section for this specific citrix issue.
In a nutshell, "VirtualChannelWhiteList" registry key can be set to ignore restrictions or to whitelist one (or more) binary in the format
<VIRTUAL_CHAN_NAME>,<PATH_TO_EXE>.