Thanks again Webster, and please pass my thanks on to your contact. I
verified the Windows Firewall on both sides is disabled, and verified
communication over port 2513 is established via Netstat. I am using an
account with admin privileges to test the script.

I've modified the script to use a Data Collector based on the location of
the XenApp database, so that should meet my immediate needs. I hate leaving
these kinds of issues unresolved so I may put more effort into it when I
have the time.

Again, I appreciate the assistance.

- Sean



On Thu, Jul 16, 2015 at 5:14 AM, Webster <[email protected]> wrote:

>  And another response from him:
>
>
>
> “Every computer by default has firewall set up. If he has firewalls
> disabled, then he needs to ensure they are in the same domain and using the
> same user account.”
>
>
>
>
>
> Thanks
>
>
>
>
>
> Webster
>
>
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Webster
> *Sent:* Thursday, July 16, 2015 8:11 AM
>
> *To:* [email protected]
> *Subject:* RE: [powershell] XenApp 6.5 Scripting
>
>
>
> I emailed the guy at Citrix who wrote the migration scripts to take you
> from older versions of XenApp to the 7.x versions. His response is similar
> to mine:
>
>
>
> “The problem is probably not about timeout, but rather about WCF. Make
> sure the controller has the port 2513 open through the firewall.”
>
>
>
>
>
> Thanks
>
>
>
>
>
> Webster
>
>
>
> *From:* [email protected] [
> mailto:[email protected] <[email protected]>] *On
> Behalf Of *Sean Martin
> *Sent:* Wednesday, July 15, 2015 8:58 PM
> *To:* [email protected]
> *Subject:* Re: [powershell] XenApp 6.5 Scripting
>
>
>
> I appreciate the assistance nonetheless. I may ping our Citrix TRM and see
> if he can dig up any resources.
>
> - Sean
>
>
> On Jul 15, 2015, at 5:12 PM, Webster <[email protected]> wrote:
>
>  BTW, the guy who created all the XA 5/6/65 PowerShell stuff was moved to
> a different product group a couple of years ago. The XA65 cmdlets are no
> longer maintained and I have no one to reach out to for help on this.
>
>
>
> Thanks
>
>
>
>
>
> Webster
>
>
>
> *From:* [email protected] [
> mailto:[email protected] <[email protected]>] *On
> Behalf Of *Webster
> *Sent:* Wednesday, July 15, 2015 8:06 PM
> *To:* [email protected]
> *Subject:* RE: [powershell] XenApp 6.5 Scripting
>
>
>
> All the Get-XA* cmdlets retrieve data from the SQL database so why does it
> matter which collector you run the cmdlet from or against?
>
>
>
> Thanks
>
>
>
>
>
> Webster
>
>
>
> *From:* [email protected] [
> mailto:[email protected] <[email protected]>] *On
> Behalf Of *Sean Martin
> *Sent:* Wednesday, July 15, 2015 8:01 PM
> *To:* [email protected]
> *Subject:* Re: [powershell] XenApp 6.5 Scripting
>
>
>
> Thanks Webster, unfortunately that didn't help. There are no firewalls to
> contend with in this scenario. Also, I'm fairly confident nothing is
> blocking communication because I can run the Get-XAApplicationReport cmdlet
> with browser name and it returns results relatively quick. I'm assuming the
> process is actually timing out because the command I'm running has to parse
> through all of the applications by browser name and filter for the
> ApplicationID. I'm thinking the latency between the remote data collector
> and the database is a contributing factor. Running the same command against
> a data collector in the same site as the database returns results in about
> 20 seconds.
>
>
>
> I'm willing to deal with the script taking longer to execute if I could
> find out where to adjust the timeout settings.
>
>
>
>  - Sean
>
>
>
> On Wed, Jul 15, 2015 at 4:50 PM, Webster <[email protected]> wrote:
>
>  Execute Set-XADefaultCOmputerName RemoteDataCollector
>
>
>
> Then try the command
>
>
>
> Make sure TCP Port 2513 is open in Firewalls (Windows and physical).
>
>
>
> Thanks
>
>
>
>
>
> Webster
>
>
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Sean Martin
> *Sent:* Wednesday, July 15, 2015 5:09 PM
> *To:* [email protected]
> *Subject:* [powershell] XenApp 6.5 Scripting
>
>
>
> I'm working on some automation scripts for VMware Site Recovery Manager,
> one of which is automating the publishing of XenApp published applications
> to workergroups based on where the back-end application is operating.
>
>
> I originally had the script working by passing the BrowserName parameter
> to Get-XAApplicationReport, and then executing the changes based on that.
> However, we'd like to pass the actual ApplicationID because the names of
> applications can change and I'd rather not have to worry about updating our
> SRM Recovery Plans.
>
>
>
> I'm running into a problem running the following command against a data
> collector that is in a different data center from the XenApp database:
>
>
>
> Get-XAApplicationReport * -Computer <name> | where {$_.ApplicationID -eq
> "xxxxx"}
>
>
>
> I'm assuming the latency between our sites (75-85ms) is attributing to the
> following error:
>
>
>
> *Get-XAApplicationReport : This request operation sent to
> net.tcp://<redacted>:2513/Citrix/XenAppCommandsRemoting did not receive a
> reply within the configured timeout (00:01:00).  The time allotted to this
> operation may have been a portion of a longer timeout.  This may be because
> the service is still processing the operation or because the service was
> unable to send a reply message.  Please consider increasing the operation
> timeout (by casting the channel/proxy to IContextChannel and setting the
> OperationTimeout property) and ensure that the service is able to connect
> to the client.*
>
>
>
> * At line:1 char:31 + $app = Get-XAApplicationReport <<<<  *
> -Computer REDACTED | where {$_.ApplicationID -eq $appid}     +
> CategoryInfo          : NotSpecified: (:) [Get-XAApplicationReport],
> TimeoutException     + FullyQualifiedErrorId :
> System.TimeoutException,Citrix.XenApp.Commands.GetAppReportCmdlet*
>
>
>
> I'm not having much luck identifying where I might be able to increase the
> timeout referenced in the error. Any help would be much appreciated.
>
>
>
> - Sean
>
>
> ================================================
> Did you know you can also post and find answers on PowerShell in the
> forums?
> http://www.myitforum.com/forums/default.asp?catApp=1
>
>
> ================================================
> Did you know you can also post and find answers on PowerShell in the
> forums?
> http://www.myitforum.com/forums/default.asp?catApp=1
>
>
>
>
> ================================================
> Did you know you can also post and find answers on PowerShell in the
> forums?
> http://www.myitforum.com/forums/default.asp?catApp=1
>
>
> ================================================
> Did you know you can also post and find answers on PowerShell in the
> forums?
> http://www.myitforum.com/forums/default.asp?catApp=1
>
>
> ================================================
> Did you know you can also post and find answers on PowerShell in the
> forums?
> http://www.myitforum.com/forums/default.asp?catApp=1
>
>
> ================================================
> Did you know you can also post and find answers on PowerShell in the
> forums?
> http://www.myitforum.com/forums/default.asp?catApp=1
>
>
> ================================================
> Did you know you can also post and find answers on PowerShell in the
> forums?
> http://www.myitforum.com/forums/default.asp?catApp=1
>
> ================================================
> Did you know you can also post and find answers on PowerShell in the
> forums?
> http://www.myitforum.com/forums/default.asp?catApp=1
>


================================================
Did you know you can also post and find answers on PowerShell in the forums?
http://www.myitforum.com/forums/default.asp?catApp=1

Reply via email to