
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-16-2023 04:25 PM - last edited on ‎04-02-2024 10:28 AM by Mercedes_O
Hi
I have a problem with LsAgent. I have deployed LsAgent last year from intune on multiple devices. A few days ago I setup a new server for Lansweeper and after that, I changed the intune policy install command to point to the new server name but it is not updating the lsagent, it still listens to the old server name. How can I fix this?
Solved! Go to Solution.
- Labels:
-
General Discussion
-
Scanning
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-16-2023 07:01 PM
Take a look at this KB article and see if it helps. Impact of a Lansweeper migration on LsAgent scanning - Lansweeper Maintenance - Lansweeper Community
Scroll down to the section called "Migration impact when not using the relay server" -- it addresses the changes necessary to ensure LsAgent data can communicate. It might not be the exact scenario, but maybe it has helpful content.
Lansweeper Employee
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-16-2023 07:01 PM
Take a look at this KB article and see if it helps. Impact of a Lansweeper migration on LsAgent scanning - Lansweeper Maintenance - Lansweeper Community
Scroll down to the section called "Migration impact when not using the relay server" -- it addresses the changes necessary to ensure LsAgent data can communicate. It might not be the exact scenario, but maybe it has helpful content.
Lansweeper Employee
