To change the XML port in XenDesktop 7.x, complete the following steps:
Open command prompt and navigate to cd “c:\Program Files\Citrix\Broker\Service” Type BrokerService.exe /show and press Enter to show the current ports. To change the XML port type, BrokerService.exe -wiport (storefrontport) port and press Enter. For storefront it would be BrokerService.exe -StoreFrontPort PortNumber. The Citrix Broker Service will then automatically stop and start to apply the change. Run the BrokerService.exe /show command again and validating the Storefront Port value to confirm.
There are multiple ways on how we can find citrix xendesktop database server name:
via powershell: Use command Get-ConfigDBConnection (or Get-BrokerDBConnection) on the delivery controller. Both these commands will show your database server, instance name and database name. Using registry: Navigate to “HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\XDservices\ ConfigLoggingSiteSchema\DataStore\Connections” registry key on the delivery controller and check value of key, ConnectionString. This will have same information as above powershell command. This will be useful if server is not responding to any powershell commands.
On PVS 7.15 LTSR, with server 2016 OS, you might end up with below error while using xendesktop setup wizard or streaming wizard:
You might install your vcenter server certificate on your pvs server and navigate to https://vcenterserver/sdk without certificate errors, but still it wont work. On 2012 OS, TLS is enabled by default, in 2016 we have to manually enable it. Follow below steps to do so:
Goto HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework folder.
Issue: copying OS via pvs imaging wizard in pvs base machine, would show a green status bar with the progress. It completes till the end, you wont see Done button. It will be in green progress bar forever. You might see an error in pvs event log:
Event id: 11
Detected one or more hung threads. Please send Stream.log to support.
In other event id 11 entry, you would see, Terminating StreamProcess.
Issue: Some of the citrix VDIs are powered off in vcenter automatically. Logs show that citrix powered off these machines. OR When users try to login to their VDI, it throws an error. Powerstate for all the VDIs in citrix site show as unknown.
Analysis and Solution:
when citrix tries to power on a VDI, it should be brokered through a citrix delivery controller (Lets say DDC1). If this delivery controller has any issue from contacting the vcenter, it will report this VDI state as unknown and power off that VDI.
Booting target device to a vDisk was showing the following error after downloading the bootstrap file: “Server [IP Address]:6930: vDisk file access permission denied.”
Solution1: Open services.msc, goto stream service, check the account that stream service is running on. Add that account that runs the “Stream Service” to the security properties of the .vhd and .pvp files. Retry your PVS vm and check.
Solution2: If you have copied the vhd/vhdx file, remove it and copy it again.
In XenDesktop setup wizard, it guides same as creating catalog, adding number of vms, create ad accounts or not,what will be the new vm name, what is the new vms boot order, PXE or BDM etc etc.. same process as creating catalog. It creates catalog in xd and manages those vms.
In Streamed VM Setup wizard, it just creates multiple vms, and adds them to pvs so that they can be monitored/managed only from pvs console.
Citrix Provisioning supports several write cache destination options. The write cache destination for a vDisk is selected on the General tab, which is available from the vDisk File Properties dialog.
Considerations and requirements:
Consider the impact of using server side persistent write cache. Persistent cache should only be used where unauthorized users have unprivileged access to a machine. Ensure that machines are not shared among users. If you are selecting cache on local hard drive, ensure that the hard-disk drive is formatted with NTFS for Window devices, with a minimum of 500 MB.
To remove any locally stored storefront sites list, go to the following keys and delete your store entries from the list:
HKCUSoftwarecitrixdazzle* HKCUSoftwarecitrixreceiverSR* HKCUSoftwarecitrixreceiverctxaccount* If you have pushed store name and link thorough a policy, run a gpupdate. If not, manually enter site name or run config file from your storefront web link.
We have two ways to update a pvs vDisk. Lets see both of them below:
Process 1 (official):
Right click on a Standard Mode vDisk and choose version and create new version. This will create avhdx and pvp files. You can do this when there are existing connections on the vDisk. Set the update target device to maintenance mode. Boot the target device VM in hypervisor. While booting, it will prompt whether you want to boot into maintenance mode or regualr mode.
