The Accidental Citrix Admin - The site for those who find themselves supporting Citrix involuntarily or accidentally
About a year ago, I released V1.0 of this script and stated if I ever found the time I would update it to not require XenApp 6.5. Finally, I took the time between customer calls to update this script (and two others).
About a year ago, I released V1.0 of this script and stated if I ever found the time I would update it to not require XenApp 6.5. Finally, I took the time between customer calls to update this script (and two others).
About a year ago, I released V1.0 of this script and stated if I ever found the time I would update it to not require XenApp 6.5. Finally, I took the time between customer calls to update this script (and two others).
A few months back, I worked on a project where the customer needed to find all services on all servers that used a specific Active Directory (AD) account name. The problem was, they had no idea how the account name had been entered, nor did they know which server or what service used the account. I created a hard-coded script to search all computers in Active Directory for a partial account name. I finally made the time to make the script more useful and generic.
Five weeks ago, on the same day, I received three emails asking if I had a spreadsheet listing all the Citrix policy settings like Microsoft supplies. I replied I did not and had been asking Citrix for such an Excel file since March 2012. Someone pointed me to this Citrix article on Citrix Policy Reference but it has not been updated in three years. It also contains no data for any version of XenApp or XenDesktop 7.x. I reached out to several people at Citrix to see if such a file existed and all promised to get back to me. No one ever responded. So I started my own Excel file based on what little I had from the documentation scripts. There was so much missing information that I reached back out to my Citrix contacts because surely this information is sitting on some developer’s computer somewhere at Citrix. After pestering my Citrix contacts, I, again, never received a single response. I decided to take matters into my own hands and start a community project.
A few weeks ago, the town I live in had extremely severe thunderstorms roll through. When the tornado sirens went off and all our mobile devices started screaming “Warning: tornado sighted in your immediate area. Take shelter immediately!”, I did not bother doing a proper shutdown of all my lab equipment. The tornado did extensive damage in our town but missed our house by about a mile or two as the crow flies. We were without power most of the night. The power outage lasted longer than the batteries in all my battery backup systems. Needless to say, all my XenServer, vSphere, and vCenter hosts did an ungraceful power off. My two Synology NAS units have USB connections to their UPS and are configured for proper shutdowns in the event of power loss. For the past few weeks, I thought all was well in my lab, but that wasn’t the case I found out.
On a recent project, I needed to set up high availability for the Citrix Virtual Apps and Desktops (CVAD) databases. The customer wanted to use Microsoft SQL Server 2016 Standard and I was tasked with implementing the new Basic Availability Groups. This article details the steps I took to implement Microsoft SQL Server 2016 Standard Basic Availability Groups for CVAD.
I have been told that if you install the Citrix Provisioning Services (PVS) 7.7, or later, console on version 7.0 through 7.6 LTSR that you can use the new Citrix PVS PowerShell. You know, the new, real, object-oriented PowerShell. I decided to test this to see if it was true.
Recently on a project, I noticed lots of home folder errors in the customer’s System event log. I offered to take my Folder Redirection Error script and modify it to find home folder errors.
I have received numerous emails and comments from people having issues running the Active Directory (AD) documentation script in a forest that contains multiple domains. I finally got off my lazy rear end and took the time to figure out the issue and solution.