09-11-2018 08:30 PM - edited 06-05-2024 09:12 AM
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.
In order for Lansweeper to scan Exchange Server information from your Windows computers, make sure that the following requirements are met.
Your client machine is running Exchange Server 2013 or higher and has .NET Framework 4.0 or higher installed. PowerShell scanning of older Exchange Server versions is not currently supported.
Scanning server and client machine are in the same domain.
PowerShell is enabled on the client machine as well as your scanning server.
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
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.
The Windows Remote Management service (WinRM) is running on the client machine.
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.
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.
If Exchange Server information fails to scan after you've double-checked the scanning requirements above, put your scanning server into debug mode:
Program Files (x86)\Lansweeper\Tools\ConfigEditor.exe
on the scanning server.
Configure the pop-up as shown below and click Add.
Open the ErrorLog file at Program Files (x86)\Lansweeper\Service\Errorlog.txt
on your scanning server and look for any errors related to the Exchange Server, which may provide more information on the failure.
When you've finished debugging, remove the LogExchangeScanning option from your appSettings again, to prevent unnecessary growth of your log file.
Was this post helpful? Select Yes or No below!
Did you have a similar issue and a different solution? Or did you not find the information you needed? Create a post in our Community Forum for your fellow IT Heroes!
More questions? Browse our Quick Tech Solutions.
Experience Lansweeper with your own data. Sign up now for a 14-day free trial.
Try NowExperience Lansweeper with your own data. Sign up now for a 14-day free trial.
Try Now