Server 2019 Essentials - Domain controller requirement
-
In past versions of Server Essentials Microsoft has mandated (AFAIK) that you have to run it as a domain controller. Server 2019 Essentials is a much different setup and doesn't push you to setup a domain controller.
Is it still a requirement in 2019 Essentials or can it now just be left as a workgroup?
-
Interesting - what is your intended use?
-
@Dashrender As a server for a small veterinary clinic. No need for a domain though.
-
Interesting question. Why would you not want to run it as a domain?
-
@Mike-Davis said in Server 2019 Essentials - Domain controller requirement:
Interesting question. Why would you not want to run it as a domain?
The question should be the opposite.
If there isn't a business need for a domain, why would you want to run it as a domain?
-
@CCWTech Even with only 4 users, wouldn't that mean create 4 user accounts on the server and then manage 4 user accounts on 4 machines. I supposed you could use the net user command in screen connect, but setting up a domain is so easy. Does the connector for Essentials work when they are not domain joined, or does it domain join them when you run it?
-
The install is weird. It installs like the regular OS. I thought it didn't install LOL. Then I checked system and it said Server essentials Rok 2019 and you enter the key there. Very different from 2016 and other versions in general.
-
@Mike-Davis said in Server 2019 Essentials - Domain controller requirement:
@CCWTech Even with only 4 users, wouldn't that mean create 4 user accounts on the server and then manage 4 user accounts on 4 machines. I supposed you could use the net user command in screen connect, but setting up a domain is so easy. Does the connector for Essentials work when they are not domain joined, or does it domain join them when you run it?
In the environment each user is transient, users move around the office and use whatever computer is available to them. So really a need for only 1 user unless we need to lock down certain directories for managers, owners, etc.
However no need to put complexity where the need does not exist. Creating 4 users (or more) is very easy. Once created not really any need to change them often.
-
@LilAng said in Server 2019 Essentials - Domain controller requirement:
The install is weird. It installs like the regular OS. I thought it didn't install LOL. Then I checked system and it said Server essentials Rok 2019 and you enter the key there. Very different from 2016 and other versions in general.
Yes almost looks like a Windows 10 install. -
But the question remains, are you forced to use it as a DC?
-
@Mike-Davis said in Server 2019 Essentials - Domain controller requirement:
Interesting question. Why would you not want to run it as a domain?
Simplicity, reliability. Running Essentials as a domain introduces a bunch of overhead that you can remove. If the domain isn't adding benefits, adding the complexity of it can be a fair hassle.
-
@Mike-Davis said in Server 2019 Essentials - Domain controller requirement:
@CCWTech Even with only 4 users, wouldn't that mean create 4 user accounts on the server and then manage 4 user accounts on 4 machines. I supposed you could use the net user command in screen connect, but setting up a domain is so easy.
Not as easy as running "net user". One command sequence four times is nothing.
But why the assumption of four user accounts per machine? That's not normal in small businesses. People with AD always assume that, but I've almost never seen an SMB that used more than a couple like that. The "everyone will log in as their own account, and on every machine" theory is an extreme niche edge case, not at all the norm.
-
@CCWTech said in Server 2019 Essentials - Domain controller requirement:
@Mike-Davis said in Server 2019 Essentials - Domain controller requirement:
@CCWTech Even with only 4 users, wouldn't that mean create 4 user accounts on the server and then manage 4 user accounts on 4 machines. I supposed you could use the net user command in screen connect, but setting up a domain is so easy. Does the connector for Essentials work when they are not domain joined, or does it domain join them when you run it?
In the environment each user is transient, users move around the office and use whatever computer is available to them. So really a need for only 1 user unless we need to lock down certain directories for managers, owners, etc.
However no need to put complexity where the need does not exist. Creating 4 users (or more) is very easy. Once created not really any need to change them often.
And "net user" is trivial to manage remotely. Managing AD remotely takes quite a bit more work. Needs solid benefits to offset the overhead.
-
@CCWTech said in Server 2019 Essentials - Domain controller requirement:
But the question remains, are you forced to use it as a DC?
A DC with no joined machines, is just a stand alone machine. Even the old one didn't have to be used for AD. Yes, AD would run, but it would not impact the environment. Using AD was never a requirement, only that no other root was allowed.
-
@scottalanmiller said in Server 2019 Essentials - Domain controller requirement:
@CCWTech said in Server 2019 Essentials - Domain controller requirement:
But the question remains, are you forced to use it as a DC?
A DC with no joined machines, is just a stand alone machine. Even the old one didn't have to be used for AD. Yes, AD would run, but it would not impact the environment. Using AD was never a requirement, only that no other root was allowed.
Use was not a requirement but setting it up was. I'm trying to find out if there will be any unexpected behavior if I don't promote it.
-
Why not just use Linux at this point? If you aren't using AD and don't want any additional overheard. Then just use Linux
-
@IRJ said in Server 2019 Essentials - Domain controller requirement:
Why not just use Linux at this point? If you aren't using AD and don't want any additional overheard. Then just use Linux
They have a Windows based application that runs on the server. Linux isn't an option.
-
@CCWTech said in Server 2019 Essentials - Domain controller requirement:
@IRJ said in Server 2019 Essentials - Domain controller requirement:
Why not just use Linux at this point? If you aren't using AD and don't want any additional overheard. Then just use Linux
They have a Windows based application that runs on the server. Linux isn't an option.
Why not segregate duties virtually then? Have file shares on Linux and have your app run on Windows?
-
@IRJ said in Server 2019 Essentials - Domain controller requirement:
@CCWTech said in Server 2019 Essentials - Domain controller requirement:
@IRJ said in Server 2019 Essentials - Domain controller requirement:
Why not just use Linux at this point? If you aren't using AD and don't want any additional overheard. Then just use Linux
They have a Windows based application that runs on the server. Linux isn't an option.
Why not segregate duties virtually then? Have file shares on Linux and have your app run on Windows?
That wouldn't work for this program. Windows is a requirement for this case.
-
@CCWTech said in Server 2019 Essentials - Domain controller requirement:
@IRJ said in Server 2019 Essentials - Domain controller requirement:
@CCWTech said in Server 2019 Essentials - Domain controller requirement:
@IRJ said in Server 2019 Essentials - Domain controller requirement:
Why not just use Linux at this point? If you aren't using AD and don't want any additional overheard. Then just use Linux
They have a Windows based application that runs on the server. Linux isn't an option.
Why not segregate duties virtually then? Have file shares on Linux and have your app run on Windows?
That wouldn't work for this program. Windows is a requirement for this case.
he means for files outside of the program. Word docs and the like.
