A message for Linux.com registered users: We are in the process of making changes to the Linux forums. Starting Monday, 8/13/18 at 6:00 PM PT, you will be unable to access the forums. They will re-launch as soon as possible on Wednesday, 8/15/18 with new features and improved functionality. Thank you for your patience and stay tuned for the new improved forums.
Transition from Windows-based network to Linux-bas
I am looking to make the switch from a Windows based network to a Linux (preferably Ubuntu, because I used it the most) based one. Currently the network includes a Windows 2003 server which acts as a domain controller and file server, a network shared printer (Canon 2300N) and 7 clients running Windows. Several other Windows-based clients connect remotely via RDP.
I would like to setup a server to act as a domain controller, file server, and (if possible) terminal server. The clients should be authenticated via the server and have access to the files stored on it (via ssh?).
Here are several points that I was wondering about:
[li]All the clients use Outlook, some of the clients run Quickbooks Pro and another program called Tentant File Pro. I was thinking about replacing Outlook with Thunderbird (I contact, calendar, and tasks) and I know that Wine can't run Quickbooks and Tenant File Pro so I may have to use VirtualBox/VMWare because these applications can't be replaced by native Linux versions.[/li]
[li]I need an adequate backup solution for the files on the server running as a daily backup.[/li]
[li]Should I use webmin to administer the server?[/li]
[li]What antivirus / firewall solution should I use for the server and the clients?[/li]
[li]How can I allow remote clients the login to the server to be able to run applications (Outlook, Browser, Tenant File Pro, etc.) remotely on the server?[/li]
What is the best solution for this? And what would be the least painful way of making the transition for the users?
I know this is a lot, but any feedback would be appreciated.