I recently installed Azure DevOps Server 2020 and at the time of installation I set the Search Service User to a specific AD user group that I had planned on using later on for search in TFS/Web UI.
According to the Microsoft documentation below, changing this parameter should be doable based on running the Server Configuration Wizard again or by launching the Search Configuration Wizard. However, Microsoft fails to mention how to reopen the Server Configuration Wizard or how to use/open the Search Configuration Wizard.
https://learn.microsoft.com/en-us/azure/devops/project/search/administration?view=azure-devops-2020#config-tfs
Following another guide to open D:\Program Files\Azure DevOps Server 2020\Tools\TfsMgmt.exe configure opens the original Wizard to which the buttons are grayed out since they are already set.
Does anyone know how to relaunch or open these Wizards?
You need to remove the search service before you re-configure it.
You can open command prompt as administrator and navigate to Elastic search directory.
For azure devops 2019. The directory is C:\Program Files\Azure DevOps Server 2019\Search\ES\elasticsearchv6.2\bin. In Azure devops 2020 the elasticsearch version might be higher.
Then run command elasticsearch-service.bat remove
After the search service is removed, you can go the Azure devops server administration console to reconfigure it.
If removing elastic search service doesnot work, try removing the Search feature too.
See document here for more information.
Related
I had installed Azure Devops on our Windows 2019 server. The server has 5 users and all of them were created as local users on the server. I added these 5 users in Dev Ops project. Four of these users started using visual studio directly on the same server and have cloned project from on premises Azure dev ops. When they connected to the Azure dev ops server, they simply used User1, User2.... username and their windows password to connect to the Azure.
After a couple of weeks, we implemented Active Directory and added this server into the active directory group. The existing four users are still able to pull, push the same project. However, when the fifth user which never logged in now needs to connect to the Azure Dev Ops to clone the project. When he tries to connect via Visual Studio, the visual studio adds Domain into the user name e.g. DomainName\User5 and azure dev ops connectivity is not accepting his windows password. This user is not a domain user and is local to the server. This user can login to Azure Dev Ops when accessing it from browser, but unable to connect when trying it from Visual Studio.
Also, when I logged in directly to Azure Dev Ops (on premises) and try to add members to project, it does not show domain users. It only shows local server users.
Do I need to reinstall Azure dev ops, what should be the apprpriate way to fix this issue?
Thanks
When the fifth tried to use Visual Studio to connect the project, and access the project on web browser, did he do these things also directly on the same server machine?
Due the fifth user can access the project on web browser, the account of this user should not have issue. The problem seems occurs on Visual Studio when trying the authentication for the account.
Please try to check with the following things to see if the problem can be solved:
Check if the user has login to Visual Studio with his account.
Check if Visual Studio has saved or cached the account information of other users. If yes, clean the cache. Then login to Visual Studio with the fifth user's account.
When trying to connect to the project on Visual Studio, make sure the the selected user id the fifth user.
If the issue still exists, please share us with the details error message that the fifth user gets.
We have TFS 2019 installed on premise, want to create PowerBI reports based on analytics Views that are already predefined in TFS. Selecting GetData in PowerBI yields a login screen with collection URL and Team Project. We entered TFS sever name in URL connection and the Team Project respectively, getting an error "invalid account". Prior to this PowerBI asked for Login, logged in with my microsoft user. Can u please advise how to connect Power BI to a TFS on premise, we didn't find helpful material searching for it on the internet. Thanks in advance.
Can u please advise how to connect Power BI to a TFS on premise, we
didn't find helpful material searching for it on the internet.
Assuming you have Power BI Desktop in MachineA. Now you need to make sure:
1.The Azure Devops Server is running and you can login the web portal of Azure Devops Server(once called TFS) in MachineA's browser:
2.The Analytics View option is enabled and you have access to view/edit them:
3.In Power BI Desktop: For on-premise Azure Devops Server, the Collection Url shoule be the team collection url instead of simple ServerName or OrgName:
The Team Project name is one of your project name. For me I have Project ForTest in organization Test. And my full url of the project is: http://xxx/Test/ForTest/. So I enter http://xxx/Test/ for Collection Url and ForTest(simple name of team project !!) for Team Project, then it works well to connect to the server:
Ps: I use Azure Devops Server 2019 Update1(1.1) and latest Power BI Desktop downloaded from Microsoft Store.
Hope my steps make some help for you :)
When the login window appears which asking for Account Name to connect TFS, you need to write only name of the account (beginning name of visualtstudio.com) and write specific project name or * if you want to get data for all existing projects.
Eventually what worked was full URL of the collection in the first field and name of team proejct in the second field.
Is it possible to browse the file system in Azure Devops. Like when using SSH to connect to a server? Or if it's possible to browse using Explorer.
It would really simplify things if I could see what files were created and where they end up after builds.
Now I don't feel I have any way to know which files ended up where after the builds are done.
Thanks!
I don`t think so. You may add build steps (Build and release tasks - Utility) and create cmd or bath file to browse the file system of the build servers.
As alternative way, you may use your own build server (Self-hosted agents) on Azure VMs and you will have the full control.
This is a different issue as I am accessing and using my visualstudio.com server. Please see the image.
I am currently working on an automation in powershell which is to create a new project in VSTS using my account. Unfortunately, I am having an error which is below.
System.Management.Automation.RemoteException: The project collection does not have a default location for creating project portal sites configured.
Either configure this location using the Team Foundation Administration Console or specify the /w
ebapplication and /relativepath arguments.
tfpt only works with TFS2015 or more older version. It does not work with VSTS and TFS2017.
You can use Rest API to create the team project via script just as you found. Or you can also consider to use the VSTS CLI: VSTS Create Project.
I'm trying to use TFS 2015.1 on premise to build a CI pipeline for our dev & uat. I've created a vNext CI build, which builds fine. But when I want to add a deploy step for on prem IIS server, I only then see Azure Web Deployment options.
Ideally I wanted to add a step which uses the existing deploy (MS Deploy) profiles, which I'm able to use from VS2015 directly, using 'Publish'. However I see no option to do so.
How can I deploy the latest build to internal dev servers (not Azure)? I would like to use the MS Deploy option, unless there's a better way of doing it?
The fact that their is no option to starts to make me think there's probably a different way to accomplish it!
Thanks.
If you're able to upgrade to TFS 2015.2, web-based Release Management came out with it that works similarly to Build vNext with flexible and open-source tasks. You can also customize tasks.
Here's a link for IIS Web App Deployment from the vso-agent-task's GitHub repo where Microsoft stores updated versions of their tasks that you can download for web-based Build and Release Management.
I'll be publishing a blog about web-based RM with TFS 2015 Update 2 or VSTS on my website in the next few weeks. To give you an idea though, the starting point (for a web application) is a folder in your web project called WebDeploy (no significance - any name will do) that contains a PowerShell DSC script that configures the server, deploys the web files and then replaces any tokenised configs. To give you an idea see this post about how to use DSC to configure servers. (Only covers part of the final script though!) The next steps are:
In the build hub create a Website artifact - containing your web files and DSC script.
In the release hub for an environment use a Windows Machine File Copy task to deploy the artifact to a temp folder on the target node.
Then use a PowerShell on Target Machines task to execute the DSC script. After configuring the server the script copies the web files to their proper location, sorts out config using xReleaseManagement and cleans up the WebDeploy folder.
See this article for general details of the route I'm taking, but watch out as it has some errors eg the firewall instructions are incomplete (file and print sharing through the firewall needs to be enabled).
I can thoroughly recommend the PowerShell DSC route - I've had a few glitches but on the whole it feels very productive and the right way to be going.