Cisco CloudCenter 4.10.0 Release Notes

Release Date

First Published: October 16, 2018


  • October 23, 2018: Updated the Documentation section.

  • October 29, 2018: Updated the Applications and Services section.

  • November 4, 2018: Removed certain issues from the resolved section as no changes were made and updated other issues for accuracy.

  • March 14, 2019: Updated the API section to address the Action Management and Deployment Environment API updates.

  • March 21, 2019: Added documentation for the Security Policy APIs.

  • September 23, 2019: Linked Install Worker on a Windows Image to the release notes and added the Go-based agent details to that section.

  • June 16, 2020: Added a known issue for clean-up scripts.


  • CloudCenter 4.10.0 is available as virtual appliances. See Virtual Appliance Overview for additional context.

  • A new REPO package is available – this package is useful if you do not want to use the Repo (Conditional) appliance for the following use cases:

    • You are maintaining your own package repositories.

    • You do not have internet access.

    • Your organizational policies do not allow you to use CentOS 7 OS, which is required for the REPO appliance.

  • Contact the CloudCenter Support team to obtain manual installation instructions.

Upgrade Instructions

You can only upgrade to CloudCenter 4.10.0 from CloudCenter 4.8.2 and later releases. 

  • To upgrade to CloudCenter 4.10.0, see Upgrade Overview.

  • If you are upgrading your environment to use tagless governance, you must use the latest CloudCenter 4.10.0 ccm-response.xml file to upgrade to CloudCenter 4.10.0. See Migrate to Tagless Governance for additional context.

  • When you upgrade the CCM, you will see an additional warning if the ccm-response.xml file is not edited as mentioned in the migration procedure, you can dismiss the warning if this change does not affect your environment.

Upgrade Path

The recommended upgrade path if you are using CloudCenter 4.10.0 is to upgrade to CloudCenter 4.8.2 or later releases.

Security Hardening Requirements

As a one-time task for all OS configurations, you must tighten the security configuration for all components used by the CloudCenter platform to ensure security compliance. The security configuration needs to be tightened for Log Monitor, PostgreSQL, and Load Balancer instances using a one-time procedure before upgrading. See Upgrade Overview for additional context.

For new installations, these security settings are already configured and the one-time procedure is not required.

Component Version Matrix

See the Version Matrix for a list of third-party or Open Source application versions used by CloudCenter 4.10.0.


The Management Agent is now a Go-based agent and introduces the following differences: This is a change!  

  • Earlier CloudCenter releases, the agent used a Java-based installer and installing Java on Application VMs was a requirement. CloudCenter 4.10.0 uses a Golang-based agent and removes the requirement to have Java on Application VMs, unless the applications themselves need Java.

  • Approximately 95% of the space needed by the agent is reduced (down to ~7Mb from ~200Mb) with this strategy and the delay when the node is booting (in the Deployment Details page) is considerably reduced. You will also see a substantial reduction in CPU/Memory usage on Application VMs.

  • Logs are now verbose and you will see additional status messages in the Deployment Details page.

  • The CloudCenter platform no longer uses the node metadata service, JVM, and Jetty on Worker VMs by default.


  • Azure Pack:

    • Support for VM action - Sync VM Information feature. See Actions Library for additional context.

    • Support for instance naming callout. See Region-Level Cloud Settings > Instance Naming Strategy for additional context.

  • Google:

    • For VMs in the stopped state in GCP environments, it is now possible to select Resize Instance Type from the VM actions dropdown menu in the Deployment Details page, VM List page, or VM Details page.

    • See Actions Library for additional context.

  • IBM Cloud:

  • Kubernetes:

    • Export and import application profiles with container based tiers from the Application Profile page.

    • To manage Kubernetes deployments, the CloudCenter platform uses standard Kubernetes APIs as an endpoint.

    • Manually scale up or scale down the number of replicas in container service tiers from the Deployment Details page. See Deployment Details for additional context.

    • New out-of-box, container-based services for Apache, Nginx, MongoDB, and MySQL.

    • Placement group support provides the ability to combine multiple services into a single pod. See Resource Placement and Validation for additional details.

    • New Kubernetes container service variables for deployment parameters. In release 4.9, CloudCenter introduced new CloudCenter variables for referencing various Kubernetes network parameters which are still available in 4.10. See CloudCenter-Defined Parameters for additional context.

Applications and Services

When sharing an application that has manage privileges with a sub-tenant, there is a chance that the subtenant user(s) attach policies and other resources (for which the parent tenant does not have access) to the application. To avoid this scenario, Applications shared (for any permission) with sub-tenant(s) can only be viewed in read-only mode.

See Permission Control > Application Profile Permissions for additional details.

CloudCenter Management

  • Deployment Details:

    • The Deployment (Job) Details page has a new look to provide relevant information for each deployment with better user experience that allows you to use the page more effectively. In previous releases, this page was frequently referred to as the Job Details page or the Deployment (Job) Details page. Effective CloudCenter CloudCenter, the name of choice is Deployment Details!

    • The new architecture provides a stream of updates to the web client.

    • The Auto-refresh rate dropdown that was available in previous releases is removed due to the new subscription to stream architecture. This is a change!

    • Both batch actions or single actions are available to terminate VMs – batch action support was not available in earlier releases. This is a change!

  • Policy Enhancement:

    • All the policy pages have two new columns: Last Updated and Share with Sub-tenants.

    • The Aging policy tab has a new column, Age By, with Time Duration and Cost Limit as possible values.

    • On the Add Event Policy form, the Auto Enable for sub-tenants, with another option to Restrict sub-tenants from modifying this settingThis is a change!

    • See Policies for additional context.

Administration and Governance

  • Lifecycle Actions:

    • Users can define lifecycle actions to control the span of resources (cloud regions, applications, services) in which the lifecycle action is made available.

      • Once a lifecycle action is defined by a CloudCenter user, other permitted users can select that action in one of the resource editor screens.

      • Like on-demand actions, lifecycle actions may include one or more parameters specified in the action definition.

      • When importing an application profile, users can also map a used lifecycle actions to other newly-defined actions.

      • See Actions Library > Lifecycle Actions for additional context.

    • Lifecycle actions have access to a separate list of environmental variables that are associated with the resources to which they are mapped.

      • You can use these variables in a script, default value, or body fields modeled as part of the action, and are passed on as environment variables to the VM.

      • See CloudCenter-Defined Parameters > Lifecycle Actions Variables for additional context.

    • When importing application profiles, you have the option to select a Profile Package option to map lifecycle actions. See Application Profile Export/Import > Import Process for additional context.

    • Users now have granular control for deployment parameters – if the field is not locked, then users can type a value for the parameter. See Deployment Parameters > Granular Control for User-Defined Parameters for additional context.

  • Tagless Governance: This is a change!

    • The Governance mode concept is deprecated and results in significant changes around policies, deployment environments, application-level service settings, and system tags to simplify overall user experience.

      • Policies:

        • The Security Profiles page is renamed to Security Policies and the page is moved to the Policies section.

        • Policies can no longer be assigned a priority, and the column for the priority field that was visible when governance mode was turned on is removed. See Policies > Security Policies for additional context.

        • The Share form is no longer available for any Policy as a policy is now a tenant-owned resource. Instead, the admin can then grant permissions to a sub-tenant by enabling the (ON) toggle switch for the required policy. See Policies > Share with Subtenants for additional details.

      • Deployment Environments:

        • Previously, setting priority of environments was only available when governance mode was enabled. Now this feature is always enabled.

        • The deployment submission process now has three steps in the form of tabs for each step: General Settings, Cloud Settings, and Policy Settings:

          • The General Settings tab now includes the initial cloud selection.

          • The Cloud Settings tab now includes the ability to Define Default Cloud Settings within the Default Tier Cloud Settings section, and the additional button that used to reside at the bottom of the Deploy form is no longer available! 

          • The Policy Settings tab allows you to identify the required policy and duration on a per-deployment basis. See Deployment Environments > Adding an Environment for additional details.

      • Permissions:

        • The Deploy To permission setting is moved to the first column while the Access permission to update a deployment environment has been removed from the shared settings page. 

        • The access to deployment environments and policies has been revoked for all users except the Admin and Ops users. All other permissions remain the same.

        • Tenant administrators can share the deployment environment with users who are directly under the tenant owner – if they have inherited deployment environment permissions based on a role configuration. Users further down this tenant hierarchy can only view the environment.

        • The dependency between Others’ Deployments and Authorized Approver has been removed and both are now independent permissions. Previously, if a user did not have Access or Manage permission for Others' Deployments that user could not have Authorized Approver permission as well. This connection resulted in a user’s own deployments being auto approved. Now, if a user’s deployment requires approval and the user does not have Authorized Approver permission, then the deployment must be approved by someone else before it being deployed.

        • See Permission Control > Deployment Environment Permissions for additional details.

      • Service Properties for Application-level Tier Settings:

        • The General Settings section that specifies Service Properties in the Topology Modeler tab for each application-level tier has two additional fields to identify policies and metadata-based system tags on a per-tier basis. See Application Tier Properties > General Settings for additional details.

        • The Deploy form, when deploying an application, has several changes:

          • Selection of the deployment environment moves from moves to the General Settings section on Page 1 as this selection determines the aging, suspension, and security policies that are visible and selectable at deploy time.

          • Tags in the deploy form have no influence over which policies are applied to the deployment at deploy time.

          • New fields for selecting deployment-wide aging, suspension and security policies appear in the General Settings section of Page 1 when the corresponding allowed policies field in the deployment environment is populated with your selections.

          • For tiers that scale, a new field for selecting the scaling policy is displayed in the per-tier sections of Page 1 when the corresponding allowed scaling policy field in the application profile is populated with choices and set to visible.

          • See Deploying an Application for additional context.

        • The Specify Deployment Environment toggle switch in the Basic Information tab, if enabled (ON), allows you to specify select deployment environments for an application. See Topology Modeler > Basic Information Tab for additional details.

      • System Tags:

        • Tags are only used for metadata association and is now part of the Reports section in the Admin menu. Tags are only used for tracking purposes and no longer associated with policies.

        • The ability to limit what policies can be applied to deployments using system tags is replaced by the ability to associate allowed policies to deployment environments and application profiles, as appropriate.

        • Now, system tags are tenant owned objects without any access control list association. If a user has access to the Admin tab, that user will have manage access to all tags in the tenant; therefore, it is unnecessary to share a tag with another user in the tenant.

        • The Actions dropdown menu has been replaced with a delete icon for all tags within the current tenant. You can continue to edit a tag by clicking on the tag name provided you have the required permission.

        • The Share form is no longer available for any tag as tags are now a tenant-owned resources.

        • See System Tags for additional context.

    • Users who have been assigned Policy and Deployment Environment permissions inherited through roles will continue to have access to these resources.

    • By default, only the administrator has access permission to the Policy and Deployment Environment roles. See Permission Control > Role-Based Permissions for additional context.


No updates.

End of Life Notices

See End of Support Notices for additional details.


The following features are deprecated effective CloudCenter 4.10.0 as already published in the CloudCenter 4.10.0 release notes:

  • The Governance section in the Admin menu is removed and the Governance Mode functionality is deprecated.

  • The Access permission to update a deployment environment has been removed from the Share settings page.


  • New Menu Items: No updates.

  • Browser Compatibility: Cisco supports the two latest versions of each browser. See Browser Compatibility for a list of compatible browsers.

  • Localization: No updates. See UI Behavior for context.


CloudCenter 4.6.0 introduces v2 APIs, where applicable. If a new API is introduced for the first time, it continues to use v1 as it is still the first version of that particular API. The following list differentiates between the New and Updated APIs for CloudCenter 4.10.0.


No updates.


This section lists the documentation changes implemented in CloudCenter 4.10.0.

Known Issues

CloudCenter 4.10.0 has the following known issues:

  • For hybrid cloud deployments, the Scale up/Scale down options are not displayed as these options are not supported for hybrid cloud deployments.

  • Using Macros that contain values with special characters in a command line (batch execute / cluster compute application) or command line type for any service input, results in a job/deployment failure. Special characters in the values of parameters must be escaped and used as macros.

  • Security Policy for an environment that is not listed in the deploy flow for a sub-tenant – the visibility toggle for security policies within the policy settings of a deployment environment is OFF by default.This needs to be turned ON to make it visible in the deploy flow.

  • The option to enable the terminate protection needs to be enabled in the policy settings of the deployment environment. See the Policies section for additional details.

  • As deigned, the enable Terminate Protection option in the deployment environment is effective even for already deployed applications. The latest setting in the deployment environment when enabling terminate protection is also applicable to already launched deployments.

  • When deploying an application as part of the agent lifecycle actions, the default node clean up script (cleans up the CloudCenter artifacts) is executed along with the user-defined node clean up script.

Resolved Issues

The following issues were resolved/addressed in CloudCenter 4.10.0:

  • CSCvf54067: The CCM UI is either unavailable (404 error after a certificate warning), or does not accept some changes (for example, an application profile cannot be saved) in non-HA standalone CCMs or HA CCM with external databases when using CloudCenter 4.8.0.
    Resolution: CloudCenter 4.10.0 includes a fix to ensure that customers can use IPs instead of FQDNs during the database configuration of the CCM master IP address.

  • CSCvf60682: The startTime and lastUpdated attributes on the Job Details page is not in sync with either the UTC or the local timezone setting.
    Resolution: The CloudCenter 4.10.0 Deployment Details changes listed in the CloudCenter Management section above includes a fix to address this issue.

  • CSCvg38302: Some out-of-box services ignore the CUSTOM_REPO_URL and attempt to download packages from the internet. This indicates that these services will not work in restricted environments.
    : CloudCenter 4.10.0 provides a fix to ensure that the packages are only downloaded from the CUSTOM_REPO_URL, if provided.

  • CSCvg68168: When modeling an app using MySQL database service, General Settings, the SA Password field heading should be Root Password, not SA password. MSSQL 2012 appliances for AWS does not accept the SA password for Administrator logins.
    The General Settings section for the MySQL database service now reverts to displaying Root Password in this field. This field is already described in the My SQL service properties page. 
The SA password is for logging into the SQL Server database alone and will not work for host authentications. For host authentications, get the password from the Deployment Details or Managed Virtual Machines pages.

  • CSCvh72367: Currently there is no dropdown menu (for any deployment actions) in the Deployment Details page. So to suspend/terminate/etc that deployment, a user must return to the Deployments page, find the deployment, and then find the action from the dropdown menu.
    Resolution: The CloudCenter 4.10.0 Deployment Details changes listed in the CloudCenter Management section above includes a fix to address this issue. 

  • CSCvi10828: When a deployment is in the In Progress state, issuing a terminate deployment request takes time to complete. Users may assume that the terminate action did not work and rush to delete VMs manually.
    Resolution: CloudCenter 4.10.0 includes a fix to ensure that the Deployment list page explicitly displays a message indicating that the deployment in the In Progress state takes time to complete.

  • CSCvi44799: CloudCenter 4.8.2 mandated the username and password setting for SMTP configurations. Due to this feature, any SMTP setting cannot be saved in the tenant or sub-tenant information if the username and password were not provided.
    : CloudCenter 4.10.0 includes a fix to ensure that the Username and Password are not mandatory fields in SMTP configurations.

  • CSCvi69212: During an upgrade from CloudCenter 4.8.2 to CloudCenter, a user ran the cco-installer.jar and received a warning: Failed to determine hostname and IP address, even though the /etc/hosts file was populated with hostnames and IP Addresses.
    Resolution: This failure was not related to the hostname but to a user permission issue that was fixed in CloudCenter 4.9.1.

  • CSCvi71541: The hostnames for some CCOs were modified by the CloudCenter platform after a user assigned the originally hostnames.
    : CloudCenter 4.10.0 provides a fix to ensure that the hostname is not changed when configuring CCOs in HA mode.

  • CSCvi80285: A user wanted a direct API to get VM details once Submit Job (v2) API is submitted. If there is no direct API, can this be an enhancement request.
    ResolutionUse Submit Job (v2) API to deploy an application profile, then use the resulting jobId as the parentJobId in the newly introduced View Child VM Details API to get VM details for this deployment.

  • CSCvi80325: When creating new instance types in the cloud region and correctly mapping them to an image all instance types should be displayed when deploying if no other filters are set.
    Resolution: This issue was caused by the hourly cost being rounded up to 2 decimals. CloudCenter includes a fix to ensure that for hourly cost displays 4 decimals and it is not rounded up, but monthly and approximate cost display 2 decimals and they are rounded up. 

  • CSCvi84343: Deployment tags are duplicated when an application is shared to another user/ admin with manage permission. When the user modifies the application profiles which was shared by another user with system tags, it duplicates while deploying an application.
    Resolution: CloudCenter 4.10.0 includes a fix to ensure that tags are not duplicated even if shared application profiles and deployment environments are edited multiple times.

  • CSCvi96146: Initial firewall rules are lost when enabling and disabling microsegmentation
    Resolution: If you disable microsegmentation, after enabling it and configuring any change, all firewall rules revert to the initial state – any change done after microsegmentation is enabled are lost.

  • CSCvj05379When trying to deploy on a Azure RM cloud and the user selects some instance types that support premium storage, only the standard storage account shows up in the list.
    Resolution: CloudCenter 4.10.0 includes a fix to ensure that this list displays as designed.

  • CSCvj19947: At deployment time, a user selects the Unmanaged storage type option in an Azure environment, at which point, the hosting storage account disappears and sets the storage account to null, thus resulting in a failed deployment.
    Resolution: CloudCenter 4.10.0  includes a fix to ensure that the StorageAccount is displayed in the deployment page, when the Unmanaged storage type is selected, even if the environment is locked.

  • CSCvj13299: If the CloudCenter platform is installed in a closed environment (with access only to AWS E2 Endpoint, no direct Internet) external RDS services can't be used as the AWS CLI package is fetched from URL, which is blocked by proxy/firewall settings. 
    Resolution: CloudCenter 4.10.0 includes a fix to ensure that the AWS CLI file is now hosted in the repository that is set up using the REPO appliance.

  • CSCvj16953: By default, Docker Containers use the Bridge IP subnet When a user needs to change the current segment to a new segment, the user cannot bypass the default subnet.
    Resolution: CloudCenter 4.10.0 includes a fix to provide the
    Docker Bridge as a new configurable option in the cco_config_wizard.

  • CSCvj17078: When creating a policy, users may press the Create button multiple times and that creates duplicated values after a policy is created.
    ResolutionCloudCenter 4.10.0 includes a fix to ensure that the Done button is only accepted once even if users click on it multiple times in quick succession, and only one aging policy is created.

  • CSCvj47464: IBM cloud throws an exception during migration about not finding the user target.
    Resolution: CloudCenter 4.10.0 includes a fix to remove special characters that are not acceptable to IBM cloud from these tags.

  • CSCvj50048: A customer requested the ability to force terminate a failed deployment in order to have the same name as the original node which failed.
    Resolved: CloudCenter 4.10.0 includes a fix to address this enhancement.

  • CSCvj55271: A customer required a single API to get all UI logs for each tier in an application profile deployment using one API, instead of using multiple APIS (get Job details, get Job ID, get Child Job ID, and then use the Child Job ID to get job log for each tier).
    Resolution: Use the Get Tier-Specific Log Details API to fetch details of all job (including child jobs) information using a single call. 

  • CSCvj56135: An inaccurate error message is returned when communication to the agent is not established.
    Resolution: CloudCenter 4.10.0 includes a fix to list the correct error message as follows: VM Agent version is not available. So, all the custom actions are not supported for execution.

  • CSCvj73134: AgentLite is not installed on Windows 2016.
    Resolution: CloudCenter 4.10.0 includes a fix to address this enhancement.

  • CSCvj75414: When updating the exchange rate (and the amount is less then 1) on the Tenant Information page, the value is rounded up.
    Resolution: CloudCenter 4.10.0 includes a fix to ensure that the exchange rate can be specified.

  • CSCvj83944: In CCM HA environments, the /usr/local/cliqr/conf folder is not synchronized between the primary and secondary CCM servers.
    Resolution: CloudCenter 4.10.0 includes a fix to ensure that this folder is synchronized between both CCM servers.

  • CSCvj85208: The REPO sync function adds the DenyUsers repo environment variable to the end of the line in the /etc/sshd/sshd_config file instead of adding the variable as a new line.
    Resolution: CloudCenter 4.10.0 includes a fix to ensure that this variable is added as a new line in the /etc/ssh/sshd_config file.

  • CSCvj99016: When setting up the system the first time, an empty nonProxyHosts setting results in an incorrect entry inside the gateway.conf file.
    Resolution: The proxy configuration setting was revamped in CloudCenter 4.9.1 and no longer uses Java options for proxy settings. The wizard sets values in the /etc/sysconfig/mgmtserver.conf file for HTTP/HTTPS connections.

  • CSCvk14373: The Job Details page intermittently does not show tier information.
    Resolution: The CloudCenter 4.10.0 Deployment Details changes listed in the CloudCenter Management section above includes a fix to address this issue.

  • CSCvk14394: CloudCenter does not store encrypted credentials in CloudCenter
    CloudCenter 4.10.0 includes a fix to ensure that this function is possible with Lifecycle Actions support in the Actions Library. You can now define a Lifecycle Action and use it at the region level for lifecycle scripts.

  • CSCvk14726: Ubuntu requires the Date field in the package repository.
    Resolution: CloudCenter 4.10.0 includes a fix to ensure that this field is included in All other REPOs need to synchronize this change from the master REPO.

  • CSCvk40641: Attempting to delete a deployment environment (shared with a sub-tenant) by the root tenant results in an error if the sub-tenant is already deleted and linked to an activation to a deployment environment. The root tenant cannot delete either the activation profile or the deployment environment.
    Resolution: CloudCenter 4.10.0 includes a fix to ensure that the root tenant can delete deployment environments even if a deleted sub-tenant has linked an activation profile to the deployment environment.

  • CSCvk42441: Restarting a VM from VMware and restarting Jetty appends a line to the /etc/hosts file.
    Resolution: CloudCenter 4.10.0 includes a fix to address this issue the restart functions as designed.

  • CSCvk48628: The REPO contains outdated Ubuntu package information.
    Resolution: CloudCenter 4.10.0 includes a fix to ensure that outdated packages are removed from the repository and updated with the latest ones. A resync of the local repository with removes older files and rebuilds the metadata.

  • CSCvk51078: In a ServiceNow environment, a user was unable to delete the Deployment Environment when a job was in the Submission Canceled state.
    Resolution: CloudCenter 4.10.0 includes a fix to address this issue and the deletion functions as designed when a job submission is rejected.

  • CSCvk77740: Some application deployments with external initialization scripts fail when the parameter is of type PATH and its value is a URL which cannot be downloaded. Avoid using parameters of type PATH if its value cannot be downloaded. Instead, add this value as a string.
    Resolution: CloudCenter 4.10.0 includes a fix to ensure that a parameter of type PATH with a URL value functions as designed.

  • CSCvk77758: The Docker (docker) service must be explicitly (re)started after the CCO server is (re)started. See Certificate Authentication > Dedicated Components for process details.
    Resolution: While using updating custom certificates for Docker installations through a CCO configuration wizard, you had to explicitly restart the Docker service. You do not need to explicitly start or restart the Docker service as the CCO wizard executes this step automatically. This is a change!

  • CSCvm29566: The CCO log displays the action parameter of type password is displayed in clear text. 
    Resolution: CloudCenter 4.10.0 includes a fix to ensure that the password is redacted in the CCO log file.

  • CSCvm58750: The CCM instance fails to start after a upgrade from CloudCenter
    Resolution: CloudCenter 4.10.0 includes a fix to ensure that this issue, caused by a offset value in the SQL query, is addressed.

  • CSCvm75612: Under certain conditions, scaling down a specific node terminates a different node.
    Resolution: The CloudCenter 4.10.0 Deployment Details changes listed in the CloudCenter Management section above includes a fix to address this issue. 

  • CSCvk36356: When configuring the CCO instance from the CloudCenter platform, the configuration fails. The CCM is in an on-prem VMware environment and the CCO is in AWS. The CCO requires a proxy in order to access the internet. 
    Resolution: CloudCenter 4.10.0 includes a fix to ensure that proxy settings are saved and updated in the /etc/sysconfig/gateway.conf file as well as the /etc/sysconfig/cloudblade.conf file. This is a change!

  • CSCvk74475: Windows deployments intermittently fail as the c:\sysprep folder is not deleted by VMware tools.
    Resolution: Additional antivirus software installed on the system in this environment did not allow the c:\Sysprep folder to be deleted. This deletion is done by VMware. The CloudCenter platform includes a fix to mitigate this behavior.

  • CSCvm26135: The Simplified Network feature does not work in an ELB environment. 
    Resolution: CloudCenter 4.10.0 includes a fix to ensure that this feature works as designed.

  • CSCvm41598: If the password contains certain special characters, the PostgreSQL database authentication fails.
    Resolution: CloudCenter 4.10.0 includes a fix to ensure that special characters are accepted in the CCM configuration wizard.

  • CSCvm77436: The CCM UI did not load for a customer because the system was out of memory and the backend Java process required to display the UI was killed.
    : CloudCenter 4.10.0 includes a fix to optimize memory usage by caching security key specifications when encrypting/decrypting data.

  • No labels
Terms & Conditions Privacy Statement Cookies Trademarks