[SOLVED] Building a server for office use

gotenks111

Honorable
Dec 30, 2017
15
0
10,510
Just wanted to get some advice,

I was looking to build a server for office use, there are about 8 staff who will need access to the server through remote desktop to use application and work on documents - remotely and/or while working at the office whatever the needs must.

If I use the following:

Ryzen 3700x
32gb ram (2x16)
SSD 2tb
any graphics
Gold rated PSU
Decent MB, possibly Tomahawk or something
Standard Cooling

possibly use windows server as OS unless advised otherwise - has to be windows based as per software that needs to be installed on to it, for staff to use for their job.

The server will be on 24/7 - i will also use a synology to back up the server every hour or so

will this suffice - or would I be better off buying a prebuilt Dell or something.

the purpose is to have all documents and software installed on the server so staff can use their own computers to remote desktop into the server using their own login credientials - do the work they need to do, and all files are saved on the server and backed up every hour onto the synology.

will this work?
is there better/cost effective way ?
thank you
 
Solution
Will need install software on server so that doesn't need to be installed on everyone's PC and staff can remote into server to use.

You said it's for 8 people, that is trivial to install the software on their systems. You may have the wrong ideas on how "remoting into servers" works. Remoting into a sever will give you one connection on it, what you need is a terminal server license for each person that connects to the server for virtual machines or setup something like Citrix to run the program in a virtual environment on the computers. It will cost you way more than just installing the software on the 8 computers and sharing the files off the server or a NAS. You will need an operating system license for the server, than...

USAFRet

Titan
Moderator
"building a server"

If "IT Guy" is not your full time position, don't do this.


Hosting documents on the server is fine.
Hosting all the applications is quite something else.
And saves you zero $$.

If you're using MS Office, for instance, you will still need a license for each person. And they will also need an actual "PC" to remote into this server.
You might as well reduce the complexity, and have Office installed on the client systems anyway.

What "applications" are you working with?
 

gotenks111

Honorable
Dec 30, 2017
15
0
10,510
"building a server"

If "IT Guy" is not your full time position, don't do this.


Hosting documents on the server is fine.
Hosting all the applications is quite something else.
And saves you zero $$.

If you're using MS Office, for instance, you will still need a license for each person. And they will also need an actual "PC" to remote into this server.
You might as well reduce the complexity, and have Office installed on the client systems anyway.

What "applications" are you working with?
Will be using accountancy software on the server so staff can access it through remote desktop
 

USAFRet

Titan
Moderator
Will be using accountancy software on the server so staff can access it through remote desktop
OK. And what are the hardware requirements for this?

Is there one single instance, used by multiple people at once, or a client/server type thing.

What software will they use to "remote into" whatever box is hosting this?

What else will be installed on the client systems?

I'm asking this stuff, because it looks like you are too focused on the 'server hardware', and have not yet laid out the actual requirements. Not to us out here, anyway.
 
  • Like
Reactions: Nemesia
I would never, ever spend time or money to build a server when you can get used Dell R710s for under $200 these days. Server hardware is a lot more than just specs and there is a quality and reliability with them that you will never get with consumer hardware.

If the program is single instance and everyone will only be using it in turn, then you don't even need windows server and can use any version of windows that supports rdp access. If it is a multi-user program, you will need to look into licensing and multi-user requirements as mentioned by others.

One of the most important things though that seems to have been overlooked is network security. I absolutely would not run an rdp server open to the world, and would only run this setup if you have ipsec tunnels that your clients will use to connect to the network. Then you can run the rdp as you normally would locally, except it goes over the tunnel so it is secure. This isn't a hard setup to put together, but will take some time to get it right.
 
Will need install software on server so that doesn't need to be installed on everyone's PC and staff can remote into server to use.

You said it's for 8 people, that is trivial to install the software on their systems. You may have the wrong ideas on how "remoting into servers" works. Remoting into a sever will give you one connection on it, what you need is a terminal server license for each person that connects to the server for virtual machines or setup something like Citrix to run the program in a virtual environment on the computers. It will cost you way more than just installing the software on the 8 computers and sharing the files off the server or a NAS. You will need an operating system license for the server, than a license for the remote users for terminal server, and a license on the computers you already have. Plus all the extra security for remote access to the server from the outside.

There are some programs that run off a sever installation where the main parts of the program are on another computer for central updates and there is a small setup file you run on the desktops to put in the shortcut to start the program and maybe a few local files for it. You would need to find out from the software vendor you use if their programs offer that. Not the same are creating remote logon sessions to a server.
 
  • Like
Reactions: Nemesia
Solution