...
- 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. |
Other Solutions
- You can configure the LANDesk Remote Control Service to “Automatic (Delayed Start)”
- This was suggested by LANDesk for computers that take a long time to initialize the network.
- Disable Gateway on LANDesk Agents that you know don't need Gateway Mode by changing .0 file
- To change the .0 you need to copy the .0 from the core under LANDesk/Shared Files/cbaroot/certs directory.
- On existing .0 file, remove last two lines referring to BrokerIP and BrokerHost.
- That one will not have the gateway information in it. (open it up to be sure it doesn't)
- Then you can replace the .0 on the clients with this one and it will not switch to gateway mode.
- To change the .0 you need to copy the .0 from the core under LANDesk/Shared Files/cbaroot/certs directory.