Question Locked

Domain or Workgroup Network

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Currently, our network is setup as a workgroup. We have 19 workstations. One of them is a satellite office that comes in VPN (Ipsec), with some employees using VPN (PPTP) to connect sometimes. There is a legacy server that everyone telnets to that is just another peer. The VPN happens through the router. We have purchased a new server running Windows Server Standard 2003. For the moment, I have it setup on the workgroup as well, but I am going to have to set it up as the Terminal Server. I see that if I make the server domain, than I have AD, which is a good thing. I have been tussling with this whole question. Is it really best to use Domain and have all the workstations flow through the Server? The server is a Dell PowerEdge 2950, which should be enough resource for our little network. What is going to be the effect on the users, who are used to using their PCs in a very free use environment? Do I have to use Domain in order to support that remote user who is using VPN right now? I am all for a more secure centralized environment as long as it doesn't mean a revolt among the users. Thoughts?

6 replies

by dumphrey

For example, you have a single place to set up and manage passwords, no need to go machine to machine. Group Policy lets you automate a lot of features and security practice. Routing and Remote Access part of server 2003 will allow you to set up a radius server to use to authenticate VPN users against AD and VPN group membership. As for the users use to a "free" environment, that is still your call. If you want, you can add their domain account to the local machine Power Users group or Local Machine Admin group (not recommended). Some will whine, some will prefer it; some will not care at all.
The Power Edge will be more then sufficient for your network, no worries there. And each workstation will still be independent, all AD will be doing is providing authentication, authorization, access control, and some accounting (logs).
There are a few steps in getting it up and running, but not that hard, and in my opinion, you are right on the edge of needing to move to a domain. It will greatly simplify your job I think.
I do not think you have to have a domain to support your remote user. After all, are you not supporting them now? Overall, they will most likely be the least effected.
Overall, if you have a mostly Windows environment, and have several network resources to control (network shares/printers for example) then by all means set up a domain. But if you just have a single resource to manage, your network is small enough that the domain may not be worth the set up time, as its benefits would be minimal. But these are decisions you will have to make. I personally would set up the domain. After all, you can always just not use it, or only use it on one or two test machines until you decide on if its of use. And in the long run, you can dcpromo the domain controller back to a regular server.

by starry997

Thanks for the reply. I will also have to buy more CALS. It came with the basic 5, but if I go to domain, I will need the additional right away, I see. There are 3 addtional workstations that are really saw controllers that we file share to. I imagine the terminal server will want to have CALS for them as well? You said something about testing with a few workstations. What if I left those saw controllers on workgroup permanently? Would I still be able to file share to them OK? They have no need to access the Internet.

by dumphrey

would be based on login when attempting to access those machines. It SHOULD prompt you to log in with local credentials. That being said, by joining them to the domain, you could set permissions based on AD group membership, user, or what have you. And you only need cals for machines that Connect TO the domain controllers. For example a Windows based file server needs a cal for each connecting client, but you do not need a cal for that machine to be a member of the domain. I think...
In server 2000 it was much clearer.

http://www.microsoft.com/windowsserver2003/howtobuy/licensing/caloverview.mspx
May help some.

by starry997

I have several network printers set up on the network as well and have to set up the print drivers on each individual workstation that needs to use it. Does domain control change that at all? Do I have to have all the printers set up in the server only and then the workstations access them as a service via the server?

by dumphrey

is install the printers directly on the DC, and then share them out. The DC can cache the drivers for the printers, so connecting a client is as simple as browsing to the \\DCservername unc path, right clicking on the printer, and choosing connect.

This discussion is closed to new replies.