|
 |  |  |  |  |  |  |
| Welcome to Windows Vista Forums. Our forum is dedicated to helping you find solutions with any problems, errors or issues you are experiencing with Windows Vista. The Vista forum also covers news and updates and has an extensive Windows Vista tutorial section that covers a wide range of tips and tricks. |
| |||||||
 |
| |
06-09-2006
| #1 (permalink) |
| | Monad / PowerShell / Exchange 2007 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 |
My System Specs |
|
06-09-2006
| #2 (permalink) |
| | Re: Monad / PowerShell / Exchange 2007 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 |
| My System Specs |
|
06-09-2006
| #3 (permalink) |
| | Re: Monad / PowerShell / Exchange 2007 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 |
| My System Specs |
|
06-13-2006
| #4 (permalink) |
| | Re: Monad / PowerShell / Exchange 2007 Guy, I just asked a question about this in a TechEd webcast on Exchange 2007. Apparently, the MSH > PowerShell transition didn't make the cut for Exchange 2007 Beta 2. It will happen in some later build. Andrew Watt MVP On Fri, 9 Jun 2006 15:33:37 +0100, "Guy Thomas" <guy@computerperformance.co.uk> wrote: >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 |
| My System Specs |
|
06-14-2006
| #5 (permalink) |
| | Re: Monad / PowerShell / Exchange 2007 "Guy Thomas" <guy@computerperformance.co.uk> wrote in message news:OjJ2Cg8iGHA.4284@TK2MSFTNGP05.phx.gbl... EXchange Beta2 hasn't made transition from Monad to Powershell name. if you are using Exchange beta, you need to continue to use the old monad terminology and commands. Exchange will make the transition to the new name post beta2. > 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 > > |
| My System Specs |
|
| Thread Tools | |
| |
Similar Threads | ||||
| Thread | Forum | |||
| Powershell with exchange 2007 - Add-PsSnapin | PowerShell | |||
| Running powershell via exchange 2007 | PowerShell | |||
| Exchange 2007 and PowerShell | PowerShell | |||
| Exchange 2007 PowerShell.. | PowerShell | |||
| Getting Exchange Beta 1 Monad and PowerShell RC1 to co-exist | PowerShell | |||
