Background: I work at a college where we have roughly 4,600 PCs. Currently, they have the LANDesk agent 10.0.0.455 installed which reports to our LANDesk Core Server. The Core is running version LDMS 2016 (Base) Service Update 5. We also have another LANDesk Core set up on an individual server, and that's running LDMS 2016.3. That core has no agents deployed. The reason this Core was set up was because I inherited LANDesk back when it was 9.6 (which was just upgraded from 9.5), and we've had a number of irregularities with 9.6 and also 2016 (base) + SU 5. As a manner of trial & error, we decided it would be best if we just started fresh and install 2016.3 standalone; no upgrading. For the most part, it's ready to deploy (once I import my settings, packages, etc. from the current core). But the problem is that with 4,600 devices, it would be a daunting task to deploy 4,600 new agents, especially since I don't have the ability to wake up the thousands of machines I have at other campuses (Power Management has been an ongoing issue, and seems to be problematic across different subnets).
Talks in our department have discussed the future deployment of Windows 10 to all our machines, and they want us to abandon Windows Deployment Services in favor of LANDesk's Provisioning feature. I'm thinking that would be the ideal time to deploy the new 2016.3 agents! But then I'm struck with a conundrum: I don't think I can deploy a new agent that reports to a different core by using the LANDesk provisioning from the current core. For what it's worth, I'm very very rusty on my knowledge of Provisioning. I've signed up for LANDesk/Ivanti's remote course on Provisioning this week to re-learn the function. But if I were to understand it, the target machines need the LANDesk agent on them to use LANDesk Provisioning. If I were to capture & deploy the image on the new Core, I would need to have the target PCs already using the new Core's agent. If I were to capture & deploy the image using my current Core, then it would only include the agent from the Core I'm sending it from, right?
The Question: Is it possible to deploy an agent from a different core in a captured image that's deployed from a Core different than the bundled agent? Should I just deploy the new agent from the new core to 4,600 PCs before we start deploying Windows 10? The only reason I haven't so far is because I'm constantly using LDMS 2016 SU 5 for patching, package deployment, power management testing, etc.