Release Notes for Build 52.15 of Citrix ADM 12.1 Release

Fixed Issues

• If you upgrade or restart the Citrix ADC instances that are managed in a Citrix ADM, the Logstream data does not appear in the Citrix ADM.
  [# NSADM-37039]

• The active session tables are not created in Citrix ADM. Therefore, the active session data dump does not appear for HDX and Gateway insights.
  [# NSHELP-19121]

Applications

• When you try to enable AppFlow configuration for the Citrix ADC instance using the Citrix ADM agent, the AppFlow configuration might appear as disabled in Citrix ADM.
  [# NSHELP-18656]

• The Application Dashboard page displays incorrect information for external users.
  [# NSHELP-19690]

• In Applications > Dashboard, when you click an application, the following error intermittently appears:

  “Either Application is deleted or no virtual servers are bound to this app".
  [# NSHELP-6402, NSADM-20206]

High Availability

• If you shut down the Citrix ADM high availability server during FileSync process, the synchronization job is aborted. The job does not resume even after the server has restarted.
  [# NSHELP-19455]

Networks

• When you try to export the logs in CSV format, Citrix ADM exports all command logs, irrespective of the selected ADC instances.
  [# NSADM-32733]

• When you try to execute an aborted config job, you might see an "Invalid Request" error.
  [# NSADM-34242]

• The Citrix ADM event subsystem crashes if the following conditions are met:

  - You delete the instance or device partition from which an event is received.

  - The event is configured to send a repeat email notification for a specified interval.
  [# NSHELP-19401]

• The temporary folders created to maintain the difference between configuration audit reports are not cleared from Citrix ADM regularly.
  [# NSHELP-19436]

• When a scheduled configuration audit and “Poll Now” action is triggered at the same time, the polling might fail because of a shortage of threads to complete the action.
  [# NSHELP-19454]

• When you remove the VPX instances from Citrix ADM, the instances are automatically managed again after sometime.
  [# NSHELP-19456]

• If you modify the “event_filter” API using the Citrix ADM NITRO API, it resets the name of the event rule to empty or null.
  [# NSHELP-19474]

• When you restore the Citrix ADM server using the backup of a different Citrix ADM server, the restored Citrix ADM server displays an invalid “Host ID” in the Networks > License page.
  [# NSHELP-19485]

• While creating a configuration template, Citrix ADM does not check for the invalid characters given in the template name.
  [# NSHELP-19507]

• When you want to install an SSL certificate in the Citrix ADC appliance using the Import Certificate option from the Citrix ADM GUI, the "ns_ssl_keys" file is created instead of "ns_ssl_keys" directory. As a result, the installation fails in the Citrix ADC appliance.
  [# NSHELP-19525]

• An authorization error appears when the following conditions are met:

  - A user fetches and deletes configuration templates

  - The user belongs both to an admin group and a non-admin group without configuration templates.
  [# NSHELP-19622]

System

• If you create an application using an instance that is not in the scope of your authentication, the Citrix ADM does not display any error message.
  [# NSADM-17877]

• If a disaster recovery node has an incorrect file permission, high network traffic flows between the Citrix ADM primary node and disaster recovery node.
  [# NSHELP-19153]

• After restoring the backup of the Citrix ADM high availability server on to the standalone Citrix ADM server, the System > System Events page displays the loopback IP address as the source IP address.
  [# NSHELP-19465]

• The Citrix ADM configuration subsystem might crash because of an incorrect file permission given to the "/mpsconfig/cipher_settings.conf" file.
  [# NSHELP-19497]

• In the Citrix ADM, the registration of disaster recovery node fails with an error message "untar command failed".
  [# NSHELP-19623]

Known Issues

High Availability

• If you manually break high availability on the Citrix ADM servers, the configuration on the managed instances is not sent to the IP address of the primary node.
  [# NSADM-34478]

• In the System Administration > SSL Settings page, if you disable TLS protocols or ciphers, and enable SSLv3 protocol settings, the high-availability events are not generated.
  [# NSADM-36077]

• Both the nodes of a Citrix ADM high-availability pair running on VMware ESXi hypervisor might not work.
  [# NSHELP-19635]

Hybrid Multi-Cloud

• When you are creating an autoscale group if provisioning fails for one of the availability zones, the activity progress window might become unresponsive.

  Workaround:

  Refresh the page to continue.
  [# NSADM-37255]

Licensing

• When you change the time zone in License Usage from local to GMT, it does not change the custom time to GMT. And, the License Usage report is not generated.
  [# NSADM-17670]

• If you delete a license server from a Citrix ADC instance, the Citrix ADM continues to display the values for that instance. Even after the instance is restarted, the value still appears.
  [# NSADM-35400]

• When you upgrade Citrix ADM from 50.28 to 50.30, the count for entitled virtual servers become 0 whereas the default license is for 30 virtual servers. This issue occurs only when no license file found in the Citrix ADM.
  [# NSHELP-18880]

Networks

• The Citrix ADM does not display any error message when you delete a DNS domain that is used in an application.
  [# NSADM-17870]

• DNS domain names are not visible in Citrix ADM GUI immediately after an external user or a local user configures it through API.

  Workaround: Log out and log on again.
  [# NSADM-17883]

• When you try to generate the CSV report for SSL protocol, the report is not displayed with the virtual server IP address.
  [# NSADM-32522]

• In the Citrix ADM, when you try to upload and install certificates and key files on Citrix ADC instances discovered through agents, you might see an error.

  Workaround: Try uploading the certificates another time, and it might succeed.
  [# NSADM-34558]

• In Citrix ADM, when a non-nsroot user navigates to the Networks > Agents page and clicks View Details for the selected agent, the instances list might display the instances to which the user does not have access. However, when the user tries to access the instances, an error is displayed.
  [# NSADM-34794]

• When you want to create a Certificate Signing Request (CSR) by uploading the key in DER format locally, the Citrix ADM displays the key in PEM format and does not generate a CSR.
  [# NSADM-824]

Orchestration

• As an OpenStack user, you cannot change the admin_state_up to down for the load balancer, listener, pool, and health monitor.

  Note: You can still set the pool member's state as up and down. Instead of setting the entities' admin_state_up to false, you can choose to delete the entity and re-create when required.
  [# NSADM-19673]

• In OpenStack and Citrix ADC integration, when you use service package to allot partition on OpenStack Compute, after all LBaaS entities are deleted, the allotted partitions should also be deleted and the VPX instance on OpenStack compute should also get deleted. But in this build only the partitions are deleted and the VPX is not removed. That means, Citrix ADM still retains the ADC VPX instance, even though it is not used. Later if new LBaaS entities are created, new partitions are created in the retained Citrix ADC VPX instance that can be reused.
  [# NSADM-32777]

StyleBooks

• The StyleBooks compiler considers the escape characters in default values of parameters as real characters and escapes them again to preserve the characters which might result in an error.
  [# NSHELP-6257]

System

• If you have configured a Citrix ADM as SNMP trap destination for SNMP V2 protocol, and then upgrade the ADM, SSL certificates expiry trap might not get forwarded to the external manager. And, the ADM is unable to send events created with SNMP V3 to the external SNMP trap manager.

  Workaround: Delete the existing SNMP trap destination and configure it again with V2.
  [# NSADM-34198]

• Executing fsck command for verifying the integrity of the filesystem might produce inconsistent outputs on a mounted filesystem.

  Workaround: Do not run the fsck command on a mounted filesystem.
  [# NSHELP-19316]

• During the Citrix ADM upgrade the migration subsystem might crash. This issue does not cause any functionality loss.
  [# NSHELP-19637]

What's New in Previous Citrix ADM 12.1 Releases

• Ability to view client reports based on receivers in HDX Insight

  User agents represent the overall bandwidth/total bytes consumed by each receiver client in the form of a doughnut chart. Each colored segment in the chart represents one receiver client. You can click on each segment to view the details of the users using that receiver client. For more information, see https://docs.citrix.com/en-us/netscaler-mas/12-1/analytics/hdx-insight/view-reports-metrics.html#user-view-reports-and-metrics
  [From Build 49.37]
  [# 702268]

• Viewing security insight for Citrix ADC instances with an application firewall

  Citrix ADM now supports security insight from all Citrix ADC instances that have application firewall configured on them. For more information, see https://docs.citrix.com/en-us/netscaler-mas/12-1/analytics/security-insight.html
  [From Build 49.37]
  [# 708013]

• Self-diagnostic check for analytics

  Citrix ADM performs self-service diagnostic check every 12 hours to identify any license issues or configuration issues on the managed instances that are associated with the following analytics features:

  • Web Insight

  • HDX Insight

  • Gateway Insight

  • Security Insight

  • Secure Web Gateway Analytics

  The self-service diagnostic generates a diagnostic report if issues are found. For more information, see https://docs.citrix.com/en-us/netscaler-mas/12-1/analytics/self-service-diagnostic.html
  [From Build 49.37]
  [# 709970]

• Support for displaying Citrix ADC instances in high availability in Web Insight reports

  The Citrix ADM analytics reports now display reports for ADC instances that are deployed in high availability mode. Aggregated reports for instances in high availability mode is supported in all analytics. For example, in HDX insight reports, both total session launch count and total application count is displayed as a combined report instead of individual reports for each instance in the group.

  Note:

  All data previously collected before you upgraded to Citrix ADM 12.1 build 50.x continues to be displayed as independent reports for the period of time until the data persists.
  [From Build 50.33]
  [# NSADM-17899, NSHELP-5502]

• Support for EDT sessions in HDX Insight reports

  The HDX Insight displays now displays the number of EDT sessions and non-EDT sessions as part of the active sessions report. The Users table displays a detailed report of all the users in the system. Also, a new donut chart has been introduced to allow you to see bandwidth consumed by the user and also the total number of bytes based on the type of protocol used by the users.
  [From Build 50.33]
  [# NSADM-17937]

• Support for displaying both load balancing and content switching virtual servers in Web Insight report

  The Web Insight reports now displays data from load balancing virtual servers that are bound to content switching virtual servers, you can view data for both virtual servers separately. For more details, see Load balancing servers bound to content switching servers.
  [From Build 50.33]
  [# NSHELP-4263]

• Including aggregated attack time in Security Insight reports

  The Total Violations report in Security Insight displayed the attack time as “NA” if the selected duration is more than one hour. Now, if you select “1 Day” from the list, the report displays all attacks that are aggregated and the attack time is displayed in one-hour range. If you choose “1 Week” or “1 Month,” all attacks are aggregated and the attack time is displayed in one-day range.
  [From Build 50.33]
  [# NSHELP-4280]

Licensing

• Support for pooled licensing for Citrix ADM license servers deployed in high availability

  You can now assign the same license to both Citrix ADM license servers that are deployed in high availability. This is possible because the host id of the primary server is configured as the virtual host id of the secondary server whenever failover happens. Therefore, the license recognizes the same host id on both servers and gets assigned to both servers.
  [From Build 50.33]
  [# NSADM-18208, NSADM-14406]

• Support to view the bandwidth license usage report on Citrix ADM

  You can now view the usage report of the bandwidth licenses that you have uploaded in Citrix ADM, by navigating to Networks > Licenses > Virtual CPU licenses.
  [From Build 50.33]
  [# NSHELP-5342, NSADM-14321]

Networks

• Ability to send event notifications to Slack

  Earlier, in Citrix ADM GUI you had an option to send email notifications for events. You can now send an event notification to Slack channel also.

  Configure the required Slack channel by providing the profile name and the webhook URL in Citrix ADM GUI. The event notifications are then sent to this channel. For more details, see Adding event rule actions section in https://docs.citrix.com/en-us/citrix-application-delivery-management-service/networks/events/create-event-rules.html
  [From Build 49.37]
  [# 656472]

• Test button for email configuration for Citrix ADM event notifications

  While sending emails for event notifications, you might want to send a test email to test the configured settings. The “Test” button now allows you to send a test email after configuring an email server, associated distributed lists and other settings. This feature ensures that settings are working fine. For more details, see Create event rules. For more details, see Adding event rule actions section in https://docs.citrix.com/en-us/citrix-application-delivery-management-service/networks/events/create-event-rules.html
  [From Build 49.37]
  [# 684948]

• Customization of event notification email subject line

  In a large network that has many virtual servers configured, you as an admin might receive a high number of emails every day. But you might want to see the name of the affected entity in the mail popup when the mail is received so that you can determine the affected entity without having to open the email. Under Networks > Event > Rules, when you create a rule and set email notification rules, you now have an option to include some additional information such as the name of the affected entity (failure object.) For more details, see Adding event rule actions section in https://docs.citrix.com/en-us/citrix-application-delivery-management-service/networks/events/create-event-rules.html
  [From Build 49.37]
  [# 705142]

• Customizing the Subject while scheduling the export of network reports

  While scheduling network reports, you can customize the heading of the report by entering a text string in the Subject field. The report created at the scheduled time will have this string as its name. For example, for network reports originating from a particular virtual server, you can type in the subject as "authentication-reports-10.106.118.120," where 10.106.118.120 is the IP address of the monitored virtual server. For more details, see https://docs.citrix.com/en-us/netscaler-mas/12-1/networks/network-reporting.html
  [From Build 49.37]
  [# 705515]

• Role Based Access Control on GSLB domains

  You can now allow only authorized users to perform GSLB configuration using StyleBooks as RBAC is currently supported on GSLB domains also.

  Citrix ADM now supports a new entity called “DNS Domain Name.” In Citrix ADM, navigate to Networks > DNS Domain Name and add the DNS domain names entries. Navigate to System > User Administration > Groups. Define RBAC settings for a user group on selected domain names from the available list of domain names.

  This RBAC setting applies to your users when they are trying to configure GSLB using StyleBooks. The users can use only one or more DNS Domain Names that they are authorized to use.
  [From Build 49.37]
  [# 706988, 708419]

• Configurable auto license support for non-addressable virtual servers

  Citrix ADM, by default, does not automatically apply licenses to non-addressable virtual servers. For licensing non-addressable virtual servers, you must disable the auto-license option and manually select the non-addressable virtual servers. This increases your effort to manually select the non-addressable servers initially when you apply the licenses, and also when you need to select the new non-addressable virtual servers whenever they are added to your network.

  The new option in Citrix ADM under Networks > Licenses > System Licenses is “Auto-select non-addressable Virtual Servers.” Enabling this option now allows you to explicitly specify that the licensing should include non-addressable virtual servers also. For more details, see https://docs.citrix.com/en-us/netscaler-mas/12-1/licensing.html

  Note:

  Citrix ADM, by default, still does not auto select non-addressable virtual servers for licensing.

  Application analytics (App Dashboard) is the only analytics supported currently on licensed non-addressable virtual servers.
  [From Build 49.37]
  [# 707843]

• Support for HTTP and HTTPS port customization

  You can now specify non-default ports in Citrix ADM to send HTTP and HTTPS requests to a Citrix ADC CPX instance. The non-default HTTP and HTTPS ports are configured while creating a Citrix ADC Profile. For more details, see How to create a Citrix ADC Profile section in https://docs.citrix.com/en-us/netscaler-mas/12-1/configure/add-instances.html
  [From Build 49.37]
  [# 708213]

• Ability to tag Citrix ADC instances

  Tags are terms or keywords that you can assign to a Citrix ADC instance to associate some additional description about the Citrix ADC instance. Citrix ADM now allows you to associate your Citrix ADC instances with tags. These tags allow you to group, identify, and search for the Citrix ADC instances. For more details, see Create tags and assign to instances. For more details, see https://docs.citrix.com/en-us/netscaler-mas/12-1/networks/instance-management/create-tags.html
  [From Build 49.37]
  [# 708603]

• Improvements in Citrix ADC pooled capacity feature

  A few modifications have been made in the pooled licenses page in Citrix ADM for Citrix ADC VPX instances. A new set of states have been introduced while you allocate licenses in the license pool to Citrix ADC instances on demand. The states are as follows:

  -Allocated

  -Grace

  -Sync in progress

  -Partially allocated

  -Device not managed

  -Allocated. Not applied to the device

  -Connection lost

  Also, a few more details about the state of license allocation have been added to Citrix ADM. For more details, see https://docs.citrix.com/en-us/netscaler-mas/12-1/license-server/netscaler-pooled-capacity/configuring-netscaler-pooled-capacity.html
  [From Build 49.37]
  [# 709975, 711457]

• Improved functionality to search Citrix ADC instances

  Consider a scenario where Citrix ADM is managing many Citrix ADC instances. You might want the flexibility to search the inventory of instances based on some search parameters. Citrix ADM now offers two search criteria - tags and properties to search efficiently for a subset of Citrix ADC instances that qualifies the search parameters.

  Example: Consider you want to search all Citrix ADC instances that are on version 12.1 and are in the UP state. For more details, see https://docs.citrix.com/en-us/netscaler-mas/12-1/networks/instance-management/create-tags.html
  [From Build 49.37]
  [# 709997]

• Support for the autoscaling of Citrix ADC instances deployed in AWS

  The Citrix ADM autoscaling feature now supports provisioning and autoscaling of Citrix ADC instances in AWS. The Citrix ADM collects statistics (CPU usage, memory usage, throughput) from the autoscale provisioned clusters. These statistics are evaluated against the customer-configured value. Depending on whether the statistics exceed the maximum threshold or are operating below the minimum threshold, scale-out or scale-in is triggered respectively.

  The advantages of the autoscaling features are:

  - Ensures that the application is up and running all the time irrespective of traffic demands.

  - Citrix ADC instances are added and removed dynamically making to a zero-touch manual configuration.

  - DNS management is automatic.

  - Enables better cost management.

  To use the autoscale feature, you must create a site, an agent, autoscale groups and then deploy the application using StyleBooks.
  [From Build 50.33]
  [# NSADM-17998]

Orchestration

• Deploying OpenStack LBaaS configurations through StyleBooks

  In the OpenStack orchestration workflow, Citrix ADM now uses the "os-cs-lb-mon" StyleBook to deploy LBaaS configurations on Citrix ADC instances allotted to the OpenStack tenant. Using StyleBooks for configuration in OpenStack workflow provides the following benefits:

  • better visualization by providing the ability to view all the configuration objects

  • reliability through rollback

  • support for various Citrix ADC instance types (Citrix ADC HA, partitions, VPX, MPX, and others)

  • customization by using your own StyleBooks to deploy configuration for OpenStack tenants

  For more details, see https://docs.citrix.com/en-us/netscaler-mas/12-1/orchestration/integrate-with-openstack-platform/provisioning-adc-vpx-instance-on-openstack-using-stylebooks.html
  [From Build 49.37]
  [# 702345, 702340]

• Ability to enable CICO and pooled license support for OpenStack environment

  The service package page in the Orchestration feature in Citrix ADM is enhanced to provide the license that is required to be installed on the Citrix ADC instances that are created on demand. The licenses provided can be either CICO or pooled capacity license. For more details, see https://docs.citrix.com/en-us/netscaler-mas/12-1/orchestration/integrate-with-openstack-platform/license-support-for-openstack-environment.html
  [From Build 49.37]
  [# 709181]

• Ability to route traffic from Citrix ADC to back-end servers through the client network

  In the OpenStack orchestration workflow, Citrix ADC instances are dynamically bound to the load balancer or client networks and member or server networks. In certain deployments servers are also reachable through client networks and can be routed through the client gateway. In such cases, the Citrix ADC instances need not be bound to server networks, but they need to be bound only to client networks. Citrix ADM then configures the Citrix ADC instance to client networks by adding a SNIP in that network, and will further add a default route to the client network gateway. This enables the instance to reach the servers through the client gateway. For more details, see https://docs.citrix.com/en-us/netscaler-mas/12-1/orchestration/integrate-with-openstack-platform/preconfiguration-tasks-mas-openstack.html#enabling-traffic-from-citrix-adc-instances-to-backend-servers-through-client-network
  [From Build 49.37]
  [# 709950]

StyleBooks

• Back-end SSL Protocol support by SharePoint StyleBook

  SharePoint StyleBook now supports SSL to bind service groups (SharePoint application servers) to the target load balancing virtual servers. For more details, see https://docs.citrix.com/en-us/netscaler-mas/12-1/stylebooks/business-application-stylebooks/microsoft-sharepoint-stylebook.html
  [From Build 49.37]
  [# 706507]

• Using StyleBooks to create load balancing virtual servers with an application firewall

  You can now automate the configuration of Citrix ADC WAF (Web Citrix Web App Firewall) feature using the new default WAF StyleBook in Citrix ADM. This StyleBook allows users to create a load balancing virtual server with associated App Firewall policies and settings.

  Note: Before you can configure App Firewall signatures, you must create the signatures objects in the Citrix ADC instance from the appropriate default signatures object template. You cannot configure or modify the default signatures objects through the WAF StyleBook.
  [From Build 49.37]
  [# 708597]

• Ability to migrate existing config packs created through application dashboard to a different StyleBook

  Citrix ADM now allows you to migrate (or upgrade) an existing configpack to a new StyleBook for all applications created using StyleBooks in application dashboard. Click "Define Custom App" to view the configpacks created. Click "Migrate Configpack" and select the new StyleBook from the "Choose target StyleBook for migration" page. For more information on how to migrate configpacks, see https://docs.citrix.com/en-us/citrix-application-delivery-management-service/stylebooks/how-to-create-custom-stylebooks/migrate-configpack.html
  [From Build 49.37]
  [# 717133]

• GitHub import and sync for StyleBooks

  You can now use the “Repositories” feature in Citrix ADM to directly import and sync StyleBooks from GitHub repositories. You can sync StyleBooks from multiple GitHub repositories. StyleBooks that are created in GitHub and imported from GitHub repositories are still dependent on Citrix ADM RBAC policies in the same way as StyleBooks imported manually. You can configure a GitHub repository using either GitHub username and password or an API token.
  [From Build 50.33]
  [# NSADM-15841, NSADM-3622]

System

• Improvements to Citrix ADM user interface

  Citrix ADM user interface has been updated to help you accomplish your tasks more easily and conveniently. Some of the major changes that you will see are as follows:

  • Some of the action buttons have been repositioned.

  • The instances overview page is removed. Citrix ADC VPX, MPX, CPX, SDX instances are now grouped under Citrix ADC page, and you can access them as different tabs. Similarly, Citrix ADC SD-WAN WO and SE/EE instances are grouped.

  • On SSL Dashboard page, SSL Audit trails has been renamed as "SSL Audit Logs."

  • On Network Functions page, "virtual servers, services, service groups, and servers" sub nodes now appear as tabs for each selected network functions such as Load Balancing, Content Switching, Cache Redirection, Global Server Load Balancing (GSLB), Authentication, and Citrix Gateway.

  • You can now create IP blocks by navigating to Analytics > Settings > IP Blocks.

  • A table can spill over to multiple pages because Citrix ADM displays only a definite number of row entries that you have selected in one page. Earlier you were able to sort row entries only on the current page. The other pages never displayed sorted entries. You can now sort the table in any page, and all the pages of that table will display the sorted results.
  [From Build 49.37]
  [# 710010]

• Configuring customer identity on Citrix ADM

  Citrix proactively collects statistics on your ADM deployments to understand your deployment usage and deployment scale. The statistics collected on health, status, and usage pattern of the ADM deployment on your premises allows Citrix to provide an enhanced user experience. To utilize this feature, create a customer identity on Citrix Cloud and provide the user details on ADM.
  [From Build 50.33]
  [# NSADM-18107]

• Support to shut down Citrix ADM from the user interface

  You can navigate to System > System Administration and click on Shut Down Citrix ADM to completely shut down Citrix ADM. Note: Once you shut down Citrix ADM, be aware that you can start Citrix ADM again only from the hypervisor where you have installed it.
  [From Build 50.33]
  [# NSADM-18372]

• Support for message for the day

  You can now create a welcome message that is displayed when you logon to Citrix ADM. You can use this feature to set reminder messages for yourself or the user who logs on to Citrix ADM.
  [From Build 50.33]
  [# NSHELP-5454, NSHELP-5153]

• Ability to upload MAS collector bundle to CIS directly

  You can now upload the technical support files to Citrix Insight Services (CIS) website by running a script on the ADM console.
  [From Build 50.33]
  [# NSHELP-6278]

Fixed Issues in Previous Citrix ADM 12.1 Releases

• Citrix ADC instance might occasionally crash when there is a toggle between enabling/disabling AppFlow configuration.
  [From Build 49.37]
  [# 702155]

• The combined graphical view in HDX insight shows incorrect time zone.
  [From Build 49.37]
  [# 703906]

• Aggregation of Gateway Insight fails if HDX Insight is not enabled, because the the report time was not getting set as required. This build fixes this issue.
  [From Build 49.37]
  [# 709233]

• Citrix ADM upgrade from 12.0 to 12.1 fails for this scenario: the database summarization configuration (days to persist hourly data) is set for more than ten days (default is one day) for Analytics.
  [From Build 49.37]
  [# 710501]

• Agent registration fails because of the Unicode characters seen in the location details.
  [From Build 49.37]
  [# 711737]

• When you edit a previously created IP block in the Configure IP Blocks page under Analytics > Settings by changing the city, region, and country, and when you try to edit the settings again, the Configure IP Blocks page displayed the name of the previous city. This build fixes this issue.
  [From Build 49.37]
  [# 712110]

• In some cases, the Citrix Gateway appliance dumps core during the authentication if the following conditions are met:

  - The Citrix ADC appliance is configured for nFactor authentication.

  - The Gateway Insight feature is enabled for the appliance.
  [From Build 49.37]
  [# 713011, 713168]

• You cannot configure AppFlow on Citrix ADC instances when the virtual server name has "blank" spaces.
  [From Build 49.37]
  [# 713133]

• It is not possible to see information in Web insight when you access Citrix ADM with “read-only” privileges.
  [From Build 49.37]
  [# 713404]

• Citrix ADM analytics might not show web insight reports consistently. Delay in accessing GeoMap location sometimes delays the aggregation of analytics reports for web insight.
  [From Build 49.37]
  [# 713648]

• Citrix ADM does not display HTTP transactions that happen without user agent in Web Insight reports. With this fix you will be able to see all details of these transactions in ADM.
  [From Build 50.39]
  [# NSADM-13876]

• You can disable the collection of afdecoder logs by creating the disable_refresh_interval_config file in the /mpsconfig folder in the Citrix ADM file system.
  [From Build 50.33]
  [# NSADM-30159]

• On Application dashboard, value in some of the parameters such as Data Volume might get truncated when the string length is long.
  [From Build 50.43]
  [# NSADM-31818]

• When you replace the default Geo database files with other customised database files you might find that the mas_afdecoder crashes. Citrix recommends that you should first check for the Geo database files in ADM folders.
  [From Build 50.39]
  [# NSHELP-18150]

• You might not be able to view the Security Insight reports in Citrix ADM if the afdecoder has crashed.
  [From Build 50.39]
  [# NSHELP-18585]

• Application health dashboard nitros triggered from Citrix ADM might fail if invalid arguments are passed.
  [From Build 50.39]
  [# NSHELP-18620]

• Consider that you want to configure analytics for virtual servers for an ADC instance in Citrix ADM by navigating to Networks > Instances. You can then select an instance and then select Configure Analytics from the action list. When you search for any virtual server name or by IP address and then clear the search from Configure Analytics page, the page lists the virtual servers from all the available ADCs that are managed by ADM.
  [From Build 50.39]
  [# NSHELP-18623]

• When you try to refresh the Application Dashboard, the performance becomes slow if there are large number of virtual servers configured in Citrix ADM and also if RBAC is implemented on these virtual servers.
  [From Build 50.39]
  [# NSHELP-18646]

• When Citrix ADM manages two Citrix ADC gateways that have the same name, Citrix ADM fails to differentiate the sessions that belong to these Citrix ADC gateways.
  [From Build 50.39]
  [# NSHELP-18716]

• The application dashboard does not display proper metrics in app summary panel for applications configured on Citrix ADC high availability pair.
  [From Build 50.39]
  [# NSHELP-18733]

• The application dashboard does not display correct data, because the CPU and memory information from the node is not appended to all virtual servers.
  [From Build 50.39]
  [# NSHELP-18736]

• In Citrix ADM, the afdecoder process might crash because of any one of the following reasons:

  - Bad format code

  - Either Citrix ADM or Citrix ADC sends the report in wrong date and time format
  [From Build 50.39]
  [# NSHELP-18761]

• When you navigate to Users > Transactions, you might not see the transaction report for more than 0.1 million transactions.

  This issue is fixed.
  [From Build 50.39]
  [# NSHELP-18785]

• AppFlow is not supported on Cache Redirection virtual server. Therefore the "Enable AppFlow" option is removed for CR virtual server in Citrix ADM.
  [From Build 50.39]
  [# NSHELP-18817]

• Citrix ADM now periodically runs AppFlowParamConfig and EnableFeatureAppFlow commands for each partition on the ADC instances, if the ADC instances are deployed in high availability mode.
  [From Build 50.33]
  [# NSHELP-18928]

• Threshold Email Notification template had limited information on the breach. This release the Email Notification template includes the breach location information with the breach value.
  [From Build 50.43]
  [# NSHELP-6093, NSADM-15511, NSHELP-18719]

• If Citrix ADM is configured to receive traffic from ADC instance through the IPFIX protocol, then there is memory leak observed in mas_afdecoder process. If the mas_afdecoder process memory consumption continues for a longer period of time, it might affect the overall system performance.
  [From Build 50.33]
  [# NSHELP-6352]

• In HDX insight > Users, different Client IP address is displayed in the session selected from the Current Sessions table than the IP address displayed in the Current Sessions table.
  [From Build 50.43]
  [# NSHELP-6395]

• When you navigate to Users > Transactions, you might see that the transaction details under the Users tab are scrambled and do not appear legibly.
  [From Build 50.39]
  [# NSHELP-6399]

• If you are a user with "read-only" permissions, you cannot see the diagnostic related icons in any of the analytics pages.
  [From Build 50.33]
  [# NSHELP-6407]

• When you provide a name to the virtual server, both Citrix ADM and ADC instance adds a string of characters to the name as a prefix to generate the required AppFlow. Ensure that the name of the virtual server do not exceed 60 characters, as this might lead to unwanted behaviour in ADC instance.
  [From Build 50.39]
  [# NSHELP-6520]

Applications

• Citrix ADC exports "multiple application terminate" records for the same application. This causes Citrix ADM afdecoder process to crash.
  [From Build 49.37]
  [# 709462]

• If a GSLB virtual server is part of any custom application, Citrix ADM doesn't display the statistics correctly for the newly added GSLB server.
  [From Build 49.37]
  [# 715639]

• Citrix ADM does not display the number of transactions and the data flow volume for GSLB applications on the application dashboard.
  [From Build 49.37]
  [# 716878]

• Citrix ADM doesn't display any information for virtual servers related to applications created on ADC instances deployed in high availability.
  [From Build 49.37]
  [# 716906]

• Citrix ADM GUI becomes unresponsive while enabling AppFlow for multiple virtual servers in some specific cases. This issue is typically seen when you select multiple types of load balancing servers that includes TCP and if TCP is at the beginning of the list.
  [From Build 50.43]
  [# NSADM-35039]

• On application dashboard info panel and application detailed dashboard pages, data under "Transactions" title were showing differently. It was cumulative data on one place and transaction rate at the other place. With this fix, the data is now displayed correctly as total transactions and the Key Metric trends section show the transactions per second.
  [From Build 50.39]
  [# NSHELP-18799]

• If a GSLB virtual server is part of any custom application, Citrix ADM doesn't display the statistics correctly for the newly added GSLB server.
  [From Build 50.33]
  [# NSHELP-5648]

High Availability

• When a Citrix ADC instance in high availability mode is assigned to a user group, and if the instance pair fails over, the instance is no longer assigned to the user group.
  [From Build 49.37]
  [# 709202, 709126]

• When there is no communication between both the nodes due to downtime in the network link, the primary node continues to operate as primary. But the secondary node takes over as primary because of the failure to receive heartbeats, and both the nodes would run their database instances. As there is no heartbeat exchange for over 180 seconds, both the nodes consider themselves to be the primary node. Both nodes act as active nodes and run their instances of the database. This is known as a split-brain scenario.
  [From Build 49.37]
  [# 709770, 709768]

• After a manual failover, Citrix ADM doesn't receive SNMP v3 traps. This is because, the configuration changes in the Citrix ADC instance are not complete for the new primary node in the high availability, and the Citrix ADC instance is not sending the traps to Citrix ADM after a failover.
  [From Build 49.37]
  [# 709802]

• If you configure one node in a pair of Citrix ADC instances in high availability mode with the IP address in the range 171.31.200.x, this pair of Citrix ADC instances is not discovered by Citrix ADM.
  [From Build 49.37]
  [# 710589]

• When you upgrade the disaster recovery node, communication between the high availability pair and disaster recovery node breaks.
  [From Build 50.43]
  [# NSHELP-19223]

• The communication between the HA pair and DR node is broken. The Primary node is displayed with the error message “Database streaming channel is broken between HA nodes”.
  [From Build 50.43]
  [# NSHELP-19260]

High availability

• When you upgrade Citrix ADM from 12.1 release 49.31 build to 49.34 build, database streaming might stop syncing between the Citrix ADM nodes that are deployed in high availability.
  [From Build 49.37]
  [# 717049]

• Consider that there is a forced failover between two Citrix ADM servers deployed in high availability, or that the primary node is down. You then see a message that the database streaming channel is down between the two ADM nodes. But Citrix ADM still displayed the message even after the nodes are synced with one another. With this fix, you will now see a new message that says the database replication lag is now normal.
  [From Build 50.39]
  [# NSADM-13889]

• When the secondary node of two Citrix ADM servers in high availability is down, you cannot perform manual failover in ADM.
  [From Build 50.39]
  [# NSADM-30424]

• The "manifest_taas.xml" file does not get updated with latest information for ADM secondary node.
  [From Build 50.39]
  [# NSADM-30546]

• When you deploy a pair of Citrix ADM servers in high availability, you can monitor only the primary ADM. Currently there is no support to monitor the secondary ADM.
  [From Build 50.39]
  [# NSHELP-18432]

• When the Citrix ADM agent attached to a pair of ADM servers deployed in high availability becomes inactive, the instances managed by that agent is shared among the active agents. The ADM servers might then split into two and get attached to two different agents.
  [From Build 50.39]
  [# NSHELP-18614]

• Citrix ADM UI does not display both SSL Keys and Certificates files for both primary and secondary nodes of ADM servers high availability pair. This issue is now fixed.
  [From Build 50.39]
  [# NSHELP-18637, NSADM-33452]

• Suppose you upgrade a pair of Citrix ADM servers deployed in high availability to 12.1-50.30. When you try to log on, you might see an error message that says you are unable to connect to the remote node.
  [From Build 50.39]
  [# NSHELP-18657]

• Citrix ADM server is receiving multiple requests to configure disaster recover (DR), as ADM is now taking more than three minutes to configure DR.
  [From Build 50.39]
  [# NSHELP-18746]

• Citrix ADM high availability monitoring script has failed because of the missing or corrupted high availability configuration file.
  [From Build 50.39]
  [# NSHELP-18800]

• In Citrix ADM high availability setup, the SSL cipher fails to synchronise between primary and secondary node.
  [From Build 50.39]
  [# NSHELP-18913]

• Citrix ADM in high availability goes to split-brain state intermittently after upgrade from 12.1 48.18 build to 12.1 49.23 build.

  During upgrade, if the ADM subsystems do not start within three minutes, failover occurs, and this might lead to split-brain state.
  [From Build 50.33]
  [# NSHELP-5680]

• After upgrading Citrix ADM high availability from 12.0 to 12.1, the duplicate scheduled jobs are still found in Citrix ADM.
  [From Build 50.39]
  [# NSHELP-5933]

Licensing

• When auto licensing is off, and when you try to manually remove the license from some of the virtual servers, the warning message might not indicate the correct number of virtual servers that are not licensed.
  [From Build 50.43]
  [# NSADM-34767]

• When you upgrade Citrix ADM from 50.28 to 50.30, the entitled virtual servers count become 0 where the default license is for 30 virtual servers. This issue occurs only if there is no license file found in Citrix ADM.
  [From Build 50.39]
  [# NSHELP-18880]

• In Citrix ADM, the Licensing page shows encoded character on the notification message. This issue is now fixed.
  [From Build 50.39]
  [# NSHELP-18908]

• When you log on, Citrix ADM displays alerts for licensing of those virtual servers that are discovered in Citrix ADM, but are not managed.

  Note: Citrix ADM displays alerts only when auto selection of virtual servers is enabled and only if the number of discovered virtual servers is more than 30.
  [From Build 50.33]
  [# NSHELP-5614, NSADM-15893]

• 1. When a particular virtual server is configured with DNS server which can correspond to multiple IPs, Citrix ADM is not able to discover the virtual servers.

  2. When a virtual server has some non-English characters in the comment or any other field, ADM returns an error and does not discover virtual servers for that instance.
  [From Build 50.39]
  [# NSHELP-6557]

Networks

• There might be a situation where a table spills over to multiple pages because Citrix ADM displays only 25 row entries in one page. Earlier you were able to sort row entries only on the current page. The other pages never displayed sorted entries. You can now sort the table in any page, and all the pages of that table will display the sorted results.

  Note: This feature works only if the number of records in a table is less than 25,000.
  [From Build 49.37]
  [# 689564, 688717, 686689, 708454]

• If a Citrix ADC VPX instances on the Citrix ADC SDX platform is discovered independently of the SDX, and if you later configure the Citrix ADC SDX platform, the already discovered VPX should be correctly linked to the SDX.
  [From Build 49.37]
  [# 699718]

• Reports are not visible after Citrix ADM fails to respond when the EventFilterManager::execute_action command is run.
  [From Build 49.37]
  [# 701430, 710050]

• Duplicate entries are displayed when you filter all listed entries in network function such as load balancing, content switching, cache redirection, and others.
  [From Build 49.37]
  [# 704095]

• Though you can see system notifications about "userlogout," you might not receive any email notifications.
  [From Build 49.37]
  [# 704344]

• The Networks event digest report data is getting truncated due to formatting issues.
  [From Build 49.37]
  [# 704980]

• You cannot configure AppFlow on virtual servers if Citrix ADM is configured with any interface other then 0/1.
  [From Build 49.37]
  [# 705330]

• Consider a scenario where you have RBAC access to only Networks, Analytics, and System nodes. The default behavior is that the first node in the navigation pane, that is, Networks should be the landing page when you access Citrix ADM. But now the Analytics node is the landing page.
  [From Build 49.37]
  [# 705347]

• Do not include white spaces in configuration audit template names.
  [From Build 49.37]
  [# 708003]

• When you select a CB5000 Citrix ADC SD-WAN instance and click Current Configuration, Citrix ADM displays a message that says there is an error in retrieving CloudBridge Current Config. This build fixes this issue.
  [From Build 49.37]
  [# 708771]

• When you add Citrix ADC SD WAN WO instance to Citrix ADM, SNMP connection is not successful, and the GUI becomes unresponsive.
  [From Build 49.37]
  [# 709146]

• Though you disable the auto selection of virtual servers for licensing feature, it is enabled by default after upgrading to 12.1
  [From Build 49.37]
  [# 710490]

• SNMP v3 based event reporting does not work after upgrading Citrix ADM to version 12.1. Citrix recommends the following workaround for the Citrix ADC instances in version 12.1 build 48.13 added in Citrix ADM.
  [From Build 49.37]
  [# 710564, 673744]

• You cannot schedule exporting of reports in Network Reporting because the export input parameter for the external user list exceeds the limit of 4096 chars.
  [From Build 49.37]
  [# 710872]

• In accordance with the new naming conventions, VPN in Configure Analytics view is renamed as "Citrix Gateway" as seen in the Citrix ADM user interface.
  [From Build 49.37]
  [# 711012]

• While creating configuration jobs using the master config template, you might have to upload the same config file multiple times after editing the file. You can successfully upload the file the first time. Later uploads fail without any user notification.
  [From Build 49.37]
  [# 711593]

• Consider a situation when you configure an event rule with the action as "send trap." If there are multiple events that match the above rule, and when Citrix ADM attempts to send multiple traps at the same time, the event crashes. This is due to multithreading process failure.
  [From Build 49.37]
  [# 712016]

• Citrix ADM does not discover the service group members when the server members are configured with same server name but different port numbers.
  [From Build 49.37]
  [# 712022]

• Auto-rollback in Citrix ADM doesn't happen when you run wrong commands. For example, "rm" commands. You get a "null" if rollback command is not available.
  [From Build 49.37]
  [# 713923]

• If you use the name of an existing configuration template as the name of the configuration job, you might not be able to edit the job later.
  [From Build 49.37]
  [# 713926, 713927]

• If you add a Citrix ADC SDX of version that is of 11.0 or lesser release in Citrix ADM, then the dashboard of SDX from Citrix ADM UI displays an error.
  [From Build 49.37]
  [# 715803]

• Citrix ADM performance subsystem reports high CPU utilization that might impact the data points in network reporting dashboard.
  [From Build 49.37]
  [# 716235, 716602, 716917, 717603]

• When you navigate to Networks > Events, the events are not displayed in the order for the first time. If you click the Date column header, the events appear chronologically sorted.
  [From Build 49.37]
  [# 716615]

• When you export a dashboard or schedule an export report on the Network Reporting Dashboard page, the report is generated based on the duration and not the start and end time.
  [From Build 50.39]
  [# NSADM-20017]

• When you export a dashboard or schedule an export report on the Network Reporting Dashboard page, the report is generated based on the duration and not the start and end time.
  [From Build 50.33]
  [# NSADM-20017]

• The default task log is sorted in the descending order based on the start time column.
  [From Build 50.33]
  [# NSADM-29891, NSADM-30011]

• Citrix ADM fails to upload a file in Config Job or Audit template if the filename is same as the one which is already uploaded. This failure may occur if you don't have write permission for the file.
  [From Build 50.33]
  [# NSADM-30009]

• When you delete and create a new partition in an ADC instance, the partition ID is not updated in the managed_device table.
  [From Build 50.39]
  [# NSADM-30367]

• You were unable to create clusters of ADC instances from Citrix ADM as ADM was unable to locate the instances. With this fix, you can create clusters in ADM.
  [From Build 50.39]
  [# NSADM-30527]

• When you search for configuration templates by using the Type search criteria, Citrix ADM displays True or False. Note that True = Default config templates and False = Custom config templates. You must choose accordingly.
  [From Build 50.43]
  [# NSADM-34802]

• When you create an event rule with Suppress Action, for instances that are discovered through agents, the events are getting suppressed even after the scheduled time expires.
  [From Build 50.43]
  [# NSADM-35023]

• When you select the “Attach Site” option in the "Add Agents" page, Citrix ADM does not update the site for the instance which belongs to that site or agent.
  [From Build 50.43]
  [# NSADM-35049]

• Slack profile is not visible in the Config Job module while sending report to slack channel.
  [From Build 50.43]
  [# NSADM-35079]

• Navigate to Network Functions > Load Balancing > Service Groups. In the Service Groups tab, enabling or disabling action for a selected service fails.
  [From Build 50.43]
  [# NSADM-35183, NSADM-32214]

• When you edit an existing configuration job, you might see that the configuration commands are not saved. With this fix, the commands are saved and you can edit the commands in the configuration job editor.
  [From Build 50.39]
  [# NSHELP-18427]

• With this fix, you cannot terminate the configuration jobs that are in execution, if you select the "Ignore error and continue" option for command failure execution mode.
  [From Build 50.39]
  [# NSHELP-18433]

• In Networks > Configuration audit, there might be a situation when you click on instances in the “Top 10 Instances by Configuration Change” section, ADM might not show any data for that instance. Also, when you select a particular period, for example, “daily” and then select an instance in the “Top 10 Instances by Configuration Change” section, ADM might show data for a different period.
  [From Build 50.39]
  [# NSHELP-18452]

• In the Configuration Audit page, when you hover on the host name or IP address, the hover text doesn’t display the full host name or IP address.
  [From Build 50.39]
  [# NSHELP-18470]

• Event digest reports are not generated when there are huge entries in database.
  [From Build 50.39]
  [# NSHELP-18617]

• If an agent is configured with Citrix ADM and if Citrix ADM is upgraded to 12.1 release 50.x build, the active session in HDX insight is incorrectly displayed.
  [From Build 50.39]
  [# NSHELP-18674, NSHELP-18983, NSHELP-19121]

• When an ADM agent goes down, though you can reassign the ADC instances to other agents, the reconfiguration of policies on the instances might fail intermittently. ADM will generate notification under System events for such cases.
  [From Build 50.43]
  [# NSHELP-18760]

• Earlier when you upgraded SSL certificate, you had to provide the format of the certificate. This issue is now fixed. Citrix ADM automatically retrieves the format and uses it to upgrade the certificate.
  [From Build 50.39]
  [# NSHELP-18763]

• You might see a difference in behaviour between ADM API and ADM GUI, when you enable or disable the event rule.

  This issue is fixed.
  [From Build 50.39]
  [# NSHELP-18767]

• When you upgrade Citrix ADM, the master configuration job might not work as expected.

  This issue is fixed.
  [From Build 50.39]
  [# NSHELP-18769]

• When you log on to Citrix ADM as an external user (LDAP) authorized for few devices and few applications, you should be able to see only the authorized virtual servers. But currently, all the services and service groups of authorized devices are displayed.
  [From Build 50.39]
  [# NSHELP-19011]

• When you tag an instance, ensure that you are not using restricted keys in the Key and Value field. For example, you can use Key=Country and Value=US. But using Key=Region and Value=US is not allowed.
  [From Build 50.39]
  [# NSHELP-19047]

• In configuration audit, ADM is unable to create a configuration audit report and send through email.
  [From Build 50.43]
  [# NSHELP-19089]

• In Configuration Editor, when a non nsroot user drags the configuration template from the Configuration Source pane to the command field the configuration job displays an authorization error.
  [From Build 50.43]
  [# NSHELP-19143]

• While creating or configuring an instance group, GUI might display the IP addresses of high availability Citrix ADC instances twice. Selecting any one IP address adds both the instances to the instance group.

  This fix applies for creating a new instance group. For the groups that are created before upgrading, you must remove the duplicate entries from the group.
  [From Build 50.43]
  [# NSHELP-19176]

• When you restore a standalone ADM or HA pair ADM, the SSL ciphers are not getting restored as expected.
  [From Build 50.43]
  [# NSHELP-19284]

• Citrix ADM polls SSL certificate and configuration audit twice. This issue is fixed and now polls once for every cycle.
  [From Build 50.43]
  [# NSHELP-19377]

• When the SNMP option is enabled on the partition of an instance and the Citrix ADC configuration is not saved, the SNMP configuration is lost and SNMP traps in Citrix ADM will disappear after restarting the instance.

  The fix applies only for the newly added instances or partitions. Ensure you have executed the “set snmp option -partitionNameINTrap ENABLED” command on all Citrix ADC partitions and the configuration is saved.
  [From Build 50.43]
  [# NSHELP-19384]

• When you are creating an event rule, you can add new trap destinations. But if yo modify the newly added trap destination, it might get removed from the list.
  [From Build 50.33]
  [# NSHELP-5625]

• Citrix ADM performance subsystem crashes every few hours and this has an impact on the network reporting.
  [From Build 50.33]
  [# NSHELP-5628, NSADM-15847, NSHELP-5519, NSHELP-5522]

• When you configure two event rules that corresponds to the same event, but have different event ages, Citrix ADM considers only the rule that has a lesser event age configured on it. With this fix, Citrix ADM considers both event rules.
  [From Build 50.33]
  [# NSHELP-5638]

• Statistics of virtual servers are not displayed if the virtual servers are part of Citrix ADC instances that are deployed in high availability.
  [From Build 50.33]
  [# NSHELP-5650]

• Syslog messages are displayed in multiple pages in Citrix ADM. When you search for Syslog messages in one page by entering a keyword, the same search results are not retained when you move to another page. You have to search again by entering the same keyword. With this fix, Citrix ADM displays the result of the search in all pages.
  [From Build 50.33]
  [# NSHELP-5652]

• Though you can upload any certificate or certificate key file from your local storage system to Citrix ADM, the “read” permissions for such files are not retained by Citrix ADM. When such files are uploaded by Citrix ADM to respective Citrix ADC instances, ADC displays such files as invalid files.
  [From Build 50.33]
  [# NSHELP-5842]

• Intermittently, Citrix ADM might miss collecting data points. This might affect the daily, weekly or monthly reports.
  [From Build 50.33]
  [# NSHELP-5856]

• Citrix ADM fails to process any SNMPv3 packets received from the ADC instance intermittently. This failure can occur after upgrading the Citrix ADC instance or Citrix ADM itself, or rebooting the ADC instance. Such failures can occur because invalid memory (freed memory) is used for some other memory allocation.
  [From Build 50.33]
  [# NSHELP-5880]

• Title header information was not correct in the generated config audit report because of the incorrect label on the exported report. With this fix, you see the correct title in the config audit reports.
  [From Build 50.39]
  [# NSHELP-5897]

• The vsvr_state_timestamp column in the exported CSV report of Network Functions does not display the time stamp in date format as in other columns of the same report. With this fix, the vsvr_state_timestamp column shows the time in the correct date format.
  [From Build 50.39]
  [# NSHELP-5903]

• Exported configuration jobs from Citrix ADM appear in a single line json file.
  [From Build 50.39]
  [# NSHELP-6229]

• In Networks > Configuration Audit, if you click "Poll Now" and start polling for all instances, the progress message was displayed incorrectly. This issue was occurring when the secondary instance was skipped.
  [From Build 50.39]
  [# NSHELP-6233]

Orchestration

• Citrix ADM displays an unknown system error when a service package is created for the first time for OpenStack. This error occurs when tenants are being assigned to the service package.
  [From Build 49.37]
  [# 709947]

• When you add an extra management IP (floating public IP) address during Citrix ADC VPX high availability deployment, you had to perform a forced failover and then rediscover the instances from Citrix ADM. With this fix, a forced failover and rediscovering the instances is not necessary and you can deploy configurations on OpenStack.
  [From Build 50.33]
  [# NSHELP-5686]

• OpenStack does not concurrently process multiple requests from multiple tenants.
  [From Build 50.33]
  [# NSHELP-5695, NSHELP-5564]

StyleBooks

• If there is an error while importing a StyleBook in 'raw' format, the scroll bar in the StyleBook editor stops working. Sometimes, the scroll bar doesn't work after deleting a StyleBook.
  [From Build 49.37]
  [# 710372]

• Citrix ADM displays an error message that says "Invalid format found. Upload .yaml files" when you earlier tried to upload a valid .yaml file using Chrome or Firefox browser. This issue is fixed, and now you can upload valid .yaml files from Chrome or Firefox browser.
  [From Build 49.37]
  [# 716670, 716466, 716693]

• Citrix ADM displayed an error message that says "No JSON Object Decoded" when an externally authenticated user creates a custom application using StyleBooks. This issue is fixed, and an external user can now create custom applications using StyleBooks.
  [From Build 49.37]
  [# 716793]

• Citrix ADM displays an error message that says "Invalid format found. Upload .yaml files" when you earlier tried to upload a valid .yaml file using Chrome or Firefox browser. This issue is fixed, and now you can upload valid .yaml files from Chrome or Firefox browser.
  [From Build 50.33]
  [# NSADM-18097, NSADM-16828, NSHELP-5543]

• A few StyleBooks that have a bigger YAML definition are intermittently not rendering correctly on Chrome browser.
  [From Build 50.39]
  [# NSHELP-18652]

• As an externally authenticated user, you were earlier able access the configpacks created using Stylebooks that you are not authorized to use. The issue has been fixed in this release.
  [From Build 50.43]
  [# NSHELP-19274]

• End of line characters (“\r\n”) appearing at the end of string values are incorrectly stripped.
  [From Build 50.33]
  [# NSHELP-5662]

• Citrix ADM displayed an error message that says "No JSON Object Decoded" when an externally authenticated user creates a custom application using StyleBooks. This issue is fixed, and an external user can now create custom applications using StyleBooks.
  [From Build 50.33]
  [# NSHELP-5664]

• Passwords should be obfuscated in "dry-run" and "objects created" window in GUI.
  [From Build 50.39]
  [# NSHELP-6289]

System

• When you attempt to restore Citrix ADM, it may fail to respond, and the following error is displayed: "Restore exception: File access error: directory not empty: /var/mps/tenants/root/device_backup​" when restore is attempted.
  [From Build 49.37]
  [# 705132]

• To defend against ClickJacking attacks, configure a list of allowed hosts. The content security policy (CSP) frame-ancestors and X-Frame-Options are not included in the whitelist. Add them explicitly to the whitelist.
  [From Build 49.37]
  [# 706431, 705731]

• When you try to connect to Citrix ADC instances using SSH, the Citrix ADM subsystem crashes. This is fixed in this build.
  [From Build 49.37]
  [# 707100]

• Citrix ADM fails to prevalidate the Citrix ADC instance if the NTP details are added in rc.netscaler file. You can now select those Citrix ADC instances and remove them while upgrading the instances.
  [From Build 49.37]
  [# 708466]

• When you upgrade Citrix ADM from 12.0 to 12.1, only one non-default site is preserved, and the rest are deleted. You must create the sites again. There is no workaround for this issue.
  [From Build 49.37]
  [# 710509]

• Certificates that have passphrase in them have difficulty connecting to the database.
  [From Build 49.37]
  [# 710876]

• When a Citrix ADC instance is removed from Citrix ADM, the backup files associated with the instance are not removed.
  [From Build 49.37]
  [# 711302]

• In Citrix ADM, auto purging of data in the database does not free up disk space.
  [From Build 49.37]
  [# 711405]

• While upgrading Citrix ADM to 12.1-48.18, the tenant_id in some of the entries in a job_schedule table in the database does not get updated. The jobs in this job_schedule table also include a job with job name -> "DeviceBackupSchedule" which is responsible for performing the automatic back up from NS instances. As the tenant_id is not present against this job in the table, the automatic back up is not working.
  [From Build 49.37]
  [# 712073, 714304]

• Citrix ADM might fail to create or edit a user group when you try add more than 500 applications in the group. This is specifically noticed when the name of the application is more than 65536 characters.
  [From Build 49.37]
  [# 716102]

• You cannot perform a global poll on all virtual servers and services when you have "read-only" access permission. But, Citrix ADM doesn't display any error message that says you are not authorized to perform this action until the last step in that task.
  [From Build 50.33]
  [# NSADM-14885]

• The Task Log counter in System > Diagnostics now displays the accurate count of task logs.
  [From Build 50.33]
  [# NSADM-29895]

• While migrating during build upgrade, old entries such as AppFlowParamConfig and EnableFeatureAppFlow in System -> Diagnostics -> Task Logs are removed.
  [From Build 50.33]
  [# NSADM-30157]

• UI enhancement for cloud Customer Identity page load time.
  [From Build 50.33]
  [# NSADM-30161]

• When you access Citrix ADM using a floating IP address, Citrix ADM responds to the request using primary IP address which causes an issue in SNMP manager.
  [From Build 50.43]
  [# NSADM-30401]

• You might see errors in saving the kernel code dump on the additional hard disk that you had attached to Citrix ADM VM. With this fix, all core dump files are saved in the additional hard disk.
  [From Build 50.39]
  [# NSADM-32975]

• Citrix ADM now provides an option of delay for graceful disabling of ADC server objects.
  [From Build 50.39]
  [# NSADM-33953]

• When you use Citrix ADM to upgrade firmware for ADC MPX instances, during pre upgrade check, ADM shows an incorrect "Device not configured" error message.
  [From Build 50.39]
  [# NSHELP-18402]

• Citrix ADM agent crashes randomly because of multi-threading issues while sending mail notifications.
  [From Build 50.39]
  [# NSHELP-18439]

• This issue is noticed after you upgrade to Citrix ADM release 12.1 build 50.28. Consider that you navigate to System > User administration > Group, and create a user group. There, you first unselect all options in the Authorization tab and manually select a few instances and complete the creation of the group. When you later edit the same group and select the Authorization tab, the instances are no longer displayed.
  [From Build 50.39]
  [# NSHELP-18442]

• Citrix ADM becomes inactive because of uncompressed PostgreSQL log files with an incorrect file permission.
  [From Build 50.39]
  [# NSHELP-18448]

• Occasionally you might see that the CPU usage is 100% when you navigate to System > Diagnostics > Task Log and it takes a longer time to complete the first query. This issue is because of the frequent AppFlow configurations and broken pruning job. 
  [From Build 50.39]
  [# NSHELP-18449]

• Citrix ADM service subsystem crashes after you upgrade to 12.1-50.30. This issue occurs intermittently when there are many concurrent requests.
  [From Build 50.43]
  [# NSHELP-18595]

• In the default view, when you sorted the columns in the required order, the column lacked the indicator to show if the sort is in ascending or descending order. Now indicators are provided to show whether the records are arranged in ascending or descending order. This change is applied for the appropriate Citrix ADM pages.
  [From Build 50.39]
  [# NSHELP-18647]

• The non-nsroot user must select the instances from the authorized instances to create a rule.
  [From Build 50.39]
  [# NSHELP-18650]

• When you navigate to System > Events and select an event and click History, the Events History displays the main Events screen and not the expected history for that event. You need to close the Events History page and repeat the selection to view the correct history for that event. This issue is now fixed.
  [From Build 50.39]
  [# NSHELP-18651]

• When you enable the "Do instance backup when Citrix ADCConfigSave trap is received" option from Instance Backup Settings, and when ADM receives frequent "saveconfig" trap from the ADC instances, SCP during device backup might fail intermittently. This issues is fixed by introducing a delay of one hour between receiving "saveconfig" and device backup. Any saveconfig trap received during the cool off period from the same device is ignored for backup.
  [From Build 50.39]
  [# NSHELP-18654]

• The system backup configuration is lost after a system reboot.
  [From Build 50.39]
  [# NSHELP-18655]

• As a Citrix ADM user with view/edit permissions for Network functions, you are able to modify global poll interval settings.
  [From Build 50.43]
  [# NSHELP-18688]

• You might intermittently see that the mas_inventory subsystem core dumps due to multithreading scenarios in libssh2 client.
  [From Build 50.43]
  [# NSHELP-19042]

• As a non-nsroot user, you might see an error when you try to retrieve client-side details in HDX Insight when you are not authorized to perform this action.
  [From Build 50.43]
  [# NSHELP-19087]

• Citrix ADM GUI with multiple agent might become unresponsive intermittently.
  [From Build 50.39]
  [# NSHELP-19119]

• For the ADC HA pair Instance Backup Settings, you can now take independent backup for both primary node and secondary node.
  [From Build 50.43]
  [# NSHELP-19144]

• Self diagnostic tool for no data in Analytics was giving incorrect warning about ULFD server in ADC 11.0 56.x builds. This issue is now fixed.
  [From Build 50.43]
  [# NSHELP-19272]

• The temporary files created during Configuration Audit of templates were earlier stored in /tmp folder of the Citrix ADC file system. The files are now stored in /var/tmp folder.
  [From Build 50.43]
  [# NSHELP-19346]

• When you upgrade Citrix ADM, the upgrade images are not cleaned up from the system even if you select the option to clean the images.
  [From Build 50.43]
  [# NSHELP-19365]

• Sometimes, you might not be able to restart Citrix ADC instances from Citrix ADM. This is because some instances require more than ten minutes to restart and Citrix ADM waits only for ten minutes for the instances to restart. With this fix, you can now configure the Citrix ADM reboot time up to 30 minutes.
  [From Build 50.33]
  [# NSHELP-5632, NSADM-15926]

• Citrix ADM upgrade task logs continues to display "in progress" state even after the upgrade is completed.
  [From Build 50.43]
  [# NSHELP-5839]

• If you are authorized to view only certain applications in a Citrix ADC instance, Citrix ADM should display only those servers, service groups, and domains that belong to that application.

  ADM currently displays only authorized virtual servers but shows all servers, service groups, and domains present in that instance.
  [From Build 50.33]
  [# NSHELP-5862]

• You can now search using special characters such as \,$, &, or ' in any table in Citrix ADM.
  [From Build 50.39]
  [# NSHELP-5927]

• Citrix ADM intermittently sends unsupported Nitro requests to ADC partitions. This might result in errors in ns.log file. The issue is fixed as part of this bug.
  [From Build 50.39]
  [# NSHELP-5935]

• Citrix ADM might fail to modify a user group, when you try to add more than 500 applications in the group.
  [From Build 50.43]
  [# NSHELP-6470, NSADM-21082]

Release history