Skip to main content

Change the regional settings of the Sharepoint site in a TFS Process Template

Last week I had an interesting customer request. For every Team Project SharePoint site they created in Team Foundation Server, the time zone information was wrong. Setting the "Default Time Zone" in the "Virtual Server Default Settings" for the "Default Web Site" makes no difference.

I found out that TFS places two global templates in SharePoint, which are referenced from the Agile and CMMI process templates. These two global templates include both the Locale and Time Zone settings to be used for newly create TFS SharePoint sites.

So, how can we solve this?

The first step is creating a new template with the correct regional settings. Therefore we have to create a new SharePoint site based on the existing templates and then change the regional settings. This site can then be saved as new global templates in SharePoint which can then be used by the TFS process templates.

  1. Use IE to navigate to the default web site on the TFS application tier
  2. Create a new sub-site via:
    1. Create
    2. Sites Workspaces
  3. When prompted, select the VSTS_MSFAgile template
  4. Change the Regional Settings in the newly created sub-site via:
    1. Site Settings
    2. Go to Site Administration
    3. Change Regional Settings
  5. Save the regionalized site as a new SharePoint template via:
    1. Site Settings
    2. Go to Site Administration
    3. Save site as a template
  6. Navigate to the site template gallery, either by following the link displayed after saving the template or:
    1. Navigate to the default web site on the TFS application tier
    2. Site Settings
    3. Go to Site Administration
    4. Manage site template gallery
  7. Save the template to the TFS application tier disk.

Now we have a regionalized template available. To register this new template, do the following:

  1. Log onto the TFS application tier
  2. From a Windows Command Prompt, cd to [Program Files]\Common Files\Microsoft Shared\web server extensions\12\BIN\
  3. Run the following command and then restart IIS: 
   1:  stsadm -o addtemplate -filename <template file> -title <template title>

As a last step we have to update our process template to use this new Sharepoint template:

  1. Use Process Template Manager to download the "MSF for Agile Software Development - v4.1" process template to disk. For the uninitiated, "Process Template Manager" can be accessed using the following steps:
    1. Launch Team Explorer and connect to your TFS box
    2. Using the context menu of the server node (right-click on the root node in Team Explorer), expand Team Foundation Server Settings
    3. Select Process Template Manager
  2. Locate the directory containing the downloaded process template and open the .\Windows SharePoint Services\WssTasks.XML file
  3. Look for the "template" attribute in the "site" element near the top of the file. For the MSF Agile template, this should have the value "VSTS_MSFAgile".

    wsstasks 

  4. Now change the value of the "template" attribute to the name of your previously regionalized SharePoint template.
  5. Save the WssTasks.XML file.
  6. Save the ProcessTemplate.xml file.
  7. Use Process Template Manager to upload the modified set of files.

If that succeeds, you should be ready to create a new Team Project based on the regionalized template. The SharePoint sites based on this new process template should now show dates etc in the format that is used by your region.

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