Vista - Re: VMware remote console causing powershell scripts to terminate?

Hi blah,
Yes! And this is the reason why I actually dont't use powershell in
scheduled tasks. Here's my thread:

[Scheduled script prematurely exits with [PipelineStoppedException]]
http://groups.google.de/group/micros...2e193490594ea7

cu

Max

On Tue, 11 Mar 2008 Maximilian Hänel <ngSpam@xxxxxx> wrote:Thanks Max

I now think that this is an issue with the VMware. Out
administrator is using the vmware console whereas everyone else
is using remote desktop without the same issue. I think
we will need to log a support call with VMware.

--
http://www.krustybrandinternet.com

On Tue, 11 Mar 2008 blah <nospam@xxxxxx> wrote:Actually forget that.
We've run a few further tests. It seems that the powershell scripts stop
when using remote desktop "console"
(eg Start > Run "mstsc /v:machinename /console")
(or VMware remote console)
It seems that after logging in using the console option, rather than the
default terminal is causing the powershell scripts to terminate on logout.



--
http://www.krustybrandinternet.com

Hi blah,
I don't think it is a problem with VMware because I have the same
problem on "real" machines by using either remote desktop or "direct"
login, too.

If someone else want to reproduce the bug, here are some instructions:

http://groups.google.de/group/micros...ded6182e329a9a

cu

Max

blah wrote:Ahh...ok. Yes, that is "by design". Logging out of the local console ends the
session and all processes started during it. Ending an RDP session just
disconnects, and the session stays open unless your group policy settings cause
it to do otherwise.

If you intend for a task to stay running independent of a user's session then
you really need to run it as a scheduled task or a service. Alternately you can
use WMI to start a process remotely, that should also work.

None of this has anything to do with VMware, PowerShell, or Websphere, this is
strictly Windows stuff.

--

Hal Rottenberg
Blog: http://halr9000.com
Webmaster, Psi (http://psi-im.org)
Co-host, PowerScripting Podcast (http://powerscripting.net)

Hi Hal,
Please read this thread:

[Scheduled script prematurely exits with [PipelineStoppedException]]
http://groups.google.de/group/micros...2e193490594ea7

The script stops even if it runs on a ***different*** user account!!

cu

Max

On Tue, 11 Mar 2008 Maximilian Hänel <ngSpam@xxxxxx> wrote:Yes, that's what's happening.
The script is running, called by Websphere MQ (which runs as a service,
under a local user). The scripts do not run as a service.
Administrator(not me) logs in using remote desktop console
Administrator logs out of remote desktop console
Scripts stop.

The problem is that there's a third party application running
and the administrator needs to log in using remote desktop
console.

I log in using the default remote desktop terminal.

But I haven't found any description of this problem on any other
forum (except max's link). I would assume that people's powershell
scripts would be failing everywhere because of this problem?


--
http://www.krustybrandinternet.com