With any versions of ProGet – from free to Enterprise – you’ll be able to access the repositories but scaling down from Enterprise to basic, or basic to free , you'll lose access to license filtering, feed-level user privileges, and other benefits that many users have come to enjoy, depend on, and take advantage of throughout their use of enterprise or basic ProGet. Very rare are there cases folks want to lose those features but if it's necessary, your team will still be able to access the repositories. Take a look at the full break-down of features and benefits per version here: http://inedo.com/proget/pricing/features-by-edition

I was able to get this working. I had to change the license key to something else and save it, then change it back to the proper key and save it again. Once I did that, it asked me to manually validate.

Hi Stephen, Although we don't offer reseller discounts, we are happy to (and often do!) work with any software reseller. If you have an approved reseller on your list, chances are they have already purchased from us before... and if not, we make it very easy. They can just submit a purchase order to us (or start by requesting a formal quote), and we will go from there. Does that help? best, Alana

Although we do not provide a reseller discount, we do work with quite a few software resellers who purchase on behalf of their clients, as those clients prefer to have a single source for all procurement. If, as a reseller, you purchase directly from the MyInedo portal, just contact us with the end-user information, and we will update the licensing information. You can also submit a quote request as needed.

ProGet is licensed per server, therefore this scenario requires 2 licenses. I believe the FAQ you are referring to is for one of our other products BuildMaster that is licensed per user, which allows the same key to be used in test instances.

Yes, but note ProGet is licensed for each server it's installed on, so if you keep both servers active, then you'll need an additional license.

As of BuildMaster 4.9, many of the restrictions in the express edition have been removed. #####Features Available Only in Enterprise Edition (4.9 and later): Enterprise Support Active Directory / LDAP Integration #####Limitations of Free Edition (4.9 and later): 5 Users 10 Applications 5 Servers The following information is outdated, but remains for users of older versions. #####Features Available Only in Enterprise Edition (4.8 and earlier): Enterprise Support Active Directory / LDAP Integration Automated Promotion Requirements Change Controls Configuration File Templates Database Change Script Deployer Deployable Dependencies Group-based Approvals Multiple Active Builds Scoped Privileges Server Groups/Pools #####Limitations of Free Edition (4.8 and earlier): 5 Users 10 Applications 1 Automatic Build / application 1 Configuration Files / deployable 1 Database Connection / environment & application 3 Deployables / application 1 Workflow / application 3 Environments 1 Imported Deployable / application 2 Issue Trackers 5 Servers 3 Source Control Providers

Hi Dan, we don't offer any additional pricing options; although we do provide licenses for free open-source projects.

It looks like that was a holdover from when it was copied from the BuildMaster licensing page :/.... It should say: If you would prefer additional terms or an otherwise customized license agreement, we are amicable to negotiation for sales of 5 or more server licenses. From: http://inedo.com/proget/license-agreement

BuildMaster Enterprise is licensing on annual or perpetual/lifetime basis. If you purchase an annual license, then you'll receive a key that will active the software for a year, and we will provide maintenance/support during that period. To continue after the first year, you'd have to purchase another license. If you purchase a perpetual license, then you'll receive a non-expiring key and a year of maintenance/support. You can renew support/maintenance after that, but the software will work regardless. Hope that helps.

If you look in the Service subdirectory of the BuildMaster installation, you'll find BuildMaster.Configuration.AdminTool.exe which can clear the set of licensed users. Since licensed users are added back as soon as they log in, that should be all you need.

Hi Tim, BuildMaster is licensed on a "per team" basis, so each user who accesses BuildMaster needs to have either a full or limited-access license. You can reassign users as needed, but not to workaround licensing policies. Hope that helps, Steve

Thank you. The server was activated fine and is working very well. I am satisfied.

BuildMaster is licensed to named users who can be managed at any time within the software itself. In our Enterprise Edition we also offer User Classes, which permit only the necessary functions in the BuildMaster software for certain users. For example, your workflow process may require that managers sign-off on a build before it is promoted to the Production environment. The only operation the manager will ever perform in BuildMaster is that approval; therefore, you may purchase an "Approval Only" license at significantly reduced cost for this user.

From a licensing standpoint, a "user" is simply someone who has access to and uses the functionality of BuildMaster: whether that's designing deploying plans, kicking off new builds, or analyzing data. That being said, BuildMaster is designed (and priced) to be used by the entire development organization. The reason is that we believe everyone involved in development should be involved in (or atleast aware of) the process, not just those on a Change Management team. While you can buy as few licenses as you'd like, there's a lot less value when only a small group has access