Comments on: New PowerShell Script: Remove-HostingConnection V1.0 https://www.carlwebster.com/new-powershell-script-remove-hostingconnection-v1-0/ The Accidental Citrix Admin - The site for those who find themselves supporting Citrix involuntarily or accidentally Mon, 31 May 2021 19:22:30 +0000 hourly 1 https://wordpress.org/?v=6.8.2 By: Carl Webster https://www.carlwebster.com/new-powershell-script-remove-hostingconnection-v1-0/comment-page-1/#comment-1663 Mon, 18 Feb 2019 14:29:28 +0000 https://www.carlwebster.com/?p=10546#comment-1663 In reply to Jonathan Redford.

I have not heard of that before and without having access to your system, I don’t know what you need to do to resolve it. Are you able to open a support ticket with either Nutanix or Citrix? I have a few friends who work at Nutanix. I will see if they have any suggestions.

Thanks

Webster

]]> By: Jonathan Redford https://www.carlwebster.com/new-powershell-script-remove-hostingconnection-v1-0/comment-page-1/#comment-1662 Sun, 17 Feb 2019 05:21:21 +0000 https://www.carlwebster.com/?p=10546#comment-1662 Ok… I have a pesky controller in my environment that won’t let go of Nutanix after I upgraded the hypervisor. I’ve removed the machine catalogs and there are still 13 background jobs pending. Now, I have looked into clearing these jobs, but there are a lot to sift through. Like over 10000 kind of a lot. Your script cannot handle that too easily apparently. I am not sure what needs to be changed with the script so I figured I would nudge you and see if you’ve heard of this one before. Code looks pretty tight, btw.

]]> By: Carl Webster https://www.carlwebster.com/new-powershell-script-remove-hostingconnection-v1-0/comment-page-1/#comment-1469 Sat, 04 Nov 2017 20:56:31 +0000 https://www.carlwebster.com/?p=10546#comment-1469 In reply to Andrew Williamson.

I found the logic issue you reported. Thanks for finding the bug. I have submitted the fix to my PowerShell mentor for his feedback. It appears to work for me. If you would like to test the fix, just send me an email. webster@carlwebster.com

Thanks

Webster

]]> By: Carl Webster https://www.carlwebster.com/new-powershell-script-remove-hostingconnection-v1-0/comment-page-1/#comment-1468 Thu, 02 Nov 2017 10:27:59 +0000 https://www.carlwebster.com/?p=10546#comment-1468 In reply to Andrew Williamson.

When I get back home and to my lab, I will re-test that scenario. Thanks for looking at the script.

Webster

]]> By: Andrew Williamson https://www.carlwebster.com/new-powershell-script-remove-hostingconnection-v1-0/comment-page-1/#comment-1467 Thu, 02 Nov 2017 10:23:39 +0000 https://www.carlwebster.com/?p=10546#comment-1467 Nice script Carl – can’t test it, but I think I spotted a slight logic flaw?

Your ShouldProcess will rightly only operate if -WhatIf isn’t provided – but it looks like you’re going to write fails to your log if you supply WhatIf. Which isn’t really a fail – you just didn’t carry out the action, in which case no point in logging?

If I’m reading it right, here’s a typical sample with line numbers where I think the issue is:

552: Set Succeeded = false
555: Start the highlevel log action with Start-LogHighLevelOperation
563: remove-item with whatif…
569: and if that worked, succeeded = true
But we passed -whatif, so succeeded = false – for something we never tried to do
583: close and write a log for that fail

Would suggest perhaps wrapping the logging elements as well in the ShouldProcess blocks. Otherwise, every time you pass WhatIf (testing etc), you’ll be logging fails all over the place.

]]>