
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-24-2025
11:08 AM
- last edited on
‎03-14-2025
10:35 AM
by
Obi_1_Cinobi
Hi guys,
We're looking to upgrade to Windows 11 24H2 in the near future, however the first step in testing our deployment methods etc is upgrading to windows 10 22H2 using a feature update deployed via Windows Update.
Since upgrading our estate, we have noticed that Lansweeper is no longer able to scan these devices.
The asset page has the following
|
|
The account is the same as it is for 20H2, which scans fine. and the username/password is correct, I can interactively login to the device with the account and perform admin functions. I've tested RPC access and WMI etc and all seem to work with the account credentials however Lansweeper still can't scan them. I've looked into it and saw questions around DCOM Hardening. I tried the workaround for the DCOM hardening with the regedit, however the problem still persists.
The only differnce between old device and new device, is the feature update to 22H2. Any assistance is appreciated!
Thanks
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-24-2025 07:37 PM
Hi,
As of March of 2023 the bypass method does not work anymore. Make sure that all assets are ruining the same patch level I.E. scanning servers and the assets they are trying to scan.
More information can be found in the MS article https://techcommunity.microsoft.com/blog/windows-itpro-blog/dcom-authentication-hardening-what-you-n...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-24-2025 07:37 PM
Hi,
As of March of 2023 the bypass method does not work anymore. Make sure that all assets are ruining the same patch level I.E. scanning servers and the assets they are trying to scan.
More information can be found in the MS article https://techcommunity.microsoft.com/blog/windows-itpro-blog/dcom-authentication-hardening-what-you-n...

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-25-2025 12:50 PM
Yep, that's the one! Turns out WSUS hasn't been working for a while so I've fixed that and deployed the latest update to the Lansweeper server and it's now scanning the assets again! Thank you for pointing me in the right direction!
Cheers!
