Invoke-Command start process failing on freshly deployed virtual machine

This post has been de-listed

It is no longer included in search results and normal feeds (front page, hot posts, subreddit posts, etc). It remains visible only via the author's post history.

Post Flair (click to view more posts with a particular flair)

Question

Post Body

I am attempting to use start-process on a virtual machine that is imported within the same script. However the process seems to not start until the virtual machine has been logged in at least once. If I manually login and try running the script remotely again the process will successfully execute.

I believe I ran into this a few years ago for a different project but don't remember if I ever found a fix for it. The command I am executing looks similar to the following -

Invoke-Command -Session $session -ScriptBlock {Start-Process "C:\Temp\myprocess.cmd"}

Any help would be greatly appreciated on this issue.

Author

Account Strength

90%

Account Age

12 years

Verified Email

Yes

Verified Flair

Total Karma

4,721

Link Karma

2,348

Comment Karma

2,373

Profile updated: 20 hours ago

Posts updated: 3 months ago

Insight54

Subreddit

r/PowerShell

Post Details

We try to extract some basic information from the post title. This is not always successful or accurate, please use your best judgement and compare these values to the post title and body for confirmation.

Posted: 4 years ago
Reddit URL: View post on reddit.com
External URL: reddit.com/r/PowerShell/...