Very small office benefit from Windows Server 2022?

[ArtieJ]

I'm not much of an IT guy, just helping out where I work.
My experience includes setting up a WAMP package on a computer running Windows 7 about 15 years ago.
It seemed to impress everyone here, we still use it daily. They come running to me for this kind of thing, even though it's not my specialty.
Dammit Jim, I'm an electronics tech, not a computer specialist!

So, there are 2 people in an office that will need to use a couple of programs on a computer.
Open the program, do the work and save the files, optionally on their local computer or the server computer.
Both people need to access both programs but not at the same time.
However they may need to each access one program (person 1 on program 1 and person 2 on program 2) at the same time.

Can this be done with the 2 programs installed on a computer with Windows Server Standard and user accounts for the 2 people, and they use Remote Desktop Protocol to access that computer?

Am I way off base? Is there a better way?
I presume there's more than one way to do this and I've never treaded here before.
Thanks for any info or suggestions.

 

[ChatGPT]

Hello, ArtieJ! First off, your “Dammit Jim, I’m an electronics tech, not a computer specialist!” line made my day! It sounds like you're doing great stepping up to handle tech issues that might not be in your wheelhouse—props to you for tackling this!
Now, let’s dive into your scenario. The short answer is yes, your concept is doable with Windows Server 2022 and Remote Desktop Protocol (RDP), but there are some details and considerations to sort out.

Can it Be Done?​

Yes, Windows Server 2022 can absolutely handle the setup you described. By installing the two programs on the server and allowing both users to access them remotely via RDP, they can:

• Run the programs.
• Work on their files.
• Save files either locally (on their local devices) or directly to the server.

Each user will have their own unique session via RDP, which means User 1 won’t interfere with User 2 even if they’re both working at the same time—provided they’re accessing separate programs during concurrent use.

Requirements and Steps​

1. Windows Server 2022 Essentials or Standard
   • Essentials might be sufficient for your scenario since it’s targeted at small businesses and supports up to 25 users (or devices), but double-check feature compatibility with your programs.
   • You might prefer Standard if you want more flexibility and features.
2. Remote Desktop Services (RDS) Licensing
   • By default, Windows Server allows two concurrent RDP sessions for administrative purposes. If you want both users to use it as regular user accounts, you’ll need to enable RDS.
   • For RDS, you’ll need CALs (Client Access Licenses). In your case, you’ll need two User CALs.
3. Program Licensing
   • Some commercial programs have restrictions on installing and running over RDS. Carefully verify the EULA (End User License Agreement) of the software to ensure compliance. If they’re proprietary in-house or freely licensed, you’re good to go.
4. Server Hardware
   • Make sure the server has enough muscle for concurrent sessions. Two lightweight programs shouldn’t be a big issue unless they’re resource-intensive (e.g., heavy database or graphic-rendering software).
   • Basic specs: A decent processor like an Intel Xeon, 16GB of RAM, and SSDs for fast access should suffice for your use case.
5. Network Setup
   • Your network needs a solid connection to avoid lag over RDP. Gigabit Ethernet (or at least a reliable LAN setup) works great for small offices.
6. Remote Desktop Security
   • Ensure that RDP access is secured:
     • Enable NLA (Network Level Authentication).
     • Use strong passwords for user accounts.
     • Avoid exposing RDP to the public internet unless protected by a VPN or similar solution.

Is There a Better Way?​

• Shared Network Drive
  If remote work isn’t absolutely necessary (i.e., both users can sit in the office), you might save some complexity by simply setting up that computer as a file server with shared folders. Both users can map the shared drive and run the programs locally on their individual PCs while saving documents on the server.
  • This avoids the need for RDP and RDS CALs but requires the programs to be installed on both local machines.
  • Downside: Programs with server-hosting requirements won’t work this way.
• Cloud Options
  Depending on the specific programs, you might consider cloud-hosted alternatives:
  • Services like Microsoft 365 (OneDrive/SharePoint) or Google Workspace for file sharing, collaboration, and remote access.
  • Cloud-hosted software options if program replacements are viable.
• Virtual Desktop Infrastructure (VDI)
  If you envision growth or scalability beyond these 2 users, a VDI setup on Windows Server Standard might be overkill right now but highly efficient in the long run. This allows thin clients or low-powered devices to interact with virtual machines hosted on the server.

Pros and Cons of Your Current Approach​

Pros:​

• Centralized control: Everything is on the server.
• No need for powerful local workstations: Users just need decent devices capable of RDP.
• Flexibility: Users can access the programs from essentially anywhere if the setup allows for external connections.

Cons:​

• Potential licensing complexities for both server and software.
• Hardware-dependent: The server must be consistently reliable to prevent downtime for both users.
• More setup work required.

Key Questions​

To determine the best option for your office:

1. Are the programs compatible with being run on a server environment (like RDS)?
2. Are there software licensing restrictions for server-based usage?
3. Is accessing files locally on the user’s PCs a firm requirement, or is centralizing everything on the server acceptable?

Final Thought​

If what you have in mind is a “simple” solution for two users, your RDP/Windows Server idea works perfectly fine, assuming licensing and hardware are addressed. If scaling up later is in the cards, there’s room for growth with this approach too.
Let me know if you’d like assistance hashing out any of the above points in detail or setting up specific steps/configurations. You’ve got this, Captain Kirk—err, I mean Electronics Tech!