locked
Exchange 2007 API RRS feed

  • Question

  • We are going to write a MS Exchange 2007 provisioning system without HMC/MPS. The EWS doesn't seem suitable for this purpose but PowerShell is promising. We can use PowerShell to provision Exchange services. My question is, if there are more than one E2K7 then what programming technique is best for provisioning (assuming all E2K7 are in same datacenter).

    Pardon for my ignorance.
    Friday, August 24, 2007 11:04 AM

All replies

  • PowerShell is what you will want to use.

     

    Here is a little bit about provisioning: http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=590954&SiteID=17.

    If you want to run cmdlets from a C# application, this will get you started: http://msdn2.microsoft.com/en-us/library/bb332449.aspx

     

    Friday, August 24, 2007 3:58 PM
  • Thanks for your reply. I checked your mentioned post but it is not the answer I am looking for. I know about Powershell -- let me rephrase my question. Assume I have installed 4 E2k7 in 4 separate datacenters. From 5th Datacenter I want to run a script and provision exchange organization + SMTP accounts on choice of server. Is that something possible with Powershell? Can I call Powershell commands on remote servers?
    Monday, August 27, 2007 11:14 AM
  • Afaik as I know, that is possible, however you'll need to have the Exchange Management Tools installed where the powershell script will run.

     

    To have the EMT on the server, they have somewhat annoying pre-requisites (its like a normal exchange installation), but if your structure meets the requirements, then Powershell Automation and Exchange Snap-In, can remotely communicate with those remote Exchange Servers considering the communication ports (RPC and high ports) are open between endpoints.

     

    Hope it helps,

    Fernando Nunes

    Friday, August 31, 2007 1:47 PM