To use the collections command, you must be a member of the Team Foundation Administrators security group as well as the local Administrators group on the machine running TfsConfig. To manage collections interactively or to create a collection, you can use the Project Collections node in the administration console for Azure DevOps.
See Manage project collections. The following example shows how to duplicate the Contoso Summer Interns Projects project collection, name it Contoso Winter Interns Projects , and attach the duplicate collection to the deployment of Azure DevOps Server. You can use the Collection command to attach, detach, or delete a project collection from a deployment of TFS. You can also use the Collection command to duplicate the database of an existing collection, rename it, and attach it to the deployment.
However, you cannot use the Collection command to create a project collection. Specifies the name of the project collection. If the name of the collection contains spaces, you must enclose the name in quotation marks for example, "My Collection". This option specifies the name of the server that is running SQL Server and the name of the collection database that is hosted on that server.
If you specify this option, the original collection database will be attached as a clone in SQL Server, and this database will be attached to Azure DevOps Server. This option is primarily used as part of splitting a project collection.
To use the Collections command, you must be a member of the Team Foundation Administrators security group as well as the local Administrators group on the machine running TFSConfig. The following example shows how to permanently remove the "Contoso Summer Intern Projects" project collection from a deployment of Azure DevOps Server.
The following example shows how to duplicate the "Contoso Summer Interns Projects" project collection, name it "Contoso Winter Interns Projects," and attach the duplicate collection to the deployment of Azure DevOps Server. You use the columnStoreIndex command to enable or disable column store indexes for the databases used by your Azure DevOps Server deployment.
You would typically use the columnStoreIndex command if you were moving a database from a SQL instance which supported column store index to one which did not. In this case, you would need to disable all column store indexes before you could successfully move the databases.
Similarly, if you were moving a database back to a SQL instance which supported column store index you might wish to re-enable column store index in order to save space and gain performance. You use the ColumnStoreIndex command to enable or disable column store indexes for the databases used by your TFS deployment. Specifies whether you are enabling or disabling column store index for the given SQL instance and database.
Specifies the name of the server that hosts the database for which column store index is being enabled or disabled, and the name of the instance if an instance other than the default is used. You would typically use the ColumnStoreIndex command if you were moving a database from a SQL instance which supported column store index to one which did not. To use the configureMail command, you must be a member of the Team Foundation Administrators security group on the Azure DevOps application-tier server.
The following example shows the syntax used to configure the from email address to TFS contoso. You use the dbCompression command to enable or disable database page compression for the databases used by your Azure DevOps Server deployment.
To use the dbCompression command, you must be a member of the sysadmin role for the specified SQL Server instance. You would typically use the dbCompression command if you were moving a database from a SQL instance which supported compression to one which did not. In this case, you would need to disable compression and decompress all indexes before you could successfully move the databases. Similarly, if you were moving a database back to a SQL instance which supported compression you might wish to re-enable compression in order to save space.
This command only changes whether Azure DevOps Server prefers to use database page compression or not - your databases must still be hosted in a SQL instance whose edition supports compression. You use the DBCompression command to enable or disable database page compression for the databases used by your Azure DevOps Server deployment.
Specifies whether you are enabling or disabling page compression for the given SQL instance and database. Specifies the name of the server that hosts the database for which page compression is being enabled or disabled, and the name of the instance if an instance other than the default is used.
Specifies whether database indexes should be rebuilt and compressed or decompressed as necessary immediately. If not used, indexes will be rebuilt by a background job which runs weekly.
This will block other operations, but may be faster than an online index rebuild. You would typically use the DBCompression command if you were moving a database from a SQL instance which supported compression to one which did not.
You use the deleteTestResults command to delete old stored test results from your collection store. This is typically done to reduce the store size or to reduce the time taken when migrating test results to a new schema. To use the deleteTestResults command, you must be a member of the sysadmin role for the specified SQL Server instance. You use the DeleteTestResults command to delete old stored test results from your collection store.
The name of the server that hosts the database for which test results are being deleted or previewed, and the name of the instance if an instance other than the default is used. The type of test results to delete. Valid values are automated , manual , and all. Display the number of test results that would be deleted based on the age in days, but do not delete these results. The deploymentPool command is designed to migrate all deployment groups from one deployment pool to another.
You might need to change or update the SID for users and groups in one of the following scenarios:. You do not need to run this command if you are changing domains within the same Active Directory forest.
To use the identities command, you must be a member of the Team Foundation Administrators security group and a member of the sysadmin role for all SQL Server instances that Team Foundation Server uses. You can optionally specify the database to change identities before you configure an application-tier server for the deployment. For example, you might specify the database to change the service account when you clone a deployment of Azure DevOps Server. You must wait for the next identity synchronization with Windows before the properties of accounts that you change with this command will be updated.
This requirement includes changes from group to user, user to group, and domain account to local account. Only account names that match will have their SIDs updated. To change a system account such as Network Service, you must follow a two-stage process.
Specifies the original domain of the identities that you want to change. If you are changing from a workgroup environment, specifies the name of the computer.
Specifies the domain to which you want to change identities. If you are changing to a workgroup environment, specifies the name of the computer. If you specify an instance, you must use the following format:. You can use the jobs command to create a log file that provides the details of the most recent job activity for a specific project collection, or to retry a job for one or all project collections.
To use the jobs command, you must be a member of the Azure DevOps Administrators security group. To retry a job interactively, you can open the administration console for Azure DevOps, select the Status tab for the collection, and then select Retry Job.
The following example shows how to create a log file that lists the most recent job activity for the Contoso Summer Intern Projects project collection in Azure DevOps Server. You can use the Jobs command to create a log file that provides the details of the most recent job activity for a specific project collection, or to retry a job for one or all project collections.
Specifies that the most recent job will be reattempted for the specified project collection. Specifies that the most recent job activity for the collection will be sent to a log file. To use the Jobs command, you must be a member of the Team Foundation Administrators security group. To retry a job interactively, you can open the administration console for Azure DevOps, click the Status tab for the collection, and then click Retry Job.
The following example shows how to create a log file that lists the most recent job activity for the "Contoso Summer Intern Projects" project collection in Azure DevOps Server. In this case, you will have to delete all the lab assets and reconfigure lab for the project collection.
In the following example, all lab objects in the DefaultCollection project collection are removed. Azure DevOps Server uses the suffix you enter when it registers a unique external name with DNS for each virtual machine in a network-isolated environment. The DNS alias record makes it possible for machines and other objects outside the isolated network to communicate with machines inside the isolated network.
If your Team Foundation Server deployment has more than one application tier and each application tier runs under a different service account, then each application-tier service account must have permission to edit the DNS alias records created by the other application tiers. DNS record management is performed automatically by Lab Management. If these steps are not performed in the previous scenarios, the new Azure DevOps Server service account will not be able to perform automatic management of those DNS records.
As a result, users will not be able connect to virtual environments. If you do not specify any target options, the operation acts on all virtual machines of all network isolated environments that belong to all project collections in the Team Foundation Server database.
In the first example, records for all network-isolated environments in a project are added to DNS. In the second example, an individual DNS record is removed. If your Azure DevOps Server deployment has more than one application tier and each application tier runs under a different service account, then each application-tier service account must have permission to edit the DNS alias records created by the other application tiers. If you do not specify any target options, the operation acts on all virtual machines of all network isolated environments that belong to all project collections in the Azure DevOps Server database.
Removes the specified host group from the project collection. Specify the name of the project collection host group to add, delete, or edit. Sets True or clears False the AutoProvision property of the host group. AutoProvision specifies whether the host group is automatically assigned to each project in the collection. Specifies how Lab Management treats the physical machines in a host group on which it deploys new virtual lab environments.
Do not prompt user for confirmation. Host groups are containers that an administrator creates within SCVMM to group a set of virtual machine hosts for easy management. Each host group is identified by its host path, a sequence of host group names that specifies the location of a host or host group within the hierarchy of host groups in SCVMM.
True Default. The host group is assigned to each project in the project collection. The host group is not assigned to each project in the project collection. LabEnvironmentPlacementPolicy specifies whether Lab Management considers the existing virtual machines when it deploys new environments on a physical machine in a host group.
Conservative Default. Consider non-running virtual environments in deployment decisions. This includes all virtual machines that are part of environments and that are in "Stopped" state also. Aggressive Do not consider non-running virtual environments in deployment decisions. You can also use this command set properties that are specific to Visual Studio Lab Management and to display the library shares that are currently assigned to a collection in Lab Management or to display all the library shares in SCVMM.
A library share is a designated share on a Virtual Machine Manager library server. A library share provides access to file-based resources for virtual Lab Management environments that are stored on your library servers, such as ISO images and virtual hard disks.
Library shares are created in Virtual Machine Manager. Visual Studio Lab Management uses library shares to provision virtual machines in the lab. By default, library shares in a project collection are automatically assigned to each of the projects in the collection. The Settings option. Sets the network location, such as the network domain or workgroup, that the physical computers in all host groups can connect to.
However, you can specify these options on separate command lines. Network isolation enables you to use multiple copies of a virtual machine without machine name or IP address conflicts. Because the IP addresses are used only for internal routing among virtual machines and are not exposed beyond the boundaries of an environment, you can specify any IP range that is not used within your public network.
In most cases, the default range of If you encounter problems connecting to network-isolated environments, you might have to choose a different range. You use the offlineDetach command to make an offline collection database into a detached offline collection database.
To use the offlineDetach command, you must be a member of the sysadmin role for the specified SQL Server instance.
This command modifies the schema of the specified collection database and should never be run against databases which are in use by a Team Foundation Server deployment.
This command is useful when you need to restore an individual collection database from backup without restoring other collection databases that are part of the same Azure DevOps Server deployment.
Previously this required restoring a complete and consistent set of databases configuration and all collections to a staging environment, configuring a Azure DevOps Server deployment using those databases, and detaching the one collection of interest. Instead, you can now restore consistent copies of the configuration database and the collection database of interest and run the offlineDetach command. The detached collection database can then be attached to any Azure DevOps Server deployment at an appropriate version.
You use the OfflineDetach command to make an offline collection database into a detached offline collection database. This command modifies the schema of the specified collection database and should never be run against databases which are in use by a Azure DevOps Server deployment. Instead, you can now restore consistent copies of the configuration database and the collection database of interest and run the OfflineDetach command.
Azure DevOps Proxy Server provides support for distributed teams to use version control by managing a cache of downloaded version control files in the location of the distributed team. By configuring Azure DevOps Proxy Server, you can significantly reduce the bandwidth needed across wide area connections. In addition, you do not have to manage downloading and caching of version files; management of the files is transparent to the developer who is using the files.
Meanwhile, any metadata exchanges and file uploads continue to appear in Azure DevOps Server. If you use the Azure DevOps Services to host your development project in the cloud, you can use the Proxy command to not only manage the cache for projects in the hosted collection, but also to manage some of the settings used by that service.
For more information about installing Azure DevOps Proxy Server and initial configuration of the proxy,. To use the proxy command, you must be a member of the Azure DevOps Administrators security group and an administrator on the proxy server.
You cannot use the proxy command for initial installation and configuration of the proxy. The following example shows how to add a project collection hosted on Azure DevOps Services to the proxy list using a Personal Access Token to authenticate. This token will be used only to register the proxy with the Azure DevOps Services account - the default service account will still be used to run the proxy.
The following example shows how to add a project collection to the proxy list. The following example shows how to change the service account used by the proxy for the project collection hosted on Azure DevOps Services.
Because the account name contains spaces, quotation marks are used to enclose the name. Team Foundation Server Proxy provides support for distributed teams to use version control by managing a cache of downloaded version control files in the location of the distributed team.
By configuring Team Foundation Server Proxy, you can significantly reduce the bandwidth needed across wide area connections. For more information about configuring proxy on client computers, see Team Foundation Version Control Command Reference. All special characters in account names must be specified in accordance with command-line syntax. Optionally specifies the path to a file that contains a personal access token.
This token will be used authenticate to the collection or account while registering a proxy. Added in TFS Update 1. To use the Proxy command, you must be a member of the Team Foundation Administrators security group and an administrator on the proxy server.
If you see the requests from the build server in the IIS log on the proxy server then it is going through there. Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums V. Team Foundation Server - Setup and Administration. On Windows, we use the Credential Store.
Agent version Because the Windows Credential Store is per user, you must configure the agent using the same user the service is going to run as. You can do that by logging into the machine with that user or using Run as a different user in the Windows shell. Since the code for the Get Source task in builds and Download Artifact task in releases are also baked into the agent, those tasks will follow the agent proxy configuration from the.
The agent exposes proxy configuration via environment variables for every task execution. Task authors need to use azure-pipelines-task-lib methods to retrieve proxy configuration and handle the proxy within their task.
Note that many tools do not automatically use the agent configured proxy settings. We strongly recommend the more modern method, which you can access by switching to the TFS or Azure Pipelines docs. If your proxy doesn't require authentication, then you're ready to configure and run the agent. See Deploy an agent on Windows. Jose Antonio. Improve this question. Jose Antonio Jose Antonio 2 2 gold badges 7 7 silver badges 22 22 bronze badges.
Have you looked at the traffic with Fiddler or Wireshark? Add a comment. Active Oldest Votes. Improve this answer. Sign up or log in Sign up using Google.
Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown.
0コメント