Scanning Exchange Server mailboxes

Exchange Server scanning was introduced in Lansweeper 7.0 and significantly expanded in Lansweeper 7.1. If you are using an older Lansweeper release, you will need to update by following the instructions in this knowledge base article.
Not all Lansweeper licenses support Exchange Server scanning. If your particular license does not support this feature, please visit this page for more information.

From version 7.0 onward, Lansweeper can scan mailbox information of Exchange servers, by running PowerShell commands locally on the Exchange Server. Exchange scanning was expanded and reworked in Lansweeper 7.1 and is now enabled by default. Kerberos authentication is used for the PowerShell connection.

Once scanned, the Exchange data can be found in the Exchange tab of the server's Lansweeper webpage. Built-in reports and dashboard widgets are available as well. Scanned Exchange Server data includes version, edition, users, groups, CALs, mailbox lists and sizes, ActiveSync devices and more.

scanned Exchange Server data
Exchange Server reports
Exchange Server widgets

Scanning Exchange Server mailboxes

In order for Lansweeper to scan Exchange Server information from your Windows computers, make sure that:

  1. The EXCHANGE item is checked under Scanning\Scanned Item Interval in the web console. From Lansweeper 7.1 onward, this item is checked by default.
  2. Your client machine is running Exchange Server 2013 or higher. PowerShell scanning of older Exchange Server versions is not currently supported.
  3. Scanning server and client machine are in the same domain.
  4. PowerShell is enabled on the client machine as well as your scanning server.
  5. The client machine is configured to allow scripts that are signed by a trusted publisher. This can be done by running the below command in PowerShell on the client machine.
    Set-ExecutionPolicy RemoteSigned
  6. The Exchange PowerShell snap-in is enabled on the client machine. Lansweeper automatically tries to enable it. The snap-in is required as this allows Lansweeper to use a single session for data retrieval, even if more PowerShell data is added in the future.
  7. The Windows Remote Management service (WinRM) is running on the client machine.
    Windows Remote Management service
  8. A software whose name includes "Microsoft Exchange Server" is installed on the client machine and listed in the Software tab of the machine's Lansweeper webpage. If the software was successfully scanned by Lansweeper, Exchange scanning will also be performed.
    Microsoft Exchange Server software
  9. The client machine's FQDN has been successfully scanned or manually added to the asset in Lansweeper. For Exchange Server scanning, a connection is made to the computer's FQDN.
    Windows computer FQDN
  10. The client machine's FQDN correctly resolves to the computer's IP address from your Lansweeper scanning server. This can be verified by performing a ping request from the Lansweeper server to the client machine's FQDN.
    pinging an FQDN from Command Prompt
    Keep in mind that the online status indicator you see below the client machine's name in Lansweeper is based on a ping request performed from your web server to the computer's NetBIOS name. This status indicator therefore cannot be used as an indication of successful FQDN resolution.
  11. A domain administrator is submitted and mapped as a credential to the client machine. More info on submitting and mapping credentials can be found in this knowledge base article. Whereas normal Windows computer scanning can be done with either a domain or local credential, Exchange Server scanning requires a domain credential. Specifically, this credential must be a domain administrator.
  12. The client machine has been submitted for scanning in the Scanning\Scanning Targets section of the web console. More info on how to scan a Windows computer can be found in this knowledge base article. Exchange Server scanning is currently only supported for agentless scanning methods.

Debugging Exchange Server scanning

If Exchange Server information fails to scan after you've double-checked the scanning requirements above, put your scanning server into debug mode:

  1. Stop the Lansweeper Server service in Windows Services on the scanning server you'd like to put into debug mode.
    stopping the Lansweeper service
  2. Run the following tool found on the scanning server:
    Program Files (x86)\Lansweeper\Tools\ConfigEditor.exe
    opening ConfigEditor
  3. Hit the Add button under appSettings
  4. Configure the popup as shown below and hit Add.
    debugging Exchange Server scanning
  5. Hit the Save button below your appSettings.
    saving settings in ConfigEditor
  6. Restart the Lansweeper Server service on your scanning server.
    starting the Lansweeper service
  7. Hit Rescan Asset on the left side of the problem client machine's Lansweeper webpage and wait for the Last Seen or Last Tried date listed on the page to update.
  8. Open the following file on your scanning server and look for any errors related to the Exchange Server, which may provide more information on the failure:
    Program Files (x86)\Lansweeper\Service\Errorlog.txt
  9. When you've finished debugging, remove the LogExchangeScanning option from your appSettings again, to prevent unnecessary growth of your log file.

Related Articles