Re: Exchange Management Shell killed the CDO star

2008-03-20 Thread Micheal Espinola Jr
undershirts = underoos

On Fri, Mar 21, 2008 at 1:29 AM, Matteson, John H Jr USA Mr USA 25th SigBN
(ITT) <[EMAIL PROTECTED]> wrote:

> But you have a drawer full of "Root" and "I read your mail" undershirts.
> :-)
>
>
> John H. Matteson, Jr.
> Systems Administrator/ITT Systems
> FOB Orgun-E
> Afghanistan
> DSN - 318 431 8001
> VoSIP - (308) 431 - 
> 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: Micheal Espinola Jr [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 21, 2008 3:02 AM
> To: MS-Exchange Admin Issues
> Subject: Re: Exchange Management Shell killed the CDO star
>
> ;-P   Preppy button down white boy, all my life.   But, I'm not a *nix
> d00d either!   But I dont know any *nix d00ds nuder the age of 45 that
> fit that stero type either.
>
> At least not any more...  :-D
>
>
> On Thu, Mar 20, 2008 at 3:14 PM, Schwartz, Jim <[EMAIL PROTECTED]>
> wrote:
>
>
>Let me know when you take that shower. ;-)
>
>
>
>From: Micheal Espinola Jr [mailto:[EMAIL PROTECTED]
>Sent: Thursday, March 20, 2008 1:50 PM
>
>To: MS-Exchange Admin Issues
>Subject: Re: Exchange Management Shell killed the CDO star
>
>
>
>
>
>How rediculously steriotypical of you.  Let me know when you
> send your time machine back to the future.
>
>On Thu, Mar 20, 2008 at 1:32 PM, Schwartz, Jim
> <[EMAIL PROTECTED]> wrote:
>
>Yeah. If I wanted to be a *nix guy, I would have stopped
> showering daily
>and let my hair grow long.
>
>
>-Original Message-
>From: Matteson, John H Jr USA Mr USA 25th SigBN (ITT)
>[mailto:[EMAIL PROTECTED]
>
>Sent: Thursday, March 20, 2008 1:01 AM
>To: MS-Exchange Admin Issues
>
>
>Subject: RE: Exchange Management Shell killed the CDO star
>
>
>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 - 
>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
> ~
>
>
>
>
>--
>ME2
>
>
>
>
>
>
>
>
>
> --
> ME2
>
>
>
>
> ~ 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~

RE: more on PS

2008-03-20 Thread Matteson, John H Jr USA Mr USA 25th SigBN (ITT)
And all of that typing is to do what, exactly?   


John H. Matteson, Jr.
Systems Administrator/ITT Systems
FOB Orgun-E
Afghanistan
DSN - 318 431 8001
VoSIP - (308) 431 - 
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: Michael B. Smith [mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 20, 2008 10:28 PM
To: MS-Exchange Admin Issues
Subject: more on PS

And come on, you gotta admit, being able to do the below just rocks:

 

$perfObject = new-object
System.Diagnostics.PerformanceCounterCategory("Process")

 

$perfObject.GetInstanceNames() | foreach {

$counter =
($perfObject.GetCounters($_))[0];

$counter.CounterName = "Thread Count";

if ($counter.RawValue -gt 50 -and $_ -ne
"_Total")

{

$_;

("threadcount: " +
$counter.RawValue);

$counter.CounterName =
"Working Set";

("workingsetsize: " +
$counter.RawValue);

" ";

}

}

 

Or if you want it in one line via a different interface:

 

gwmi win32_process | where { $_.threadcount -gt 50 } | fl name,
threadcount, workingsetsize

 

w00t!

 

Regards,

 

Michael B. Smith

MCSE/Exchange MVP

http://TheEssentialExchange.com

 


 


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


RE: Exchange Backups and Restores

2008-03-20 Thread Matteson, John H Jr USA Mr USA 25th SigBN (ITT)
Ontrack was an outstanding product the last time I used it (about 4
years ago). The major problem was that I would have to run the tape
twice, once to build an index of the contents on the tape, then run it a
second time to actually recover the data. I shoeshined many a linear
meter of tape doing restores for upper management and the legal
department(the consequence of having a SCSI tape unit and SATA disk
drives).


John H. Matteson, Jr.
Systems Administrator/ITT Systems
FOB Orgun-E
Afghanistan
DSN - 318 431 8001
VoSIP - (308) 431 - 
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: Joseph L. Casale [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 21, 2008 12:52 AM
To: MS-Exchange Admin Issues
Subject: RE: Exchange Backups and Restores

Ontrack PowerControls can do this and there was one other I can't recall
that I used from a company that made AD tools as well...
The caveat is getting the db off the tape if that's where it is.
jlc

> -Original Message-
> From: McCready, Robert [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 20, 2008 10:59 AM
> To: MS-Exchange Admin Issues
> Subject: Exchange Backups and Restores
>
> Over the years, we've used several different versions of Exchange with

> several different backup solutions.  Is there some third party 
> software that could be purchased, allowing us to access an Exchange 
> backup tape across multiple platforms and recover a mailbox without 
> actually building a lab for the restore?  For instance, we used
>
> Veritas Backup Exec with Exchange 5.5.
> Data Protector 6.0 with Exchange 2003
> NT Backup with Exchange 2007
>
> I'd like to find out if there is ONE solution to access the data on 
> all these tapes?
>
> Thanks all.
>
> Robert
>
> ~ 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~

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


RE: Exchange Management Shell killed the CDO star

2008-03-20 Thread Matteson, John H Jr USA Mr USA 25th SigBN (ITT)
But you have a drawer full of "Root" and "I read your mail" undershirts.
:-) 


John H. Matteson, Jr.
Systems Administrator/ITT Systems
FOB Orgun-E
Afghanistan
DSN - 318 431 8001
VoSIP - (308) 431 - 
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: Micheal Espinola Jr [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 21, 2008 3:02 AM
To: MS-Exchange Admin Issues
Subject: Re: Exchange Management Shell killed the CDO star

;-P   Preppy button down white boy, all my life.   But, I'm not a *nix
d00d either!   But I dont know any *nix d00ds nuder the age of 45 that
fit that stero type either.
 
At least not any more...  :-D


On Thu, Mar 20, 2008 at 3:14 PM, Schwartz, Jim <[EMAIL PROTECTED]>
wrote:


Let me know when you take that shower. ;-)

 

From: Micheal Espinola Jr [mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 20, 2008 1:50 PM 

To: MS-Exchange Admin Issues
Subject: Re: Exchange Management Shell killed the CDO star



 

How rediculously steriotypical of you.  Let me know when you
send your time machine back to the future.

On Thu, Mar 20, 2008 at 1:32 PM, Schwartz, Jim
<[EMAIL PROTECTED]> wrote:

Yeah. If I wanted to be a *nix guy, I would have stopped
showering daily
and let my hair grow long.


-Original Message-
From: Matteson, John H Jr USA Mr USA 25th SigBN (ITT)
[mailto:[EMAIL PROTECTED]

Sent: Thursday, March 20, 2008 1:01 AM
To: MS-Exchange Admin Issues


Subject: RE: Exchange Management Shell killed the CDO star


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 - 
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
~




-- 
ME2 

 


 




--
ME2 

 


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


RE: Exchange Management Shell killed the CDO star

2008-03-20 Thread Matteson, John H Jr USA Mr USA 25th SigBN (ITT)
Guess they have a bad case of NIH - ittis. 


John H. Matteson, Jr.
Systems Administrator/ITT Systems
FOB Orgun-E
Afghanistan
DSN - 318 431 8001
VoSIP - (308) 431 - 
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: Ben Scott [mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 20, 2008 9:58 PM
To: MS-Exchange Admin Issues
Subject: Re: Exchange Management Shell killed the CDO star

On Thu, Mar 20, 2008 at 1:18 PM, Michael B. Smith
<[EMAIL PROTECTED]> wrote:
> There was no other language that was designed to deal with objects...

  >cough< >splutter<

  C++, Java, Python, Ruby, Smalltalk, just to name a few.

  PowerShell was a solution in search of a problem to solve.
Microsoft made sure to manufacture problems for it to solve in their
newer releases.  :-p

  Don't get me wrong, it's not that PowSh is technically flawed -- it's
very capable by all accounts -- it's just that PowSh is one more damn
thing to learn and worry about, when there were countless other options
out there Microsoft could have gone with.

-- Ben

~ 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~


RE: IMAP

2008-03-20 Thread Campbell, Rob
Protocol logs?

Sent from my GoodLink synchronized handheld (www.good.com)


 -Original Message-
From:   David Lum [mailto:[EMAIL PROTECTED]
Sent:   Thursday, March 20, 2008 10:48 PM Central Standard Time
To: MS-Exchange Admin Issues
Subject:RE: IMAP

Single bump here...

-Original Message-
From: David Lum [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, March 19, 2008 12:40 PM
To: MS-Exchange Admin Issues
Subject: RE: IMAP

Thanks all! My output is this:
? BAD Protocol Error: "Unidentifiable command specified".

It's like the port is open but that's it. IMAP4 is enabled in the
Exchange account in question

-Original Message-
From: Steven Peck [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, March 18, 2008 3:55 PM
To: MS-Exchange Admin Issues
Subject: Re: IMAP

cmdline and technet

http://support.microsoft.com/kb/189326/en-us

An _important_ note... In steps 2 and later, that question mark '?',
that's not for show.  You _have_ to type it in.  You _have_ to add a
space after it.  It's very irritating...

? LOGIN NTDOMAIN/NTACCOUNT/ALIAS PASSWORD

Domain: corp
NtAccount: john
Alias: jdoe
Password: something

? LOGIN corp/john/jdoe something

This will tell you if IMAP is working at all.

Steven Peck



On Tue, Mar 18, 2008 at 3:07 PM, David Lum <[EMAIL PROTECTED]> wrote:
>
>
>
>
> My apologize for not being knowledgeable here, but I was told we need
to
> enable IMAP so some app could use it. We are testing using Outlook
Express
> and get the following message:
>
>
>
> I just tried an got the following error: "No connection could be made
> because the target machine actively refused it."
>
>
>
> My first thought is that the IP address is not being allowed to talk
to the
> Exchange server, but checking access permissions the IP's of the
clients are
> allowed - we're trying to connect from the same LAN as the Exchange
box.
>
>
>
> Where should I look next?
>
>
>
> Dave Lum  - Systems Engineer
>  [EMAIL PROTECTED] - (971)-222-1025
>  "When you step on the brakes your life is in your foot's hands"
>
>
>
>
>
>
>
>
>

~ 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~



~ 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~


RE: IMAP

2008-03-20 Thread David Lum
Single bump here...

-Original Message-
From: David Lum [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, March 19, 2008 12:40 PM
To: MS-Exchange Admin Issues
Subject: RE: IMAP

Thanks all! My output is this:
? BAD Protocol Error: "Unidentifiable command specified".

It's like the port is open but that's it. IMAP4 is enabled in the
Exchange account in question

-Original Message-
From: Steven Peck [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, March 18, 2008 3:55 PM
To: MS-Exchange Admin Issues
Subject: Re: IMAP

cmdline and technet

http://support.microsoft.com/kb/189326/en-us

An _important_ note... In steps 2 and later, that question mark '?',
that's not for show.  You _have_ to type it in.  You _have_ to add a
space after it.  It's very irritating...

? LOGIN NTDOMAIN/NTACCOUNT/ALIAS PASSWORD

Domain: corp
NtAccount: john
Alias: jdoe
Password: something

? LOGIN corp/john/jdoe something

This will tell you if IMAP is working at all.

Steven Peck



On Tue, Mar 18, 2008 at 3:07 PM, David Lum <[EMAIL PROTECTED]> wrote:
>
>
>
>
> My apologize for not being knowledgeable here, but I was told we need
to
> enable IMAP so some app could use it. We are testing using Outlook
Express
> and get the following message:
>
>
>
> I just tried an got the following error: "No connection could be made
> because the target machine actively refused it."
>
>
>
> My first thought is that the IP address is not being allowed to talk
to the
> Exchange server, but checking access permissions the IP's of the
clients are
> allowed - we're trying to connect from the same LAN as the Exchange
box.
>
>
>
> Where should I look next?
>
>
>
> Dave Lum  - Systems Engineer
>  [EMAIL PROTECTED] - (971)-222-1025
>  "When you step on the brakes your life is in your foot's hands"
>
>
>
>
>
>
>
>
>

~ 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~



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


Re: Exchange Management Shell killed the CDO star

2008-03-20 Thread Kurt Buff
Pity.

On Thu, Mar 20, 2008 at 3:59 PM, Michael B. Smith
<[EMAIL PROTECTED]> wrote:
> 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 - 
>  >  > 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~
>  >
>  >
>  >
>  *

RE: Exchange Management Shell killed the CDO star

2008-03-20 Thread Michael B. Smith
There are not significant differences in concept (certainly in
implementation).

 

Regards,

 

Michael B. Smith

MCSE/Exchange MVP

http://TheEssentialExchange.com

 

From: Campbell, Rob [mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 20, 2008 1:45 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange Management Shell killed the CDO star

 

I'm afraid I'm not particularly fluent in perl, so you'll have to forgive me
if this is an ignorant question.

 

What's the difference between a perl module and a powershell snapin?

 

  _  

From: Micheal Espinola Jr [mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 20, 2008 12:29 PM
To: MS-Exchange Admin Issues
Subject: Re: Exchange Management Shell killed the CDO star

 

 



** 
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~

RE: Exchange Management Shell killed the CDO star

2008-03-20 Thread Michael B. Smith
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 - 
>  > 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 th

RE: Exchange Management Shell killed the CDO star

2008-03-20 Thread Michael B. Smith
To use a phrase I've already used today, LDAP syntax just gripes my groin.

 

I agree that they could've done it using an already existing syntax MUCH
more easily.

 

Regards,

 

Michael B. Smith

MCSE/Exchange MVP

http://TheEssentialExchange.com

 

From: Campbell, Rob [mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 20, 2008 3:05 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange Management Shell killed the CDO star

 

Somehow I doubt that there has ever been a new language developed that other
people didn't think the effort wouldn't have been better spend adapting some
other language (I suspect that invariably it was some other language the
person making the argument was already fluent in).

 

I know I've been perturbed that there has to be different rules and syntax
for LDAP queries, SQL queried and WMI queries, and didn't care much for SDDL
at all.  But none of that got me one bit closer to solving the problem at
hand.  The only thing that did was deciding that they are what they are and
aren't going to change, so I'm going to have to.

 

FWIW

 

  _  

From: Michael B. Smith [mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 20, 2008 12:18 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange Management Shell killed the CDO star

 

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 - 
> 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:

RE: redimensioning OS and logs partitions

2008-03-20 Thread Miguel Gonzalez
I was thinking of using rescuecd linux live cd but I'm
really scare that I could crap the machine out.

Also, If any of the processes can be done while the
machine is online would be great (not need that the
Exchange services are running, but at least that I can
do it remotely - at least for the data drive, not the
OS).

Miguel

--- Stephan Barr <[EMAIL PROTECTED]>
escribió:

> Lot's of options but check out Acronis.  Fine stuff
> there.
> Cheers.
> 
> -Original Message-
> From: "Miguel Gonzalez" <[EMAIL PROTECTED]>
> To: "MS-Exchange Admin Issues"
> 
> Sent: 3/20/2008 5:33 PM
> Subject: redimensioning OS and logs partitions
> 
> Hi,
> 
>  I have three partitions in my SBS 2003 server.
> 
>  C - OS
>  D - Exchange databases (only)
>  E - Exchange logs and AV
> 
>  C and E are partitions within the same RAID array
> (RAID 1+0). I want to shrink the E drive and expand
> the C drive.
> 
>  The partitions are basic (not dynamic) and I've
> read
> that diskpart could help me to shrink the E drive.
> However apparently it wouldn't of no help for the C
> drive.
> 
>  Is it possible to shrink the E drive partition so
> the
> unallocated space is left in the beginning of the E
> partition and not at the end?
> 
>  Any clarification that I need to know?
> 
>  Thanks,
> 
>  Miguel
> 
> 
> 
>   __
> 
> Enviado desde Correo Yahoo! 
> Más formas de estar en contacto.
> http://es.docs.yahoo.com/mail/overview/index.html
> 
> 
> ~ 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  
>  ~
> 



  __ 
Enviado desde Correo Yahoo!
Disfruta de una bandeja de entrada más inteligente. 
http://es.docs.yahoo.com/mail/overview/index.html


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


RE: Exchange Backups and Restores

2008-03-20 Thread Barsodi.John
Quest Recovery Manager for Exchange

-Original Message-
From: Michael B. Smith [mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 20, 2008 3:51 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange Backups and Restores

Quest has a solution as well. The name escapes me at the moment.

Regards,

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


-Original Message-
From: Joseph L. Casale [mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 20, 2008 4:23 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange Backups and Restores

Ontrack PowerControls can do this and there was one other I can't recall
that I used from a company that made AD tools as well...
The caveat is getting the db off the tape if that's where it is.
jlc

> -Original Message-
> From: McCready, Robert [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 20, 2008 10:59 AM
> To: MS-Exchange Admin Issues
> Subject: Exchange Backups and Restores
>
> Over the years, we've used several different versions of Exchange with
several
> different backup solutions.  Is there some third party software that
could
be
> purchased, allowing us to access an Exchange backup tape across
multiple
> platforms and recover a mailbox without actually building a lab for
the
> restore?  For instance, we used
>
> Veritas Backup Exec with Exchange 5.5.
> Data Protector 6.0 with Exchange 2003
> NT Backup with Exchange 2007
>
> I'd like to find out if there is ONE solution to access the data on
all
these
> tapes?
>
> Thanks all.
>
> Robert
>
> ~ 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~


~ 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~


RE: redimensioning OS and logs partitions

2008-03-20 Thread Miguel Gonzalez
any free tool?

Miguel

--- Stephan Barr <[EMAIL PROTECTED]>
escribió:

> Lot's of options but check out Acronis.  Fine stuff
> there.
> Cheers.
> 
> -Original Message-
> From: "Miguel Gonzalez" <[EMAIL PROTECTED]>
> To: "MS-Exchange Admin Issues"
> 
> Sent: 3/20/2008 5:33 PM
> Subject: redimensioning OS and logs partitions
> 
> Hi,
> 
>  I have three partitions in my SBS 2003 server.
> 
>  C - OS
>  D - Exchange databases (only)
>  E - Exchange logs and AV
> 
>  C and E are partitions within the same RAID array
> (RAID 1+0). I want to shrink the E drive and expand
> the C drive.
> 
>  The partitions are basic (not dynamic) and I've
> read
> that diskpart could help me to shrink the E drive.
> However apparently it wouldn't of no help for the C
> drive.
> 
>  Is it possible to shrink the E drive partition so
> the
> unallocated space is left in the beginning of the E
> partition and not at the end?
> 
>  Any clarification that I need to know?
> 
>  Thanks,
> 
>  Miguel
> 
> 
> 
>   __
> 
> Enviado desde Correo Yahoo! 
> Más formas de estar en contacto.
> http://es.docs.yahoo.com/mail/overview/index.html
> 
> 
> ~ 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  
>  ~
> 



  __ 
Enviado desde Correo Yahoo! 
Más formas de estar en contacto. 
http://es.docs.yahoo.com/mail/overview/index.html


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


RE: Exchange Backups and Restores

2008-03-20 Thread Michael B. Smith
Quest has a solution as well. The name escapes me at the moment.

Regards,

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


-Original Message-
From: Joseph L. Casale [mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 20, 2008 4:23 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange Backups and Restores

Ontrack PowerControls can do this and there was one other I can't recall
that I used from a company that made AD tools as well...
The caveat is getting the db off the tape if that's where it is.
jlc

> -Original Message-
> From: McCready, Robert [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 20, 2008 10:59 AM
> To: MS-Exchange Admin Issues
> Subject: Exchange Backups and Restores
>
> Over the years, we've used several different versions of Exchange with
several
> different backup solutions.  Is there some third party software that could
be
> purchased, allowing us to access an Exchange backup tape across multiple
> platforms and recover a mailbox without actually building a lab for the
> restore?  For instance, we used
>
> Veritas Backup Exec with Exchange 5.5.
> Data Protector 6.0 with Exchange 2003
> NT Backup with Exchange 2007
>
> I'd like to find out if there is ONE solution to access the data on all
these
> tapes?
>
> Thanks all.
>
> Robert
>
> ~ 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~


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


RE: redimensioning OS and logs partitions

2008-03-20 Thread Stephan Barr
Lot's of options but check out Acronis.  Fine stuff there.
Cheers.

-Original Message-
From: "Miguel Gonzalez" <[EMAIL PROTECTED]>
To: "MS-Exchange Admin Issues" 
Sent: 3/20/2008 5:33 PM
Subject: redimensioning OS and logs partitions

Hi,

 I have three partitions in my SBS 2003 server.

 C - OS
 D - Exchange databases (only)
 E - Exchange logs and AV

 C and E are partitions within the same RAID array
(RAID 1+0). I want to shrink the E drive and expand
the C drive.

 The partitions are basic (not dynamic) and I've read
that diskpart could help me to shrink the E drive.
However apparently it wouldn't of no help for the C
drive.

 Is it possible to shrink the E drive partition so the
unallocated space is left in the beginning of the E
partition and not at the end?

 Any clarification that I need to know?

 Thanks,

 Miguel



  __ 
Enviado desde Correo Yahoo! 
Más formas de estar en contacto. 
http://es.docs.yahoo.com/mail/overview/index.html


~ 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~


redimensioning OS and logs partitions

2008-03-20 Thread Miguel Gonzalez
Hi,

 I have three partitions in my SBS 2003 server.

 C - OS
 D - Exchange databases (only)
 E - Exchange logs and AV

 C and E are partitions within the same RAID array
(RAID 1+0). I want to shrink the E drive and expand
the C drive.

 The partitions are basic (not dynamic) and I've read
that diskpart could help me to shrink the E drive.
However apparently it wouldn't of no help for the C
drive.

 Is it possible to shrink the E drive partition so the
unallocated space is left in the beginning of the E
partition and not at the end?

 Any clarification that I need to know?

 Thanks,

 Miguel



  __ 
Enviado desde Correo Yahoo! 
Más formas de estar en contacto. 
http://es.docs.yahoo.com/mail/overview/index.html


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


Re: Exchange Management Shell killed the CDO star

2008-03-20 Thread Micheal Espinola Jr
;-P   Preppy button down white boy, all my life.   But, I'm not a *nix d00d
either!   But I dont know any *nix d00ds nuder the age of 45 that fit that
stero type either.

At least not any more...  :-D

On Thu, Mar 20, 2008 at 3:14 PM, Schwartz, Jim <[EMAIL PROTECTED]> wrote:

>  Let me know when you take that shower. ;-)
>
>
>
> *From:* Micheal Espinola Jr [mailto:[EMAIL PROTECTED]
> *Sent:* Thursday, March 20, 2008 1:50 PM
> *To:* MS-Exchange Admin Issues
> *Subject:* Re: Exchange Management Shell killed the CDO star
>
>
>
> How rediculously steriotypical of you.  Let me know when you send your
> time machine back to the future.
>
> On Thu, Mar 20, 2008 at 1:32 PM, Schwartz, Jim <[EMAIL PROTECTED]>
> wrote:
>
> Yeah. If I wanted to be a *nix guy, I would have stopped showering daily
> and let my hair grow long.
>
>
> -Original Message-
> From: Matteson, John H Jr USA Mr USA 25th SigBN (ITT)
> [mailto:[EMAIL PROTECTED]
>
> Sent: Thursday, March 20, 2008 1:01 AM
> To: MS-Exchange Admin Issues
>
> Subject: RE: Exchange Management Shell killed the CDO star
>
>  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 - 
> 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~
>
>
>
>
> --
> ME2
>
>
>
>
>



-- 
ME2

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

redimensioning OS and logs partitions

2008-03-20 Thread Miguel Gonzalez
Hi,

 I have three partitions in my SBS 2003 server.

 C - OS
 D - Exchange databases (only)
 E - Exchange logs and AV

 C and E are partitions within the same RAID array
(RAID 1+0). I want to shrink the E drive and expand
the C drive.

 The partitions are basic (not dynamic) and I've read
that diskpart could help me to shrink the E drive.
However apparently it wouldn't of no help for the C
drive.

 Is it possible to shrink the E drive partition so the
unallocated space is left in the beginning of the E
partition and not at the end?

 Any clarification that I need to know?

 Thanks,

 Miguel


  __ 
Enviado desde Correo Yahoo! 
Más formas de estar en contacto. 
http://es.docs.yahoo.com/mail/overview/index.html


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


RE: mailboxes and public folder

2008-03-20 Thread Campbell, Rob
I don't know about the public folder aspects, but exmerge is the tool you want 
for command line exporting of mailboxes from a mail store to .pst.

-Original Message-
From: Miguel Gonzalez [mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 20, 2008 4:51 PM
To: MS-Exchange Admin Issues
Subject: mailboxes and public folder

Hi,

 We have SBS 2003. Everytime an employee leaves the
company they require me to copy the mailbox to the
Public Folders (apart of giving someone permissions to
read the mailbox).

 It is very painful to create the folder and move the
folders manually from outlook (authenticated as the
user) and copy all the folders to the public folders.

 Can anybody think of a better way to do this?

 Another thing, how can I export a mailbox from
Exchange 2003 to a PST format or something that could
be imported easily? Do I have to export it from
Outlook?

 Miguel


  __ 
Enviado desde Correo Yahoo!
Disfruta de una bandeja de entrada más inteligente. 
http://es.docs.yahoo.com/mail/overview/index.html


~ 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~


mailboxes and public folder

2008-03-20 Thread Miguel Gonzalez
Hi,

 We have SBS 2003. Everytime an employee leaves the
company they require me to copy the mailbox to the
Public Folders (apart of giving someone permissions to
read the mailbox).

 It is very painful to create the folder and move the
folders manually from outlook (authenticated as the
user) and copy all the folders to the public folders.

 Can anybody think of a better way to do this?

 Another thing, how can I export a mailbox from
Exchange 2003 to a PST format or something that could
be imported easily? Do I have to export it from
Outlook?

 Miguel


  __ 
Enviado desde Correo Yahoo!
Disfruta de una bandeja de entrada más inteligente. 
http://es.docs.yahoo.com/mail/overview/index.html


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


Re: Outlook Calendar

2008-03-20 Thread Alex Alborzfard
I seem to have the opposite issue in regards to OL & TREO:

Recurring Outlook meetings created before 2007 DST change are displaying 1
hour ahead of schedule for the user and the meeting recipients. If he goes
to the suspect recurring meeting instance in the month of April it shows the
correct meeting time.

DST patch is in place on the user's machine. Also his Treo is showing the
correct OL meeting time where as his laptop OL client is not.
Does the user's machine needs the fix in this MSKB:

http://support.microsoft.com/kb/931667/

 Or is this an issue at the EXCH level?

 TIA

 Alex

On Wed, Mar 12, 2008 at 10:21 AM, Dennis Rogov <
[EMAIL PROTECTED]> wrote:

>  Some of the Outlook Calendar recurring appointments are
> showing up to be off by an hour?
>
>
>
> All my users have the latest DST patch running exchange 03 . I send this
> email out last week to the forum a
>
>
>
> Lot of your stated you were experiencing same issues has anyone found a
> fix.
>
>
>
> Dennis Rogov
>
> Senior Network Analyst
> THE *P**eer* GROUP *an informed medical communications company*
>
> 379 thornall street, 12th floor  | edison, nj 08837 usa
>
> Direct: 732-205-8376 | fax: 732.321.0636 |Cell:732.861.2277
>
> [EMAIL PROTECTED]   www.peergroupinc.com
> [This e-mail and any attachments thereto, is intended only for use by the
> addressee(s) named herein and may contain legally privileged and/or
> confidential information. No confidentiality or privilege is waived or lost
> by any mistransmission. If you are not the intended recipient of this
> e-mail, you are hereby notified any dissemination, distribution or copying
> of this email, and any attachments thereto, is strictly prohibited. If you
> receive this email in error please immediately notify me at (732) 205-8376
> and permanently delete the original copy and any copy of any e-mail, and any
> printout thereof. ]
>
>
>
>
>
>
>

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

RE: Exchange Backups and Restores

2008-03-20 Thread Joseph L. Casale
Ontrack PowerControls can do this and there was one other I can't recall that I 
used from a company that made AD tools as well...
The caveat is getting the db off the tape if that's where it is.
jlc

> -Original Message-
> From: McCready, Robert [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 20, 2008 10:59 AM
> To: MS-Exchange Admin Issues
> Subject: Exchange Backups and Restores
>
> Over the years, we've used several different versions of Exchange with several
> different backup solutions.  Is there some third party software that could be
> purchased, allowing us to access an Exchange backup tape across multiple
> platforms and recover a mailbox without actually building a lab for the
> restore?  For instance, we used
>
> Veritas Backup Exec with Exchange 5.5.
> Data Protector 6.0 with Exchange 2003
> NT Backup with Exchange 2007
>
> I'd like to find out if there is ONE solution to access the data on all these
> tapes?
>
> Thanks all.
>
> Robert
>
> ~ 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~


RE: Exchange Management Shell killed the CDO star

2008-03-20 Thread Schwartz, Jim
Let me know when you take that shower. ;-)

 

From: Micheal Espinola Jr [mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 20, 2008 1:50 PM
To: MS-Exchange Admin Issues
Subject: Re: Exchange Management Shell killed the CDO star

 

How rediculously steriotypical of you.  Let me know when you send your
time machine back to the future.

On Thu, Mar 20, 2008 at 1:32 PM, Schwartz, Jim <[EMAIL PROTECTED]>
wrote:

Yeah. If I wanted to be a *nix guy, I would have stopped showering daily
and let my hair grow long.


-Original Message-
From: Matteson, John H Jr USA Mr USA 25th SigBN (ITT)
[mailto:[EMAIL PROTECTED]

Sent: Thursday, March 20, 2008 1:01 AM
To: MS-Exchange Admin Issues

Subject: RE: Exchange Management Shell killed the CDO star

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 - 
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~




-- 
ME2 

 


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

Outlook, Fonts, Group Policy (Cross Post)

2008-03-20 Thread Sam Cayze
Looks like I need a Control ID to disable some parts of Outlook 2003?
Anyone done this?  I am having a hard time finding these control IDs...

 

Thanks!

 

 

My users keep trying to change the fonts for outgoing messages.  I want
to lock this down.

 

I can't find anything in the GPO Admin Template.

 

Has anyone done this?

 

thanks

 

Sam

 

 

 

 

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

RE: Exchange Management Shell killed the CDO star

2008-03-20 Thread Campbell, Rob
Somehow I doubt that there has ever been a new language developed that
other people didn't think the effort wouldn't have been better spend
adapting some other language (I suspect that invariably it was some
other language the person making the argument was already fluent in).

 

I know I've been perturbed that there has to be different rules and
syntax for LDAP queries, SQL queried and WMI queries, and didn't care
much for SDDL at all.  But none of that got me one bit closer to solving
the problem at hand.  The only thing that did was deciding that they are
what they are and aren't going to change, so I'm going to have to.

 

FWIW

 



From: Michael B. Smith [mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 20, 2008 12:18 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange Management Shell killed the CDO star

 

There was no other language that was designed to deal with objects...

 

If you want to continue to do text processing, stick with Perl. :-) 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 - 
> 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

RE: Exchange Management Shell killed the CDO star

2008-03-20 Thread Schwartz, Jim
FTFY ;-)

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

On Thu, Mar 20, 2008 at 1:32 PM, Schwartz, Jim <[EMAIL PROTECTED]>
wrote:
> Yeah. If I wanted to be a *nix guy, I would have stopped showering
daily
>  and let my hair grow long.

  Hey, I'm a nix guy, too.  And I don't have hair.  ;-)

-- Ben

~ 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~


RE: forwarding a contact

2008-03-20 Thread Joe Heaton
Never mind, I found it.  In Outlook 2K3, it's in the contact file
itself, you choose Action -> forward as vCard.
 
Joe Heaton
 



From: Joe Heaton [mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 20, 2008 11:29 AM
To: MS-Exchange Admin Issues
Subject: forwarding a contact


I know it's possible to attach your own information to an e-mail, as a
vCard.  Is it possible to do this type of thing with one of your
contacts, in order to forward contact information?
 
Joe Heaton
AISA
Employment Training Panel
1100 J Street, 4th Floor
Sacramento, CA  95814
(916) 327-5276
[EMAIL PROTECTED]
 


 


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

forwarding a contact

2008-03-20 Thread Joe Heaton
I know it's possible to attach your own information to an e-mail, as a
vCard.  Is it possible to do this type of thing with one of your
contacts, in order to forward contact information?
 
Joe Heaton
AISA
Employment Training Panel
1100 J Street, 4th Floor
Sacramento, CA  95814
(916) 327-5276
[EMAIL PROTECTED]
 

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

Re: Exchange Management Shell killed the CDO star

2008-03-20 Thread Kurt Buff
Well, except for the hair, what's changed for you? :)

On Thu, Mar 20, 2008 at 10:32 AM, Schwartz, Jim <[EMAIL PROTECTED]> wrote:
> Yeah. If I wanted to be a *nix guy, I would have stopped showering daily
>  and let my hair grow long.
>
>
>  -Original Message-
>  From: Matteson, John H Jr USA Mr USA 25th SigBN (ITT)
>  [mailto:[EMAIL PROTECTED]
>
> Sent: Thursday, March 20, 2008 1:01 AM
>  To: MS-Exchange Admin Issues
>
> Subject: RE: Exchange Management Shell killed the CDO star
>
>  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 - 
>  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~
>

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


Re: Exchange Management Shell killed the CDO star

2008-03-20 Thread Kurt Buff
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 - 
>  > 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

Re: Exchange Management Shell killed the CDO star

2008-03-20 Thread Kurt Buff
Oh, yes...

Heh.

On Thu, Mar 20, 2008 at 8:53 AM, Kevin Miller <[EMAIL PROTECTED]> wrote:
> I just spilled a 16oz glass of ice water on my lap.. does that make you happy?
>
>
>  -Original Message-
>  From: Kurt Buff [mailto:[EMAIL PROTECTED]
>  Sent: Thursday, March 20, 2008 8: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 - 
>  > 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~
>
>  ~ 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~


Re: E2k7 Unified Messaging and Avaya

2008-03-20 Thread matt
To be fair the cisco system was in 2001.  Pretty early dev.  I do understand 
that the Avaya code is co-authored with Cisco now.  A long time friend jumped 
the Avaya ship when they were shutting down here (redmond) and went to cisco, 
he telecommutes to Cal somewhere and has to fly for meetings once a month.
  - Original Message - 
  From: Maglinger, Paul 
  To: MS-Exchange Admin Issues 
  Sent: Thursday, March 20, 2008 9:20 AM
  Subject: RE: E2k7 Unified Messaging and Avaya


  Hmmm... We've had it for 2-3 years and (knock on wood) has been pretty 
stable.  The most painful part of upgrading a single part of it is having to 
sift through the release notes for the unified messaging AND the callmanger AND 
the CRSS, AND Exchange and anything else that's attached to it to make sure you 
don't miss anything.  When they say unified, believe me brother, they mean it!



--
  From: Matt Moore [mailto:[EMAIL PROTECTED] 
  Sent: Thursday, March 20, 2008 9:59 AM
  To: MS-Exchange Admin Issues
  Subject: RE: E2k7 Unified Messaging and Avaya


  Done that too and it was worse than Avaya.  Worst support I've ever 
encountered.  Bar none.

   


--

  From: Maglinger, Paul [mailto:[EMAIL PROTECTED] 
  Sent: Thursday, March 20, 2008 7:56 AM
  To: MS-Exchange Admin Issues
  Subject: RE: E2k7 Unified Messaging and Avaya

   

  We went with Cisco...

   


--

  From: Matt Moore [mailto:[EMAIL PROTECTED] 
  Sent: Wednesday, March 19, 2008 7:26 PM
  To: MS-Exchange Admin Issues
  Subject: RE: E2k7 Unified Messaging and Avaya

  I had the Avaya connected to e2k3 via their software, IP Office.  To put it 
mildly, it sucked.  If it wasn't users bitching for speakers to hear their 
messages... I had it set to only go through the handset but then it wouldn't 
delete the messages when you told it to.  About 6 patches and upgrades later, I 
decided it wasn't going any further.  If you allowed it to fully interact with 
outlook, it attaches a wav file to the email it puts in the inbox.  Guess what 
happens when they don't get deleted?  Look hard at the MS Unified.  I'll be 
embarking on a Mitel voip system with e2k7 very soon.  

  M

   


--

  From: Matt Lathrum [mailto:[EMAIL PROTECTED] 
  Sent: Wednesday, March 19, 2008 2:01 PM
  To: MS-Exchange Admin Issues
  Subject: E2k7 Unified Messaging and Avaya

   

  Does anyone on this list have E2k7 Unified Messaging with an Avaya backbone?  
Are you using Modular Messaging or Microsoft Unified Messaging?  Our company is 
currently evaluating which path to take and would love to hear lessons learned 
about either approach.

   

  Matt

   

   

   

   

   

   

   









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

Re: Exchange Management Shell killed the CDO star

2008-03-20 Thread Micheal Espinola Jr
I guess time will tell to see if Joe continues to dev/use compiled utils, or
opts for PS scripts.

On Thu, Mar 20, 2008 at 1:44 PM, Michael B. Smith <
[EMAIL PROTECTED]> wrote:

>  Um-hmmm.
>
>
>
> I think I will have to agree to disagree with you gentlemen.
>
>
>
> Writing a module doesn't overcome the inherent limitations of dealing with
> a pipe that is basically a text pipe, unless you are going to write
> everything in a module, at which point you might as well write in C# or C++.
>
>
>
> That would be why Joe Richards, the biggest proponent of Perl-on-Win32
> that I know, still has a huge number of utilities that are written in C++
> (like adfind, admod, oldcmp, etc.).
>
>
>
> Regards,
>
>
>
> Michael B. Smith
>
> MCSE/Exchange MVP
>
> http://TheEssentialExchange.com 
>
>
>
> *From:* Micheal Espinola Jr [mailto:[EMAIL PROTECTED]
> *Sent:* Thursday, March 20, 2008 1:29 PM
> *To:* MS-Exchange Admin Issues
> *Subject:* Re: Exchange Management Shell killed the CDO star
>
>
>
> Or abilty to limitelessly extend with modules that tap into API's etc.
>
>
>
> I mean seriously.  I applaud MS's work on PS - but what a gargantuan waste
> of misplaced time and effort.
>
>
>
> Perl can do far more than process text.   Modules, baby, modules!
>
> On Thu, Mar 20, 2008 at 1:21 PM, Ben Scott <[EMAIL PROTECTED]> wrote:
>
> On Thu, Mar 20, 2008 at 12:41 PM, Michael B. Smith
> <[EMAIL PROTECTED]> wrote:
>
> >  PS contains all the good parts of Perl and PHP 
>
>  Except the "multi-platform", "Open Source", "huge library of
> third-party software" , "small footprint", "doesn't re-invent the
> wheel", and "something people already know" parts.  >rolls eyes<
>
>  Microsoft should introduce a new scripting language with *every*
> version of Windows.  That'll be even better.
>
> -- Ben
>
>
> ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~
> ~ http://www.sunbeltsoftware.com/Ninja~
>
>
>
>
> --
> ME2
>
>
>
>
>



-- 
ME2

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

Re: Exchange Management Shell killed the CDO star

2008-03-20 Thread Ben Scott
On Thu, Mar 20, 2008 at 1:32 PM, Schwartz, Jim <[EMAIL PROTECTED]> wrote:
> Yeah. If I wanted to be a *nix guy, I would have stopped showering daily
>  and let my hair grow long.

  Hey, I'm a nix guy, too.  And I don't have long hair.  ;-)

-- Ben

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


more on PS

2008-03-20 Thread Michael B. Smith
And come on, you gotta admit, being able to do the below just rocks:

 

$perfObject = new-object
System.Diagnostics.PerformanceCounterCategory("Process")

 

$perfObject.GetInstanceNames() | foreach {

$counter = ($perfObject.GetCounters($_))[0];

$counter.CounterName = "Thread Count";

if ($counter.RawValue -gt 50 -and $_ -ne
"_Total")

{

$_;

("threadcount: " +
$counter.RawValue);

$counter.CounterName =
"Working Set";

("workingsetsize: " +
$counter.RawValue);

" ";

}

}

 

Or if you want it in one line via a different interface:

 

gwmi win32_process | where { $_.threadcount -gt 50 } | fl name, threadcount,
workingsetsize

 

w00t!

 

Regards,

 

Michael B. Smith

MCSE/Exchange MVP

http://TheEssentialExchange.com

 


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

Re: Exchange Management Shell killed the CDO star

2008-03-20 Thread Micheal Espinola Jr
How rediculously steriotypical of you.  Let me know when you send your time
machine back to the future.

On Thu, Mar 20, 2008 at 1:32 PM, Schwartz, Jim <[EMAIL PROTECTED]> wrote:

> Yeah. If I wanted to be a *nix guy, I would have stopped showering daily
> and let my hair grow long.
>
> -Original Message-
> From: Matteson, John H Jr USA Mr USA 25th SigBN (ITT)
> [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 20, 2008 1:01 AM
> To: MS-Exchange Admin Issues
> Subject: RE: Exchange Management Shell killed the CDO star
>
> 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 - 
> 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~
>



-- 
ME2

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

RE: Exchange Management Shell killed the CDO star

2008-03-20 Thread Michael B. Smith
Um-hmmm.

 

I think I will have to agree to disagree with you gentlemen.

 

Writing a module doesn't overcome the inherent limitations of dealing with a
pipe that is basically a text pipe, unless you are going to write everything
in a module, at which point you might as well write in C# or C++.

 

That would be why Joe Richards, the biggest proponent of Perl-on-Win32 that
I know, still has a huge number of utilities that are written in C++ (like
adfind, admod, oldcmp, etc.).

 

Regards,

 

Michael B. Smith

MCSE/Exchange MVP

http://TheEssentialExchange.com

 

From: Micheal Espinola Jr [mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 20, 2008 1:29 PM
To: MS-Exchange Admin Issues
Subject: Re: Exchange Management Shell killed the CDO star

 

Or abilty to limitelessly extend with modules that tap into API's etc.

 

I mean seriously.  I applaud MS's work on PS - but what a gargantuan waste
of misplaced time and effort.

 

Perl can do far more than process text.   Modules, baby, modules!

On Thu, Mar 20, 2008 at 1:21 PM, Ben Scott <[EMAIL PROTECTED]> wrote:

On Thu, Mar 20, 2008 at 12:41 PM, Michael B. Smith
<[EMAIL PROTECTED]> wrote:

>  PS contains all the good parts of Perl and PHP 

 Except the "multi-platform", "Open Source", "huge library of
third-party software" , "small footprint", "doesn't re-invent the
wheel", and "something people already know" parts.  >rolls eyes<

 Microsoft should introduce a new scripting language with *every*
version of Windows.  That'll be even better.

-- Ben


~ 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~

RE: Exchange Management Shell killed the CDO star

2008-03-20 Thread Campbell, Rob
I'm afraid I'm not particularly fluent in perl, so you'll have to
forgive me if this is an ignorant question.

 

What's the difference between a perl module and a powershell snapin?

 



From: Micheal Espinola Jr [mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 20, 2008 12:29 PM
To: MS-Exchange Admin Issues
Subject: Re: Exchange Management Shell killed the CDO star

 

 


**
 
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~

RE: Exchange Management Shell killed the CDO star

2008-03-20 Thread Don Andrews
Don't forget your propeller beanie. ;)

-Original Message-
From: Schwartz, Jim [mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 20, 2008 10:33 AM
To: MS-Exchange Admin Issues
Subject: RE: Exchange Management Shell killed the CDO star

Yeah. If I wanted to be a *nix guy, I would have stopped showering daily
and let my hair grow long.

-Original Message-
From: Matteson, John H Jr USA Mr USA 25th SigBN (ITT)
[mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 20, 2008 1:01 AM
To: MS-Exchange Admin Issues
Subject: RE: Exchange Management Shell killed the CDO star

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 - 
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~



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


RE: Exchange Management Shell killed the CDO star

2008-03-20 Thread Schwartz, Jim
Yeah. If I wanted to be a *nix guy, I would have stopped showering daily
and let my hair grow long.

-Original Message-
From: Matteson, John H Jr USA Mr USA 25th SigBN (ITT)
[mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 20, 2008 1:01 AM
To: MS-Exchange Admin Issues
Subject: RE: Exchange Management Shell killed the CDO star

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 - 
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~


RE: Exchange Management Shell killed the CDO star

2008-03-20 Thread Michael B. Smith
Whatever. I've been through 30+ languages in the last 30 years. Picking up a
new one is no big deal.

It's optimized to the platform. It's object oriented. It does included a
huge library of software - the .net framework.

Hey, MSFT has released a new model of administration for Exchange, every
single release. I'm used to it. :-)

Regards,

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

-Original Message-
From: Ben Scott [mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 20, 2008 1:22 PM
To: MS-Exchange Admin Issues
Subject: Re: Exchange Management Shell killed the CDO star

On Thu, Mar 20, 2008 at 12:41 PM, Michael B. Smith
<[EMAIL PROTECTED]> wrote:
>  PS contains all the good parts of Perl and PHP 

  Except the "multi-platform", "Open Source", "huge library of
third-party software" , "small footprint", "doesn't re-invent the
wheel", and "something people already know" parts.  >rolls eyes<

  Microsoft should introduce a new scripting language with *every*
version of Windows.  That'll be even better.

-- Ben

~ 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~


RE: Exchange Management Shell killed the CDO star

2008-03-20 Thread Michael B. Smith
Allow me to say scripting language then. Java, in my mind, is an
abomination.

I think they could've extended Perl. And that would've been fine. But I
don't think any of the other options have the breadth of PS. Or it's glide
path.

Regards,

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


-Original Message-
From: Ben Scott [mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 20, 2008 1:28 PM
To: MS-Exchange Admin Issues
Subject: Re: Exchange Management Shell killed the CDO star

On Thu, Mar 20, 2008 at 1:18 PM, Michael B. Smith
<[EMAIL PROTECTED]> wrote:
> There was no other language that was designed to deal with objects.

  >cough< >splutter<

  C++, Java, Python, Ruby, Smalltalk, just to name a few.

  PowerShell was a solution in search of a problem to solve.
Microsoft made sure to manufacture problems for it to solve in their
newer releases.  :-p

  Don't get me wrong, it's not that PowSh is technically flawed --
it's very capable by all accounts -- it's just that PowSh is one more
damn thing to learn and worry about, when there were countless other
options out there Microsoft could have gone with.

-- Ben

~ 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~


Re: Exchange Management Shell killed the CDO star

2008-03-20 Thread Micheal Espinola Jr
Or abilty to limitelessly extend with modules that tap into API's etc.

I mean seriously.  I applaud MS's work on PS - but what a gargantuan waste
of misplaced time and effort.

Perl can do far more than process text.   Modules, baby, modules!

On Thu, Mar 20, 2008 at 1:21 PM, Ben Scott <[EMAIL PROTECTED]> wrote:

> On Thu, Mar 20, 2008 at 12:41 PM, Michael B. Smith
> <[EMAIL PROTECTED]> wrote:
> >  PS contains all the good parts of Perl and PHP 
>
>  Except the "multi-platform", "Open Source", "huge library of
> third-party software" , "small footprint", "doesn't re-invent the
> wheel", and "something people already know" parts.  >rolls eyes<
>
>  Microsoft should introduce a new scripting language with *every*
> version of Windows.  That'll be even better.
>
> -- Ben
>
> ~ 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~

Re: Exchange Management Shell killed the CDO star

2008-03-20 Thread Ben Scott
On Thu, Mar 20, 2008 at 1:18 PM, Michael B. Smith
<[EMAIL PROTECTED]> wrote:
> There was no other language that was designed to deal with objects…

  >cough< >splutter<

  C++, Java, Python, Ruby, Smalltalk, just to name a few.

  PowerShell was a solution in search of a problem to solve.
Microsoft made sure to manufacture problems for it to solve in their
newer releases.  :-p

  Don't get me wrong, it's not that PowSh is technically flawed --
it's very capable by all accounts -- it's just that PowSh is one more
damn thing to learn and worry about, when there were countless other
options out there Microsoft could have gone with.

-- Ben

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


Re: Exchange Management Shell killed the CDO star

2008-03-20 Thread Ben Scott
On Thu, Mar 20, 2008 at 12:41 PM, Michael B. Smith
<[EMAIL PROTECTED]> wrote:
>  PS contains all the good parts of Perl and PHP 

  Except the "multi-platform", "Open Source", "huge library of
third-party software" , "small footprint", "doesn't re-invent the
wheel", and "something people already know" parts.  >rolls eyes<

  Microsoft should introduce a new scripting language with *every*
version of Windows.  That'll be even better.

-- Ben

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


RE: Exchange Management Shell killed the CDO star

2008-03-20 Thread Michael B. Smith
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 - 
> 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~

Re: Exchange Management Shell killed the CDO star

2008-03-20 Thread Micheal Espinola Jr
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 - 
> > 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~

Exchange Backups and Restores

2008-03-20 Thread McCready, Robert
Over the years, we've used several different versions of Exchange with several 
different backup solutions.  Is there some third party software that could be 
purchased, allowing us to access an Exchange backup tape across multiple 
platforms and recover a mailbox without actually building a lab for the 
restore?  For instance, we used

Veritas Backup Exec with Exchange 5.5.
Data Protector 6.0 with Exchange 2003
NT Backup with Exchange 2007

I'd like to find out if there is ONE solution to access the data on all these 
tapes?

Thanks all.

Robert

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


RE: Exchange Management Shell killed the CDO star

2008-03-20 Thread Michael B. Smith
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 - 
> 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~


RE: Exchange Sp1 Rollup1 CAS\HT server problem

2008-03-20 Thread Fergal O Connell
remote registry was not started...
seems fine now..


From: Fergal O Connell [mailto:[EMAIL PROTECTED]
Sent: 20 March 2008 15:28
To: MS-Exchange Admin Issues
Subject: Exchange Sp1 Rollup1 CAS\HT server problem

Hi Folks,

Just installed the following update on our CA\HT server and it seemed to have 
fallen over -
Nothing worked! Exchange errors everywhere and IIS and all the exchange 
services were disabled -

Downloaded the .exe and then ran it manually - eventually it installed and back 
up again with some issues -

MailFlow seems to be fine - although delays in sending\recieving external mail

[PS] C:\Documents and Settings\admin>Test-SystemHealth
Test-SystemHealth : Exchange server ExchangeServerName is down or unreachable. 
This could b
e the result of a network or permissions problem. Error: The network path was n
ot found
At line:1 char:17
+ Test-SystemHealth 

Also ran Exchange ExBPA and I get
Exchange server "ExchangeServerName" is down or unreachable. This could be the 
result of a network or permissions problem. Error: The network path was not 
found

Event viewer is now clean
Any thoughts?




The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorized. If you are not the intended recipient, any disclosure,
copying, distribution or any action taken or omitted to be taken in reliance
on it, is prohibited and may be unlawful. If you are not the intended
addressee please contact the sender and dispose of this e-mail. Thank you.






The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorized. If you are not the intended recipient, any disclosure,
copying, distribution or any action taken or omitted to be taken in reliance
on it, is prohibited and may be unlawful. If you are not the intended
addressee please contact the sender and dispose of this e-mail. Thank you.

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

RE: Exchange Management Shell killed the CDO star

2008-03-20 Thread Campbell, Rob
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 - 
> 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~


RE: E2k7 Unified Messaging and Avaya

2008-03-20 Thread Maglinger, Paul
Hmmm... We've had it for 2-3 years and (knock on wood) has been pretty
stable.  The most painful part of upgrading a single part of it is
having to sift through the release notes for the unified messaging AND
the callmanger AND the CRSS, AND Exchange and anything else that's
attached to it to make sure you don't miss anything.  When they say
unified, believe me brother, they mean it!



From: Matt Moore [mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 20, 2008 9:59 AM
To: MS-Exchange Admin Issues
Subject: RE: E2k7 Unified Messaging and Avaya



Done that too and it was worse than Avaya.  Worst support I've ever
encountered.  Bar none.

 



From: Maglinger, Paul [mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 20, 2008 7:56 AM
To: MS-Exchange Admin Issues
Subject: RE: E2k7 Unified Messaging and Avaya

 

We went with Cisco...

 



From: Matt Moore [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, March 19, 2008 7:26 PM
To: MS-Exchange Admin Issues
Subject: RE: E2k7 Unified Messaging and Avaya

I had the Avaya connected to e2k3 via their software, IP Office.  To put
it mildly, it sucked.  If it wasn't users bitching for speakers to hear
their messages. I had it set to only go through the handset but then
it wouldn't delete the messages when you told it to.  About 6 patches
and upgrades later, I decided it wasn't going any further.  If you
allowed it to fully interact with outlook, it attaches a wav file to the
email it puts in the inbox.  Guess what happens when they don't get
deleted?  Look hard at the MS Unified.  I'll be embarking on a Mitel
voip system with e2k7 very soon.  

M

 



From: Matt Lathrum [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, March 19, 2008 2:01 PM
To: MS-Exchange Admin Issues
Subject: E2k7 Unified Messaging and Avaya

 

Does anyone on this list have E2k7 Unified Messaging with an Avaya
backbone?  Are you using Modular Messaging or Microsoft Unified
Messaging?  Our company is currently evaluating which path to take and
would love to hear lessons learned about either approach.

 

Matt

 

 

 

 

 

 

 


 


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

Re: Exchange Management Shell killed the CDO star

2008-03-20 Thread Micheal Espinola Jr
shrinkage: its whats not for dinner.

On Thu, Mar 20, 2008 at 11:53 AM, Kevin Miller <[EMAIL PROTECTED]> wrote:

> I just spilled a 16oz glass of ice water on my lap.. does that make you
> happy?
>
> -Original Message-
> From: Kurt Buff [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 20, 2008 8: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 - 
> > 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~
>
> ~ 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~

RE: NDR attachment stripping or recipient filtering - which is better?

2008-03-20 Thread Jason Gurtz
> If I eliminate NDRs completely for invalid addresses, though, then
> people who make innocent typing mistakes will not know that their
> message did not get through.

If you think about mail flow more completely, you will see this most
likely isn't the case.

1. [EMAIL PROTECTED] submits mail to mta.foo.com addressed to [EMAIL PROTECTED]
2. mta.foo.com attempts to relay mail to mx.bar.com:

mta.foo.com -> HELO foo.com
mx.bar.com  <- 250 'Hi, Pleased to meet you'
mta.foo.com -> MAIL FROM: <[EMAIL PROTECTED]>
mx.bar.com  <- 250 'Sender OK'
mta.foo.com -> RCPT TO: <[EMAIL PROTECTED]>

3. mx.bar.com queries ldap and finds [EMAIL PROTECTED] invalid

mx.bar.com  <- 550 #5.5.1 '[EMAIL PROTECTED] doesn't exist'
mta.foo.com -> QUIT

4. mta.foo.com sends report to [EMAIL PROTECTED] that message couldn't be
delivered

A couple cases where there would be no notification...

1. The "typoed" address exists and mail is delivered to a non-intended
destination
2. mta.foo.com is broken and doesn't do step 4.

In short, not a big concern.

~JasonG

-- 

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

RE: Exchange Management Shell killed the CDO star

2008-03-20 Thread Kevin Miller
I just spilled a 16oz glass of ice water on my lap.. does that make you happy?

-Original Message-
From: Kurt Buff [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 20, 2008 8: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 - 
> 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~

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


Re: Exchange Management Shell killed the CDO star

2008-03-20 Thread Kurt Buff
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 - 
> 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~


Exchange Sp1 Rollup1 CAS\HT server problem

2008-03-20 Thread Fergal O Connell
Hi Folks,

Just installed the following update on our CA\HT server and it seemed to have 
fallen over -
Nothing worked! Exchange errors everywhere and IIS and all the exchange 
services were disabled -

Downloaded the .exe and then ran it manually - eventually it installed and back 
up again with some issues -

MailFlow seems to be fine - although delays in sending\recieving external mail

[PS] C:\Documents and Settings\admin>Test-SystemHealth
Test-SystemHealth : Exchange server ExchangeServerName is down or unreachable. 
This could b
e the result of a network or permissions problem. Error: The network path was n
ot found
At line:1 char:17
+ Test-SystemHealth 

Also ran Exchange ExBPA and I get
Exchange server "ExchangeServerName" is down or unreachable. This could be the 
result of a network or permissions problem. Error: The network path was not 
found

Event viewer is now clean
Any thoughts?




The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorized. If you are not the intended recipient, any disclosure,
copying, distribution or any action taken or omitted to be taken in reliance
on it, is prohibited and may be unlawful. If you are not the intended
addressee please contact the sender and dispose of this e-mail. Thank you.

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

Re: Exchange Management Shell killed the CDO star

2008-03-20 Thread Rubens Almeida
I'm migrating my VBS + CDO/CDOEXM code to POSH+CDO/CDOEXM with very
little problems. POSH is far way more easy to debug than VBS. I think
you should give it a try.

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


RE: E2k7 Unified Messaging and Avaya

2008-03-20 Thread Matt Moore
Done that too and it was worse than Avaya.  Worst support I've ever
encountered.  Bar none.

 

  _  

From: Maglinger, Paul [mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 20, 2008 7:56 AM
To: MS-Exchange Admin Issues
Subject: RE: E2k7 Unified Messaging and Avaya

 

We went with Cisco...

 

  _  

From: Matt Moore [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, March 19, 2008 7:26 PM
To: MS-Exchange Admin Issues
Subject: RE: E2k7 Unified Messaging and Avaya

I had the Avaya connected to e2k3 via their software, IP Office.  To put it
mildly, it sucked.  If it wasn't users bitching for speakers to hear their
messages... I had it set to only go through the handset but then it wouldn't
delete the messages when you told it to.  About 6 patches and upgrades
later, I decided it wasn't going any further.  If you allowed it to fully
interact with outlook, it attaches a wav file to the email it puts in the
inbox.  Guess what happens when they don't get deleted?  Look hard at the MS
Unified.  I'll be embarking on a Mitel voip system with e2k7 very soon.  

M

 

  _  

From: Matt Lathrum [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, March 19, 2008 2:01 PM
To: MS-Exchange Admin Issues
Subject: E2k7 Unified Messaging and Avaya

 

Does anyone on this list have E2k7 Unified Messaging with an Avaya backbone?
Are you using Modular Messaging or Microsoft Unified Messaging?  Our company
is currently evaluating which path to take and would love to hear lessons
learned about either approach.

 

Matt

 

 

 

 

 

 

 


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

RE: E2k7 Unified Messaging and Avaya

2008-03-20 Thread Maglinger, Paul
We went with Cisco...



From: Matt Moore [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, March 19, 2008 7:26 PM
To: MS-Exchange Admin Issues
Subject: RE: E2k7 Unified Messaging and Avaya



I had the Avaya connected to e2k3 via their software, IP Office.  To put
it mildly, it sucked.  If it wasn't users bitching for speakers to hear
their messages. I had it set to only go through the handset but then
it wouldn't delete the messages when you told it to.  About 6 patches
and upgrades later, I decided it wasn't going any further.  If you
allowed it to fully interact with outlook, it attaches a wav file to the
email it puts in the inbox.  Guess what happens when they don't get
deleted?  Look hard at the MS Unified.  I'll be embarking on a Mitel
voip system with e2k7 very soon.  

M

 



From: Matt Lathrum [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, March 19, 2008 2:01 PM
To: MS-Exchange Admin Issues
Subject: E2k7 Unified Messaging and Avaya

 

Does anyone on this list have E2k7 Unified Messaging with an Avaya
backbone?  Are you using Modular Messaging or Microsoft Unified
Messaging?  Our company is currently evaluating which path to take and
would love to hear lessons learned about either approach.

 

Matt

 

 

 


 


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

RE: E2k7 Unified Messaging and Avaya

2008-03-20 Thread Matt Moore
I can see where the Avaya could be a good system.  It had lots of features
and was easy to manage after the install. We had a combo PBX VIOP system six
of them.  The entire setup was chosen by the CFO because it was going to
save them money to do some other things.  I've found new phone systems
rarely save any money.  They make money for the HW vendor and the line
providers.  It was the old "I bought this now you have a month to make it
work".  Well that entailed an entire new network because the PBX's
communicated via VOIP and they were running a very network intensive legacy
management app.  Another story.  0 testing..  In the end it was my fault
it didn't work as expected in a month.  It took 6.

M

 

  _  

From: Davies,Matt [mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 20, 2008 4:06 AM
To: MS-Exchange Admin Issues
Subject: RE: E2k7 Unified Messaging and Avaya

 

Matt,

 

We just made the decision to go Modular Messaging, although we are still on
Exchange 2003, we looked into UM a lot, but found that the feature set is
still very basic, compared to MM 3.1

 

With connection to the PBX with MM, you have the option for H.323 based ip
trunks or Qsig via E1 or T1 card in the server, both options work well.

 

We currently have a number of networked Avaya S8xxx PBX's worldwide running
CM3  to CM 5, all using 2 Avaya MM systems ( 1 in the US and 1 in the UK) to
be honest the installation experience really depends on the person you get,
I have seen a lot of people who do not understand MM trying to install it
failing, but if you get someone who knows what they are doing, it makes a
great difference.

 

If you want any further info, please feel free to contact me off list.

 

Cheers

 

Matt

 

 



Matt Davies

Director of International IT Operations

General Atlantic

83 Pall Mall

London

SW1Y 5ES

 

Tel: +44 207 484 3203

Fax: +44 207 484 2803

Mobile: +44 777 559 4265



 

 

 

 

 

 

From: Matt Lathrum [mailto:[EMAIL PROTECTED] 
Sent: 19 March 2008 21:01
To: MS-Exchange Admin Issues
Subject: E2k7 Unified Messaging and Avaya

 

Does anyone on this list have E2k7 Unified Messaging with an Avaya backbone?
Are you using Modular Messaging or Microsoft Unified Messaging?  Our company
is currently evaluating which path to take and would love to hear lessons
learned about either approach.

 

Matt

 

 

 

 



This e-mail (including all attachments) is confidential and may be
privileged.  
It is for the exclusive use of the addressee only.  If you are not the
addressee, 
you are hereby notified that any dissemination of this communication is
strictly 
prohibited. If you have received this communication in error, please erase
all 
copies of the message and its attachments and notify us immediately at 
[EMAIL PROTECTED]  Thank You.

 

 

 


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

RE: Outlook sending mails to junk folder with no junk filtering enabled

2008-03-20 Thread Oliver Marshall
No IMF here. We aren't that state-of-the-art

-Original Message-
From: Steve Szabo [mailto:[EMAIL PROTECTED] 
Sent: 20 March 2008 11:12
To: MS-Exchange Admin Issues
Subject: RE: Outlook sending mails to junk folder with no junk filtering
enabled

Are you using IMF on your server? Messages within a certain SCL range
will
be put into the user's Junk E-Mail folder.

\\Steve// 


-Original Message-
From: Oliver Marshall [mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 20, 2008 6:41 AM
To: MS-Exchange Admin Issues
Subject: Outlook sending mails to junk folder with no junk filtering
enabled

We have a user here who is seeing some emails being sent to the junk
mail folder despite the junk filtering being disabled. 

I've removed all of his rules (not that he had that many anyway) and it
hasn't made a difference. I've recreated his profile (though not his
mailbox) and moved him to a new TS box but that hasn't helped either.

Any ideas why Outlook 2003 would adamantly think that it should filter
emails even with the filtering set to none ?

Olly

~ 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~

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


RE: E2k7 Unified Messaging and Avaya

2008-03-20 Thread Thomas Gonzalez
Our site, reviewed Avaya and we were not impressed by the features after
several test runs and going out to view businesses with the Avaya System
in place with Exchange 2k3 or 2k7. 

 

However, we went with the ESI with E2K3 and the unified messaging of ESI
works very well. We have not had any issues with the ESI unified
messaging. 

 

I have a lab with e2k7 without the ESI and have another one with ESI
Unified. Still conducting tests and having the lame to power users test.

 

T

 

 

From: Matt Moore [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, March 19, 2008 7:26 PM
To: MS-Exchange Admin Issues
Subject: RE: E2k7 Unified Messaging and Avaya

 

I had the Avaya connected to e2k3 via their software, IP Office.  To put
it mildly, it sucked.  If it wasn't users bitching for speakers to hear
their messages. I had it set to only go through the handset but then
it wouldn't delete the messages when you told it to.  About 6 patches
and upgrades later, I decided it wasn't going any further.  If you
allowed it to fully interact with outlook, it attaches a wav file to the
email it puts in the inbox.  Guess what happens when they don't get
deleted?  Look hard at the MS Unified.  I'll be embarking on a Mitel
voip system with e2k7 very soon.  

M

 



From: Matt Lathrum [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, March 19, 2008 2:01 PM
To: MS-Exchange Admin Issues
Subject: E2k7 Unified Messaging and Avaya

 

Does anyone on this list have E2k7 Unified Messaging with an Avaya
backbone?  Are you using Modular Messaging or Microsoft Unified
Messaging?  Our company is currently evaluating which path to take and
would love to hear lessons learned about either approach.

 

Matt

 

 

 

 

 




This email and any attached files are confidential and intended solely for the 
intended recipient(s). If you are not the named recipient you should not read, 
distribute, copy or alter this email. Any views or opinions expressed in this 
email are those of the author and do not represent those of the Girl Scouts of 
Southwest Texas company. Warning: Although precautions have been taken to make 
sure no viruses are present in this email, the company cannot accept 
responsibility for any loss or damage that arise from the use of this email or 
attachments.
~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~
~ http://www.sunbeltsoftware.com/Ninja~

RE: Outlook sending mails to junk folder with no junk filtering enabled

2008-03-20 Thread Steve Szabo
Are you using IMF on your server? Messages within a certain SCL range will
be put into the user's Junk E-Mail folder.

\\Steve// 


-Original Message-
From: Oliver Marshall [mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 20, 2008 6:41 AM
To: MS-Exchange Admin Issues
Subject: Outlook sending mails to junk folder with no junk filtering enabled

We have a user here who is seeing some emails being sent to the junk
mail folder despite the junk filtering being disabled. 

I've removed all of his rules (not that he had that many anyway) and it
hasn't made a difference. I've recreated his profile (though not his
mailbox) and moved him to a new TS box but that hasn't helped either.

Any ideas why Outlook 2003 would adamantly think that it should filter
emails even with the filtering set to none ?

Olly

~ 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~


RE: E2k7 Unified Messaging and Avaya

2008-03-20 Thread Davies,Matt
Matt,

 

We just made the decision to go Modular Messaging, although we are still
on Exchange 2003, we looked into UM a lot, but found that the feature
set is still very basic, compared to MM 3.1

 

With connection to the PBX with MM, you have the option for H.323 based
ip trunks or Qsig via E1 or T1 card in the server, both options work
well.

 

We currently have a number of networked Avaya S8xxx PBX's worldwide
running CM3  to CM 5, all using 2 Avaya MM systems ( 1 in the US and 1
in the UK) to be honest the installation experience really depends on
the person you get, I have seen a lot of people who do not understand MM
trying to install it failing, but if you get someone who knows what they
are doing, it makes a great difference.

 

If you want any further info, please feel free to contact me off list.

 

Cheers

 

Matt

 

 



Matt Davies

Director of International IT Operations

General Atlantic

83 Pall Mall

London

SW1Y 5ES

 

Tel: +44 207 484 3203

Fax: +44 207 484 2803

Mobile: +44 777 559 4265



 

 

 

 

 

 

From: Matt Lathrum [mailto:[EMAIL PROTECTED] 
Sent: 19 March 2008 21:01
To: MS-Exchange Admin Issues
Subject: E2k7 Unified Messaging and Avaya

 

Does anyone on this list have E2k7 Unified Messaging with an Avaya
backbone?  Are you using Modular Messaging or Microsoft Unified
Messaging?  Our company is currently evaluating which path to take and
would love to hear lessons learned about either approach.

 

Matt

 

 

 



_
This e-mail (including all attachments) is confidential and may be privileged. 
It is for the exclusive use of the addressee only. If you are not the 
addressee, 
you are hereby notified that any dissemination of this communication is 
strictly 
prohibited. If you have received this communication in error, please erase all 
copies of the message and its attachments and notify us immediately at 
[EMAIL PROTECTED] . Thank You.

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

RE: Exchange Management Shell killed the CDO star

2008-03-20 Thread Michael B. Smith
It's arguable as to whether the GUI was decent or not... and in larger
(where I define that as more than one hundred Exchange users!) environments,
the lack of an adequate scripting environment was a real problem.

Regards,

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


-Original Message-
From: Matteson, John H Jr USA Mr USA 25th SigBN (ITT)
[mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 20, 2008 1:01 AM
To: MS-Exchange Admin Issues
Subject: RE: Exchange Management Shell killed the CDO star

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 - 
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~


Outlook sending mails to junk folder with no junk filtering enabled

2008-03-20 Thread Oliver Marshall
We have a user here who is seeing some emails being sent to the junk
mail folder despite the junk filtering being disabled. 

I've removed all of his rules (not that he had that many anyway) and it
hasn't made a difference. I've recreated his profile (though not his
mailbox) and moved him to a new TS box but that hasn't helped either.

Any ideas why Outlook 2003 would adamantly think that it should filter
emails even with the filtering set to none ?

Olly

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