Hi @rick-kramer_9238 , It looks like you're using ProGet 2023? That functionality was relatively new in that version and there is very possibly some kind of bug linking the two together. We've since made some big improvements to SCA/compliance, so I would recommend upgrading. Many of the changes were in ProGet 2024: https://docs.inedo.com/docs/proget-upgrade-2024#new-features-in-proget-2024 -- Dean

@rick-kramer_9238 I added the default source as the nuget feed instead of https://proget.corp.com. Seems to be working now.

Hi @rick-kramer_9238, You could do this via the API; it would involve first Querying Package Versions, and then for each version returned, Setting Package Status. I think it'd be a "relatively easy" script to write - so if you create one that can do it, please share :) Hope that helps, Alana

If you're using Chocolatey at a version lower than 2.0.0 then there was only NuGet v2 support. Since 2.0.0 we've added support for NuGet v3. We also send chocolatey cli in the headers of the request, so you would be able to monitor the traffic and determin which traffic is originating from that tool. But as others mentioned, you wouldn't be able to determine much from the ProGet side.

Hi @rick-kramer_9238, I'm really not sure what the underlying issue is or how to troubleshoot :( NuGet dependency resolution is really complicated, and what you're saying is probably related. If you get a "package/version cannot be found" error from the NuGet client, it doesn't necessarily mean that the version isn't there... jsut that the dependency search wasn't successful. You can just look at the ProGet server to see what packages/versions are there. If it's in the UI, iut will be in the API. Cheers, Alana

@stevedennis I swtiched from "V3: Active Directory (LDAP)" to "V4: Active Directory/LDAP (Preview)" and all is good now. Logon went from two/three minutes down to one second.