Exchange Meeting Room Statistics

This script uses Exchange Web Services to connect to one or more meeting rooms and gather statistics regarding their usage between to specific dates.

 
 
 
 
 
(0)
149 times
Add to favorites
Exchange
5/18/2017
E-mail Twitter del.icio.us Digg Facebook
Sign in to ask a question


  • Does this work with Exchange Online?
    4 Posts | Last post June 14, 2017
    • I run the script as directed, but it returns nothing, not even an error.
    • Hi Tom,
      
      Did you use the -Verbose switch when running the script?
      
      Regards,
      Nuno
    • I don't think it works with Exchange Online, at least not with the way our autodiscover is configured.
      
      VERBOSE: Loading EWS Managed API
      VERBOSE: Loading module from path 'C:\Program Files\Microsoft\Exchange\Web
      Services\2.2\Microsoft.Exchange.WebServices.dll'.
      VERBOSE: Creating Exchange Service Object using AutoDiscover
      Exception calling "AutodiscoverUrl" with "1" argument(s): "Autodiscover blocked a potentially insecure redirection to
      https://autodiscover-s.outlook.com/autodiscover/autodiscover.xml. To allow Autodiscover to follow the redirection, use
      the AutodiscoverUrl(string, AutodiscoverRedirectionUrlValidationCallback) overload."
      At C:\Scripts\Get-MeetingRoomStats_EWS.ps1:86 char:2
      +     $service.AutodiscoverUrl($Mailbox)
      +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
          + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
          + FullyQualifiedErrorId : AutodiscoverLocalException
      
      VERBOSE: Error conneting to Exchange Web Services (no AutoDiscover URL). Exiting Script.
    • Hi Tom,
      
      Exchange Online works differently. Instead of using:
      $service.AutodiscoverUrl($Mailbox)
      
      Try manually specifying the URL for Exchange Online, such as:
      $service.Url = [System.URI] "https://autodiscover.outlook.com/ews/exchange.asmx"
      
      Please note that I haven't tested this script with Exchange Online!
      
      Regards,
      Nuno
  • Is it working with Exchange 2007 SP3 ?
    1 Posts | Last post May 29, 2017
    • Hi Nuno, 
      I thinks it is not working with Exchange 2007 SP3, It keeps showing this error:
      
      PS C:\> .\Get-MeetingRoomStats_EWS.ps1  -RoomListSMTP "conf_room@litwareinc.com" -From "05/01/2017" -To "05/29/2017" -V
      erbose
      Missing expression after unary operator '-'.
      At C:\Get-MeetingRoomStats_EWS.ps1:18 char:4
      +   -  <<<< You must use the room's SMTP address;
      
      Any idea ?
      Many thanks for you help.
  • Exchange 2007
    1 Posts | Last post May 29, 2017
    • Hi, thanks for posting the script. Is there any chance this could work with Exchange 2007 ?
  • Exchange 2007
    1 Posts | Last post May 29, 2017
    • Hi, thanks for posting the script. Is there any chance this could work with Exchange 2007 ?
  • How to report against O365
    2 Posts | Last post May 25, 2017
    • We are in a Hybrid environment.  When I ran this script I got errors because AutoDiscovery blocked a redirection attempt.  It seems AutoDiscovery is trying to direct from the local installation to the cloud.  Any ideas on how I can modify this to bypass this error?
    • Hi Mark,
      
      Instead of using:
      $service.AutodiscoverUrl($Mailbox)
      
      Try manually specifying the URL, such as:
      $service.Url = [System.URI] "https://mail.domain.com/ews/exchange.asmx"  
      
      Regards,
      Nuno
  • Will this work with Exchange 2016 CU3?
    3 Posts | Last post May 25, 2017
    • Nuno, it has this version in it (Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2013_SP1) will this work with Exchange 2016?
      
      Thanks and awesome script!!!! 
    • I ran a test this morning and left in the version Exchange2013_SP1. Ran it against my Exchange 2016 CU3 environment and it is working.
      
      Thanks again Nuno, this is an awesome script!!
    • Hi SSemanco,
      
      Yes, the script should work with Exchange 2010, 2013 and 2016. That variable only makes a difference in particular scenarios, but ideally you would want to set it to the correct version of Exchange you are using.
      Thank you for the feedback, glad it's useful!   :)
      
      Regards, Nuno