Your Lansweeper scanning server must be configured to allow scripts that are signed by a trusted publisher.Your Lansweeper scanning server’s WinRM client configuration must have Basic authentication enabled.If you only just installed this PowerShell version, make sure to reboot your machine. Your Lansweeper scanning server must have PowerShell version 5.Your Lansweeper scanning server must have a 64-bit architecture.Your Lansweeper scanning server must be running Windows 7 or a more recent operating system.Your Lansweeper scanning server must be able to access the Internet to connect to your Office 365 environment.But we will get back to that later.īeside those there are requirements which should apply to on-prem scanning server: Account should have assigned permissions to use Exchange Online cmdlets.If you restrictions to view Azure AD by users you may need to exclude this scanning account from policy.Also this account cannot be included in MFA policy in your organization Azure AD account - which credentials will be used for scanning.Lansweeper 7.1 or above - I recommend installing the newest update which is 7.2 it was released on 7th of September.There are a few things you should do and check before implementing this feature. So it is nice to have it all in one console. Scanning is done using Powershell cmdlets and provides you with data of organizations, domains, users, admins, password enforcement settings, groups, licenses, mailbox lists, ActiveSync devices and more. Lansweeper is a great IT assets management tool! This new feature was introduced in version 7.1.

Lansweeper professional