Powershell excution policy on server with Exchange 2007

[RD]

Isn't that the only option to port existing Excahnge 2003 service application
using VB script and COM client program to port to Exchange 2007?

I'll read a bit on that in the next day or so. I wasn't aware Exchange
had a different default policy.
For starters, you shouldn't be considering running a PS script as a
service. PS isn't really useful/designed for that.
A scheduled job is a much better fit.
Marco
--
Microsoft MVP - Windows PowerShell
http://www.microsoft.com/mvp
PowerGadgets MVP
http://www.powergadgets.com/mvp
http://marcoshaw.blogspot.com

[Marco Shaw [MVP]]

Post by RD
Isn't that the only option to port existing Excahnge 2003 service application
using VB script and COM client program to port to Exchange 2007?

I don't know that much about Exchange, so I'll have to do some research...

Marco

[RD]

I'm in process of installing Exchange 2007. After I installed PowerShell 1.0
(KB926139) as part of prerequisite, I checked the execution policy through
cmdlet "Get-ExecutionPolicy" and it returns "Restricted". However there is no
value key named "ExecutionPolicy" under
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft.PowerShell". Strange!

Post by Marco Shaw [MVP]

Post by RD
Isn't that the only option to port existing Excahnge 2003 service application
using VB script and COM client program to port to Exchange 2007?

I don't know that much about Exchange, so I'll have to do some research...
Marco
--
Microsoft MVP - Windows PowerShell
http://www.microsoft.com/mvp
PowerGadgets MVP
http://www.powergadgets.com/mvp
http://marcoshaw.blogspot.com

[RD]

I installed Exchange 2007 EE and now Execution policy is "RemoteSigned". The
registry value for it is also created and set to "RemoteSigned". I also
noticed that there a new log file created in EventViwer "PowerShell". Does
any one know how this works.

Thanks.

Post by RD
I'm in process of installing Exchange 2007. After I installed PowerShell 1.0
(KB926139) as part of prerequisite, I checked the execution policy through
cmdlet "Get-ExecutionPolicy" and it returns "Restricted". However there is no
value key named "ExecutionPolicy" under
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft.PowerShell". Strange!

Post by Marco Shaw [MVP]

Post by RD
Isn't that the only option to port existing Excahnge 2003 service application
using VB script and COM client program to port to Exchange 2007?

I don't know that much about Exchange, so I'll have to do some research...
Marco
--
Microsoft MVP - Windows PowerShell
http://www.microsoft.com/mvp
PowerGadgets MVP
http://www.powergadgets.com/mvp
http://marcoshaw.blogspot.com