Three years later, you're still consulting for CNT Books. The network has more than 15 subnets and 10 routers in several buildings and locations. You have been keeping up with the network by configuring the routers statically. However, users have had problems with downtime in the past year because of network links going offline, as there's only one route to reach every subnet. The owner wants fault tolerance built into the network to include backup links in case a primary link goes offline. You're concerned that the current router configuration method will still cause some downtime, even if the backup links operate correctly. Why might there be downtime if a primary link goes offline but the backup link is okay? What can you do to reduce the possibility of downtime?
The explanation is shown in the answer section.
If you're responsible for technical support for a network of any size, in general, you'll probably find that you don't know how to make the best use of your time and are completely overwhelmed. One way to achieve this goal is to take on a job. Murphy's law makes sure that every computer is online at that moment. So what you need is to keep your station staff as simple as possible to minimize downtime in case of problems.
If you can reduce the users' downtime, you will receive less hateful emails from them and free time for most intermediate tasks. In this article, we will discuss techniques that you can use to reduce the length of time your workplace is running after a major intervention.
The easiest way to make sure that you can fix the crash is to do it on your computer. In short, each PC configuration should be as general as possible. All profiles, login scripts, files, and user accounts are stored on the server.