Topics created by luke.duddridge_1525

It was generalized to use ProGet's API keys which have more granular security options: https://inedo.com/support/documentation/proget/feeds/nuget#nuget-api-key

If it's an "active" DR (i.e. the servers are running, it's used for testing purposes, etc) then each server would require a license. If it's something like, a snapshot of a server (and isn't running... but could be as soon as production goes off), then you can use the same license. It's similar to a lot of Microsoft (and other vendors) licenses for non-production environments.

I have renamed the roles just incase, but as soon as I upgrade to 4 it appears I get knocked out of the necessary task groups. Your user account does not have the Admin_ConfigureProGet task. I also get the same message if I don't change the role names.

Please note the privilege changes in v4: Upgrade Notes for ProGet 4.0

Hi Luke, you'll want to put the connection string in quotes: bmdbupdate UPDATE /conn="Data Source=DB1;Initial Catalog=ProGet;Integrated Security=SSPI;User ID=Account;Password=Password;" We'll try to add that to a new version of the database updater! Cheers!

It's hard to say... 3.6 was almost a year ago, and I know the npm api/format specification has likely changed since then. So, it could be a related to that...