Problem: A factory had a time clock system setup on 3 computers. Of the computers, one of them acted as the server and stored all the data. The employees could not clock in when the server computer went to sleep or was shut down.

Solution: I checked with the manufacturer that the program could run on an actual server without an issue, then remoted into the server and client computers to collect information about the existing setup and environment. Then, I installed the programs needed on the server and setup a client with it as a test. Everything looked stable so I moved on to migrate the database from the computer acting as the server for the Time Clock to the actual server. After doing so, I modified the 3 computers to point to the server. I also setup the Time Clock terminal to work over the network instead of plugging it directly into the computer that was acting as the server for the system. Everything went smoothly and migrated quickly.