Thanks for this instresting info.
What I actually use to do myself is to first install the Centos 64 as a small and minimized as possible host operating system. Then I install wmware server on this as "the host".
On the host system I install Smoothwall as a virtual gateway software, and behind that, at a virtual lan segment I use to install 2 sme servers (server only) and 1 Windows 2000 Pro workstation.
The idea is to combine "the best fram some different wolds" in one installaion. The Smoothwall does the "firewall things", the one sme server is the "production server" and the other is the "testing server". Then the Windows 2000 is the "local windows client".
I also tried to run one extra virtual Asterisk server, but I ended up in using a Asterisk server running "inside" the sme server.
For connecting to "the machine" for remote control I use
www.logmein.com and the virtual Windows 2000 installation. Of course other "remote windows" alternatives can be used.
This installation using wmware smooththwall - sme server(s) - and windows 2000 har been running rock stable and more stable than the "sme server only" installations I used to use before.
(Reason: In the old days new software had to be tested on the "production server". Now all testing is done at "virtual server copies" that van be deleted after testing.)
I guess the idea of using a local Windows 2000 installation as the "local windows administrator" also can be used when wmware is running "under" the SME server, rather than "above it".
The reason tha I use Windows 2000 raher than the XP is just because i consume less ram as a virtual machine. Its more easy with licenses, updates, etc. A second hand Windows 2000 license might not be to expensive these days.
I run the virtual Smoothwall gateway, the 2 sme servers and the local Windows 2000 client on 4 Gig of RAM, but I guess that 2 GB could also be enough.
Just some ideas ..
17 Replies
3377 Views