We just create a self-contained agent installation package, place it on the package server, create a package for it and deploy it that way. More steps, but less to replicate.
That's what I've been doing now but I'd like to eliminate the need to have so many packages, one per site at the moment.
But it would be nice not to need to build the install package at a..
You can't use the schedule agent deployment option. It is designed for a pure push using RPC or the LANDesk common base agent and knows nothing about preferred servers (by design as for that to work software distribution would need to be there and that might be what you are trying to push.
So you would need to either use a self-contained exe and put that in a replicated share with an associated distribution package configured or you create an advance agent msi and make sure you have the location it is configured with also replicated on your preferred servers.
With the advance agent, you can push an agent deployment but the MSI itself will always come from the core as it takes the default view that the target might not be a managed device already. With the software distribution package the target is assumed to have the software distribution component so preferred/peer etc. are immediately made use of.
Hope this helps.
MarXtar Ltd/MarXtar Corporation
LANDesk Expert Solution Provider
The One-Stop Shop for LANDesk Enhancements
Update - New Stand-Alone State Notifier Console for Service Desk Operators
Update - State Notifier now detects machine and user Idle states
Update - WoW & State Notifier now integrate for even more functionality