...
- In some cases where the network connection takes too long to initialize after a reboot, the Landesk agent will switch to gateway mode since the agent cannot communicate with the Landesk core.
- Workarounds: instruct the user to change it back to direct mode, change the IP of the computer (which forces the agent to check again for connectivity)
- This is a known bug in the LANDesk. There is currrently no patch available for fix. There is an open case with LANDesk (Case 00579289)
Info When a LANDesk agent starts, if it can't reach the core, it will automatically switch to gateway mode.
What triggers the switch back at that point is an IP change.
If for some reason the client is not able to reach the core initially, say they are required to log into a proxy, or something else is needed to be done to start the network, or even if it is slow to initialize its possible that on initial bootup the client is not able to reach the core.
Then after everything is initiated it can then reach the core, but the IP has not changed to trigger the switch back that could cause the issue.