DJ_Anuz

I have been speaking with them. The solution is relatively simple it just requires writing office specific files to the installation folder rather than to the OS registry. I'm just exploring other options before telling the CEO that dev resources are the only way to accomplish this realistically.

It's something written by our devs. It's a bridge program that reaches out to a dental clients cloud database, requests their data, and then transforms the received data and sends it to our marketing server. I agree with you spotty, but our devs for whatever reason don't want to do it so I'm exploring whether or not it's possible to achieve this through virtualization. Technically speaking each instance runs the program for 8 different clients, so we're actually running about 1000 instances off of those 150+ VM's.

Hey all, I need to be able to run about 150 instances of a program, and there can only be 1 program installed per OS. The nice thing is that this program can run just fine on old dental servers that are running windows 2000. Because of this we need to build a server that can run about 150+ Instances of windows 10 dedicated to the sole purpose of running this 1 program from 11pm to 4 am MST. I'm familiar with hardware building and virtualization, but I've honestly never run into a use case like this so I was wondering if anyone would have advice on the most cost effective way to do this. The application itself is only about 20 mb, large so the biggest system drain is going to be the OS itself for each instance. The only requirement for the OS that needs to be used is that it runs .net 4.6 or higher. Thanks!