#Version 5.00 14-Dec-2018

• Version 5.00 created on June 1, 2015
• V5.00 released to the community 14-Dec-2018
• Removed minimum requirement for PowerShell V3
• Fixed all code to make it work in PowerShell V2 (That was a royal PITA)
• Removed all SMTP related code as we could not could that code to work with PowerShell V2 (If you think you can make it work, let me know)
• Added HTML and Text output options
• Added parameters to bring the code up to the same standard as the other documentation scripts
  • AdminAddress
  • MaxDetails
  • Dev
  • ScriptInfo
  • Log
  • NoPolicies
  • NoADPolicies
• Update help text

Your first question is why did I bother to update an old script? I started adding HTML and Text output back in early 2015 and stopped in June, for a reason I don’t remember.  Recently, I have had a few projects to move companies from XenApp 6.5 to XenApp 7.15 LTSR. Unfortunately, none of the XenApp 6.5 servers had PowerShell 3 or later installed and I was not allowed to install PowerShell V3 either. Also, a couple of companies don’t publish WOrd so Word was not available. Also recently, I have received several emails from other consultants in the same boat. They have customers with lots of XenApp 6.5 Farms that needed to be documented before the migration or the consultant needed documentation to know what all was needed in the new 7.15 Site.

There were a lot of subtle differences in PowerShell code that had to be addressed to backport this script to work with PowerShell V2. Also, getting the email code to work with TLS 1.2 on Windows Server 2008 R2 was very problematic. It would work on one server but not work on any others. PowerShell V2 also did not like all the parameter sets the script uses to handle four output formats and SMTP. Unfortunately, we wasted a lot of time trying to get the SMTP stuff working but never could. I made the decision to remove all SMTP related help text, parameters, and code.

Along the way in updating the code, I found many typos and incorrect variables. Some had been in the code since 2011 and made me wondered why no one reported the report had missing data. Oh well, I fixed all I found.

For you consultants who needed HTML or Text output or who couldn’t use PowerShell V3+, here you go. I hope you find this update useful.

For those that helped test this script, thank you for your time. The Citrix community rocks.

You can always find the most current script by going to https://www.carlwebster.com/where-to-get-copies-of-the-documentation-scripts/

Thanks

Webster