Yes, you can use network usernames for access.
Yes, you can use network usernames for access.
Hello, I'm managing a modest computer network with five PCs for users, one PF-Sense server, and two virtual machines. I'm using Windows 10 as the storage system and need to set up individual desktops for each user while keeping configurations distinct. My goal is to avoid creating multiple identical accounts for each machine. I considered running Windows locally but found it unreliable across switches. An alternative idea is purchasing SSDs for each user's account and storing them on a central device, with you as the administrator. This would eliminate the need for physical cables and simplify management. Let me know if this approach works for your setup!
Your request seems unclear. Are you aiming to deploy the same solution across several devices? If so, develop one, set it up, and create clones. As long as the target drive type matches and has enough space—typically at least the image size plus 10-20% it should function smoothly.
I understand your request needs clarification. You're seeking secure storage of user accounts on the network, a cloned disk with full software setup, and automatic login functionality across different machines. Your current PCs are highly similar, which works well for Windows 10, 8.1, or even older versions like Windows 7—though you prefer Windows 10 1803. You want consistent access from any device, including a college-era setup with personalized apps and configurations. Since you're new to this, a simple step-by-step guide would be helpful.
The applications installed across all devices use a roaming profile. When you enter a domain, the profile is saved in the domain controller and moved to your logged-in computer. Typically, it resides at c:\Users\YourName, but with a domain controller it stays on the server and updates when redirected. Users won’t notice any change. If the software isn’t installed correctly, icons may appear distorted and the program might fail to save preferences in the User folder or MyDocuments. For instance, Photoshop scripts are stored in the program’s folder specific to each PC. On another machine, those files won’t be available unless you adjust the preference location and mapping. If the app doesn’t support preference redirection, switching computers can result in missing bookmarks.
The concept involves using a single Windows Server 2012 or newer computer as the domain controller, with other machines joining via Windows 7 or later (though SBS setups may differ). Each connected device must have at least Windows 7 Professional and be added to the domain. Management happens entirely from the domain controller. You can also route personal folders through the controller, which typically oversees network drives or NAS. Devices only need minimal space to run the software. After setup, logging in with your domain account grants access to all desired resources. Be aware of limitations: auto-installation is required on every machine, some apps depend on specific components or settings, and certain small business tools may not support virtualization. High traffic on a single server can become an issue when many computers are part of the domain. An alternative approach uses virtual machines per user for easier cloning and backup. Thin clients—small PCs with remote desktop capabilities—are another option, though they may not work well with graphics-intensive apps like SolidWorks, which often fail or require updates. Remote Desktop relies on GDI emulation, meaning it lacks full DirectX/OpenGL support.
It seems impractical to rely on a Windows server in such a small network. The setup process is too time-consuming, and if the server goes down, access becomes unavailable. If you're determined, consider this guide: https://blogs.technet.microsoft.com/cani...rver-2016/