Requires .net 2.0.

MONO isn't quite there yet.

Regards,

Michael B. Smith
MCSE/Exchange MVP
http://TheEssentialExchange.com


-----Original Message-----
From: Kurt Buff [mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 20, 2008 2:25 PM
To: MS-Exchange Admin Issues
Subject: Re: Exchange Management Shell killed the CDO star

Has it been ported to FreeBSD?

On Thu, Mar 20, 2008 at 10:18 AM, Michael B. Smith
<[EMAIL PROTECTED]> wrote:
>
>
>
>
> There was no other language that was designed to deal with objects.
>
>
>
> If you want to continue to do text processing, stick with Perl. J PS is
> great for object processing.
>
>
>
>
> Regards,
>
>
>
> Michael B. Smith
>
> MCSE/Exchange MVP
>
> http://TheEssentialExchange.com
>
>
>
>
> From: Micheal Espinola Jr [mailto:[EMAIL PROTECTED]
>  Sent: Thursday, March 20, 2008 1:00 PM
>
>  To: MS-Exchange Admin Issues
>
>
> Subject: Re: Exchange Management Shell killed the CDO star
>
>
>
>
>
>
> Sure.  There's nothing like inventing another language that already
exists.
>
>
>
>
>
>
>
> On Thu, Mar 20, 2008 at 12:41 PM, Michael B. Smith
> <[EMAIL PROTECTED]> wrote:
>
> Seriously, ain't that the truth...
>
>  PS contains all the good parts of Perl and PHP and few of the problems
>  (except for those extraneous parens around single-statement blocks, which
>  just gripe my groin...)
>
>
>
>  Regards,
>
>  Michael B. Smith
>  MCSE/Exchange MVP
>  http://TheEssentialExchange.com
>
>
>  -----Original Message-----
>
>
> From: Campbell, Rob [mailto:[EMAIL PROTECTED]
>
>
> Sent: Thursday, March 20, 2008 12:31 PM
>  To: MS-Exchange Admin Issues
>
>
>
> Subject: RE: Exchange Management Shell killed the CDO star
>
>  If (($mailserver = "E2K7") -and ($($admin | gm -membertype method)
>  -notcontains "powershell"))) {$admin.future = $nul}
>
>  -----Original Message-----
>  From: Kurt Buff [mailto:[EMAIL PROTECTED]
>  Sent: Thursday, March 20, 2008 10:51 AM
>  To: MS-Exchange Admin Issues
>  Subject: Re: Exchange Management Shell killed the CDO star
>
>  I won't be happy until I can do it in perl...
>
>  Heh.
>
>  On 3/19/08, Matteson, John H Jr USA Mr USA 25th SigBN (ITT)
>  <[EMAIL PROTECTED]> wrote:
>  > See what happens when the penguin gets it's flippers into something?
>  We
>  > go from a decent GUI back to C/Korn/Bash-shell scripting.
>  >
>  >
>  > John H. Matteson, Jr.
>  > Systems Administrator/ITT Systems
>  > FOB Orgun-E
>  > Afghanistan
>  > DSN - 318 431 8001
>  > VoSIP - (308) 431 - 0000
>  > Iridium - 717.633.3823
>  > Roshain - 079 - 736 - 3832
>  >
>  > "A man who thinks of himself as belonging to a particular national
>  group
>  > in America has not yet become an American. And the man who goes among
>  > you to trade upon your nationality is no worthy son to live under the
>  > Stars and Stripes."  Woodrow Wilson
>  >
>  >
>  > -----Original Message-----
>  > From: Boggis, Josh [mailto:[EMAIL PROTECTED]
>  > Sent: Wednesday, March 19, 2008 6:38 PM
>  > To: MS-Exchange Admin Issues
>  > Subject: Exchange Management Shell killed the CDO star
>  >
>  > Currently where I work we are using Exchange 2003.  I have written
>  some
>  > VB code that uses CDO and CDOEXM to create mailboxes for new users.
>  > Another process creates new accounts in active directory, and my code
>  > goes through all the accounts, sees what department they are in, goes
>  to
>  > a lookup table to figure out if the department they are in gets
>  > mailboxes on our servers (some departments have their own servers so
>  we
>  > leave them alone).
>  >
>  >
>  >
>  > Now I go to the Microsoft Upgrading skills from Exchange 2003 to 2007
>  > class and I am introduced to the horror of the exchange management
>  > shell.  I want to keep using CDO!!!  But from what I was told, CDO
>  will
>  > not work fully with Exchange 2007, especially since the RUS is gone.
>  > CDO, from my little experience with it so far, isn't a robust language
>  > to program with.  It's more of a scripting system.
>  >
>  >
>  >
>  > Am I the only one who isn't happy with the management shell?
>  >
>  >
>  >
>  >
>  >
>  > ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~
>  > ~             http://www.sunbeltsoftware.com/Ninja                ~
>  >
>
>  ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~
>  ~             http://www.sunbeltsoftware.com/Ninja                ~
>
>
>
****************************************************************************
>  **********************
>  Note:
>  The information contained in this message may be privileged and
> confidential
>  and
>  protected from disclosure.  If the reader of this message is not the
>  intended
>  recipient, or an employee or agent responsible for delivering this
message
>  to
>  the intended recipient, you are hereby notified that any dissemination,
>  distribution or copying of this communication is strictly prohibited. If
> you
>
>  have received this communication in error, please notify us immediately
by
>  replying to the message and deleting it from your computer.
>
>
****************************************************************************
>  **********************
>
>  ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~
>  ~             http://www.sunbeltsoftware.com/Ninja                ~
>
>
>  ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~
>  ~             http://www.sunbeltsoftware.com/Ninja                ~
>
>
>
>
>  --
>  ME2
>
>
>
>
>

~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~
~             http://www.sunbeltsoftware.com/Ninja                ~


~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~
~             http://www.sunbeltsoftware.com/Ninja                ~

Reply via email to