Logo
programming4us
programming4us
programming4us
programming4us
Home
programming4us
XP
programming4us
Windows Vista
programming4us
Windows 7
programming4us
Windows Azure
programming4us
Windows Server
programming4us
Windows Phone
 
Windows Server

SharePoint 2010 : Farm Governance - Configuring a Managed account

- Free product key for windows 10
- Free Product Key for Microsoft office 365
- Malwarebytes Premium 3.7.1 Serial Keys (LifeTime) 2019
4/19/2013 6:42:25 PM

A Managed account in SharePoint is an account that is completely managed by Active Directory.

Service accounts are a prime example. These accounts are typically domain-level accounts that are managed in Active Directory (AD)&;. Being an active directory account means it is subject to the policies implemented across the organization. For example, a user may have to change their password every six months. The policy may dictate that the password meet certain criteria such as containing upper case and lower case characters.

The problem with this scenario in SharePoint terms occurs when the password needs to be changed. The service stops working when the password expires. If the account is the identity for multiple services, they stop working too, which potentially brings a working SharePoint installation to a stop.

In many organizations, there is a division of responsibilities that can prohibit the SharePoint Farm Administrator from changing the password of an AD account. The Managed account resolves this issue. SharePoint manages this account and, through central administration, you can register these accounts.

In this recipe, we see how to create and manage an account.

Getting ready

You must have farm-level administrative permissions to the Central Administration site.

The account that you are configuring must be set up in Active Directory. It must be an existing AD account.

How to do it...

  1. Open up the SharePoint 2010 Central Administration website.

  2. Click Security.

  3. Under the section titled General Security, select the Configure managed accounts option.

  4. Click Register Managed Account. The following form appears:

    Fill in the required information:

    • User name: Supply the AD account. It does not have to be prefaced with domain.

    • Password: This must match the account password in AD.

    • Enable automatic password change: Checking this will allow you to set the time and notifications by e-mail.

    When finished filling the required data, click OK. The account is now added.

How it works...

When the account is added as shown in the recipe, its credentials are now managed and stored within SharePoint. SharePoint 2010 can leverage the AD policies to automatically reset passwords.

Once the account is in SharePoint, it is encrypted using the farm encryption key that was specified when the farm was created based on the passphrase. A key benefit of using managed accounts is the ability conferred upon the Farm Administrator to join machines to the farm without specifying the credentials.

There's more...

PowerShell can be used to do anything you can do through the Central Administration user interface.

Powershell: Get a listing of managed accounts&;
Get-SPManagedAccount

Powershell: Create a new account&;
New-SPManagedAccount

Powershell: Set&;
Set-SPManagedAccount -identity

Powershell: Delete a managed account&;
Remove-SPManagedAccount

More info

You cannot use the Central Administration UI to assign local accounts to be managed accounts. This is achievable, but only through PowerShell.

Other -----------------
- SharePoint 2010 : Farm Governance - Administering SharePoint Designer
- SQL Server 2008 R2 : Creating and Managing Stored Procedures - Debugging Stored Procedures Using SQL Server Management Studio
- SQL Server 2008 R2 : Creating and Managing Stored Procedures - Using Output Parameters, Returning Procedure Status
- Windows Server 2008 : Designing the Active Directory Administrative Model (part 3) - Planning to Audit AD DS and Group Policy Compliance, Planning Organizational Structure
- Windows Server 2008 : Designing the Active Directory Administrative Model (part 2) - Using Group Strategy to Delegate Management Tasks
- Windows Server 2008 : Designing the Active Directory Administrative Model (part 1) - Delegating Active Directory Administration
- BizTalk Server 2006 : Starting a New BizTalk Project - Organizing Artifacts in BizTalk 2006
- BizTalk Server 2006 : Starting a New BizTalk Project - Structuring and Integrating with Visual Studio
- Deploying the Client for Microsoft Exchange Server 2007 : Planning Considerations and Best Practices, Preparing the Deployment
- Deploying the Client for Microsoft Exchange Server 2007 : Outlook 2007 Auto Account Setup, Understanding Deployment Options
 
 
Top 10
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 2) - Wireframes,Legends
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 1) - Swimlanes
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Formatting and sizing lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Adding shapes to lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Sizing containers
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 3) - The Other Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 2) - The Data Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 1) - The Format Properties of a Control
- Microsoft Access 2010 : Form Properties and Why Should You Use Them - Working with the Properties Window
- Microsoft Visio 2013 : Using the Organization Chart Wizard with new data
 
programming4us
Windows Vista
programming4us
Windows 7
programming4us
Windows Azure
programming4us
Windows Server