To streamline password management, the automatic password modification attribute enables you to upgrade and deploy passwords without having to perform manual password upgrade tasks across multiple accounts, services, and web applications. You can configure the automatic password modification function to identify whether a password is about to expire and reset the password utilizing a long, cryptographically-strong random string. To implement the automatic password change function, you need to set up managed accounts. SharePoint 2013 supports the best ways to create managed accounts to improve security and assurance application isolation. By using managed accounts, you can configure the automatic password modification attribute to deploy passwords throughout all services in the farm. You can configure SharePoint web applications and services, working on application servers in a SharePoint farm, to make use of various domain accounts. You can develop several accounts in Active Directory Domain Services, and then register each of these accounts in SharePoint 2013. You can map managed accounts to numerous services and web applications in the farm.
Prior to the implementation of the automatic password modification attribute, upgrading passwords required resetting each account password in AD DS and then manually updating account passwords on every one of the services that are working on all the computer systems in the farm. To do this, you needed to run the Stsadm command-line tool or use the SharePoint Central Administration web application. Using the automatic password change feature, you can now sign up managed accounts and allow SharePoint 2013 to manage account passwords. Individuals need to be informed about prepared password modifications and related service interruptions. Nonetheless, the accounts that are utilized by a SharePoint farm, web applications, and numerous services can be automatically reset and deployed within the farm as required, based upon independently set up password reset schedules. IT departments normally enforce a policy requiring that all domain account passwords be reset frequently, for example, every 60 days. SharePoint 2013 can be set up to spot impending password expiration, and send an e-mail notice to a marked administrator. Even without requiring administrator intervention, SharePoint 2013 can be set up to generate and reset passwords instantly. The automatic password reset schedule is likewise configurable to ensure that the impact of possible service disturbances during a password reset are be minimal.You can always override any automatic password reset book and require an instant service account password reset by utilizing a particular password value. In this scenario, the password for the service account can likewise be changed in AD DS by SharePoint 2013. The brand-new password is then right away propagated to various other servers in the farm.
If AD DS and SharePoint 2013 account passwords are not integrated, services in the SharePoint farm won’t start. If an Active Directory administrator changes an Active Directory account password without coordinating the password change with a SharePoint administrator, there is a danger of service interruptions. In this situation, a SharePoint administrator can immediately reset the password from the Account Management page utilizing the password value that was altered in AD DS. The password is upgraded and instantly propagated to the other servers in the SharePoint farm. If an administrator all of a sudden leaves your organization, or if the service account passwords need to be immediately reset for other reason, you can rapidly create a Windows PowerShell script that calls the password modification cmdlets. You can utilize the script to generate brand-new random passwords and deploy the brand-new passwords right away.
When SharePoint 2013 modifications the credentials for a managed account, the credential modification process are take place on one server in the farm. Each server in the farm are be notified that the qualifications are about to change and servers can perform important pre-change actions, if they are necessary. If the account password has not yet been altered, then SharePoint 2013 tries to change the password making use of either a manually entered password, or a long, cryptographically-strong random string. The complexity settings will be queried from the proper policy (network or regional), and the generated password will be equivalent to the detected settings. SharePoint 2013 will try to commit a password modification. If it is not able to dedicate the password modification, it will retry by using a new sequence, for a pointed out lot of times. If the account password update process prospers, it will proceed to the next reliant service, where it will again try to dedicate a password change. If it does not eventually succeed, each dependent service will be notified that they can resume regular activity. Either success in dedicating a password change or failure to dedicate are result in the generation of an automated password modification condition notice that are be sent out by e-mail to farm administrators. When an administrator does a password change for the servers in the SharePoint search topology, there is an implied query downtime when the services are restarted. The query downtime is usually in the range of 3-5 minutes.