Click to Rate and Give Feedback
TechNet
TechNet Library
Exchange Server
Technical Reference
Recipient Cmdlets
 Get-LogonStatistics: Exchange 2007 ...

  Switch on low bandwidth view
Collapse All/Expand All Collapse All
Get-LogonStatistics

Applies to: Exchange Server 2007 SP2, Exchange Server 2007 SP1 Topic Last Modified: 2007-06-28

Use the Get-LogonStatistics cmdlet to retrieve logon statistics, such as user name, logon time, last access time, client version, and adapter speed.


Get-LogonStatistics [-Identity <LogonableObjectIdParameter>] [-DomainController <Fqdn>]

Get-LogonStatistics -Database <DatabaseIdParameter> [-DomainController <Fqdn>]

Get-LogonStatistics -Server <ServerIdParameter> [-DomainController <Fqdn>]

Parameter Required Type Description

Database

Required

Microsoft.Exchange.Configuration.Tasks.DatabaseIdParameter

The Database parameter specifies the name of the mailbox database. When you specify a value for the Database parameter, the Exchange Management Shell returns logon statistics for all the mailboxes on the database specified.

You can use the following values:

  • Server\StorageGroup\Database
  • Server\Database
  • Database

This parameter accepts pipeline input from the Get-MailboxDatabase cmdlet.

Server

Required

Microsoft.Exchange.Configuration.Tasks.ServerIdParameter

The Server parameter specifies the server from which you want to obtain logon statistics. You can use one of the following values:

  • Fully qualified domain name (FQDN)
  • NetBIOS name

When you specify a value for the Server parameter, the command returns logon statistics for all the mailboxes on all the databases, including recovery databases, on the specified server. If you do not specify this parameter, the command returns logon statistics for the local server.

This parameter accepts pipeline input from the Get-ExchangeServer and Get-MailboxServer cmdlets.

DomainController

Optional

Microsoft.Exchange.Data.Fqdn

To specify the fully qualified domain name (FQDN) of the domain controller that retrieves data from the Active Directory directory service, include the DomainController parameter in the command.

Identity

Optional

Microsoft.Exchange.Configuration.Tasks.LogonableObjectIdParameter

The Identity parameter specifies a mailbox for which you want to obtain logon statistics. You can use one of the following values:

  • GUID
  • Distinguished name (DN)
  • Domain\Account
  • User principal name (UPN)
  • Legacy Exchange DN
  • SmtpAddress
  • Alias

This parameter accepts pipeline input from the Get-Mailbox cmdlet.

The Get-LogonStatistics cmdlet retrieves logon information about sessions that are currently active.

Bb124415.note(en-us,EXCHG.80).gifNote:
Users who log on to their mailboxes using Microsoft Outlook Web Access are not continually connected to the Mailbox server. An Outlook Web Access client connects to the server, performs tasks, and then disconnects. Therefore, you may see very few or even no logon statistics for Outlook Web Access, even if users are logged on with this client.

To run the Get-LogonStatistics cmdlet, the account you use must be delegated the following:

  • Exchange View-Only Administrator role

For more information about permissions, delegating roles, and the rights that are required to administer Exchange Server 2007, see Permission Considerations.

On Mailbox servers only, you can use the Get-LogonStatistics cmdlet without parameters. In this case, the cmdlet will return the logon statistics for all mailboxes on all databases on the local server.

Error Description

 

Exceptions Description

 

In this example, the Get-LogonStatistics command is used to return logon statistics for all users who are connected to the server named Server01.

Get-LogonStatistics -Server Server01
Tags What's this?: Add a tag
Community Content   What is Community Content?
Add new content RSS  Annotations
get-logonstatistics - why isn't this in the GUI, where it belongs in a Microsoft product???      lachlan mcintosh ... Thomas Lee   |   Edit   |   Show History

For god sake guy, what were you thinking??


If we wanted command line tools with badly formatted output we would be using Linux based products. At least Linux has grep and less.


Having to grub around to find and then use a command line tool, with the obviously poor quality control like this one, just makes administrators hate your products.


Gives us something for our software assurance, other than a bad head ache and a jump back to 1980's.




Lachlan McIntosh

http://www.directions.com.au

PS. I like men.


Tags What's this?: rant (x) Add a tag
Flag as ContentBug
Processing
© 2009 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks | Privacy Statement
Page view tracker