This looks like it is just a preferred server. If everything is synced from that core's "Packages" folder and is an exact match on this other server then specifying it as the preferred server for the subnet in question should do the trick. This you would do on the core, configure, preferred server.
I would give that a shot. We have 25 preferred servers in the environment and it works great. All packages and patches are set up on the core and robocopied to the preferred servers on a schedule basis. Every distribution package is specified as coming from the core. Devices download from their preferred server as specified by the subnet.
Thanks for your reply but this is not a preferred server, it is the main location for our packages.
The packages were located before on the core server itself, but we had to much performance issues with all the IIS applications, thats why I moved the main package contents to an other server. This means that the core server will not hold any software files anymore and that I have to replace the file path in all packages.
in a former LANDesk version (8.5?) I've changed the path entries in LD database table (but I fear this is not recommended by LANDesk :-))
I changed the path with the server name to a DNS-alias name...
Well, I just thought of it as a quick "out of the box" resolution to your issue. It would be a simple entry in the Core for the preferred server (assuming there is not a 'zillion' subnets). If you did this your newly appointed preferred server would become the new package server and then in the event that it was inaccessible, the core could be the back up for it, and you could continue to manage your packages at the core.