Carl Webster Accessibility Statement

Carl Webster is committed to facilitating the accessibility and usability of its website, carlwebster.com, for everyone. Carl Webster aims to comply with all applicable standards, including the World Wide Web Consortium’s Web Content Accessibility Guidelines 2.0 up to Level AA (WCAG 2.0 AA). Carl Webster is proud of the efforts that we have completed and that are in-progress to ensure that our website is accessible to everyone.

If you experience any difficulty in accessing any part of this website, please feel free to email us at info@carlwebster.com and we will work with you to provide the information or service you seek through an alternate communication method that is accessible for you consistent with applicable law (for example, through telephone support).

  • Documentation Scripts Updated for Word 2016 Support

    October 5, 2015

    Active Directory, DHCP, PowerShell, PVS, VMware, XenApp 6.0, XenApp 6.5, XenApp/XenDesktop 7.0 - 7.7, XenDesktop 5.x

    The following scripts have been updated to add support for Word 2016 in all 11 supported languages.

    • Active Directory
    • DHCP
    • Provisioning Services
    • StoreFront (Client script update 7-Oct-2015)
    • VMware vSphere
    • XenApp 6
    • XenApp 6.5
    • XenApp/XenDesktop 7.x
    • XenDesktop 5

    In addition to these scripts, all the scripts currently in development have also been updated for Word 2016:

    • Provisioning Services V5 to support PVS 7.7 and the new PVS PowerShell
    • XenApp 6.5 V5 adding support for HTML and Text output
    • XenServer 6.x V1

    If you would like to help test any of the scripts in development, please send an email to Webster@carlwebster.com along with which script(s) you would like to help test.

    NOTE: The scripts are continually updated. You can always find the most current versions by going to https://www.carlwebster.com/where-to-get-copies-of-the-documentation-scripts/

    The scripts in development are only available by emailing me.

    Thanks

    Webster







    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 →

    6 Responses to “Documentation Scripts Updated for Word 2016 Support”

    1. Brian Says:
      December 29, 2016 at 12:24 pm

      Carl,
      Do the scripts need to be ran on the actual servers or can I run it from my workstation and run against the servers remotely? I am running the scripts and I get the following output below. I have all the pre-requisites installed per your documentation.

      PS C:\XA6SDK> .\XA6_Inventory_V42_signed.ps1

      Security warning
      Run only scripts that you trust. While scripts from the internet can be useful, this script can potentially harm your
      computer. If you trust this script, use the Unblock-File cmdlet to allow the script to run without this warning
      message. Do you want to run C:\XA6SDK\XA6_Inventory_V42_Signed.ps1?
      [D] Do not run [R] Run once [S] Suspend [?] Help (default is “D”): R
      VERBOSE: 12/29/2016 11:22:08: Testing output parameters
      VERBOSE: 12/29/2016 11:22:08: MSWord is set
      VERBOSE: 12/29/2016 11:22:08: CoName is
      Loading Windows PowerShell snap-in: Citrix.Common.Commands
      WARNING: Missing Windows PowerShell snap-ins Detected:
      WARNING: (Citrix.XenApp.Commands)
      C:\XA6SDK\XA6_Inventory_V42_Signed.ps1 : Missing Citrix PowerShell Snap-ins Detected, check the console above for more
      information. Are you sure you are running this script on a XenApp 6 Server? Script will now close.
      At line:1 char:1
      + .\XA6_Inventory_V42_signed.ps1
      + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      + CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
      + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,XA6_Inventory_V42_Signed.ps1

      Reply

      • Carl Webster Says:
        December 29, 2016 at 12:28 pm

        The XenApp 6 script does not support remoting and neither does the XenApp 6.x Group Policy module.

        The only scripts that support remote execution are Active Directory, DHCP, DNS, VMware, Nutanix, PVS, XenApp 6.5 (except for policies), XenDesktop 5 and XenApp/XenDesktop 7. XenDesktop 4, XenApp 5 for 2003, XenApp 5 for 2008, and XenApp 6 do not support remote execution.

        Sorry

        Webster

        Reply

        • Brian Says:
          December 29, 2016 at 2:40 pm

          Thanks Carl for the reply. I have used your scripts before in 7.x and they turned out wonderful reports.

          So if no remote then what are my options. Do I need to run this on each of the XenApp servers, DC’s, etc? But that would mean the SDK and Group Policy Module would need to be installed hence a change on production, which I’d like to avoid.

          Thanks!

          Reply

          • Carl Webster Says:
            December 29, 2016 at 4:38 pm

            Most people make most of their XenApp 6.x servers controllers. If that is your case, you can run the script from any XA6 server that has Word 2010/2013/2016 installed. If that is not your case, can you create a VM to be an IT XA6 server, join it to the farm, install Word, the other prereqs and use that VM to run the script. I do apologize for never taking the time to add HTML output to the XA6.x scripts.

            Webster

            Reply

    2. Kapil Says:
      December 19, 2016 at 12:06 am

      Hello Carl,

      Thanks for wonderful scripts. they work amazingly in my test infrastructure.

      I generally use the PVS and the XenApp scripts but most of my clients does not have Word 2010 installed on there PVS and Delivery controller, how can I run these scripts without having to install Word on these servers?

      Thanks & Regards,
      Kapil Bandlish

      Reply

      • Carl Webster Says:
        December 19, 2016 at 5:32 am

        The PVS and XenApp/XenDesktop scripts have supported being run on another computer since the beginning. Check the help text for each script. Also, those scripts will generate Text and HTML output. Again, check the help text.

        Thanks

        Webster

        Reply

    Leave a Reply