<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Orchestrator on Forward or Reverse</title>
    <link>https://blog.wannemacher.us/categories/orchestrator/</link>
    <description>Recent content in Orchestrator on Forward or Reverse</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 29 Jul 2010 20:32:24 +0000</lastBuildDate>
    
	<atom:link href="https://blog.wannemacher.us/categories/orchestrator/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Another Orchestrator/PowerShell hang issue</title>
      <link>https://blog.wannemacher.us/posts/p350/</link>
      <pubDate>Thu, 29 Jul 2010 20:32:24 +0000</pubDate>
      
      <guid>https://blog.wannemacher.us/posts/p350/</guid>
      <description>It has come to my attention that some times the scripts will still hang after using the trick from a previous post to fix an issue with standard input when running PowerShell in Orchestrator workflows. After further research there appears to be an issue with stderr hanging the scripts in a similar way to stdin. To be safe you should do something with the output from stderr (where error messages are sent).</description>
    </item>
    
    <item>
      <title>Running PowerShell in VMware Orchestrator – updated</title>
      <link>https://blog.wannemacher.us/posts/p346/</link>
      <pubDate>Tue, 27 Jul 2010 14:44:15 +0000</pubDate>
      
      <guid>https://blog.wannemacher.us/posts/p346/</guid>
      <description>Updated 7/29/2010 – I have added a new follow up post this post regarding another related hanging issue. Please make sure to check it out.
This is a copy of my comment in the VMware Communities, but some times the Google search results for items in this blog show up and the ones for the communities do not.
The original problem is that PowerShell scripts hang when running them in Orchestrator.</description>
    </item>
    
  </channel>
</rss>