-
Citrix XenApp 6.5 Documentation Script Update 4.23
August 17, 2015
- Updated for CTX129229 updated August 2015
- Added checking for Hotfix Rollup 6
- Remove Microsoft recommended hotfixes no longer in the article
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/
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 WebsterSubscribe
Subscribe to our e-mail newsletter to receive updates.
8 Responses to “Citrix XenApp 6.5 Documentation Script Update 4.23”
Leave a Reply
- Updated for CTX129229 updated August 2015
November 9, 2015 at 10:00 am
Thank you for your outstanding scripts.
I have a question in regards to the XA65_Inventory_V42_Signed.ps1 script. When I run the script, the output for some of the XenApp servers do not show any published applications. There are applications published to all the XenApp servers. Do you have any suggestions as to what I need to check to get a complete output?
Thanks in advance for your assistance.
Walt Sikora
November 9, 2015 at 10:05 am
All the script does is:
$Applications = Get-XAApplication -ServerName $server.ServerName -EA 0 4>$Null| Sort FolderPath, DisplayName
That should retrieve all the applications that are published on the server.
Try that line and replace “$server.servername” with the name of a server not showing its published apps.
Thanks
Webster
September 15, 2015 at 7:14 am
Hello Carl,
First let me say thank you for all the spot on documentation you have developed and shared on your website. You do a great job, and I am truly thankful.
Recently I started an engagement with a client and was asked to perform an analysis of their Citrix XA 6.5 farm, and I figured a great way to get started would to be the use of your XA PoSH script.
The question is: When using the script, and the remote setup steps, can I make a connection through to a XA ZDC with the use of Cisco Any connect VPN? I have opened the firewalls on both side, have everything installed and configured per your document pre req’s and I still get a PoSH error saying it cannot make a connection to the server.
Any advice would be greatly appreciated.
Kind Regards,
Michael
September 17, 2015 at 10:21 am
After you establish the VPN connection, what happens when you issue the Set-XADefaultComputerName command?
Webster
September 17, 2015 at 4:55 pm
Hello Carl,
Listed below, is the commands I ran, it seamed to take the xadefaultcomputername just fine, but went down hill from there.
Windows PowerShell
Copyright (C) 2013 Microsoft Corporation. All rights reserved.
PS C:\Windows\system32> add-pssnapin citrix*
PS C:\Windows\system32> cd C:\Windows\SysWOW64\WindowsPowerShell\v1.0
PS C:\Windows\SysWOW64\WindowsPowerShell\v1.0> set-XADefaultComputerName maczdcxml01
PS C:\Windows\SysWOW64\WindowsPowerShell\v1.0> XA65_Inventory_V42.ps1
XA65_Inventory_V42.ps1 : The term ‘XA65_Inventory_V42.ps1’ is not recognized as the name of a cmdlet, function, script
file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:1 char:1
+ XA65_Inventory_V42.ps1
+ ~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (XA65_Inventory_V42.ps1:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Suggestion [3,General]: The command XA65_Inventory_V42.ps1 was not found, but does exist in the current location. Window
s PowerShell does not load commands from the current location by default. If you trust this command, instead type “.\XA6
5_Inventory_V42.ps1”. See “get-help about_Command_Precedence” for more details.
PS C:\Windows\SysWOW64\WindowsPowerShell\v1.0> .\XA65_Inventory_V42.ps1
.\XA65_Inventory_V42.ps1 : File C:\Windows\SysWOW64\WindowsPowerShell\v1.0\XA65_Inventory_V42.ps1 cannot be loaded.
The file C:\Windows\SysWOW64\WindowsPowerShell\v1.0\XA65_Inventory_V42.ps1 is not digitally signed. You cannot run
this script on the current system. For more information about running scripts and setting execution policy, see
about_Execution_Policies at http://go.microsoft.com/fwlink/?LinkID=135170.
At line:1 char:1
+ .\XA65_Inventory_V42.ps1
+ ~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : SecurityError: (:) [], PSSecurityException
+ FullyQualifiedErrorId : UnauthorizedAccess
PS C:\Windows\SysWOW64\WindowsPowerShell\v1.0> .\XA65_Inventory_V42_Signed.ps1
Do you want to run software from this untrusted publisher?
File C:\Windows\SysWOW64\WindowsPowerShell\v1.0\XA65_Inventory_V42_Signed.ps1 is published by CN=”Carl Webster
Consulting, LLC”, O=”Carl Webster Consulting, LLC”, L=Tullahoma, S=TN, C=US and is not trusted on your system. Only run
scripts from trusted publishers.
[V] Never run [D] Do not run [R] Run once [A] Always run [?] Help (default is “D”): A
VERBOSE: 09/15/2015 06:01:04: Testing output parameters
VERBOSE: 09/15/2015 06:01:04: MSWord is set
VERBOSE: 09/15/2015 06:01:04: CoName is
VERBOSE: 09/15/2015 06:01:05: Remoting is enabled to XenApp server MACZDCXML01
VERBOSE: 09/15/2015 06:01:10: Getting initial Farm data
WARNING: Farm information could not be retrieved
C:\Windows\SysWOW64\WindowsPowerShell\v1.0\XA65_Inventory_V42_Signed.ps1 : A remote connection to MACZDCXML01 could
not be established. Script cannot continue.
At line:1 char:1
+ .\XA65_Inventory_V42_Signed.ps1
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,XA65_Inventory_V42_Signed.ps1
PS C:\Windows\SysWOW64\WindowsPowerShell\v1.0> .\XA65_Inventory_V42_Signed.ps1
VERBOSE: 09/15/2015 06:03:34: Testing output parameters
VERBOSE: 09/15/2015 06:03:34: MSWord is set
VERBOSE: 09/15/2015 06:03:34: CoName is
VERBOSE: 09/15/2015 06:03:34: Remoting is enabled to XenApp server MACZDCXML01
VERBOSE: 09/15/2015 06:03:35: Getting initial Farm data
WARNING: Farm information could not be retrieved
C:\Windows\SysWOW64\WindowsPowerShell\v1.0\XA65_Inventory_V42_Signed.ps1 : A remote connection to MACZDCXML01 could
not be established. Script cannot continue.
At line:1 char:1
+ .\XA65_Inventory_V42_Signed.ps1
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,XA65_Inventory_V42_Signed.ps1
PS C:\Windows\SysWOW64\WindowsPowerShell\v1.0> .\XA65_Inventory_V42_Signed.ps1
VERBOSE: 09/15/2015 06:23:22: Testing output parameters
VERBOSE: 09/15/2015 06:23:22: MSWord is set
VERBOSE: 09/15/2015 06:23:22: CoName is
VERBOSE: 09/15/2015 06:23:22: Remoting is enabled to XenApp server MACZDCXML01
VERBOSE: 09/15/2015 06:23:24: Getting initial Farm data
WARNING: Farm information could not be retrieved
C:\Windows\SysWOW64\WindowsPowerShell\v1.0\XA65_Inventory_V42_Signed.ps1 : A remote connection to MACZDCXML01 could
not be established. Script cannot continue.
At line:1 char:1
+ .\XA65_Inventory_V42_Signed.ps1
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,XA65_Inventory_V42_Signed.ps1
PS C:\Windows\SysWOW64\WindowsPowerShell\v1.0> .\XA65_Inventory_V42_Signed.ps1
VERBOSE: 09/15/2015 06:27:02: Testing output parameters
VERBOSE: 09/15/2015 06:27:02: MSWord is set
VERBOSE: 09/15/2015 06:27:02: CoName is
VERBOSE: 09/15/2015 06:27:02: Remoting is enabled to XenApp server MACZDCXML01
VERBOSE: 09/15/2015 06:27:04: Getting initial Farm data
WARNING: Farm information could not be retrieved
C:\Windows\SysWOW64\WindowsPowerShell\v1.0\XA65_Inventory_V42_Signed.ps1 : A remote connection to MACZDCXML01 could
not be established. Script cannot continue.
At line:1 char:1
+ .\XA65_Inventory_V42_Signed.ps1
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,XA65_Inventory_V42_Signed.ps1
PS C:\Windows\SysWOW64\WindowsPowerShell\v1.0> .\XA65_Inventory_V42_Signed.ps1
VERBOSE: 09/15/2015 06:29:03: Testing output parameters
VERBOSE: 09/15/2015 06:29:03: MSWord is set
VERBOSE: 09/15/2015 06:29:03: CoName is
VERBOSE: 09/15/2015 06:29:03: Remoting is enabled to XenApp server MACZDCXML01
VERBOSE: 09/15/2015 06:29:05: Getting initial Farm data
WARNING: Farm information could not be retrieved
C:\Windows\SysWOW64\WindowsPowerShell\v1.0\XA65_Inventory_V42_Signed.ps1 : A remote connection to MACZDCXML01 could
not be established. Script cannot continue.
At line:1 char:1
+ .\XA65_Inventory_V42_Signed.ps1
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,XA65_Inventory_V42_Signed.ps1
PS C:\Windows\SysWOW64\WindowsPowerShell\v1.0> .\XA65_Inventory_V42_Signed.ps1
VERBOSE: 09/15/2015 06:32:55: Testing output parameters
VERBOSE: 09/15/2015 06:32:55: MSWord is set
VERBOSE: 09/15/2015 06:32:55: CoName is
VERBOSE: 09/15/2015 06:32:55: Remoting is enabled to XenApp server MACZDCXML01
VERBOSE: 09/15/2015 06:32:56: Getting initial Farm data
WARNING: Farm information could not be retrieved
C:\Windows\SysWOW64\WindowsPowerShell\v1.0\XA65_Inventory_V42_Signed.ps1 : A remote connection to MACZDCXML01 could
not be established. Script cannot continue.
At line:1 char:1
+ .\XA65_Inventory_V42_Signed.ps1
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,XA65_Inventory_V42_Signed.ps1
PS C:\Windows\SysWOW64\WindowsPowerShell\v1.0> .\XA65_Inventory_V42_Signed.ps1
VERBOSE: 09/15/2015 06:42:19: Testing output parameters
VERBOSE: 09/15/2015 06:42:19: MSWord is set
VERBOSE: 09/15/2015 06:42:19: CoName is
VERBOSE: 09/15/2015 06:42:19: Remoting is enabled to XenApp server MACZDCXML01
VERBOSE: 09/15/2015 06:42:21: Getting initial Farm data
WARNING: Farm information could not be retrieved
C:\Windows\SysWOW64\WindowsPowerShell\v1.0\XA65_Inventory_V42_Signed.ps1 : A remote connection to MACZDCXML01 could
not be established. Script cannot continue.
At line:1 char:1
+ .\XA65_Inventory_V42_Signed.ps1
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,XA65_Inventory_V42_Signed.ps1
PS C:\Windows\SysWOW64\WindowsPowerShell\v1.0>
September 17, 2015 at 5:13 pm
First thing, you normally do not run scripts from the WindowsPowerShell folder. Create a folder, say c:\scripts, place your scripts there and run them from there.
Start a new PowerShell session.
Add-PSSnapin *citrix*
Run Set-XADefaultComputerName command.
Run Get-XAFarm
Does it work? If not, it is not a script problem.
If this is a VPN connection then there should be no ports blocked. Can you telnet to the remote XenApp server on port 2513?
There is also a Citrix remoting commands service that must be enabled and started. Sorry I can’t remember the name of the service. Make sure it is enabled and started.
Webster
August 25, 2015 at 3:45 am
Thanks a lot for this great script! I’ve learnt a lot from your script as well. With my Word 2013 I do sometimes get an error that the cover page isn’t installed. I cannot put my finger on it why it would go wrong, but it gives me an error message on this line:
$part = $BuildingBlocks.BuildingBlockEntries.Item($CoverPage)
The error is:
Exception getting “Item”: “Cannot convert argument “index”, with value: “Facet”, for “get_Item” to type “System.Int32”: “Cannot convert value “Facet” to type “System.Int32”. Error: “Input st
ring was not in a correct format.”””
Do you know why this would sometimes give an error, but at other times it doesn’t? (today I cannot seem to get the cover page to work, while yesterday everything worked just fine and no changes to the script have been made in the meantime)
August 25, 2015 at 6:44 am
Have you edited the script in any way?
What language of Word?
Can you give me the exact command line you use?
The Facet cover page is used in most Word languages.
Webster