I'm coming back to this thread because we're now moving toward a virtualized environment and that includes my web and DNN servers.  I don't think I'll have trouble with DNN simply because we run a half dozen installs on this server with various development and test versions and two main sites.  I also don't run SQL on the box and SQL isn't (yet) scheduled for virtualization.

I have more of a concern about the virtual/physical RAM question with DNN.  Since my server licensing will allow me more servers virtualized than I currently have physically installed, I'll be splitting mail and non-DNN sites to their own virtual servers. I had not planned on adding physical RAM, the servers are maxed at 4GB now, and instead giving the VPS's virtual RAM that may or may not be an issue now.  I had figured that all the apps currently run fine on the server and the same apps will be on the three virtual servers, so I should be okay performance wise.  Does this sound good or should I spec out new hardware?

Also, it looks like we're going totally Microsoft for virtualization, should this concern me over using VMWare?

We're just starting the process and I have at least six months before the web servers get moved into a virtual environment, and I'll be doing a lot of testing first.  Any suggestions are welcome.

Thanks,

Jeff

Tony -

Thanks, I'll spec new hardware for this.  I also have a feeling that use of this server may expand, we currently have two in the DMZ for web access and the other is a vendor-required spec which doesn't allow virtualization, but that will likely change.

I'm going to go back to our other servers as well, I think we are looking at 8GB - 16GB on each hardware node, we may want to increase that.  After all, one of our goals is hardware reduction here and adding extra boxes to run more VM's defeats that purpose.  :)

Thanks,

Jeff