New Exchange server feature scanning

[TurboGFF]

In the patch notes for the spring 2019 update, this is listed.
"Added: LAN-1822 Detailed information is now scanned from Microsoft Exchange Server: version, edition, users, groups, CALs, mailbox lists and sizes, ActiveSync devices etc"

I've updated to the spring release and rescanned my exchange servers and the only things I'm seeing is hostname and mailboxes. No version, edition, users groups, CALS, mailbox sizes, etc.

[t_doschke]

TurboGFF wrote:
In the patch notes for the spring 2019 update, this is listed.
"Added: LAN-1822 Detailed information is now scanned from Microsoft Exchange Server: version, edition, users, groups, CALs, mailbox lists and sizes, ActiveSync devices etc"

I've updated to the spring release and rescanned my exchange servers and the only things I'm seeing is hostname and mailboxes. No version, edition, users groups, CALS, mailbox sizes, etc.

hi, i installed the fall 2019 Edition lansweeper and having trouble with Exchange scanning.
i found that in the <lansweeper install directory>\Service is a Lansweeper.TestTool.App.exe

With that tool i tried to scan exchange and got Lansweeper.TestTools.Errorlog.txt Logfile errors using winrm port 5986.
Winrm port 5986 is winrm with https transport.
That ist not avail out of the box.

so i enabled it with admin cmd box:
winrm quickconfig -transport:https

and make a firewall allow rule for port 5986 on the exchange server.

since done that scanning exchange is possible.

these two websites helped me:
https://foxdeploy.com/2016/09/13/winrm-and-https-what-happens-when-certs-die/
https://www.darkoperator.com/blog/2015/3/24/bdvjiiw1ybzfdjulc5pprgpkm8os0b

and here is the tool to change cert on winrm https listener:
https://github.com/1RedOne/WinRM_CertMgmt

[Esben_D]

It's in the pipeline. You can always check what issues were resolved with the latest version here: https://www.lansweeper.com/changelog/

[jonathanbarton]

Is there any update on this?

[Esben_D]

Jon B wrote:
Is there any update on this?

We're trying to push the hotfix out ASAP. Hopefully this week, but I can't promise anything as these things can always change last minute.

The fix did not make it into version 7.1.100.12 and will most likely be included in the next hotfix.

[kim_kaberg]

Esben.D wrote:

Jon B wrote:
Is there any update on this?

We're trying to push the hotfix out ASAP. Hopefully this week, but I can't promise anything as these things can always change last minute.

The fix did not make it into version 7.1.100.12 and will most likely be included in the next hotfix.

Any update on this?

[Esben_D]

The issue has already been reported and a fix is in the works. It is planned to be included in the next hotfix which hopefully is out next week.

[keys_it]

We are running Exchange 2016 CU12. I have verified all requirements have been met and I have the same exact logs in my debug, I have opened a support ticket with Lansweeper support.

[sbAYVdQu]

keys_it wrote:
We are running Exchange 2016 CU12. I have verified all requirements have been met and I have the same exact logs in my debug, I have opened a support ticket with Lansweeper support.

Any updates on this?

[Esben_D]

sbAYVdQu wrote:

keys_it wrote:
We are running Exchange 2016 CU12. I have verified all requirements have been met and I have the same exact logs in my debug, I have opened a support ticket with Lansweeper support.

Any updates on this?

I'll try and get you an update tomorrow on this issue. I know for a fact there are bug fixes in the works for Exchange scanning.