6 replies
by starry997 Accepted solution
by dumphrey Accepted solution
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 Accepted solution
by dumphrey Accepted solution
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 Accepted solution
by dumphrey Accepted solution
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending