Block Level Transfer:
Presentation of storage can be formatted and managed as local drive.
Ex: A windows host that has been given a storage from SAN identifies the storage as a local disk and host is allowed to format the disk.
In this block level storage, raw volumes of storage are created and each block can be controlled as an individual hard drive. These Blocks are controlled by server based operating systems and each block can be individually formatted with the required file system.
One of the most critical, and challenging, architecture decisions an IT professional has to make is choosing a virtual server storage setup. Even with such a wide variety of choices, there isn’t a singular solution that is the absolute best for virtual servers. And because every work environment varies greatly, a data storage system that complements one solution may not work well with a different system.
Although Fibre Channel (FC) has been the primary choice for several years, network-attached storage (NAS) and iSCSI have become increasingly popular alternatives for virtualization because they provide solid performance for companies working with smaller budgets.
Till xenapp 6.5 we had a nice way to publish links and content. But from xenapp/xendesktop 7.X, we dont have this facility. So, we have to publish your share path as an application.
Create new app, as shown below:
Provide required permissions on your share folder to user group. Also, create registry key LogoffCheckerStartupDelayInSeconds as given in this citrix article: https://support.citrix.com/article/CTX128009
After this is done, your share path should open from a server session as a regular app.
Scalability: “Increasing” the capacity to meet the “increasing” workload.
Elasticity: “Increasing or reducing” the capacity to meet the “increasing or reducing” workload.
Scalability: In a scaling environment, the available resources may exceed to meet the “future demands”.
Elasticity: In the elastic environment, the available resources match the “current demands” as closely as possible.
Scalability: Scalability adapts only to the “workload increase” by “provisioning” the resources in an “incremental” manner.
Elasticity: Elasticity adapts to both the “workload increase” as well as “workload decrease” by “provisioning and deprovisioning” resources in an “autonomic” manner.
Most of the apps today, comes with - an exe or an msi package inside the original exe. Once you run them, they extract contents of the original exe to a folder in temp directory and start installing from that folder.
When you are installing an exe, we need to set installation mode to “install mode”. As per article, https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc754288(v=ws.10) we dont need to set installation mode to “install mode”, when we are installing an MSI.
Issue:
While creating/adding new machines to a machine catalog, if you mention 10 VDIs to create, xendesktop would create only 1 or 2, or some random number below 10, but not exactly 10.
Reason:
This happens because you have orphan AD accounts in your machine catalog.
Solution:
You have to remove those orphan AD accounts from your machine catalog. If your machine catalog has no other issues, Xendesktop would create the number of machines you specify in “add machines” option in a machine catalog.
When you create new machines in machine catalog, only some of the computer accounts would be created, and some other ad accounts would be created from citrix end, but in AD, it doesnt create those accounts.
you can check them by powershell:
1 2 Add-pssnapin citrix\* Get-AcctADAccount -IdentityPoolName machinecatalogname | ? {$\_.State -eq "Available" -and !($\_.ADAccountName)} Get the ADAccountSid value from above command, and use below command to remove those orphan AD accounts from citrix.
First view existing resources using below process:
Open powershell console and run below commands:
1 2 Add-pssnapin citrix\* Get-ProvScheme -ProvisioningSchemeName MachineCatalogName To update master image, follow steps given here:
https://www.knowcitrix.com/posts/find-master-image-used-by-machine-catalog-and-update-master-image-steps/
To increase cpu and hard disk size, you need to open master image, create new snapshot and update that snapshot as given in above link.
To change network resources, follow any one of the below steps as per your requirement:
Issue:
In one of the citrix sites that we had, all the user assignments to their existing static VDIs were removed automatically. This issue occurred every two weeks. None of the VDIs are deleted but when users login, they would get a new machine.
Solution:
In xendesktop logging tab, when I search with word “remove user” it shows me a lot of entries but only one user id is doing it.
Issue:
Not able to provision any new VDIs to existing machine catalog. All the existing machines work fine.
Solution:
As per https://support.citrix.com/article/CTX213019, enabled enableHttpDataStoreAccess value on vcenter but it didnt help. Thought to create new cluster in vcenter and move some hosts to it and add it to xendesktop, and publish new VDIs to it. As a part of this process, created new cluster, moved some hosts to it. One of the hosts in earlier old cluster was moved to maintenance mode because it was not moving all the VMs from it.
