Configure Agent Provisioning Action from preferred server

Hi All,

I have run into an issue where the agent install action will pull down from the core server rather than utlizing the preferred server. This isnt a workable solution for remote sites with low bandwidth links. Has anyone come across a good solution to this issue as you cant take advantage of any of the provisioning actions in system configuration without an agent installed on the client OS?

The options I can think of are

1. Put the agent in the image and remove the required registry keys
   
2. Have sysprep install the agent
   

Both would work but I am hoping there is a better / easiser way to resolve this.

Cheers,

Alex