Skip to main content

TFS 2012: Some features of Team Web Access are not visible to you.

After upgrading our TFS environment to Team Foundation Server 2012, the first time we logged on  in to TFS Web Access, we got the following message “Some features of Team Web Access are not visible to you”.

This is caused by the licensing model used for Team Web Access. You have 3 possible license levels:

  • Limited:
    • This level of access restricts the user so that they can only view work items that they create in Team Web Access (also known as Work Item Only View). No other features, such as team pages, are available to users in this group.
    • No client access license (CAL) is required for this level of Team Web Access.
  • Standard:
    • This is the default level of access in Team Web Access for your users. Members of this group can view all Team Web Access features except for:
      • sprint planning and backlog views
      • any of the features for requesting feedback from users and managing that feedback
    • A Team Foundation Server (TFS) CAL is required for all users with this level.
  • Full:
    • This level is reserved for users who are licensed to use all features available in Team Web Access, including the sprint planning and backlog management tools and the Request and Manage Feedback tools.
    • To use these features, your user must be licensed for one of the following MSDN subscriptions: Visual Studio Test Professional with MSDN, Visual Studio Premium with MSDN, or Visual Studio Ultimate with MSDN. These MSDN subscriptions each include a TFS CAL for the subscriber.

To add users to the correct group first click “Administer Server”. Then click “Control Panel”, “Web Access” and “Limited”, “Full” or “Standard” depending on the group you want to add your users/AD-groups to.

You can also change the default licensing mode used if you want to.

image

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

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.

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’: ...