If the SP3 update which added automatic gateway switching is giving you problems such as switching the device from LAN to Gateway and it should not, please go look at the following ER. http://community.landesk.com/support/ideas/2705#comment-16282
Ever since SP3, devices on my LAN like PCs are switching to gateway mode for some odd reason that I have yet to have discovered why it can't see the core. But when I manually switch them back to LAN, they will stay there for many. But some will switch back to Gateway mode automatically eventually.
This is not an issue of the agent being already set into gateway mode when the agent is updated and the /b on the issuser.exe service. It seems as if it is the new functionality.
So if this is bugging you, please vote on the ER for a change in this feature that does something like:
I have seen this as well and for me its mostly with my wireless VPN users. They are wireless and the connection takes a few moments as the profile loads, so the agent can't see a connection right away and and moves it into Gateway mode, when a short time later the wireless is up and then they can see the core. I just think they need a delay on the auto-switch.
At my company we are experiencing the same issue since SP3 update. We have been reinstalling the client remotely with a Task job or on the phone talk the user through switching it back to direct mode, but we need to prevent the LANDesk clients from switching automatically to gateway mode. I’m not sure what an ER is but I will vote for it if someone would guide me to the correct web page as the link provided didn’t find the page. Or if anyone knows how to fix this please post it. Thanks.
Was the automatic gateway bug fixed in LANDesk 9.0 SP3 in any recent Component Patches? I getting ready to deploy a new LANDesk Cloud Services appliance but I am concerned about the automatic gateway switching not working properly.
Are most people experiencing this issue?
Has anyone using Windows 7 tried setting the Remote Control service to "Automatic (Delayed Start)" and noted any difference? In theory this may resolve the issue.
we are using the delayed start option in windows 7 and this seems to have made a huge difference in the number of clients that are on the LAN but in gateway mode.
we found that there was another service interferring with the remote control service reaching the core during startup.
Just out of curiosity, what was the other service that was causing problems?
Is there a way to deploy with this already delayed start or is the only way to deploy it as a registry change in a scheduled task?
sorry, just seeing these replies...
@Jason, I'm not sure exactly what was determined to be the offending service. my supervisor was on the phone iwht Microsoft and LANDesk trying to figure this out for quite awhile.
@Jabramson, that I know of, there is not a way to deploy it this way. that said, if you are on windows 7 and using AD, you can set a group policy to change the service to delayed startup. there is no such setting for XP and it was recomended to me to add a service dependency to the remote service for something that starts up late in the boot sequence. we used the print spooler. that, unfortuenately, had to be pushed manually.
Jabramson - you have two options to enable delayed start via Advanced Edit for agent.
You can insert either:
EXEC70=C:\Windows\System32\sc.exe, config IISUSER start= delayed-auto", INSTALLONLY
REG70=HKEY_LOCAL_MACHINE, SYSTEM\CurrentControlSet\services\ISSUSER\DelayedAutostart, 1, , DWORD
Likely just after: "EXEC2=vulscan.exe /changesettingsnoreport, INSTALLONLY"
And just before: ";**** Begin of Data Collection Forms component ****"
For additional details on how to update Advanced edit for agents see: http://community.landesk.com/support/docs/DOC-1888
Best of luck - let me know if that does not work like you were expecting.