Quantcast
Channel: LANDESK User Community: Message List - Update agent settings via a Policy
Browsing latest articles
Browse All 15 View Live

Update agent settings via a Policy

Hi All LDMS 9.0 We have many machines that communicate to the Core Server only over the Management Gateway, these computers will never be on the network. I want to update some of the agent settings for...

View Article


Re: Update agent settings via a Policy

Cameron, The answer to this question is as follows: "You can only get to them with a policy, and you can't schedule an update as a policy. You can schedule a script as a policy, so if the change is...

View Article


Re: Update agent settings via a Policy

This answer is...not satisfactory. Redeploying our 33MB agent sounds way less enticing than deploying some text-file-equivalent settings. Feature request!

View Article

Re: Update agent settings via a Policy

I am in the same boat, I just have to try and pull a 150Meg Agent through the Gateway. Would really love a script or exe that would reach from client through  the Gateway and grab a new config file. As...

View Article

Re: Update agent settings via a Policy

I'll third this as a feature request.

View Article


Re: Update agent settings via a Policy

Any update on this issue?  I need to change the netbios name of my core in the agent to the FQDN of my core to resolve an issue with the client machines flipping to gateway mode while on the internal...

View Article

Re: Update agent settings via a Policy

Looking for the same thing. Any update on this. Would like to push agent update via policy and not redoply full agent.

View Article

Image may be NSFW.
Clik here to view.

Re: Update agent settings via a Policy

Hi, I know this is an old thread but hopefully that will work in my favor.  Is there a better way to update disconnected devices yet?  It’s been over 4 years since this post and hopefully LANDesk has...

View Article

Browsing latest articles
Browse All 15 View Live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>