active directory vs sharepoint

By kevin ·
Company is looking to put either sharepoint or active directory on the windows 2003 server. Here is the situation. We have to two offices with about 20-30 people at any given time that need access. Also would we need to go out and get Terminal server licenses? Right now the server has three connections. The server it self and the two RDP connections.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

I think you're confused, or maybe I am...

by TNT@support In reply to active directory vs share ...

All three of the products you mention serve different needs.

Active Directory is used to manage users and user groups. For instance, in order for someone to log onto your network they would need a network account, which the IT Admin would have to set up for them. The account can be another admin account, allowing them access to all network resources, or it can limit the user account to see and interact with files that they have permission to and nothing else. You can set up user groups as well, to aid in configuring access. For instance, you might have a "marketing" user group. Make the user accounts for the marketing staff members of the Marketing group and they all have the same access to the same information on your network.

SharePoint is a way to manage content on your network. It puts a web-like face to the internal network, allows you to develop document libraries and applications (like a time card app that people would use to log in and out, or a help desk app where people can report problems and IT staff can log their progress in fixing the issue).

Terminal Server allows users to log into a server and use its resources. You can set it up so that when a user logs in (using their AD account) it gives them access to their files and folders and applications. This can be resource intensive depending on how many people are logged in at one time. A better solution (for laptop users at least) is VPN. It allows their laptop to log into the network and they can work the same as if they were there in the office.

I would say you have to start with Active Directory. It is the foundation for your network services. Second priority would be off-site access which can be accomplished with Terminal Server or VPN. Third, use SharePoint to make navigation of your network easier and to help organize company resources. SharePoint is not a must have for your organization, though I think it is a great addition.

Collapse -


by kevin In reply to I think you're confused, ...

Looking for a way to manage users and have them log onto the network. With limit access for non admins.

Sorry for the confusion.

Collapse -

No problem

by TNT@support In reply to tthanks

AD is the where you want to start then. If you're company plans to grow be sure to pick a user name schema that can grow with you.

For example, I used to work for a non-profit that started out as a group of three people. They set up the user accounts and email addresses as first name and last initial (as in ""). That was fine when there was only one Greg T. in the organization, but that didn't last. When we moved email from an out-of-house provider to an in-house Exchange server I took the opportunity to restructure user and email accounts to use the first-dot-last name approach (gregt became greg.thomas, for example).

Best of luck to you.

Collapse -

apples and grapefruit

by CG IT In reply to active directory vs share ...

Here's the comparison: Active Directory is centralized administration, Sharepoint is a collaboration portal.

Related Discussions

Related Forums