The Citrix Self-Service Session Reset Tool is software that I write and manage in my own time on my lab equipment. It is often challenging to find the time to work on it as I have many projects on the go. And life in general often gets in the way. I get a lot of queries asking me when the next release will be available and if the feature they are looking for will be included. Rather than continually updating the main article, and responding to queries, I wanted to document where the project is at and what further work is to be completed.
Version 1.9 was the last public release back on 1st June 2022.
Why not ditch my APIs and use the Citrix Virtual Apps and Desktops REST APIs that are now included with on-prem Delivery Controllers from version 2209 or later?
I work in the Mining Industry where we have OT (Operational Technology) networks, also known as PCN (Process Control Network). This is a typical setup within the mining, oil and gas industries, as well as utilities such as water and electricity. Some have their own AD domain with no trusts. But they all typically have a separate Citrix Site due to risk mitigation and change management requirements, and what we refer to in the mining industry as “site survivability”, meaning that a mine site can keep running when all comms links are lost. At the time of writing this, many of these sites are still 2203 LTSR or lower. Until these platforms have been upgraded to 2402 LTSR or later, I cannot leverage the built in Citrix APIs, and will continue to leverage the PowerShell SDK that my APIs are built on. Apart from that, I also wanted to be inclusive and did not want to place others at a disadvantage that are still running older versions.
If you are running 2209 and above on-prem, or just using Citrix DaaS (Cloud), the APIs are there for you to leverage. So all you need to do is create a cool user interface (UI) using a Blazor Server Application.
HOWEVER, I have since found limitations with the CVAD APIs, especially for on-prem. The Citrix Product Manager has suggested that I should be continuing to use the PowerShell cmdlets for the foreseeable future, as the CVAD APIs are not expected to be “production” ready for some time.
I’m working on the following before the next version can be publicly released, which I’m planning for June 2025 early 2026:
- Securing the API secret information in the CtxSites.xml file
- JavaScript Bug
- Refactor Code
- Enable/Disable Maintenance Mode API
- Citrix PowerShell SDK Bug