Citrix Client not using Proxy Server. I've seen this happening when only a PAC file is in use and no other proxy settings are done in IE. The citrix client seems to ingnore the PAC file alltogether. We have had this issue where we tried to access our PS4.x farms with latest receiver, the proxy would never authenticate via Receiver. For information about configuring Citrix Receiver Updates, see using StoreFront in Citrix product documentation. There are four sections in this document: • • • • You can configure Citrix Receiver Updates as follows: • Right-click the Citrix Receiver for Mac icon in the menu bar. • Select Preferences > Advanced > Updates. ![]() Note: In Receiver for Mac version 12.6, this tab was named as Auto Update. From Receiver for Mac version 12.7, this tab is renamed to Updates. By default, Yes, notify me is enabled. If the user account is managed by an administrator or is under a company policy, the Citrix Receiver Updates options might be set according to the administrator-specified settings. Citrix Receiver Updates rollout period: Citrix Receiver Updates rollout depends on the delivery period and rollout priority. Based on the delay group settings, updates are available at the beginning, the middle, or the end of the delivery period. The delay groups are categorized as follows: • Fast – Update rollout happens at the beginning of the delivery period. • Medium – Update rollout happens at the middle of the delivery period. • Slow – Update rollout happens at the end of the delivery period. The settings above can be configured using macOS Server, StoreFront, or using Terminal Command on Client. Terminal Command to modify Updates rollout period: defaults write com.citrix.receiver.nomas AutoUpdateRollOutBucketIndex -int value Valid values are 0, 4, 9. Wherein 0 corresponds to Fast, 4 correspond to Medium and 9 correspond to Slow. For how to setup the rollout policy using macOS Server, please check the key AutoUpdateRollOutBucketIndex in Citrix Receiver Updates settings using macOS Server section. To make changes to the Citrix Receiver Updates setting using macOS Server, go to Profile Manager > Groups > Group Name > Settings > Custom Settings in macOS Server. Edit Custom Settings and create a new Preference Domain for com.citrix.receiver.nomas as shown in the below image: The following are list of supported Citrix Receiver Update settings from macOS Server: Key Type Values Description AutoUpdateState string Auto, Manual, FollowSF, Disabled Used to configure Citrix Receiver Updates state. Supported values: Auto: Citrix Receiver Updates set to check for updates automatically. Manual: Citrix Receiver Updates set to be check by User. No automatic checking for update. FollowSF: Citrix Receiver Updates check are as per policy set by Administrator on Storefront. Disabled: Citrix Receiver Updates disabled for Clients. AutoUpdateRollOutBucketIndex int 0,4,9 Used to configure the Updates rollout period. 0 corresponds to Fast, 4 corresponds to Medium and 9 corresponds to Slow. Citrix Receiver Updates logging is enabled by default with Citrix Receiver for Mac Version 12.6 and 12.7. Citrix Receiver Updates logs can be found in the ~ /Library/Logs/Citrix Receiver folder. The log files related to Citrix Receiver Updates are: • Citrix Receiver Updater_Timestamp.txt • ReceiverHelper_Timestamp.txt Another easy method of sharing log files is by using the Email Log Files option. ![]() You can do this by right-clicking the Citrix Receiver for Mac icon in the menu bar and selecting Preferences > Advanced > Logging > Email Log Files. This will share all log files corresponding to Citrix Receiver for Mac. Check for the requirement below as part of troubleshooting Citrix Receiver Updates. • If you have configured an SSL intercepting outbound proxy, you must add an exception to the Receiver Citrix Receiver Updates Signature service (and the download location (). Common issue #1: Software is up-to-date: To check for updates manually, select the Check for Updates option from the Citrix Receiver for Mac icon in the menu bar. When you check for updates manually and do not find any update available, it is due to the following reasons: • No updates are available. • Your account is set to a medium or slow category in the delay group. This indicates that the update rollout happens at the middle or at the end of the delivery period. The following dialog appears when you check for updates manually and no updates are available. Solution: You can check for updates at a later time or wait for the Citrix Receiver Updates notification. Common issue #2: Issues when checking for updates: An update check can fail for various reasons. For example: • No network connection during the update check. • Firewall settings do not allow a connection to the update server. The following error message appears if there is an issue when checking for updates.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2019
Categories |