This is how all anti-virus packages handle their definition updates.
Using Kaseya Patch Management to perform this function would introduce significant delays due to the patch approval process and the fact that automatic updates are typically run weekly.2) supporting the definition files could add a lot of extra effort by customers trying to use the patch approval process due to the potential volume of the definition files.
If you already have a Microsoft MSDN or Tech Net (paid) subscription, you can try Microsoft Forefront Client Security on your Windows Home Server, and it seems to work well. There are several, but none are really show-stoppers: 1) as always, you are responsible for following the EULA in your Microsoft Tech Net or MSDN subscription.
2) Microsoft does not list these Home Server variants in the Client Computer section of Microsoft Forefront Client Security.
Microsoft doesn't list Home Servers among the supported OSs here, so it seems likely that you are totally unsupported.
3) Microsoft does not list these Home Server variants in the Client Computer section of Microsoft Forefront Client Security 2010.
There are 2 reasons for this: 1) when MS delivers an updated definition file, it is imperative that the client get that update as soon as possible.
Unlike Microsoft Security Essentials, Forefront seems to have heuristics based scanning, although I’m not really sure how important that is.
Finding the installer was another matter, but I've documented it for you here.
It's buried in a client install MSI file dated from Oct 2007, deep inside the ISO file you download.
Historically this has been the case because Microsoft has not provided stand-alone installers for patches with this classification.
However, we are planning to incorporate Device Drivers as a supported type in a future release of the Kaseya product.