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.

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

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.
Read more

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more