All Documentation Scripts Have Been Updated 4-Jun-2014

All current scripts have had an -AddDateTime Parameter added. This has been requested by a few testers so I decided it was time to add it.

.PARAMETER AddDateTime
     Adds a date time stamp to the end of the file name.
     Time stamp is in the format of yyyy-MM-dd_HHmm.
     June 1, 2014 at 6PM is 2014-06-01_1800.
     Output filename will be ReportName_2014-06-01_1800.docx (or .pdf). [Webster: for the DHCP script, also .txt]
     This parameter is disabled by default.

This parameter has been added to the Active Directory, DHCP, all XenApp versions and the two XenDesktop scripts under development. This keeps all documentation scripts consistent in their functionality.

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

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 “All Documentation Scripts Have Been Updated 4-Jun-2014”

  1. Jeff Says:

    Hello Carl. I running the script directly from my PVS server(W2K12R2) PVS 7.1. When I try to use the -PDF option, it insists that I still install MS word. Also, when I try the -html switch, I receive a write-error, writeerrorexception..pointing to line:1 char:1. Any ideas on how to resolve this?

    Thanks,

    Jeff

    Reply

    • Carl Webster Says:

      From the Help Text:

      .PARAMETER HTML
      Creates an HTML file with an .html extension.
      This parameter is disabled by default.
      This parameter is reserved for a future update and no output is created at this time.

      The PDF option uses the Word SaveAs function to save the Word doc as a PDF file. That is why using the PDF option requires that Word be installed.

      Webster

      Reply

  2. Bjorn Says:

    Hi Carl,

    Very nice scripts 🙂 but on my XenApp 6.5 labserver the XA65_Inventory_V41.ps1 takes a very long time to run – about three hours!? Any idea why?

    Best Regards,
    Bjorn

    Reply

  3. Travis Says:

    I have tried to run this remote to my PVS servers and get this:

    PS C:\ps\pvs> .\PVS_Inventory_V41.ps1 -verbose
    VERBOSE: 07/10/2014 11:07:52: Checking for McliPSSnapin
    VERBOSE: 07/10/2014 11:07:56: Verifying PVS SOAP and Stream Services are running
    VERBOSE: 07/10/2014 11:07:56: Getting PVS version info
    WARNING: PVS version information could not be retrieved
    Write-Warning : A positional parameter cannot be found that accepts argument ‘Could not load file or assembly
    ‘EnterpriseAccess, Version=6.1.18.1236, Culture=neutral, PublicKeyToken=null’ or one of its dependencies. The system
    cannot find the file specified.’. This failure might be caused by applying the default parameter binding. You can
    disable the default parameter binding in $PSDefaultParameterValues by setting $PSDefaultParameterValues[“Disabled”] to
    be $true, and retry. The following default parameter was successfully bound for this cmdlet when the error occurred:
    -Verbose
    At C:\ps\pvs\PVS_Inventory_V41.ps1:1711 char:3
    + Write-Warning “Error(s) returned: ” $error[$x]
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : InvalidArgument: (:) [Write-Warning], ParameterBindingException
    + FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.PowerShell.Commands.WriteWarningCommand

    Write-Warning : A positional parameter cannot be found that accepts argument ‘Could not load file or assembly
    ‘EnterpriseAccess, Version=6.1.18.1236, Culture=neutral, PublicKeyToken=null’ or one of its dependencies. The system
    cannot find the file specified.’. This failure might be caused by applying the default parameter binding. You can
    disable the default parameter binding in $PSDefaultParameterValues by setting $PSDefaultParameterValues[“Disabled”] to
    be $true, and retry. The following default parameter was successfully bound for this cmdlet when the error occurred:
    -Verbose
    At C:\ps\pvs\PVS_Inventory_V41.ps1:1711 char:3
    + Write-Warning “Error(s) returned: ” $error[$x]
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : InvalidArgument: (:) [Write-Warning], ParameterBindingException
    + FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.PowerShell.Commands.WriteWarningCommand

    C:\ps\pvs\PVS_Inventory_V41.ps1 : Script is terminating
    At line:1 char:1
    + .\PVS_Inventory_V41.ps1 -verbose
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,PVS_Inventory_V41.ps1

    PS C:\ps\pvs>

    Any idea?

    Reply

Leave a Reply