安装后如何访问TFS Configuration Center并创建Self-signed-certificate

Got it, let's work through this problem together. You’re correct that the TFS Configuration Wizard typically only runs during the initial installation, but you can absolutely launch it again to generate those self-signed certificates you need for HTTPS setup—here’s how:

The wizard is still on your server; you just need to run it manually via the command line:

• First, find the TfsConfig.exe executable. It’s usually located in:
  C:\Program Files\Microsoft Team Foundation Server <Your TFS Version>\Tools
  Replace <Your TFS Version> with your actual version (e.g., 2018, 2019, 2022)
• Open an elevated Command Prompt (right-click Command Prompt > Run as administrator)
• Navigate to the Tools directory with the cd command, for example:
  cd "C:\Program Files\Microsoft Team Foundation Server 2019\Tools"
• Run this command to start the wizard:
  TfsConfig configure
  This will launch the same configuration flow you saw during installation.

Once the wizard is open, follow these steps to set up HTTPS and generate the certificates:

1. Proceed through the initial prompts until you reach the Application Tier Configuration section
2. Look for the option to configure HTTPS for your TFS server (this will be tied to setting up the web access URL)
3. The wizard will detect that no valid SSL certificate is present, and offer to generate a self-signed certificate automatically
4. Complete the remaining steps to apply the certificate, update TFS’s web settings, and finalize the configuration

If the wizard doesn’t behave as expected, you can create a self-signed certificate using PowerShell and bind it to TFS via IIS:

1. Open an elevated PowerShell window
2. Run this command to generate a certificate (replace tfs.yourdomain.com with your TFS server’s fully qualified domain name):

   New-SelfSignedCertificate -DnsName "tfs.yourdomain.com" -CertStoreLocation "Cert:\LocalMachine\My"
   

3. Open Internet Information Services (IIS) Manager, locate your TFS web site
4. Go to Bindings, click Add, select HTTPS as the type, choose the certificate you just created, and set the port (default is 443)
5. After binding, re-run the TFS Configuration Wizard to update the server’s internal settings to use the HTTPS URL

• Don’t forget to reconfigure your build agents to use the new HTTPS URL for TFS—this will resolve the "Basic authentication requires a secure connection to server" error
• Keep in mind: self-signed certificates will trigger trust warnings on client machines. If this is a production environment, you’ll want to replace it with a certificate from a trusted certificate authority (CA) later on

内容的提问来源于stack exchange，提问作者muhammad qasim