Guy Thomas

Dear Andrew

Not only was your answer clear, but also it was just what I wanted to hear.

Thank you

Guy

"Andrew Watt [MVP]" <SVGDeveloper@aol.com> wrote in message
news:gm0j829atc0gbresd2jevdgfsu65kp2tn3@4ax.com...
> Guy,
>
> The following is my surmise from various fragments of information but
> I think it's close to the truth.
>
> Exchange Beta 2 will have made the switch from "Monad" terminology and
> filenaming to the PowerShell equivalent by the time that Beta 2 is
> released. So, once Exchange 2007 has caught up "everybody" will use
> PowerShell terminology etc.
>
> What you are seeing is simply a transitional phase where the
> now-6-or-so-months-old Exchange Beta 1 was created before "core"
> PowerShell transitioned from Monad.
>
> In addition, as became clear from the Exchange 2007 webcasts a few
> weeks back, there are still significant changes being made in the
> Exchange-specific cmdlets.
>
> As far as I am aware, you shouldn't expect the hybrid PowerShell/Monad
> setup to work. In an unspecified time period when Exchange 2007 Beta 2
> is released you should be in a PowerShell world where (hopefully)
> everything plays nicely together.
>
> I hope that helps.
>
> Andrew Watt MVP
>
> On Fri, 9 Jun 2006 14:24:15 +0100, "Guy Thomas"
> <guy@computerperformance.co.uk> wrote:
>
>>Monad / PowerShell / Exchange 2007
>>
>>In Exchange 2007 beta, if I replace Monad with PowerShell, then the
>>Exchange
>>specific commands don't appear to work.
>>
>>Eg Get-Mailbox. (get-service works fine)
>>
>>
>>
>>My question is: have I missed a step?
>>
>>
>>
>>Supplementary question, if this behaviour is 'by design' what will be the
>>future? Will Monad and PowerShell diverge rather than converge?
>>
>>
>>
>>Guy Thomas