Hey everyone! I'm looking to set up a server for file sharing and to run QuickBooks, but I'm considering doing it without creating a domain. We only have local user accounts right now, and I'm wondering if anyone manages a similar setup? What are the downsides to going this route, aside from missing out on benefits like Group Policy Objects? I'm hesitant to set up a domain since everyone currently has local accounts and just needs the server for file access instead of individual PC usage, which has caused us some issues in the past. The team isn't ready to switch to QuickBooks Online, so I'm exploring the best approach here.
5 Answers
Honestly, QuickBooks can be a pain no matter how you approach it! For user management and sharing control, I'd prefer a domain setup. But if you're sticking with local accounts, you'll need to focus on permissions for the network folder. You don't have to join the workstations to the domain for QuickBooks access — just make sure the users have the right permissions to the shared folder on the server. If you’re looking for a simpler solution, you can just share the QB folder from a regular computer, but that’s really more for very small setups and not ideal.
Yeah, sharing it from a regular PC is how they have it set up now. They're a small business with no file sharing solution, just using OneDrive, which isn’t cutting it.
I’ve run setups like this for really small teams — usually up to around 10 users. You’re right about the conveniences of AD, but honestly, for local access, it’s not a strict requirement. Just set them up with the right access to a shared space and manage it that way. QuickBooks can be finicky though, so just keep that in mind.
If your client base grows, you might change your mind about using a domain. You could end up having issues with security and file access later on. I’ve had similar clients where lack of a domain caused ongoing headaches, especially needing to run the QB repair tool regularly. A domain might save you a lot of trouble in the long run!
I used to work with smaller offices too, and setting up a domain can really simplify managing user accounts and file shares, even if it seems like overkill. But if you choose to avoid a domain, be cautious with your file management. If a physical server feels too much, consider using virtualization with Hyper-V or something similar for future-proofing when you scale up. Just ensure your QB database is maintained properly, since that can be messy without a dedicated environment.
You can definitely manage without a domain, but it depends on the number of users. I've helped similar organizations, and for under 10 users, a NAS can do the job. You don't need to convert to a domain; just give users permission to the shared QB folder. The main hurdle we've encountered is figuring out a reliable file-sharing solution, so moving QB to a server is a smart call.
Totally agree! My setup involved a NAS and it worked fine for a small team. Just keep an eye on how permissions are structured!
That’s exactly how I set it up for a small office. Just shared the QB folder and created a user for access. Super simple!