Deploying OMSA from Essentials, and not having to manually choose the OMSA package

I'm reading through documentation on deploying OMSA to our physical machines, and it just says to download the package I need, and then I can set up a deployment task and choose the package.  What if there are different server models on an ip range - is there a way to just have Essentials deploy the OMSA that is appropriate for the particular machine?  Having to find out the machines models and then group them by that defeats a lot of the ease of deploying from a central location.

Thanks