Active Directory

Based on the Active Directory implementation plan that I provided in the week two discussions, I wanted to create a plan that created strategies that would separate or let you know who users in which groups using Windows material are. I want to show that nesting a plan like this will be easier on the user, administrator, and company.

Groups these days are used to keep users, connected parts, and everyone that is part of the domain. The administrator or Point of Contact can make things a lot easier when they use groups or grouping. Everything that is stored in the computer’s system from employee start date to age to termination, etc. is stored in the groups. (Microsoft TechNet, 2007)

All the groups and users will have the same setting for security and permissions. There are a few groups that can be used. The types of groups we will use here are distribution groups and Security groups. The distribution groups will be used with all email applications for emails to be sent/received to all other users in that email list.

Each group will be allowed to access the network. They can also give rights to users in the Active Directory and set different security issues on the network. Distribution and groups are made by the scope with a domain. The groups for Riordan will be local. It gives access to domains and security. (Cooper, 2011)

An example of this would be any user or member using the domain. Usually members of this group do not change. The other groups usually only have access to minimal things like resources in that local domain. These users should have and will always be up to date on information of of the administrator.

Riordan will have four domains with a total of four groups in San Jose for all the divisions. The network will be easy to monitor because each group will be in one department. The security will be easy to function as well because each user will be able to access their own domain. (Cooper,