An administrator must log in and run the ProGet.Service.exe executable and reserve the URLs you are using, which will also require a system restart before it takes effect.

Most likely, the user that ProGet is running under is having difficulty requesting this information; you can try to restart the ProGet service, or the WMI service, and if all else, just reboot the server.

ProGet logs all errors to its error log or indexing errors log in the software itself, otherwise to the Windows event log. You can test by running the service (and/or IIS app pool) as your account if you're certain that your account has enumerate privileges.

Looks like a bug; IIS detection does not work on 2012 unless 4.5.1 is also installed. Will be fixed in maintenance release, but you should install 4.5.1 anyway since it has a bunch of bugfixes.

Thank you. I have replaced the contents of the WebApp and Service folders with the contents of the 3.1.0 manual installation zip file (except the config files of course). This seems to work as well. I think it is more or less the same effect as what you did by uninstalling and reinstalling, although your method is probably a bit safer! Luckily the database schema doesn't seem to have any updates in 3.1.1 that means it doesn't work with 3.1.0.

I installed ProGet 3.1.2 today and the errors I experienced with 3.1.1 are gone. Thanks for the quick turn-around on the fix, you guys are great. Riko

Does one of your embedded scripts contain a reference to a module that doesn't exist on a remote server, e.g. Web Server Administration for IIS? Unfortunately the error returned by PowerShell is fairly useless in determining which exact module is missing :)

Thanks for the report - I'll have a dev take a look at this and fix it for the next version, which should hopefully be out today (8/14/14).

Curious, what versions of PowerShell do you have installed on the machine with the ProGet service, and also on the remote machine?

Thank you for the report - this will be fixed in the maintenance release coming out today (v3.1.1)

Looks like Chocolatey now requires the description field to have a value, whereas pre-v0.9.8 it did not require one. We've updated the editor for v3.1.1 to require a description, though this will not impact existing data, so you'd still have to edit existing descriptions so that they have a value.

It's unlikely this will be supported. There is no way to identify from metadata a symbol package vs a regular package... you have to open the zip file and see if it contains pdb/src files... which means we'd have to download every version of every package in a remote feed. If Microsoft / NuGet team ever implements a mechanism for identifying , then it's a possibility.

We will be adding a few fixes to help with retrying after indexing issues in the next maintenance release, as well as some more logging to figure out what is going wrong in these cases. Long term, we will also be redoing a lot of the indexing logic to eliminate these types of problems (but that probably will happen in a minor/major release.)

In this case, the web server user simply doesn't have permission to query the service status. You can ignore this message or increase the web server user's privileges.

At the moment, I'm not able to update our server. I do it later. I will also test with your refernced packages in a test project. Thanks a lot.

We can now support 99% of our clients using the Network Credential Manager. Only one edge case, as discussed with Alex, is still outstanding. We will address that by customising the code in the near future.

Thanks - somehow I missed that in the docs before. I will add this as an open issue (PG-221).

Hi Simeon, Windows XP is definitely not going to be a reliable server :) The TCP stack is deliberately throttled/crippled to prevent server usage.

As of 3.1: Active Directory / LDAP Integration Filter Packages by Name & License Load Balancing & High Availability Granular Privileges & Security

Thank you for the report - I have confirmed this particular page is validating the privilege at the system level instead of the feed level, we'll have it fixed in the next maintenance release.