IMO they are the same only the EMS adds some more Exchange related functions
(tip of the day) on top of the PowerShell environment
such as get-excommand which will list Exchange cmdlets only. The regular
get-command will list a full list of cmdlets.
As for performance, in my environment I'm using regular PowerShell and when
I need access to exchange cmdlets
I load it via a custom function in my profile that loads Exchange snapin.
-----
Shay Levi
$cript Fanatic
http://scriptolog.blogspot.com Quote:
> Does anyone know whether the Exchange Management Console hosts
> PowerShell and calls the Exchange cmdlets directly or whether the
> cmdlets are just another interface to do everything you can do in the
> Exchange Management Console (and more)? I know they say the Exchange
> Management Console was supposedly built on top of PowerShell, but I
> guess what I'm wondering is this: Is it really using the Exchange
> cmdlets as it's only access into the underlying .NET objects to work
> with Exchange or are we dealing with two interfaces into .NET objects
> here? If it is only using the Exchange cmdlets, what is the impact on
> performance with the extra overhead of going through PowerShell?
>
> --
> Kirk Munro
> Poshoholic
> http://poshoholic.com