Linux Thin Clients
I have many questions related to software in my head, maybe I can find answers to them with you.
- When an organization has a lot of PCs, the question arises about their management, i.e. fixing errors in software, installing additional software, getting rid of viruses, etc. One solution to these problems could be to buy server (s) and several terminals equal to the number of employees in the organization, plus some to replace in case of malfunctions or the arrival of new employees. In general, the number of terminals can be taken into account in the company's development strategy, as well as the percentage of equipment failure (global statistics?). The OS on these terminals is “loaded” through the network from the server (s), i.e. we come to centralized management of all equipment in the organization. This solution also allows you to solve, to some extent, the problem of protecting sensitive information: disconnect USB ports, lack of DVD burners,
Questions:- Is such a computer equipment management model viable? What are the pitfalls?
What server characteristics are important and what should they be?
How expensive is it compared to the common IT management model?
Who provides such solutions on the Kazakh or Russian market?
Where did you implement such a solution so that you can familiarize yourself and see in action?
What are the alternatives to good governance? Need to familiarize yourself with ITIL?
PS Question about the OS that will be used on the terminals and servers below.
Employees, as they fulfill their job responsibilities, need to install additional software, such as dictionaries, translators, graphic editors, etc. Sometimes you need to install the software one-time - worked a couple of days, and then demolished it. Given the Law on the Protection of Copyright and Related Rights, the issue of using licensed software is in the first place, after all, we are law-abiding citizens of our country or at least want to be them, firstly. Secondly, public procurement of the necessary software may take several months (say, thanks to the Law on Public Procurement). Of course, you can take a lot into account in the company's IT development strategy and purchase as planned. But MUCH is not all. Thirdly, writing a technical specification for public procurement of finished software can lead to that one of the bidders can provide alternative software with a lower price, not inferior to the software that was supposed to buy (say the second thanks to the Law on Public Procurement). This can lead to additional training costs for employees (again a time factor). Or somehow cheat with the "technical spec" so as not to contradict the Law on Civil Defense. I see a solution to these problems by using the Linux OS (Ubuntu, Mandriva, RedHat, SuSe, etc.) and open source software. But there are also many questions: I see a solution to these problems by using the Linux OS (Ubuntu, Mandriva, RedHat, SuSe, etc.) and open source software. But there are also many questions: I see a solution to these problems by using the Linux OS (Ubuntu, Mandriva, RedHat, SuSe, etc.) and open source software. But there are also many questions:- What about ready-made IPs and their “clients” developed under Windows?
How compatible are OpenOffice documents with MS Office? Will the company's customers be able to open and correct documents typed in OpenOffice or vice versa? By the way, IBM also offers its Symphony office program for free, though only it is still damp.
Who on the market offers technical support for OS and open source software?
And will all this "economy" with the open source GPL fit? All the same, the software will be used for profit.
These are the questions in my head that I myself am looking for answers to, but have not yet found. Maybe someone will explain everything to me clearly or throw a link to a FRESH article on the network, where there are answers so that there are fewer questions in my head. Although others may appear! THANKS!
- What about ready-made IPs and their “clients” developed under Windows?
- Is such a computer equipment management model viable? What are the pitfalls?