I deploy out the ClamWin.conf and ScheduleScans files out to several computers. However, at the time of deployment, I am unable to push it to the user's Application Data\.clamwin directory. Therefore, once ClamWin is installed, it appears I lack any ability to push out a new config file - is this correct, or is there a way to get ClamWin to reset its config file?

Is there a way to trigger the program to automatically reset the user specific config file form the user specified one?

try deleting the file, at the first run clamwin will re-create it

Sadly, my package deployment system won't let me in an easy manner. Anyway to run Clamscan so it is forced to reload the config file?

you can directly use clamav executables for batch scripting
there are some posts about it in this forum

That seems to be the only good way to use ClamWin in a deployed environment - I wish there was a way to get ClamWin either to use a centralized setting file or to tell it to overwrite the per user file.