Hi @mikhael_3947, I have updated our Docker documentation to include this information about using a proxy with ProGet. I have also included more information about insecure registries and using self-signed certificates with Docker registries, Thanks, Rich

Hi @kichikawa_2913, Sorry, this is actually expected. When we release our products, they include the extensions that were released at the time of the product release. In this case, I released this version of InedoCore after we did the product release. If you look at our documentation for upgrading your docker image, the command includes --volumes-from=proget-old. This will auto migrate the previous volumes created from the previous version of ProGet and that will keep the updated extension (as long as the previous extensions is newer than the included extension version). Also, in Administration -> Advanced Settings, you can change Extensions.ExtensionsPath to a mapped path and that will also do the same thing (if the version in this directory is newer than the included) and give you easier access to the extension files. Thanks, Rich

@rhessinger Thank you, Much appreciated. :)

Hi @kichikawa_2913, Could you please open another topic for the Selenium.WebDriver.ChromeDriver issue? I think that is unrelated to the authentication issue. Thanks, Rich

Hi @patchlings, No problem! We are still investigating some workarounds, but we don't have anything specific yet. We don't currently have a timeline for the .NET 5 switch. We have attempted a .NET Core transition in early 2019, but we ran into too many instability issues and scrapped it. We will wait for .NET 5 to be officially released (Microsoft says November 2020) before we attempt the switch, but it will all come down to the stability of ProGet on .NET 5. Thanks, Rich

Thanks for the update; and the upcoming fixes will certainly make it so that purging is much more efficient on the manual execution side, just in case there's an "Explosion" of executions like this. So right now, my concern is that it's "logging every sync" (once per hour), due to a sort of bug or something. Can you check what's getting logged in Infrastructure Sync? You should be able to see this under Admin > Executions, and see if you can spot a pattern? No rush. The infra sync executions should clearly show a change history of what was updated on the infra side.

It's working for us too. Thanks!

@atripp Wunderfull... Glad I could help.. Looking forward to test when it arrives :)

@valeon @miles-waller_2091 @olivier @It-purchasing_9924 @entro_4370 Took a bit, but CRAN (R) feeds have arrived https://blog.inedo.com/inedo/introducing-cran-feeds-in-proget/

Hi @gravufo, Thanks for following up. Glad to hear it is working! Thanks, Rich

Hi @Jonathan-Engstrom , Have you tried wrapping your PSEnsure inside of a with block to force everything to run as a specific Resource Credential? Example using a resource credential named AdAdminResourceCredentials: with credentials = AdAdminResourceCredentials { PSEnsure ( Key: RSHStuff, Value: True, Collect: >> $ErrorActionPreference = 'SilentlyContinue' $TargetOU = 'Users' $Value = (Get-ADComputer -Identity $env:COMPUTERNAME).DistinguishedName -match $TargetOU $CurrentValue = (Get-ADComputer -Identity $env:COMPUTERNAME).DistinguishedName ((($Value -eq $true) -and (($env:COMPUTERNAME) -match 'MyComputerName')) -or ($env:COMPUTERNAME -notmatch 'MyComputerName')) >>, Configure: >> $samAccountName = $ServerName $newOU = [adsi]"LDAP://$TargetOU" $comp= ([adsisearcher]"samaccountname=$($ServerName)$").FindOne() Write-Host $comp.GetDirectoryEntry() >>, Debug: true, Verbose: true ); } Please note that my PowerShell in collect and configure is not 1 to 1 with yours, I would replace my PowerShell script with yours in those two properties. I also was talking with one of the solutions architects on a similar Otter execution question. He suggested that sometimes it is easier to figure out PowerShell issues by running PSExec under the local system account and attempting to run your PowerShell commands that way. It will sometimes show you more detailed errors than Otter. I would try running PSExec -s powershell, which will open up a PowerShell console as the local system account, and then typing in the lines of PowerShell you have had trouble with. Thanks, Rich

I wait for the next official release. i have a workaround with disable the permission

You recommenced ADInsight previously. It is an obsolete tool that is no longer maintained. It does not work in Windows 2008 R2 nor on machines with VMWare tools installed.

Hi @arozanski_1087, That's great! I'm sorry it took this long to get this working. Thanks for working with me to figure this out! I'm going to make a change to the documentation right now to include the requirement of naming the extension file. I will also get a full release of this extension out today so it will lock in that version with the ProGet release tomorrow. Thanks, Rich

Hi @gurdip-sira_1271, Just to let you know, Otter v2022 has been released; from here it'd be best to start a new thread if you have a specific issue -- we'll be happy to help! Steve

Then we have something to look forward to, could be that we by then switched to API Keys, but the decision ain't mine. Thanks for the help and for all the RC that we got to test.

Hi @atripp and @rhessinger I gave up with the installer and decided to use the docker image. It works fine. I suggest you test the installer in the exact scenario I described above. It might cause trouble for other users. Thank you for your replies.

Hey @apxltd , Yeah having to deal with Microsoft on many different issues ourselves I totally get what you mean with this picture. I also totally understand your point and that makes sense! I'm glad the NuGet teams also push for the changes when they can. For us since everything is standardized and automated using the NuGet Restore task in our DevOps build pipelines yes it's really more convenient for us to point to our Proget Feed (thanks again for your product) and gather everything from there. We can for sure find workarounds also on our side but we had to try and contact your team as your company has been way more helpful to us than any support from Microsoft. Thanks a lot for yours and Rich`s precious time spent helping us through this issue.

Ah, I see; please note that we do not support v1 feeds (they were already obsolete when we build ProGet in 2012) and we have no intention to. Suggest you push packages from TeamCity to ProGet instead.