Error: “Your apps are not available at this time. Please try again in a few minutes or contact your help desk with this information: Cannot contact Store”

Command line installation (CLI) is not support for NetScaler URL. But, there are 3 options available that may be helpful.

1. Export store provisioning files for users https://docs.citrix.com/en-us/storefront/2-6/dws-manage/dws-manage-store/dws-export-file.html

2. Configuring NetScaler Gateway Store via GPO https://docs.citrix.com/en-us/receiver/windows/4-5/configure/receiver-windows-configure-app-delivery-wrapper.html#par_anchortitle_80df

3. Connecting to StoreFront by Using Email-Based Discovery http://docs.citrix.com/en-us/netscaler-gateway/10-1/ng-xa-xd-integration-edocs-landing/ng-clg-integration-wrapper-con/ng-clg-session-policies-overview-con/ng-clg-storefront-policies-con/ng-clg-storefront-email-discovery-tsk.html From the end-users perspective email discovery may be easiest. But requires support configuration of DNS entry and other configuration as noted in documentation. The export store provisioning file is easy to generate file in StoreFront, but requires user to open .CR file (it’s an XML file that is FTA with Receiver) and accept configuration (click “yes* button) and certificate accept dialog may display. So, it requires some user interaction and depends on end-user training even if the training is minimal. The GPO push of NetScaler URL (Configuring NetScaler Gateway Store via GPO) requires users to be connected to the domain to receive policy and configuration.

docs.citrix.com/en-us/netscaler-gateway/10-1/ng-xa-xd-integration-edocs-landing/ng-clg-integration-wrapper-con/ng-clg-session-policies-overview-con/ng-clg-storefront-policies-con/ng-clg-storefront-email-discovery-tsk.html

Related:

  • No Related Posts

Error “XDDS: 2367399E Cannot Create a Catalog Using AWS Host : Image Preparation VM Failed, Message No Facility Available for Disk Upload”

Exception:

Citrix.Console.Models.Exceptions.ProvisioningTaskException A volume service instance could not be launched in your cloud connection. In Studio, select Hosting in the left pane and then select the cloud connection. Click Test Connection in the Actions pane. The test results should provide additional information.

at Citrix.Console.PowerShellSdk.ProvisioningSchemeService.BackgroundTasks.ProvisioningSchemeTask.CheckForTerminatingError(SdkProvisioningSchemeAction sdkProvisioningSchemeAction)

at Citrix.Console.PowerShellSdk.ProvisioningSchemeService.BackgroundTasks.ProvisioningSchemeTask.WaitForProvisioningSchemeActionCompletion(Guid taskId, Action`1 actionResultsObtained)

at Citrix.Console.PowerShellSdk.ProvisioningSchemeService.BackgroundTasks.ProvisioningSchemeCreationTask.StartProvisioningAction()

at Citrix.Console.PowerShellSdk.ProvisioningSchemeService.BackgroundTasks.ProvisioningSchemeCreationTask.RunTask()

at Citrix.Console.PowerShellSdk.BackgroundTaskService.BackgroundTask.Task.Run()

DesktopStudio_ErrorId : UnknownError

ErrorCategory : NotSpecified

ErrorID : NoDiskContentTransferService

TaskErrorInformation : Terminated

InternalErrorMessage : No facility available for disk upload.”,””

Related:

  • No Related Posts

How to Resolve the Error “Operation results in exceeding quota limits” while creating MCS catalog for the VDA hosted on Azure

Going by the error message it seems to be an issue with the quota limit which points to the Azure subscription.. Solution is to add additional resources.

Running the command “azure vm list-usage” will further confirm this.

On the Azure side, you may get the following error {“code”:”OperationNotAllowed”,”message”:”Operation results in exceeding quota limits of Core}.

Following articles talks about the Azure subscription.


Most of the time when provisioning failure occurs due to quota limits, it is either Cores, NICs or Storage Accounts quota issue. So make sure you have sufficient cores, NICs and Storage Accounts to provision the VDAs.

Please contact Microsoft support to increase the quota for your subscription, once the requested quota is provisioned by Microsoft retry the MCS catalog creation, it will be successful.

User-added image

Related:

Support statement on storage migration of MCS machines

Background :

Customers using XenDesktop Machine Creation Service (MCS) with VMWare, Xenserver or Hyper-v as hypervisor may want to relocate the desktops to another datastore for various reasons such as datastore running out of space or datastore performance. This article tells why Citrix does not support the datastore migration of VMs.

Reason :

During the MCS catalog creation :

MCS creates a Provisioning scheme which is associated to the HypervisorconectionID and storage ID, the storages which are defined under the hosting unit in the hosting tab on Studio console has those catalog IDs mapped, also all these information gets stored in the database during the creation of the catalog.

So if we go ahead and migrate those VMs and put them on a new storage, first of all DDC do not identify those VMs as our DB has those VMs mapped to other storage IDs and Provisioning IDs.

Even if we create a new host connection, we will not be able to map the existing Provisioning scheme with the new Hypervisor Connection due to limitation of Xendesktop Powershell SDKs.

1. When we create a MCS catalog HypervisorconnectionID and HostingUnitID gets mapped to the MCS catalog or Proviosning Scheme. Examples :

This is our Hypervisor connection which we created using studio under hosting tab :

User-added image

Can retrieve the same information using powershell using the following commands :

PS C:Usersadministrator.ANUJ>asnp Citrix*

PS C:Usersadministrator.ANUJ> cd xdhyp:

PS XDHyp:> cd .connections

PS XDHyp:Connections> ls

User-added image

Same goes to hostingunit :

User-added image

Using powershell :

Run the following commands :

PS C:Usersadministrator.ANUJ>asnp Citrix*

PS C:Usersadministrator.ANUJ> cd xdhyp:

PS XDHyp:> cd .hostingunits

PS XDHyp:Connections> ls

User-added image


2. Now we have to consider the Hypervisorconnection ID and HostingunitID From our example :

HypervisorConnectionName : XDHost

HypervisorConnectionUid : 4fcfdde4-6799-43d8-a7c1-4aec168889ce

HostingUnitName : XDresource

HostingUnitUid : a567b103-d54e-4dc8-9455-a04171c35d68

A. Run Get-ProvScheme to get an output of MCS created catalogs and match the hosting unit name and hostingunit ID :

User-added image

b. Prov scheme or MCS catalog created with that Hosting resource should show the same ID.

3. One more alternate to check the same thing using VMs identity :

PS XDHyp:HostingUnits> Get-ProvVM -VMName “PVD2″(PVD2 is the machine name)

User-added image

Take the output and compare with above IDs.

If the IDs matches, we will get to know the machines are associated to these storages, and there is no way to change these IDs using commands or GUI.

Note : Modifying the DB tables using DB queries are not supported.

Work Around currently available:

  1. If it is a case of MCS Random catalog, we strictly recommend to create a new catalog with the available master image.
  2. If it is a MCS Dedicated catalog , we can remove the machines from the catalog (via Studio, this operation will delete the machine’s entry from the XenDesktop database), leave them in hypervisor and their machine accounts on active directory, we can now use the same machine to create a new catalog (non MCS/PVS) and import those machine in this catalog. (You can also add these machines to an existing non MCS/PVS catalog).
  3. If it is a case of MCS with PVD machines, we can go through backup and restore process as per http://docs.citrix.com/en-us/xenapp-and-xendesktop/7/cds-manage-wrapper-rho/cds-about-personal-vdisks/cds-manage-personal-vdisks.html

Note :

This documentation is only valid for MCS not PVS or any 3rd party technology to add machines into the catalog.

Related:

App Layering – How to deploy Microsoft SCCM in a layer

SCCM is best deployed in the platform layer. It is best to install the client as one of the last components on the platform layer to ensure that the client is sealed correctly before attempting to finalize the layer. Sealing a layer is the process of completing all outstanding processes, for example NGEN processes.

Note: Deploying the SCCM client in the OS layer is not recommended, because it requires handling the agent startup on the packaging machine whenever you create or update a layer.

Deploy SCCM in a platform layer

To deploy SCCM in a layer:

1.In the App Layering management console, select the Layers tab and the Platform Layers subtab.

2.Click Create Platform Layer and complete the Create Platform Layer wizard using these tips:

·On the Create Platform Wizard Connector page if you do not yet have a connector configuration, click New and follow the steps to create one for on your hypervisor.

·For Platform Types, select the radio button for creating and updating layers. Then choose your hypervisor from the dropdown menu.

·On the Confirm and Complete page, verify your settings and click Create Layer.

3.Once you’ve created the platform layer machine, connect to and log into the packaging machine.

4.Install your platform and SCCM software on the packaging machine:

·If you use a connection broker, install it.

·If the App Layering appliance is installed on a different hypervisor than the one where you will be creating this layer, install the hypervisor tools next.

·If you use provisioning software that is not Citrix Provisioning, install it next.

·Install SCCM last, unless you are also installing Citrix Provisioning.

·If you use Citrix Provisioning, install it last.

When installing SCCM, follow all of the steps in the Microsoft article, [Implementing SCCM in a XenDesktop environment](https://social.technet.microsoft.com/wiki/contents/articles/23923.implementing-sccm-in-a-xendesktop-vdi-environment.aspx).

Note: These steps apply to running the SCCM client in any VDI environment.

5.Open an administrator command window and execute the SEALSCCMClient.cmd script included in the App Layering OS Machine Tools download:

`c:windowssetupscriptsSEALSCCMCLient.cmd`

Note: Run the SEALSCCMClient.cmd script whenever you update this layer.

6.Double-click the Shutdown For Finalize icon to verify the layer and shut down the packaging machine.

·If the connector configuration selected in the wizard is set to use Offload Compositing, the layer is automatically finalized.

·If the connector configuration is not set to Offload Compositing, finalize the layer manually, as described in the detailed steps in this article.

Start the CCMEXEC service before starting Software Center

Always start the CCMEXEC service before starting Software Center and trying to interface with the server to get the status of applications and installing them. If the service is not running, the Software Center sometimes shows an error starting up, and you have to start it manually.

The layering service checks to see if the CCMEXEC is configured, and if it is, starts the service as part of the machine’s startup process. Once logged into the machine, the service should already be running, and you are less likely to run into the scenario where starting the app results in an error.

What to expect from installed applications

The SCCM server dictates and reports which applications are installed for which user on what machine.

In a non-persistent world, a user often logs into a different machine on each login. The server views every one of those logins as a new combination of the specific user from that specific machine, so it only shows the applications that it was informed about when the user installed the application from that machine. There is no way of asking the SCCM server to inventory the installed applications on a machine and report the apps found for the current user. However, when a user logs onto their desktop, the only time they need to go into the Software Center is to install an application that they don’t currently have.

In the scenario where the software is not already available from the Start menu or the desktop, users can still install the application that they need.If a user is confused about an application that they think they have installed already, they can click on the install, and the server will check to see if it is installed. If the application is already installed, the status changes to “Uninstall” and shows the application in the installed applications list and the date it was installed.

Related:

Cisco Prime Collaboration Provisioning Information Disclosure Vulnerability

A vulnerability in the web-based management interface of Cisco Prime Collaboration Provisioning could allow an unauthenticated, remote attacker to obtain sensitive information about an affected device.

The vulnerability exists because replies from the web-based management interface include unnecessary server information. An attacker could exploit this vulnerability by inspecting replies received from the web-based management interface. A successful exploit could allow the attacker to obtain details about the operating system, including the web server version that is running on the device, which could be used to perform further attacks.

There are no workarounds that address this vulnerability.

This advisory is available at the following link:
https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-prim-collab-disclo-FAnX4DKB

Security Impact Rating: Medium

CVE: CVE-2020-3193

Related:

  • No Related Posts

How to create a template for the connector and provisioning application

It is recommended to have a template set in the connector configuration.. This ensures the VMs being created and the published image are based on the same hardware specifications and also prevents issues with the time.


1) Find the Gold Image used to create the base OS Layer or use a vm which is known to be configured as wanted and working properly. Preferably use a vm with the same OS and build.

2) Make a clone of either of the VMs

3) Edit the cloned vm and remove all hard disks

4) Convert the vm to a template

5) Use the template in our connector configuration and as the template to create new VMs with the provisioning software. This is critical for PVS devices to stream properly.

NOTE: Possible issues are wrong NICs in the production desktops, issues with the hypervisor tools and associated components, possible BSOD when accessing a desktop. session.

Related:

How Your IT Team Can Take Advantage of Predictive Analytics

Is your company aiming to be a leader in the field of predictive analytics? New research suggests it should. ESG research finds that AI-enabled organizations considered to be the “Most Advanced” IT shops are 2.6x more likely to lead the competition in business intelligence and analytics. Organizations that are categorized as “Most Advanced” use: Modern servers with extensive automation capabilities (i.e., automated updating, monitoring, configuring, provisioning, and issue remediation). Accelerators such as GPUs or FPGAs to support AI workloads. Converged/hyperconverged infrastructure to support AI workloads. ESG refers to the “Most Advanced” AI-enabled organizations as Stage 3, … READ MORE

Related:

Error: “No device license is currently available for this computer”

When configuring XenDesktop or provisioned XenApp, the following error message appears:

“No device license is currently available for this computer. A system shutdown will be initiated in 96 hours. To avoid loss of data, save your work now and close all the applications.”

User-added image

Provisioning Services virtual Disk (vDisk) status reports no license information, as displayed in the following screen shot:

User-added image

Related: