![citrix xenapp 6.5 trouble connecting to distant app server citrix xenapp 6.5 trouble connecting to distant app server](https://i1.wp.com/www.virtuallyimpossible.co.uk/wp-content/uploads/2013/03/Publishing_Applications_with_Citrix_XenApp_6.5_009.png)
- #Citrix xenapp 6.5 trouble connecting to distant app server how to#
- #Citrix xenapp 6.5 trouble connecting to distant app server windows#
![citrix xenapp 6.5 trouble connecting to distant app server citrix xenapp 6.5 trouble connecting to distant app server](https://new.prtgplugins.com/images/stories/ojoc/xen02.png)
Now you can use my XenApp 6.5 PowerShell Documentation Script with absolutely no modifications and have it work with remoting.
#Citrix xenapp 6.5 trouble connecting to distant app server windows#
The Windows Firewall GUI shows my new rule created and enabled (Figure 5). netsh advfirewall firewall add rule name=" Citrix PoSH TCP Port 2513" dir=in action=allow description=" Allow communication between XenApp and remote computer running PoSH scripts" enable=yes profile=any remoteip=192.168.1.100 protocol=tcp localport=2513 Figure 4 The “remoteip” will need to be the computer’s IP address used to run the script. I created a Windows Firewall Rule on my XenApp server to open TCP Port 2513 between the domain controller and my XenApp server (Figure 4). To me, that is one less port open on my network. The help text says TCP Port 2513 must be opened on both computers, but I found I only needed it opened on the XenApp server. My wife tells me I couldn’t find a 10 gallon (37.8541 Liter) jug of milk on the fridge’s top shelf! What does this have to do with anything? DOH! At the top of the help file, I now see (Figure 3): Figure 3 I found that TCP Port 2513 needed to be opened (Figure 2).
![citrix xenapp 6.5 trouble connecting to distant app server citrix xenapp 6.5 trouble connecting to distant app server](https://docplayer.net/docs-images/42/5518164/images/page_9.jpg)
I then ran Microsoft’s Sysinternals ProcMon to get a network trace. When I ran my documentation script, I received: Figure 1 My lab XenApp 6.5 server is named XA65, so I entered on my domain controller. Specified without having to explicitly use the -ComputerName parameter every time. When the default computer name is set, all the cmdlets will automatically remote to the server Significant changes, a default computer name can be set in the client machine. In order to facilitate running existing scripts remotely without having to make In XenApp 6.5 the cmdlets can be remoted using
#Citrix xenapp 6.5 trouble connecting to distant app server how to#
This section explains how to invoke the XenApp Commands remotely. I found this information in the SDK help file on Remoting Cmdlets: All my lab servers have the Windows Firewall enabled and Server Manager Remote Management enabled. I installed the Citrix XenApp 6.5 PowerShell SDK and Group Policy modules on my lab domain controller. Go to the bottom of this article to see the updated information. Note: This article was updated on November 20, 2015. Even using the new –ComputerName parameter, he was still unable to get my script to work. After I wrote my original script and article, Citrix updated the XenApp 6.5 PowerShell SDK to support Remoting and a Default Computer Name. I received an email from a reader wanting to get my Citrix XenApp 6.5 Farm PowerShell documentation script to work remotely.