We're getting to the point in our environment where we have so many mobile users that trying to get a new agent configuration pushed out is impossible. We're constantly chasing down machines that don't have the most recent agent or the agent is damaged because the machine was turned off halfway through the install.
So this led me down the path of looking to use AD and login scripts to manage agent updates. As long as machines are on network (not worried about through the LDMG), I want to check if LANDesk is up to date and the agent is configured properly. Here's my goal, and I'm hoping there's some combination of WSCFG32 or the NTConfig kit (don't know if these are even viable anymore as of SP2) to get this done:
Step 1: Roll out standard naming convention agents (e.g. WORKSTATION, LAPTOP, SERVER, etc.)
Step 2: Prepare login script to run WSCFG32 at logon, user's have Admin rights to machines and read/execute rights to LDLOGON
Step 3: If Service Pack or agent update is applied to Core, or configuration is modified, rebuild agents and let WSCFG32 manage the update as users login, no more agent pushes
So far, WSCFG32 hasn't reacted the way I've read that it's supposed to. On a test machine I've installed my agent. I then went to the Core and modified the agent configuration but kept the name the same. The "Configured On" date is also newer for the agent. I ran WSCFG32 on the box and nothing happened.
Please keep in mind, I'm looking for a way to keep our existing agent base updated automatically. I know I can patch in SP2 and future service packs, but this doesn't accomodate for changes to the agent config. For instance, if I want to change the schedule for Inventory scans or policy updates, or change how the Desktop manager behaves, that's a new agent push. I want to automate the updating of these agents, not roll them out initially.
Thanks.