Access to Shared Folder/Domain Solution - Win Server 2012 Essentials R2

Hi Guys,

Domains aren't something I've spent a great deal of time working with, even less time with Server 2012 Essentials, so I was wondering if someone could advise me.

I've got a database living on a Windows server (2012 Essentials R2), and that OS always requires a domain and to be the domain controller.

Normally there are a couple of local Windows machines that run software which have read/write access to a couple of folders on the server (SQL Database).

I now have a situation where I'd like to add a Windows laptop into the mix, also running the same client software, and so needing the same access to the folders. I could set it up to get domain access but it would complicate things in terms of the user making use of the laptop at home for other purposes, internet, etc.

So what I'm wondering is if there's a way/what's the best way to allow the laptop access to the database in the office when needed (via wifi) and yet also retain the ability to function easily outside the office in terms of home wifi etc.

So far I've brainstormed the following:

Configure the cable network adapter to work on the office network and leave the wifi free for normal usage. (But I'd prefer wifi access in the office too if possible)

Set up two users with different network setups - A domain only login with network configuration for access to the domain and another local login with a normal open network config.

Some sort of server based solution which recognises the machine and lets it simply have access to the shared folders without any further changes on the laptop.

Not sure if those last two are even possible, so if you guys have any input on this, I'd appreciate it!

Thanks.

Again - TLDR - I need to get some client software talking to an SQL database on a server (2012 Essentials) but don't want to complicate the networking to the extent the user can't use the laptop easily outside the domain.

From my brief tinker the other day before scrapping it as a bad idea.

Windows 10 (8 as well) will allow a new user you create on the server to be setup on the laptop, you can then connect your microsoft account to this to get all the features and so on back, even have the pin number option to login.

I scrapped it off for now as I couldn't be arsed to delete my current logon as the domain controlled account said it wouldn't connect my microsoft account as it was already in use on the laptop.

Next time I need to format a machine I will give it a go again.

The laptop is running Windows 7 I believe.

I am confused what folder access has to do with accessing a SQL database!

If you are accessing SQL, then you can create a SQL-login in SQL Server and the user can supply those credentials when connecting from the client software.

If they need folder access, then create them a domain account and then disable anonymous access to the share. When they connect they will be asked for credentials to which they can enter as:
domain\user

Quote:

---

Originally Posted by shaithis

I am confused what folder access has to do with accessing a SQL database!

If you are accessing SQL, then you can create a SQL-login in SQL Server and the user can supply those credentials when connecting from the client software.

If they need folder access, then create them a domain account and then disable anonymous access to the share. When they connect they will be asked for credentials to which they can enter as:
domain\user

---

I might be mistaken about the nature of the system as per SQL. That might sound odd, but I know that SQL Server itself isn't running or necessary. Basically it's a DBISAM database and it can be set up without SQL Server just in terms of access to a shared database folder via client software.

If we work from the principle of folder access, then my problem, as I see it, is, is it possible to take a normal, pre-existing Windows laptop, with a user login, and grant server permissions so that it can access the server (which has it's own domain/workgroup - because Essentials demands it) and still make it easy for that laptop to be used elsewhere?

I could try to train the user in changing workgroups/network settings but if that can be avoided it would be better.

In that case I believe the following 2 options to pretty much be your only options:

1. On the share, grant the computer account access (this would mean ANYONE logged onto the laptop would have access to the share)
2. Create them an AD account and each day they will have to connect to the share and supply their credentials for the domain the share is part of.

I would say the best Idea is to have the permissions set on the folder as user A, B, C etc..
Then create a mapped drive on the laptop connecting to the folder on the server and tick Reconnect at sign in and connect using different credentials. This will then store user (x) credentials and allow a connection every time they are on the same network.