Title: RE: [ActiveDir] SpyWare
Personally haven't seen a CLI that provisions Exchange objects. 
 
Two issues come to mind with CLI and Exchange
CDOEXM is more difficult to work with than it should be and very limited - whatever.
Resource levelling is a difficult thing to accomplish without the MPS DLL's available.  I *heard* there were some levelling DLL's somewhere, but haven't seen where that's confirmed.  If you can't find such a thing, I'd prefer some DLL's that do this to a CLI to create mailboxes. 
 
Scripting mailbox creation is done to death on the web.  Removal is not. Levelling is unknown (to me anyway) outside of commercial provisioning apps.
Can't think why I'd want to mailenable a pre-existing group via CLI. 
Moving is something I can script pretty easily, but it might be nice to have that in CLI in addition to levelling logic.  Would make cobbling a home-grown lifecycle management app much easier for many out there.
 
Al
 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of joe
Sent: Friday, July 30, 2004 2:09 AM
To: [EMAIL PROTECTED]
Subject: [ActiveDir] [OT] CLI CreateMailBox/MailEnable/Clear Exch Attr Tool

Sorry guys and gals, completely off topic and also sorry for being AWOL lately. Trying to finish up a little project and don't like the outcome on one point.
 
Question is, is there a well known good command line tool for
 
1. Creating Mailboxes for prexisting users?
2. MailEnabling pre-existing groups/contacts?
3. Clearing Exchange Attribs on any Exchange enabled domain partition object
4. Moving mailboxes
 
When I say CLI/Command Line, I don't mean someone wrote a script, I am talking about an actual executable. Preferably something that takes some of the sting out the parameter list that needs to be sent in and can take multiple objects at once.
 
I haven't been able to find anything and several people that I have asked have looked at me strangely like I had drool on my lip or something... Command Line... Exchange...
 
If not, I am going to write the darn thing today. I will even be nice and write the initial version to actually uses the CDOEXM calls though the goal in the end would be to not use CDOEXM so I wouldn't be stuck to only running the tools on machines that have the Exchange Tools loaded and you could manage cross forest with it. The single forest management method results from laziness. No reason a machine should have to be in the forest that the mailbox work is being done in.
 
Anyway, let me know.
 
  thanks, joe
 
 
 

Reply via email to