Powered by Blogger.

How Active Directory Administrative Center Has Changed in Windows Server 2012

Active Directory is the Windows based network foundations. Large and small businesses use it, very small businesses, home based businesses, may just be part of a workgroup deployment Windows computer, possible exceptions.

Even if your business has only 50 to 100 users, management of Active Directory can be said to have a lot of tedious repetitive work. User account creation and configuration, need to reset the password and group membership need to be updated as time goes on.

Large enterprises to handle the additional Active Directory management, including creating and populating with user and computer accounts, delegate control over Ou, so that people can manage their object, configure sites and site links distributed WAN environments in an organizational unit (Ou).

Prior to Windows Server 2008 R2, the majority uses several different Active Directory Management Microsoft Management Console (MMC) snap-ins, various command line utility and third-party Active Directory management products, or some combination of the above.

One-off manual tasks of Mmc snap-ins are handy, but tedious, repetitive tasks. Dsadd LDIFDE command line utility can be used to automate some of the more common administrative work, but the syntax varies between the different tools. Some third-party dealer, great for automating Active Directory management, but administrators out of additional blocks needed to use their products.

But starting from Windows Server 2008 R2, automating Active Directory management a lot easier in two ways.

First, the launch of Microsoft Active Directory administrative center (ADAC) as the Active Directory management tools to perform routine tasks. Secondly, including Microsoft Active Directory module allows administrators to perform many administrative tasks from the command line, or even better, write scripts, Windows PowerShell can be used to automate repetitive tasks. However, you must also choose between using the ADAC to perform tasks manually one by one, and uses Windows PowerShell to perform tasks from the command line; or automate them with the use of scripts.

This Division of labor between ADAC and Windows PowerShell means that administrators who are not familiar with Windows PowerShell are housed in major shortcomings.

ADAC in Windows Server 2012:

ADAC is now Windows Server 2012 and has been enhanced to include a new feature called Windows PowerShell history Viewer. Viewer and how to learn what history can be useful, I will create a new user account using the ADAC.


Figure 1 shows how to create user tasks to be used on the page to kelunboge, in Seattle in the Users OU of the Corp.contoso.com domain user to create a new user account. By scrolling through this page, you can manually specify the new password for the user account, the Organization, membership, and profile properties.

Once I have finished configuring properties for a new account, click OK to return to the ADAC. At this point, if clicked in the right corner of ADAC the caret symbol (^), Windows PowerShell history displays, as shown in Figure 2. Display all Windows PowerShell Windows PowerShell command to create a new user account in the process of implementation of behind the scenes.


0 comments:

Post a Comment