Skip to main content

Change the Service Account for Team Foundation Server 2010

I still remember the trouble I had to change the service account on Team Foundation Server 2008.  So I’m really glad to see how easy this became in Team Foundation Server 2010.

  1. Open the administration console for Team Foundation. For more information, see Open the Team Foundation Administration Console.

  2. Expand the server name and click Application Tier.

  3. In the Application Tier pane, click Change Service Account. The Update Service Account window opens.

  4. Perform one of the following steps:

    1. If you want to use a system account, click System Account, and then choose a system account from the drop-down list.

      If your server is a member of an Active Directory domain, the default choice is Network Service. If your server is a member of a workgroup, the default choice will be Local Service. Depending on your deployment, the default might be the only choice.

      System accounts do not have passwords. If you choose to use a system account for TFSService, you should not type a password in the password field.

    2. If you want to use a domain or workgroup account, click User Account, type the name of the account in Account Name, and then type the password of the account in Password.

  5. Click OK.

Popular posts from this blog

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

.NET 9 - Goodbye sln!

Although the csproj file evolved and simplified a lot over time, the Visual Studio solution file (.sln) remained an ugly file format full of magic GUIDs. With the latest .NET 9 SDK(9.0.200), we finally got an alternative; a new XML-based solution file(.slnx) got introduced in preview. So say goodbye to this ugly sln file: And meet his better looking slnx brother instead: To use this feature we first have to enable it: Go to Tools -> Options -> Environment -> Preview Features Check the checkbox next to Use Solution File Persistence Model Now we can migrate an existing sln file to slnx using the following command: dotnet sln migrate AICalculator.sln .slnx file D:\Projects\Test\AICalculator\AICalculator.slnx generated. Or create a new Visual Studio solution using the slnx format: dotnet new sln --format slnx The template "Solution File" was created successfully. The new format is not yet recognized by VSCode but it does work in Jetbr...