11:35 Hide terminal server budgetary decision | |
| Basically, in our company all the jobs were based on thin client HP t5530. The exceptions were a few jobs with special needs (exotic hardware or software) and a few laptops of key employees. The total number of jobs was approximately 120 units. All this is served by two terminal servers (Windows 2003 Ent), an Active Directory server and one faylohranilische. Internet access - a server with FreeBSD. Workloads standard - IE (access to remote online database), TheBat with mail in large quantities, MS Office (Word / Excel), 1C. Unfortunately, all software, with very few exceptions, it was on one reason or another unlicensed. And, of course, contained a fairly large amount of information that was not supposed to go to specific organs. At some point the command was given the task - to take some measures in the event of unforeseen and not visit certain individuals. Time was given to a minimum, funding was not granted at all. After a brief brainstorming session was born the following idea: From what was found in the server was assembled otnosilno good terminal server, which, theoretically, able to withstand the input of all users. Of course, the work they're not likely to be able to. On this server placed a copy of Active Directory user accounts, a large number of white documentation ponastavili software and all kinds of simulated that all the work going on it. These servers have been cleaned away. In the same building, but where there are no search would not. The server was just a fake server, PBX and all network equipment. Thin clients and a fake server were removed to a separate subnet, say 192.168.1.1/24 (A). All these servers are located in the subnet 192.168.0.1/24 (B). At FreeBSD raised virtual interfaces on the subnet A on the number of terminal servers. In normal operation, thin clients are treated by the IP address of virtual interface, where they are forwarded to the real server in subnet B. In the event of hours X - turn forwarding on all interfaces on a fake server in the IP subnet A. Users have been instructed accordingly, that if the interrupted communication with the terminal, and after her recovery they see a picture - so be necessary, you must remain calm, to simulate the work and not to breed panic and cries of "why things are not working." The whole system worked in manual mode - that is, all the manipulations were carried out by executing a script manager on duty. Over time, the plans were implemented automatic mode, by crossing to the existing warning system for the office visit (radio stick with the secretary and visual alarm in the right cabinet). In general, the system was: a) a very low cost, and b) does not require a long recovery time after the guests leave. | |
|
| |
| Total comments: 0 | |