If you have multiple service accounts for TFS 2012 and you are in a corporation chances are that two things are true:
- Your accounts are managed out-with your control in Active Directory
- They will expire every 90 days
It is however worth asking your IT department if they can set different expiry rules for service accounts
If these things are true and you work in an awesome origination that his its stuff together you will get an email when they are expiring.
Figure: Good example, you get notified when
If you are in an organisation that does not… then you will know when your TFS server stops working . You should review http://msdn.microsoft.com/en-us/library/ms253149 which will show you all of the service accounts that you might want to look at, but there are 4 main deal breakers to look at: TFS Service Account, TFS Reporting Account, TF Build Account, SharePoint Service Accounts, & SharePoint Secure Cache account.
Here is what you need to do:
- Change the Service Account or Password for Team Foundation Server
- Open the admin console on the TFS Application Tier by clicking “Start | Team Foundation Server Administration Console”
- Go to “Server | Application Tier | Change Account”
- Enter the new account details
- Change the Service Account or Password for SQL Server Reporting Services
- Change the account or password for Team Foundation Build
Figure: Update the Team Foundation Build Service Account- Open the admin console on the build server by clicking “Start | Team Foundation Server Administration Console”
- Go to “Server | Build Configuration | Properties | Stop the Service | Change…”
- Enter the new account details
- Start the service again
- Change the account and password for SharePoint
- Change the account or password for SharePoint Secure Store credentials
- Change the account or password for SQL Server
You will need to go round all of your Team Foundation Application Tiers, Team Foundation Build, Team Foundation Proxy, System Centre Virtual Machine Manager, SharePoint Farms, SQL Server Instances, SQL Server Reporting Services instances and SQL Server Analysis Services instances and make sure that you have changed all of the accounts.
Phew…