Answer the question
In order to leave comments, you need to log in
How to organize IT infrastructure and 1c server in state institutions?
Good day friends!
I need some advice, please help.
Kazakhstani medical institutions are switching to IT. Now registration, receiving a sick card will all be through a web server. All relevant web services are ready and working in city hospitals. The director of the district hospital asked me to help normalize their Internet, connect 1c and show the accountants how to work.
That is, I need to solve two problems:
1. Normalizing the Internet
2. Setting up 1s.
The hospital has 7 telephone lines through which the Internet is connected. 7 Ordinary wi-fi routers distributing the Internet. But due to the fact that doctors downloaded the network from all possible devices, the website of doctors does not open on working computers. That is, due to the lack of control at the level of the router, their Internet is weak.
The solution of the first task and along the way the second thought to do this:
1. Install a powerful server, connect all computers to the asset directory.
2. Put 1c on this server, connect accountants
3. Remove all Wi-Fi routers, put uni-fi instead, put kerio on the server and control and distribute the Internet through it.
The main requirement of the customer: all software must be licensed.
Question:
1. Will it be so right?
2. With such an infrastructure, what kind of licenses will I need?
TK on the Internet
TK for 1s
Answer the question
In order to leave comments, you need to log in
1. No wifi in the working network, only wires. Since,
- Firstly, you are pumping personal data over the network, and getting into wi-fi and getting this data is a piece of cake.
- Secondly, WiFi has limited bandwidth, using it for 1C file databases is suicide, especially given the third:
-- Thirdly, the claimed 200 meters of coverage will easily turn into 10 meters of coverage when deployed inside a specific building. On the way, you can easily come across some poorly permeable things such as metal meshes (under plaster), thick reinforced concrete walls, various radiating equipment (X-ray machines, MRI, etc. medical equipment). Even an old flashing microwave in the staff room can create a lot of unforgettable adventures with "we have a bad signal here!", and the problem will be floating - someone is heating dinner, and the signal disappears. Warmed up - the signal appeared. Get tired of looking.
And even if in some places the signal level is more or less, then in the presence of powerful "phonites", packet drops will be such that your access from certain rooms will be very complicated or even impossible at all.
WiFi can be used if you really want to, but only for non-critical applications. Give visitors cats on the Internet to watch, for example.
Further - you will not find a pack of PCI-connectors in the "system unit" (I don't remember motherboards, where there would be more than 4 of them). Unless server mothers with raisers. But it is not necessary, from the word "absolutely". Your ADSL modems have a LAN, it makes no sense to plug them into a server directly, for this white people invented switches a long time ago. Given the speed of ADSL channels, a 100-megabyte one is enough for you. All modems into it, and the "external" network card of the gateway server - too. In total, you need only two network cards on the gateway - one to the local area, the second to the outside.
Kerio is a license. It is better to think towards a linukh or fri. In addition, I Unix can set up automatic traffic balancing on all your ADSL modems at the same time. Not sure if Kerio supports such scenarios. Failover-balancing is there,
Ah, well, yes. Instead of all this server, you can install a box from Mikrotik. Even hEX lite will cope with your loads, I think. Worth $40 ;-)
IMHO. There is no difference, state structure or not. The answer to what you ask is pulling on a decent project, so it costs money. You have two options:
It’s better not to connect the distribution of the Internet with the 1C server - 1c on your server (it can be virtual), the router on your server, and the domain controller on your server (it can be virtual). Domain controller - it depends on the number of computers - if more than 30, then it's better to set it (30 can also be configured with pens). If there is very little money, you can combine a domain controller with a 1C server.
If the work goes through the Web - Activ Directory, you need it as a fifth paw.
Kerio, by the way, too.
WiFi definitely should not be used to connect stationary computers.
Buy a simple server - with the most common components. He will distribute the Internet.
enough 2-network cards. One in an internal network, the second in intermediate to ADSL modems.
A normal managed switch (for the internal network), and a simple 8-port switch for connecting 7 ADSL modems. WiFi on which to disable physically. If you need guest WiFi - one more network card to the server -> POE switch -> several access points (the number depends on the architecture of the building)
For 1C, you can also buy a simple "server" with a mirror Ride, and you can programmatically place 1C-ku in a file version on a network ball. And another simple NAS for 1C data backup
If you master Linux, both servers can be deployed on this system. That will allow you not to buy software at all.
By the way, on Linux, the 1C server allows 10 clients to work "for free", and you can deploy 1C-ku in the SQL version.
But the most important thing is to connect everyone with wires, and block access to social networks and other entertainment on the routing server (or significantly limit the speed to them)
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question