Somewhere down the line, Citrix Admins need to upgrade their Citrix Site from one version to another, Example, from XenDesktop 71.5 LTSR to CVAD 1912 LTSR. For Citrix site upgrade, we have to mount the product ISO in Citrix server and run the setup file. But What about VDIs?
Based on your company’s VDA usage, you may have hundreds to thousands of VDIs in your company. How do you upgrade VDA agent on all those VDIs?
Images by Susanne F, Clker-Free-Vector-Images from Pixabay, and my own customization.
I have used a few hosting websites like Hpage, wordpress.com, etc.. for a long time. But I wanted to host my website on something free and fast. I thought of using GitHub pages, but converting my WordPress site to Github pages was a very big task for me. I was looking for easy to use software to generate MD pages.
As part of day to day tasks, one of the major activity for citrix admins is to maintain free VDIs in xendesktop delivery groups. If we dont have registered free VDI machines, and when new users try to connect to VDI, they would get errors like “Cannot start VM”. So, we have to make sure we have enough free VDIs in delivery groups. As a part of this process, I wrote a powershell script that would auto provision new VDIs to a given catalog and add them to delivery group.
The commands (ctxxmlss) to unregister the XML port and to reregister the XML port have not changed and can still be used as described in the Instructions. In addition, you must set the new XML service port policy in the Citrix GPO settings as shown in the screen shots. Note: The XML service port policy is a Computer policy and must also be set, even if the ctxxmlss command is successfully completed and states that the XML port is changed.
XML port in XenApp and XenDesktop 7.x version 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.
Based on your CVAD or XenDesktop version, you will find “WI port” or “Storefront port” in the output which is your xml port number.
XML port in XenApp 4.5, 5, 6.0 and 6.5 versions Open registry and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\CtxHttp path. Check the value for key “TcpPort”.
Change Time manually on NetScaler To change time and date on NetScaler, run the below command on NetScaler putty shell.
1 date +val YYMMDDHHMM where:
YY = Year
MM = Month
DD = Day
HH = Hour
MM = Minutes
Example" date +val 2208011111. This will set time as august 1st 2022.
Issue On newer netscaler machines, if you run above command, post reboot, time will change automatically. This is tested on NetScaler 13.
When configuring citrix gateway page, after entering credentials, it redirects back to login page. This happens continously.
To resolve this issue,
Open storefront console, and click manage receiver for websites. Check session policy timeout value.
use that same value in Gateway – Virtual server – Session policy – Edit session profile – Client experience – Session timeout option.
Also check in Citrix Gateway – Global Settings – Change Gloabl Settings – Client Experience – Session TIme-out (mins).
Issue When users connecting to applications from XenApp 6.5 (or less) version, randomly few users might get the error, The task you are trying to do can’t be completed because Remote Desktop Services is currently busy. Please try again in a few minutes. Other users should still be able to log on. No matter how many times that user connects to the application, they will still get same error. When Citrix admins try to logoff that session, it will not logoff.
This article explains the steps on how to login to netscaler using userPrincipalName instead of samAccountName or both at same time. If you follow these steps you can use sAMAccountName and userPrincipalName at Same Time for User Logon with Active Directory.
Configuration By default when you configure netscaler gateway, you would configure it to use userid which is samAccountName. Users enter their userid (like john.doe) and login to netscaler gateway. In this case, you will create an LDAP server with samAccountName as shown below.
Nuget error Have you ever tried to install a module through PowerShell? If yes, then you might have read or faced below error: PackageManagement\Get-PackageProvider : Unable to find package provider ‘NuGet imported yet. Try ‘Get-PackageProvider -ListAvailable’
Solution To solve this issue, open elevated PowerShell console and run the below command:
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
Next install Nuget packageprovider with the below command.
Install-PackageProvider -Name NuGet
Finally, run the install module command with the powershell vendor module you’d like to install.