Unable to Delete Resources: There is currently an active background action

An addition to CTX138318 about how to delete an old Citrix Studio Hosting connection.
Instead of deleting every task manually we make use of PowerShell piping and Out-GridView.

Today in Citrix Studio I discovered a dead Hosting connection I set up years ago for some MCS tests. When I tried to simply delete the connection, I received the following message:

The error message leads to the following (helpful!) KB article: CTX138318

After following the different steps outlined in the article …

… I ended up with something like this:

Which I should process via:

Which I didn’t want to do manually for each entry. But I remembered the session from Andreas Nick at the TecCon2018, where he showed examples about how to pipe the output of a command to a select grid. I’m not good at PowerShell at all, but I wanted to try it anyways. So after two hours of straight web research I ended up with the following code, which simplified this process a lot!

To explain each step in detail:

Line 1 Make PowerShell aware of the Citrix cmdlets.
Line 2 Switch to the Hypervisor Hosting connections of XenDesktop.
Line 3 Write the HostingUnitUid of the affected connection into a variable after a GridView Select.
Line 4 Create a list of all pending tasks and …
Line 5 Present it in a second GridView Select so you could delete all or selected tasks. The selection is being piped to the Remove command.

This will look similar to this:

In the Out-GridView you will first select the affected Hosting connection and in the second windows you will select all ProvTasks you may want to remove. Most of the time this will be all. There are certainly better ways to solve this, but the intend of this post is just to show you with how little work a repetitive task can be optimized with simple PowerShell tricks.

This worked great for me, but you should test this first!

Sometimes it can happen, that a ProvTask is “Running” and you can’t remove it. For this case I found a hint at discussions.citrix.com linked at the bottom.


This post was previously posted on mycugc.org.

How I build and maintain WSUS Server

There are hundreds of WSUS Server Tutorials available in the World Wild Web, and none of them fitted all my needs. I would never say that my way is the best way, but I spent quite some time with WSUS in the last few years and by now all of the servers I maintain work quite stable. (Except 2008, I hate Server 2008). 

First of all sorry for the German screenshots, but I thought better German screenshots than no article. The next time I setup a en-US WSUS I will swap the screenshots. 

Your best bet IMHO is to switch to Microsoft Windows Server 2016 asap. Server 2008 R2 won’t get Support for Windows 10 Feature Upgrades and Server 2012 R2 got it very delayed through an “interesting” hotfix. Windows Server 2016 seems to be the most reliable choice.
Second lesson I learned is, always install the Microsoft SQL Server Management Studio on the WSUS Server. You will need it sooner than later.
Third lesson is that WSUS will fail sooner or later, if you don’t execute a maintenance script on a regular basis.  Continue reading “How I build and maintain WSUS Server”

Neue Version: Analyze and troubleshoot the logon duration via PowerShell

Im August 2015 hat sich ControlUp bei der Citrix Community sehr beliebt gemacht, indem sie ihr Script zur Analyse des Login Prozesses frei zur Verfügung gestellt haben. Im Dezember 2015 hat dann der Entwickler eine neue Version des Scripts angekündigt.

Continue reading “Neue Version: Analyze and troubleshoot the logon duration via PowerShell”

Veeam Backup & Replication v8 PowerShell SDK AddIn nicht registriert

Durch unsere Kunden weite Migration weg von XenServer und SEP Sesam, hin zu VMware und Veeam, wurde es interessant mit Hilfe der PowerShell Befehle für Veeam den Backup Status zu überwachen. Hierzu gibt es ein schönes Template welches wir bereits erfolgreich einsetzen. (ZBX-VEEAM-BACKUP) Continue reading “Veeam Backup & Replication v8 PowerShell SDK AddIn nicht registriert”