Hi everyone I am getting a real weird error. A while back I started a Github account from an old email and wasn't active with and forgot about. Lately, I have opened a new github account with a different email that has all my current projects.
I had github desktop installed (older version) but like my old account I never really used. So I reopened it to access my new account but it is still connect to my old account. I logged out from the options and signed in via my new account through the web but the actual repositories and folders it is show are still from my old account. I have tried updating, resinstalling and installing github desktop and signing out and signing back in various times and it is still connecting to my old account.
I am thinking there is still come connection with my Github desktop and my old account and need to somehow break the connection via the terminal but not aware of any command to do this.
If I am unable to break this connecting to my old account it seems to me like a major security issue with GitHut desktop. Hopefully thats not the case.
Does anyone have anyways of solving this issue or is this something that I should report to Github?
This also happens when trying to log out from Git Bash, you have to go to "Control Panel" > "User Accounts" > "Credential Manager" > "Windows Credentials" and look for the application. Then, remove the credentials of Github. Hope this is usefull.
I don't know Jenkins at all. I want to install Jenkins on Windows 10. I downloaded the installer and ran it, but I have a problem. I don't know what to enter in the "Account" and "Password" fields on the "Service Logon Credentials" stage.
if I use the username and password of my Windows account(with administrator privileges) the following information is displayed:
When installing a service to run under a domain user account, the account must have the right to logon as a service. This logon permission applies strictly to the local computer and must be granted in the Local Security Policy.
Perform the following to edit the Local Security Policy of the computer you want to define the ‘logon as a service’ permission:
Logon to the computer with administrative privileges.
Open the ‘Administrative Tools’ and open the ‘Local Security Policy’
Expand ‘Local Policy’ and click on ‘User Rights Assignment’
In the right pane, right-click ‘Log on as a service’ and select properties.
Click on the ‘Add User or Group…’ button to add the new user.
In the ‘Select Users or Groups’ dialogue, find the user you wish to enter and click ‘OK’
Click ‘OK’ in the ‘Log on as a service Properties’ to save changes.
Then try again with the added user.
(Source)
Below solution worked for me on Windows10.
Select Logon Type = Run Service as Local System ,click Install and complete the setup
To unlock Jenkins, Go to C:\Program Files\Jenkins and open jenkins.err
Get Administrator password ,paste and Install suggested plugins.
Create first admin user and start using Jenkins
Follow Chanaka Karunarathne's answer, just in the 'enter the object name to select' section enter your PC's user name. If you do not know what is your user name then just open a command prompt and run 'whoami'.
I followed this procedure to install Jenkins and it worked like a charm,
https://www.youtube.com/watch?v=1_Zs0gQq1Yc
Step1:
Download the "jenkins.war" file.
Step 2:
Run this command java -jar jenkins.war
Step 3:
Copy the secret that you get from this location,
C:\Program Files (x86)\Jenkins\secrets\initialAdminPassword
Use this Key when prompted to "Unlock Jenkins",
If you are a windows 10 home user, you need to download and install GPEdit.msc in Windows 10 Home using PowerShell script before you can use "Local Security Policy". you can download it from here.
I was be able to follow https://stackoverflow.com/users/4309588/chanaka-karunarathne's suggestion, but when it went to the next step, I tried to enter my "admin"(aka laptop login credentials), in my case I usually login with the 4-digit code to my Windows; and even if I use the password associated with the account, it would be my email as username and it's windows password as password, but I have setup two-step authentication for my email as well. it would not work.
I ended up username + 4 digit pass-code would not work on this
username(email address) + password would not work as well (due to the MFA)
I don't know why it had to be this difficult to login to Jenkins (or not sure if I should be upset about myself for setting up MFA for my email :) )
#elysium You can solve such problem by switching from Microsoft Account to Local Account for your computer. On assuming that your computer is similar to mine, you can navigate as follows;
Press/Click the Microsoft Windows tab on your keyboard.
Navigate to your profile picture and click on "Change Account Settings"
Navigate to Log in with Local Account instead and make the switch from Microsoft Account to Local Account.
Follow #Chanaka Karunarathne 's instructions. If you cannot find Local Security Policy, Go to search and type winver to confirm if you are using either of this OS versions ; Windows 10 Pro, Windows 10 Education, Windows 10 Pro Edu, Windows 10 Enterprise, Windows 10 Pro Workstation) otherwise Windows 10 Home lucks Local Security Policy, atleast for my case.
Alternatively, as mentioned in some previous comments here, to enable Group policy in Windows 10 Home, download a from here, right click on it run as administrator. Press Window Key + R, type gpedit.msc to check if Group policy has been enabled as described in this majorgeeks youtube channel (https://www.youtube.com/watch?v=7wkgwEhtqdI&ab_channel=majorgeeks)
In Windows 11, I am getting the same error even though provided user and password are correct. So I have installed Jenkins as LocalSystem.
After completion of installation, I changed it from the services and it worked for me.
I have online TFS account.
Whenever I do a check-in it shows check in done by "Service Account(TFS)" instead of my name.
I want to show my name against the Checked-In by Name.
Any help is appreciated.
Firstly, please make sure you connect the online TFS (VSTS) with the correct account.
If connect with wrong account, you need to remove TFS credentials from Windows Vault to clear and force to ask new TFS credentials in Visual Studio. Please reference this thread: How can I change the default credentials used to connect to Visual Studio Online (TFSPreview) when loading Visual Studio up? to do that.
If the account is correct, just please check your VSTS account Profile, make sure the full name is not "Service Account(TFS)". If it is, just change it to your name, save the profile and check in again, check the Checked-In by Name, it will be changed to your name.
Ok, once again a forced password expiry has inadvertently screwed with our TFSSERVICE and other TFS accounts, so Team System (2008) no longer works. I've picked my way through all the steps I can think of to fix the issue, and I have one issue remaining:
Here are my steps so far:
On any machine on the domain change the password for domain accounts TFSSERVICE and DEVBUILDSERVER. Note the new passwords.
On the Team Foundation Server
• Update the login password for Team Foundation Server Task Scheduler service and restart the service. (TFSSERVICE account)
• Update identity password for the application pool Microsoft Team Foundation Server Application Tool, and restart it. (TFSSERVICE account)
• Execute the command "TFSADMINUTIL changepassword domain\TFSSERVICE newpassword".
• Via a browser connect to the reporting services website (http://<TFSxx>/reports) and update the password for the TfsReportDS and the TfsOlapReportDS data sources.
On the build agent update the password for the TFSBUILD service, update the login password for the SQLEXPRESS service, and restart both services. (DEVBUILDSERVER account).
However although source control and CI builds now work, when I look at a project portal I see the following:
Remaining Work
Report Generated: 12/01/2015 13:34:32 by AS\neil; Last Warehouse Update: 28/10/2014 13:59:48
How much work is left and when will it be done?
No data matches the parameters specified.
whereas I should be seeing a graph.
What vital step have I overlooked?
TIA
Background information
I need our TFS build agents to run under a specific account so that our ClickOnce certificates are authorised.
However if I run under the account X, which also is the user account of the build controller that has the correct certificates. I get the error: "Source is already in use". Even if I restart the service and/or the virtual machine.
Originally rightly/wrongly our build agents were running under the Network Service account, however this account cannot verify the certificates.
Using the Local System account does not give access to the build controller from a developer box.
So I guess my question is: What account should the service 'Visual Studio Team Foundation Build Service Host' run under?
It turned out that the account X was the correct choice (our build controller user account, that has few privileges).
It was that the account needed adding to the builders group TFS Admin.
My personal suggestion would be: a specifically-created, minimum-privelige account that is only authorised as far as is necessary to build the code on your build machines, and no more.
I'm not aware of any restriction around the user for the build agent vs the build controller, though - in fact I'm sure I've used a similar setup before. Is it possible that your error is misleading? Changing users might be a workaround, but perhaps there's something else fixable going on.