R – powershell exchange : how do you setup a scheduled task to run exchange2007 powershell

exchange-server-2007powershellscheduled-taskswindows

I'm having trouble setting up a scheduled task (now called Task Scheduler) under the actions tab to run on windows 2007 server. It also has exchange server 2007.

I've tried setting

Program/script : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
Add arguments (optional): -psconsolefile exshell.psc1 -command "& {c:\mes-detail\emsbilling08.ps1}"
Start in (optional): "C:\Program Files\Microsoft\Exchange Server\Bin\

I realize the exshell.psc1 probably also needs an explicit path so I've also tried:

-psconsolefile C:\Program Files\Microsoft\Exchange Server\Bin\exshell.psc1 -command "& {c:\mes-detail\mailall3.ps1}" as well but that doesn't work either

Any ideas?

Best Answer

I figured I'd share the resolution here to finish what is started.

1) In your .ps1 file put Add-PSSnapin exchange

2) for the scheduled task, do this: Program/script : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe Add arguments (optional): -noprofile -Noninteractive c:\mes-detail\emsbilling08.ps1 Start in (optional): "C:\Program Files\Microsoft\Exchange Server\Bin\

If it still doesn't work, run the following checks:

Start...Run C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -noprofile

Get-PSSnapin -Registered

Do you see Microsoft.Exchange.Management.PowerShell.Admin Microsoft.Exchange.Management.Powershell.Support

If so, do add-pssnapin exchange

New answer, powershell

TCP

Get-Process -Id (Get-NetTCPConnection -LocalPort YourPortNumberHere).OwningProcess

UDP

Get-Process -Id (Get-NetUDPEndpoint -LocalPort YourPortNumberHere).OwningProcess

Old answer, cmd

 C:\> netstat -a -b

(Add -n to stop it trying to resolve hostnames, which will make it a lot faster.)

Note Dane's recommendation for TCPView. It looks very useful!

-a Displays all connections and listening ports.

-b Displays the executable involved in creating each connection or listening port. In some cases well-known executables host multiple independent components, and in these cases the sequence of components involved in creating the connection or listening port is displayed. In this case the executable name is in [] at the bottom, on top is the component it called, and so forth until TCP/IP was reached. Note that this option can be time-consuming and will fail unless you have sufficient permissions.

-n Displays addresses and port numbers in numerical form.

-o Displays the owning process ID associated with each connection.

Windows – How to run a PowerShell script

Launch Windows PowerShell, and wait a moment for the PS command prompt to appear
Navigate to the directory where the script lives
```
PS> cd C:\my_path\yada_yada\ (enter)
```
Execute the script:
```
PS> .\run_import_script.ps1 (enter)
```

What am I missing??

Or: you can run the PowerShell script from cmd.exe like this:

powershell -noexit "& ""C:\my_path\yada_yada\run_import_script.ps1""" (enter)

according to this blog post here

Or you could even run your PowerShell script from your C# application :-)

Asynchronously execute PowerShell scripts from your C# application

Best Answer

Related Solutions

Windows – How to you find out which process is listening on a TCP or UDP port on Windows

New answer, powershell

TCP

UDP

Old answer, cmd

Windows – How to run a PowerShell script

Related Topic