Never heard of this happening all by itself... Here is a doc that talks about the process of switching and automating it. I would say users are switching it.
Most of my users don't even know we have LanDesk, let alone, would know how to switch modes. And, even here in the help desk ,we have noticed computers that switched, and my colleagues say they did not switch
I just looked at my machine and noticed something interesting
I noticed that while in direct mode, i did not have the registry key value/name for Gateway mode
I switched to gateway mode, and then the key value/name showed up, and had the value of 1. I switched back to Direct mode, the key name stayed, and the value changed to .
But now my concern is why did I not have dword key to begin with, until i manually switched the mode.
Thanks for the pdf, I will read that over.
Ok, i followed the suggesstion in the pdf and everything seemed to work perfectly, except, when I switched one device to direct mode (At least via the regsitry key), it still connected via gateway mode. Does it have to do a vulscan operation before it changes over, and checks in?
Run C:\Program Files\LANDesk\LDClient\BrokerConfig.exe
Gateway Information Tab
Make sure Connect Using the Management Gateway is Not checked.
Restart the LANDesk Remote Control service after changing the key. The registry value is loaded when that service is started.
The Steps in the Doc for creating the Batch File include Net Stop and Net Start on the Service
Here's a script that will take care of it all, suitable for running as a Local Scheduler task at IP Address changes. http://www.droppedpackets.org/management-gateway-and-remote-control/folder.2007-10-25.8017126077/
We are having the same issue, machines setting themseleves back to Gateway mode. The script would work really well for our Laptop users, but we are having the issues with machines on the LAN reseting back to gateway mode, even after using the BrokerConfig tool to "Connect directly to LDMS core", and manually setting the workstations to LAN mode... odd...
1. Set Computer to direct mode.
2. Open the registry.
3. Browse to HKLM\System\CurrentControlSet\Services\issuser\ImagePath
4. Remove the /b from the Remote Control Service key.
5. Reboot computer and make sure it is still in direct mode.
This happens when the machine is in Gateway mode at the time that client is reinstalled. The new client will detect it and set it as the default connection. It will add a B to the registry key below. Forcing the system to switch to Gateway mode after every reboot
I have been seeing this happen more on my LAN connected PCs since going to SP3. I verified that there isn't a /b in the image path line. I have been using a task that pushes a key change to make gateway=0 and reset the remote control service. But I am still noticing a lot of computers being changed to gateway mode. Anyone have any other ideas how this can be happening?
From what I understand in SP3 the remote control automatically detects if it can contact the core. If it can, it sets itself in direct mode, if not, then it sets itself in Gateway mode.
I have had issues with wireless connections, since the remote control comes up before my clients get on the Wireless VPN. The I have people who can contact the core directly, but are in gateway mode anyway.