• XenApp 6.5 V4.1 Documentation Script Has Been Updated 14-Apr-2014

    April 14, 2014

    PowerShell, XenApp 6.5

    I received an email from Lee Dehmer that he was getting a Divide by Zero error in the XenApp 6.5 script.  This same bug was in the XenApp 6.0 script.  When processing Worker Groups, I set a maximum table width of 60 columns.  The table is indented 36 pixels (or .5 inches/12.7 mm).  The two combined should allow the table to fit in the page width.  The problem was I made an assumption (sorry Remko) that a Worker Group defined by Security Group or Organization Unit (OU) would not have a name longer than 60 characters.  Any name longer than 60 gives a Dive by Zero.  For example, in PowerShell taking the integer result of 60/63 will give you the red, ugly “Attempt to divide by zero” error.  After fixing this bug (or my bad assumption) I took the time to add a few user requests into the script.

    The one thing that confused me when Lee first reported the bug was that the verbose message showed the server name was more than 60 characters long.  How thought how in the heck do you get a server name longer than 15 characters!!!  It turns out the verbose message said “server” even when the function was processing Security Groups or OUs.  I added an additional parameter to the function so the verbose message correctly shows what type of Worker Group is processed by the function.  The OU names are sorted by the length of the OU name.

    The function (or really my bad assumption) was also fixed so that if a Security Group or OU has a name longer than 60 characters, only one column is created for the table.

    Thanks to Lee for finding this assumption bug and working with me to make sure it was fixed.

    Worker Group by OU
    Worker Group by OU

    Now on to the user requests.

    David Figueroa requested this feature in September 2013.   It is about time I got it implemented.  David requested the in the Application section the Command Line and Working Directory be in a different font and size.  I had wanted to do this for a while but didn’t know how to do it.  Since Ryan Revord wrote the original WriteWordLine function I asked him to see if he could enhance his function to do this.  Ryan was able to enhance his function and that function is now in every completed and in development script.  Ryan’s enhanced WriteWordLine function allows for selecting a font name, font size, italics and bold.  Thanks Ryan.

    Command Line and Working Directory
    Command Line and Working Directory

    I am glad Pavel Stadler joined the testing group last fall.  He has be an extremely thorough tester and made numerous enhancement requests.  It will take a good while to implement the suggestions of his I agree with.

    Pavel has been most vocal about adding the Active Directory (AD) Group Policy name to the Citrix Policy name in the report.  This helps show which Citrix Policies are contained within what AD policies.  An AD policy can contain numerous Citrix policies.

    Citrix Policies
    Citrix Policies

    Pavel also suggested that not all Stopped Citrix services should be in Red.  If a Service startup type is Manual and the state is Stopped, that is not an error or cause for concern and should not be in red.  I agree.  Pavel went ahead and worked out the code to get the start mode and I just added some error checking.  There are some services where the code used cannot find a start mode so those are given a Startup Type of “Not Found”.

    Citrix Services
    Citrix Services

    You will see some of Pavel’s other enhancement requests in future updates.

    Script version is now 4.12.

    NOTE: This script is continually updated. You can always find the most current version by going to https://carlwebster.com/where-to-get-copies-of-the-documentation-scripts/



    About Carl Webster

    Webster is a Sr. Solutions Architect for Choice Solutions, LLC and specializes in Citrix, Active Directory and Technical Documentation. Webster has been working with Citrix products for many years starting with Multi-User OS/2 in 1990.

    View all posts by Carl Webster

    No comments yet.

    Leave a Reply