locked
Filtering get-logonstatistics for particular client of shared mailbox RRS feed

  • Question

  • Hi

    Am using Exchange 2007 SP2.

    I use the get-logonstatistics -identity <mailbox> | fl to get data on clients.

    We also have shared mailboxes that are used by 100's of people.

    If I had a client IP address of 192.168.13.4, does anyone know how I can get logonstatistics for that particular client logging onto shared mailbox Marketing?

    Saturday, March 5, 2011 6:44 PM

Answers

  • Get-LogonStatistics -Identity Marketing | where {$_.ClientIPAddress -like "192.168.13.4"}
    Jesper Bernle | Blog: http://xchangeserver.wordpress.com
    Sunday, March 6, 2011 4:56 PM

All replies

  • Get-LogonStatistics -Identity Marketing | where {$_.ClientIPAddress -like "192.168.13.4"}
    Jesper Bernle | Blog: http://xchangeserver.wordpress.com
    Sunday, March 6, 2011 4:56 PM
  • Hi Joe,

     

    Yes, you can use Powershell’s where-object cmdlet to further filter the results based on the properties returned by each cmdlet. For this issue, you can just use Jesper’s cmdlet to achieve the goal.

     

    Thanks,

     

    Evan

     

     


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Wednesday, March 9, 2011 5:15 AM
    Moderator
  • I am looking for the same solution but the command-let with the ip filter does not return any result. anybody know why?

    I was getting

    "Process Microsoft.Exchange.RpcClientAccess.Service.exe (PID=4952). User 'Sid~domain\user~RCA~false' has gone over budget '138' times for component 'RCA' within a one minute period. Info: 'Policy:DefaultThrottlingPolicy_dd2e0e86-5fbd-48b0-b408-fed11eba0ade, Parts:MaxConcurrency:137;'. Threshold value: '100'."

    It is a shared mailbox with some users using web-mail and others using outlook 2003. I looked at other shared mailboxes and they never go over budget. I want to run this command to determine which user is the culprit.

    Thursday, June 2, 2011 5:37 PM