Cloud Connector Latest Topics

Cloud Connector Command Line Installation

Wed, 12 Feb 2025 11:07:42 +0000

Did anything change in the last couple of months with the silent Cloud Connector command line installation?

The quiet switch quits unexpectedly complaining about API authentication. This has all been configured correctly as per documentation and previous installations using the same process were working.

Manually installing Cloud Connector is working.

Older versions of Cloud Connector software not working either.

Maybe the introduction to service principals has broken something?

Citrix cloud connector or Connector Appliance

Mon, 24 Feb 2025 21:06:31 +0000

I have my VDA resource location in both On-Prem and Azure. Currently I have separate On-Prem CVAD sites to house on-prem VDA and Azure VDA respectively. I'm planning to migrate to Citrix DaaS. I'm not sure if it's recommended to install Citrix Cloud Connector (Windows server) or Citrix Connector Appliance for Cloud Services (in Azure market place). Can I have Citrix Connector Appliance (in Azure market place) to act a communication to Citrix DaaS from on-prem VDA and Azure VDA, or do I require to have onPrem Citrix Cloud Connector installed for on-prem VDA and Citrix Connector Appliance for Azure VDA?

Citrix Cloud Connector Silent Installations Fails when triggered from remote server

Wed, 02 May 2018 07:13:47 +0000

Silent Installation of Citrix Cloud connector fails when the installation is triggered from a remote computer.

What I am trying to achieve ?

I want to automate Citrix Cloud connector Installation for a given resource location of a citrix customer and followed the steps given in the citrix documentation for silent installation.

https://docs.citrix.com/en-us/citrix-cloud/citrix-cloud-resource-locations/citrix-cloud-connector/installation.html#command-line-installation-non-interactive

What actually happens?

Developed a script which takes the required input parameters from the user and starts the silent installation.

The automation script works fine when the script is called from the same hostname where cloud connector needs to be installed.

The installation fails when it is triggered from remote server. During this installation process,

Installs 4 citrix packages. (Citrix cloud connector, Agent System Agent logger, Agent WatchDog)
Waits for 60 seconds (approx)
Uninstalls the 4 packages

While verifying the citrix cloud installation logs, it is unable to set a signing key. A warning message of pipe failure with access denied as shown here is logged for few seconds before failing with the error. I used the domain Administrator credentials and this installation works when running the automatic installation batch file from the same host.

Any pointers is very much appreciated. (Attached the failure log also)

2018-05-01 10:08:38.375: [13404] Warning - Unable to contact AgentSystem : System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at net.pipe://localhost/AgentSystem/Bootstrap that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ---> System.ServiceModel.AddressAccessDeniedException: The pipe name could not be obtained for net.pipe://localhost/AgentSystem/Bootstrap. ---> System.IO.PipeException: The pipe name could not be obtained for the pipe URI: Access is denied. (5, 0x5)

--- End of inner exception stack trace ---

at System.ServiceModel.Channels.PipeSharedMemory.Open(String sharedMemoryName, Uri pipeUri)

at System.ServiceModel.Channels.PipeConnectionInitiator.GetPipeName(Uri uri, IPipeTransportFactorySettings transportFactorySettings)

Exception rethrown at [0]:

at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)

at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)

at Citrix.CloudServices.AgentFoundation.Common.Contracts.IBootstrapProvider.SetSigningKey(String signingKey)

at Citrix.CloudServices.SetupTools.CustomActions.Actions.ConfigureInstallSuccess.SetSensitiveInformation(IDictionary`2 properties)

2018-05-01 10:09:31.057: [13404] Error - Configure Citrix Cloud Connector Failed: Unable to set signing key.

2018-05-01 10:09:31.120: [13404] Context execution completed successfully.

2018-05-01 10:09:31.120: [13404] Context exit code: 1729

Also attaching the Citrix EdgeServer installation log which actually failed.

Thanks.

CWCConnector_20180501220747_007_Citrix_Csg_EdgeServiceLocalConfig.log

Remote Cloud Connector checks/version/API?

Thu, 11 May 2023 14:05:24 +0000

I'm trying to do checks on our Cloud Connectors for Versions.

Is there an API or remote utility or something I can run to get back current version vs upcoming version to track?

I know about the Connector Data in the https://citrix.cloud.com/connectors/ - this requires me to manually visit that website and login, I'm looking for something more convenient for tracking.

that url tells me this - which is what I'm looking for

Connector Version:

Current: 6.57

Target: 6.71

I see a resource locations api but that doesn't return anything helpful or anything regarding connectors

https://api.cloud.com/resourcelocations/{Id}

the email subscriptions are not helpful,

(A Citrix Connector Update is scheduled to occur)

anyone find anything helpful for software tracking? or version notifications?

Connectivity check to https://reg.c.nssv.us:443/control/ping error

Fri, 17 Feb 2023 17:52:01 +0000

I'm receiving this error when I do a cloud connector check on both of my cloud connector servers:

Error - Connectivity check to [https://reg.c.nssvc.us:443/Control/Ping] executed as a service Failed reason: Unknown result

I'm unsure how to fix this.

Thanks.

Receiving error with cloud connector fails test

Fri, 10 Feb 2023 20:01:55 +0000

Receiving CitrixNetScalerCloudGateway (https://reg.c.nssvc.us:443/Control/Ping) when testing cloud connector.

I do not have a proxy. Shouldn't be an issue with the firewall. I'm not sure what the problem is.

how to access DaaS from internet?

Tue, 28 Feb 2023 18:50:23 +0000

Need some hint or help to setup DaaS from external, for WFH scenario.

so far I'm able to set it up for internal use (user can access apps and desktop)

but when I'm at home, i cannot connect into it.

My guess, i need to connect it with the ADC VPX.

Can anyone help?

Cloud Connector Offline Mode

Tue, 27 Sep 2022 19:57:09 +0000

How do you place a cloud connector offline intentionally so as to not interrupt anything if the location it is in looses connectivity to internal resources?

How does Cloud Connector failover work? Forced 2 servers to Offline Mode with 3rd server Online. VDAs would register sometimes to Offline server and appear Unregistered

Fri, 19 Aug 2022 06:17:44 +0000

I have 2 on-prem Cloud Connectors and 1 in Azure, all registered to the one Citrix Cloud Resource Location.

I forced an outage on the on-prem servers to test connectivity to the Azure server, however VDAs would sometimes register to the (primary) on-prem server and sometimes to the Azure server. When registering to the offline on-prem server they appear Unregistered in DaaS, but appear Registered if they hit the Azure server.

Is this how it is supposed to work, and if so then roughly 50% of our PVS Pooled VDAs would become Unregistered in an on-prem datacentre outage, where the Azure Cloud Connector would continue to provide access to Registered VDAs.

I know a workaround could be to update Group Policy to only contain the Azure Cloud Connector and restart the VDA service, but that is a manual intervention we had hoped to avoid.

Is there a trick to get the Cloud Connectors to failover to a fully functioning server rather than become a collection of Offline (using LHC) and Online servers, both accessible to the VDAs?

thanks.

What is new Cloud Connector Service Citrix ClxMtp Service?

Wed, 19 Aug 2020 21:30:50 +0000

An update was pushed to our Cloud Connectors today. It removed Service 'Citrix Session Manager Proxy' and added Service 'Citrix ClxMtp Service'. What is the new service for? The description of the service is the same as the name, not very useful.

DaaS: Citrix Cloud Connector placement in Azure Subscription

Mon, 08 Aug 2022 16:40:55 +0000

Hello Everyone,

I have one design related question and would be grateful if someone can assist on this.

background: I have multiple Azure subscriptions (management, test and production) and planning to deploy vdis soon.

Management subscription is dedicated for IT infrastructure or you can say supporting infrastructure.

my doubt is which one is the best option to place cloud connector in Azure and why ?

Design1: Deploy 2 cloud connector in Management subscription for redundancy and vdis session host in multiple production subscriptions but little worry if something break between subscription then what will be the impact on users? This approach is saving number of cloud connectors required.

Design2: Deploy 2 Cloud connector in each production subscription instead of management subscription.

Experts , please shed some light on this

I need to update the certificate for hosting connection but cannot find how to access teh Citrix Cloud controller powershell

Tue, 19 Jul 2022 16:26:01 +0000

I need to update the certificate for hosting connection but cannot find how to access teh Citrix Cloud controller powershell

Use Nutanix with Citrix Cloud and how to find Connector VM Password

Mon, 09 May 2022 13:46:34 +0000

Please, I cannot understand how to find or to register the "Connector VM Password" when I try to create a Citrix Cloud connection from a Nutanix Cluster. If someone can explain me where or how to find it, it will help me a lot !!!

Best Regards

Creating Cloud Connector (The service account credentials provided are invalid)

Mon, 14 Feb 2022 21:49:15 +0000

When trying to add a cloud connector to my new Azure environment I get the error below.

Any ideas?

The service account credentials provided are invalid.

Transaction ID:

e0d728ae-12b0-4748-a195-a007b034f217

Delete

Azure Resource Group: ADDSTEST

Organizational Unit: None

Machine: Standard_D2a_v4

On-Prem Active Directory Citrix Group Policy with Citrix Cloud CVAD Workspace Services Delivery Group Filter

Thu, 09 Dec 2021 20:57:34 +0000

We are managing Citrix Group Policy via On-Prem Active Directory Group Policy. We have the Citrix Group Policy admin templates installed and all is working as expected. I am trying to add my first Citrix policy filtered on Delivery Group. I can select an on-prem Delivery Controller and a list of Delivery Groups is returned in the filter pull down list. If I select the Cloud Connector I get a pop up error "Failed to connect to back-end server...on port 80 using WSHttp".

How do I filter on a Cloud Delivery Group using On-Prem Active Directory Citrix Group Policy?

Tested Cloud Connector then removed. Cant update MCS images now.

Wed, 16 Feb 2022 23:28:20 +0000

Running VADs 1912 LTSR on-prem. We tested Citrix Cloud just for the Workspace functionality a while back and just decommissioned our Cloud Connector server.

Now that the CC is offline, we get errors on our MCS Machine Catalogs saying no cloud connector was found, and it prevents us from updating the Machine Catalogs.

In our testing of Citrix Workspace, all VDAs remained on-prem so I'm not sure why updates to these machine catalogs would in any way be impacted by the presence of the CC. My Googles have been fruitless. The error stats a CC is needed for each zone, but I didnt need one before we POC'd Citrix's cloud products.

Can anybody shed some light on this for me, or point me in the right direction? Screenshot and full error are below.

Thank you!

Quote

Error Id: XDDS:84C9DE58

Exception:
DesktopStudio_ErrorId : NoWorkspaceCloudConnectorFound
Error Source : CitrixHostService
Sdk Error Message : No Citrix Workspace Cloud Connector was found, either on the site or for the required zone. At least one CWC Connector is needed for the site. Any configured zones containing hypervisors require at least one Connector per zone. New or recently moved Connectors may need a few minutes to be correctly recognized.
Sdk Error ID : Citrix.XDPowerShell.HostStatus.NoWorkspaceCloudConnectorFound,Microsoft.PowerShell.Commands.GetChildItemCommand
ErrorCategory : ResourceUnavailable
DesktopStudio_PowerShellHistory : GetHypervisorItemsScript`1
2/16/2022 5:10:24 PM

Set-HypAdminConnection -AdminAddress "DeliveryControllerHostname.MyDomain.com:80" -BearerToken ********
Get-ChildItem -BearerToken ******** -LiteralPath @("XDHyp:\HostingUnits\Citrix_Nutanix")
Get-ChildItem : No Citrix Workspace Cloud Connector was found, either on the site or for the required zone. At least one CWC Connector is needed for the site. Any configured zones containing hypervisors require at least one Connector per zone. New or recently moved Connectors may need a few minutes to be correctly recognized.
   + CategoryInfo : InvalidOperation: (:) [Get-ChildItem], InvalidOperationException
   + FullyQualifiedErrorId : Citrix.XDPowerShell.HostStatus.NoWorkspaceCloudConnectorFound,Microsoft.PowerShell.Commands.GetChildItemCommand
Get-ChildItem : No Citrix Workspace Cloud Connector was found, either on the site or for the required zone. At least one CWC Connector is needed for the site. Any configured zones containing hypervisors require at least one Connector per zone. New or recently moved Connectors may need a few minutes to be correctly recognized.
   + CategoryInfo : NotSpecified: (:) [Get-ChildItem], InvalidOperationException
   + FullyQualifiedErrorId : System.InvalidOperationException,Microsoft.PowerShell.Commands.GetChildItemCommand


StackTrace: Citrix.Orchestration.Base.LogicModels.Exceptions.HypervisorNotContactableException No Citrix Cloud Connector was found, either on the site or for the required zone. At least one Cloud Connector is needed for the site. Any configured zones containing hypervisors require at least one Connector per zone. New or recently moved Connectors may need a few minutes to be correctly recognized.
at Citrix.Orchestration.Base.PowerShellInteraction.CmdletExecutionMethods.CreateException[T](ICommonLog logger, ExecutionResults`1 results, ICmdletExecutionHost host)
at Citrix.Orchestration.Base.PowerShellInteraction.CmdletExecutionMethods.Execute[T](ISdkCmdlet`1 sdkCmd, ICmdletExecutionHost host, Boolean allowFailover)
at Citrix.Orchestration.Base.PowerShellSdk.HypervisorService.Scripts.GetHypervisorItemsScript`1.RunScript()
at Citrix.Orchestration.Base.PowerShellInteraction.PowerShellScript`1.Run()
at Citrix.Orchestration.Base.PowerShellSdk.HypervisorService.PSHypervisorService.GetNutanixMachineSnapshots(IHypervisorTreeParent treeParent, ScriptExecutionContext context)
at Citrix.Console.ProvisioningSchemes.UI.Pages.NutanixSnapshotSelectionViewModel.PrepareToBeShown()
at Citrix.Console.CommonControls.Wizard.PageContainerViewModel.<>c__DisplayClass15_0.b__0()

Inner Exception:

StackTrace: System.InvalidOperationException No Citrix Workspace Cloud Connector was found, either on the site or for the required zone. At least one CWC Connector is needed for the site. Any configured zones containing hypervisors require at least one Connector per zone. New or recently moved Connectors may need a few minutes to be correctly recognized.

Manage Subscribers button greyed out

Mon, 14 Feb 2022 23:18:55 +0000

In our environment the "Manage Subscribers" button is greyed out. In this image its not, just referencing the button.

Any idea what would cause this button to be greyed out, nothing showing in the Azure logs when going to this page, so must be something in Citrix?

How to restrict the single session desktop visibility

Fri, 05 Nov 2021 07:56:56 +0000

Scenario:

We have Domain A and Domain B. Created two different Storefront servers to two different domains.

Domain A has different store URL

Domain B has different store URL

But when user logs in Domain A URL, able to both Domain A and Domain B published desktops(Single session) and same when user logs in Domain B URL, seeing both domain published desktops.

Both domains doesn't have trust between them and sharing the same CVAD.

Adding user into AD security group is restricting to see from Domain A to B. But when we try to provide access for single session desktop, not possible to add user to a AD security group.

My requirement is how can we restrict users to see only Domain A single session desktops when he logs in Domain A URL and same as Domain B. Please assist.

Is there a command line that can remove connector from https://us.cloud.com/connectors portal ?

Mon, 30 Aug 2021 06:48:08 +0000

Is there a command line that can remove connector from https://us.cloud.com/connectors portal ? It can be done from the portal, but need the command line for automate the removal process

Citrix Cloud Conector does not get a connection to Cloud - Error: AuthenticateCwsUser Failed: Forbidden

Tue, 03 Nov 2020 13:54:33 +0000

Hi Folks,

I'm trying to get a CloudConnector running in my Lab.

I'm running a Windows 2019 Server and i get no Connection to the Citrix Cloud.

I've downloaded the Setup from Citrix Cloud and run it. Sign in works Setup is running through and it seems all is done. Setup Window Closes. But there is no Connection to the Cloud. Checking the install logs i found this error, and i have no clue what the issue is.

The needed certificates are installed. IE ESC is disabled. No Proxy configured.

Quote

2020-11-03 02:24:38.431: [1948] New installation
2020-11-03 02:24:38.431: [1948] Getting the customer org id, geo and service profile.
2020-11-03 02:24:41.462: [1948] Registering connector xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx public keys.
2020-11-03 02:24:41.868: [1948] Error - AuthenticateCwsUser Failed: Forbidden
2020-11-03 02:24:41.884: [1948] Context execution completed successfully.

See the full logfile:

. CWCConnector_20201103142124_002_Citrix_Csg_AuthenticateCwsUser_blackened.txt

I also tried to troubleshoot with the Cloud Connector Connectivity Check but this did not help anything.

If i run the tool and Import the IE Settings, the Access type of the Default Proxy changes from 1 to 3 and the connectivity Tests to the Websites fails

Quote

Validating AD domain reachability...
The operation completed successfully.
Performing AD domain logon to verify reachability...
The operation completed successfully.
Verifying reachability for [www.citrix.com] ...
Contacting [https://www.citrix.com] returned HTTP STATUS [0]
Verifying reachability for [www.microsoft.com] ...
Contacting [https://www.microsoft.com] returned HTTP STATUS [0]
Verifying reachability for [www.google.com] ...
Contacting [https://www.google.com] returned HTTP STATUS [0]
Verifying reachability for [cloud.com] ...
Contacting [https://cloud.com] returned HTTP STATUS [0]
Verifying reachability for [citrixdata.com] ...
Contacting [https://citrixdata.com] returned HTTP STATUS [0]
Verifying reachability for [sharefile.com] ...
Contacting [https://sharefile.com] returned HTTP STATUS [0]
Verifying reachability for [browser-release-a.azureedge.net] ...
Contacting [https://browser-release-a.azureedge.net] returned HTTP STATUS [0]
Verifying reachability for [browser-release-b.azureedge.net] ...
Contacting [https://browser-release-b.azureedge.net] returned HTTP STATUS [0]
Verifying reachability for [wem.cloud.com] ...
Contacting [https://wem.cloud.com] returned HTTP STATUS [0]
Verifying reachability for [dl.cacerts.digicert.com/DigiCertAssuredIDRootCA.crt] ...
Contacting [https://dl.cacerts.digicert.com/DigiCertAssuredIDRootCA.crt] returned HTTP STATUS [0]
Verifying reachability for [dl.cacerts.digicert.com/DigiCertSHA2AssuredIDCodeSigningCA.crt] ...
Contacting [https://dl.cacerts.digicert.com/DigiCertSHA2AssuredIDCodeSigningCA.crt] returned HTTP STATUS [0]
[CTX223828] Checking for presence of certificate and its validity: DigiCert Assured ID Root CA
---> DigiCert Assured ID Root CA -> FOUND
---> Certificate's time is valid.
[CTX223828] Checking for presence of certificate and its validity: DigiCert SHA2 Assured ID Code Signing CA
---> DigiCert SHA2 Assured ID Code Signing CA -> FOUND
---> Certificate's time is valid.

Setting the empty Proxy config in the tool changes the Default Proxy Access type to 1 and all Tests are successful except citrxdata.com

Quote

Validating AD domain reachability...
The operation completed successfully.
Performing AD domain logon to verify reachability...
The operation completed successfully.
Verifying reachability for [www.citrix.com] ...
Contacting [https://www.citrix.com] returned HTTP STATUS [200]
Verifying reachability for [www.microsoft.com] ...
Contacting [https://www.microsoft.com] returned HTTP STATUS [200]
Verifying reachability for [www.google.com] ...
Contacting [https://www.google.com] returned HTTP STATUS [200]
Verifying reachability for [cloud.com] ...
Contacting [https://cloud.com] returned HTTP STATUS [200]
Verifying reachability for [citrixdata.com] ...
Contacting [https://citrixdata.com] returned HTTP STATUS [0]
Verifying reachability for [sharefile.com] ...
Contacting [https://sharefile.com] returned HTTP STATUS [200]
Verifying reachability for [browser-release-a.azureedge.net] ...
Contacting [https://browser-release-a.azureedge.net] returned HTTP STATUS [200]
Verifying reachability for [browser-release-b.azureedge.net] ...
Contacting [https://browser-release-b.azureedge.net] returned HTTP STATUS [200]
Verifying reachability for [wem.cloud.com] ...
Contacting [https://wem.cloud.com] returned HTTP STATUS [200]
Verifying reachability for [dl.cacerts.digicert.com/DigiCertAssuredIDRootCA.crt] ...
Contacting [https://dl.cacerts.digicert.com/DigiCertAssuredIDRootCA.crt] returned HTTP STATUS [200]
Verifying reachability for [dl.cacerts.digicert.com/DigiCertSHA2AssuredIDCodeSigningCA.crt] ...
Contacting [https://dl.cacerts.digicert.com/DigiCertSHA2AssuredIDCodeSigningCA.crt] returned HTTP STATUS [200]
[CTX223828] Checking for presence of certificate and its validity: DigiCert Assured ID Root CA
---> DigiCert Assured ID Root CA -> FOUND
---> Certificate's time is valid.
[CTX223828] Checking for presence of certificate and its validity: DigiCert SHA2 Assured ID Code Signing CA
---> DigiCert SHA2 Assured ID Code Signing CA -> FOUND
---> Certificate's time is valid.

The Server is a plain Vanilla Windows 2019 Server joined to the LAB Domain.

I have no more idea. I'm not really sure if there is a Connection between the results of the Cloud Connector Connectivity Check and the error. The Connectivity Checks the Setup does upfront will pass without issues.

Anyone an idea?

Cloud Connector Monitoring

Thu, 15 Jul 2021 07:08:41 +0000

We want to monitor our cloud connectors.

Do you have any suggestions which local services are important?

Cloud connectivity test fails

Mon, 30 Apr 2018 10:56:45 +0000

After successful installation of the cloud connector and reboot, the final connectivity test fails with the error :

We were unable to validate connectivity.

We were unable to connect to the following addresses:

https://reg.c.nssvc.net:443/Control/Ping

A wireshark trace shows the connection failing on proxy authentication.

I have followed https://docs.citrix.com/en-us/citrix-cloud/citrix-cloud-resource-locations/citrix-cloud-connector/proxy-firewall-configuration.html and https://support.citrix.com/article/CTX221823 but neither mention a proxy account.

How/where do I configure a proxy account for the connector to use?

CVADS, Cloud Connector, MCS and SCCM Connector

Mon, 29 Mar 2021 01:34:43 +0000

So at the moment we are playing with a trial subscription to Citrix Virtual Apps and Desktop Service (CVADS). We have installed several cloud connectors and I have successfully deployed a Windows 2016 Session host via MCS to our on Premise SCVMM Cluster and connected to it via the Cloud Portal. All working wonderfully.

In our on premise installation we use SCCM to manage images via the SCCM Conector 3.1 and I noticed that MCS on the cloud offers the same option (to restart updated image later if using SCCM). Does anyone know if it is possible to configure the SCCM connector to work with CVADS and if so How? Do we specify the Cloud Connector as a Citrix Delivery Controller?

Regards,

Ian

When Install Cloud Connector trouble signin

Wed, 13 May 2020 23:38:35 +0000

Hi All,

i have a trouble when i will install cloud connector on server, the problem is "can't reach this page" after login citrix cloud account. attached the screenshot.

please your help and advice.

Thanks a lot,

Hendra

Citrix Cloud Connectivity Test Intermittently Fails

Wed, 06 Nov 2019 18:57:38 +0000

We've had an issue after last auto patch of our Cloud Connectors on Saturday Nov 2nd, after this patching all of our resource locations spanning 3 different timezones have all intermittently failed their connectivity test.

As of Monday all the Cloud Connectors failed on the same errors.

"We are Unable to connect to the following addresses"

https://........ ( not sure if i can post this URL as it has our company name in it)

As of Tuesday somehow half the connectors are now stable.

As of this morning the only one site has this same error.

There's nothing on our networking side that would point to a local problem that spanned across three geo loactions.

There's no proxy involved, if we go the website that it says it fails on through a web browser it 100% works all the time.

We uninstalled and reinstalled latest connector no avail, ran wireshark and it showed some TCP retransmissions to that URL but that is about it.

Support is trying to escalate and at the same time on Saturday we lost all our metrics on Cloud Director.

Any insight on this issue, is this a widespread issue with other companies with the latest patch possibly,.

I'm also thinking it could be a load balancing issue on Cloud side as this is intermittent if I continue to click on the connectivity test it will succeed but then a few more times it will then fail.