Servers.

What you are usually trying to solve

People cannot open the S drive. A new hire needs access and an old one still has it. The server is loud, old, or out of room. You are not sure the backup of that server has ever been opened. You want the server off the same flat network as the guest Wi-Fi.

What we do

• Windows Server file shares, and who is allowed to open which folder
• Linux servers: Ubuntu, Debian, Red Hat, Rocky, Alma, and SUSE. File shares Windows and Macs can open, users, updates, and the services the office actually runs
• A printer server on that box, Windows or Linux, so the queue is in one place
• Hyper-V when one physical server hosts the office systems
• Dell, HPE, Lenovo, Cisco, and Supermicro, including the out-of-band management on the box
• VMware as well as Hyper-V, and Synology or QNAP when the files live on a NAS
• A server VLAN, so the shares are not sitting on the guest lane
• A new server or a cutover, scoped as a project with a finish line
• The server included in the backup plan, tested with a restore

Backup of the server is not quietly included in Omega Total Care. It is set up on its own, and we prove a restore. Care covers the day-to-day. The copy you can bring back is the backup service.

Linux servers

A lot of offices already have one and do not call it a server. It holds the shares, the line-of-business app, or the printer queues. We administer it the same way we administer Windows Server: users, disk, updates, the backup, and who can reach it from the PCs and the Macs.