El conocimiento al alcance de todos.

http://www.itprocentral.com/ By default all computer objects are created under the  Computers  container and in this Tutorial we are going change (redirect) this default location to a new organization unit (OU). In the image below we can see that a few servers were added to the domain and as usual they were created in the  Computers  container. Group Policies are applied at Site, Domain or Organization Unit level however the  Computers  is a container and cannot have an OU assigned to it, as shown in the image below using Group Policy Management console. In some companies the newly joined computers may require to receive a GPO right away. Validating the prerequisites… Before planning to use an OU to be the default location for new computer objects we must make sure that the domain level is at least  Windows Server 2003 . We can find that information by right-clicking on the domain name, and then  Properties  in  Active Directory Users and Computers . Configurin

Thank to: http://itprocentral.com In some medium/large organizations, it is common practice to have different access levels for systems, such as administrator, help desk, support and auditor. When implementing virtual machine using Hyper-V Servers, it is also important to reflect these access levels as well. Since Hyper-V 2012 makes this task easier when you need to specify particular users or groups to be Hyper-V Administrators, but you also might face scenarios where different levels are required. During the task, to add advanced permissions to a user, you will need to use groups (and recommended). You can create and use local groups or Active Directory groups. NOTE:  Make sure you have created them before you start. How to do it The following steps show how to delegate control for a user by using the local Hyper-V Administrators group and by using Authorization Manager (AzMan) for advanced delegations: 1. To add users or groups as members of the local Hyper-V Administr