Here is the current version of the API (EWS 2.2):  
http://www.microsoft.com/en-us/download/details.aspx?id=42951

I probably wouldn't run that on a server, but off a workstation just to be 
safe.  I don't believe it walks across any Exchange DLLs though.  You will need 
the minimum .NET Framework version that the particular version of the EWS API 
supports, which you may not want to do on the server.  I just think of 
instances of people installing Outlook on an Exchange server and bad things 
happening due to the differing client/server MAPI DLLs...

Typically you can usually think of the version reference as the "minimum" 
version the EWS program/script supports.  There can be specific calls to 
objects/methods/properties within the API that only exist in the referenced 
version of Exchange or above.  So you can run an Exchange 2010_SP2 version of a 
.NET script/program with a newer version of Exchange, but not older.

-----Original Message-----
From: [email protected] [mailto:[email protected]] On 
Behalf Of Kurt Buff
Sent: Tuesday, December 9, 2014 2:33 PM
To: [email protected]
Subject: Re: [Exchange] Reporting on room bookings - Exchange 2010 SP3

OK - I think I figured part of this out. The article does state that I need to 
install the Exchange Managed API  - I just did a bit of googling and found this:
http://www.microsoft.com/en-us/download/details.aspx?id=35371

I'm not too sure about installing this on my servers - do any of you have 
thoughts on this, especially why I shouldn't do it?

Kurt

On Tue, Dec 9, 2014 at 12:24 PM, Kurt Buff <[email protected]> wrote:
> I've had a request to get some stats on US room bookings, as 
> management is thinking of turning some of the lesser-used rooms into 
> offices.
>
> After some searching, this is the only example that I found that looks 
> like it would give me what I want:
>  
> http://stackoverflow.com/questions/10921563/extract-the-report-of-room
> -calendar-from-exchage-server-using-powershell-scripti
>
> But this line baffles me, as I don't see anything like that path or 
> DLL on my systems - we have a CAS server and an HT/DB server in the US
> office:
>
> Add-Type -Path "C:\Program Files\Microsoft\Exchange\Web 
> Services\1.2\Microsoft.Exchange.WebServices.dll"
>
> Also, the script references Exchange2010 SP2, but as I stated above, 
> we're at SP3, so I don't know if I can just modify the line that 
> references that in the script.
>
> Can anyone point me to a script they've used for this?
>
> Kurt
>
>



Reply via email to