Chris TI highly doubt a vitalized server would void the support since usually what most companies mean by “dedicated” is only run just programs needed for their software, ie SQL and Kaseya on the server, but not Exchange, a domain controller, or some other server type software since it could interfer with Kaseya. Also, in some cases a virtualized server might not be able to handle the load of a large amount of agents since the Kaseya server and SQL server can have a large resource foot print. Right now the only time I use virtualization in house is for test servers.
The only way sure way to find out is to contact support.
Hans den Boerwe are running our live K2 on hyper V now for 4 months with approx 500 agents.
No problem with K server or support. We have assigned 10GB of mem to K2 server and 4 server cores. Running W2008 X64, IIS7 and SQL2008X64
email@example.comSphere is a winner for us. The host is very lightweight in terms of resources and requires very little (if any) upkeep. The console is also very polished and feature rich.
One reason to go with a different platform might be compatibility (AFAIK) as ESX has its own HW compatibility list that needs to be thoroughly checked before making the decision to move forward.
ReedMikelHmmm, I never heard of vSphere - then again I'm a total newbie to virtualization I Googled vSphere and it looks to be a VMware product (so is ESX). What are the differences between the VMware's ESX and VSphere products? Last I heard, ESX was free (unless you need some of the enterprise add-ons). Is VSphere free? If not, any idea about what is costs?
Interestingly, when I searched these Kaseya forums, this was the only thread that mentioned vSphere. So I guess you might be one of very few people using it with Kaseya?
josh.tippingThe following link from VMWare will give you an idea of the differences!
ESX vs ESXi