Hi @Ashley, I can confirm that F7\._proget_file_history_ is specific to the Feed with an ID 7. Thanks, Rich

Hi @carl.westman_8110, I ran a test against our test Dev Ops instance. I created a connector and I used basic authentication with my Microsoft account username (my email) as the username and the PAT as the password. I found it was finding my package, but ADO's simple API was not returning the file list which is causing our connector to skip over it. We are currently investigating this further. As a work around, have you tried importing those packages into your ProGet feed? You can do that by using Import Package -> Download Package from Another Source. That will allow you to import all the packages and version from your ADO artifact feed. Thanks, Rich

Hi @Nils-Nilsson, we were facing similar issue maybe 2 years ago (I am not even sure if pgutil was available at that time). There may be other approaches besides pgutil. ProGet exposes native APIs, but not all features are enabled by default; some aspects can be modified directly in the database. The native API is visible at: https://<ProgetServer>:<port>/reference/api FeedGroups APIs [image: 1791188466717-48fdf5f8-ccce-44da-b858-e625d4494986-image.jpeg] The Enabled features can be checked in the following table (we are using an MS SQL database): __StoredProcInfo Internal_Indicator shows what is exposed and can be used. We set Internal_Indicator = 'N' for the APIs (stored procedures) that we want to use for our automation purposes. Kind regards Ivan

Hello @gdivis I've tested the new release and can verify that it now works as intended :) Best regards Nils Nilsson

Hi @stevedennis, I appreciate the reply but I will be honest and say it doesn't really make any sense. To my knowledge I'm not using docker desktop for this feature. I installed WSL on my machine and I'm assuming it is using that. One of the things I learned in this process is that docker desktop doesn't allow the same command line usage that WSL does. I still have Docker Desktop as well, but I'm using that for running the results of what BuildMaster is building, not anything BuildMaster itself is doing. As far as the Id command and git, I've always had git installed. Apparently the directory with that utility is not part of the normal path. There is another directory in the install of git that is part of the path but it doesn't include the Id command. I just added the other directory to the path manually. Either way, the question I was trying to get answered was regardless of my set up, what is the requirements for someone trying to use this feature as expected. From my digging the Inedo code is trying to run a Linux command (Id) on the box hosting the agent (not a docker container). The code is trying to get a user to apparently use in running the docker command. This is where I was hoping you or someone at Inedo could fill in the gaps. I just want to be able to tell my company that if they want to use that feature should the have an agent running an Linux box (VM or a real one). Good news is I at least proved it "can" run on a windows box. Thank you, Brandon

Hi @hardik.turakhia, Using nginx as a reverse-proxy in front of ProGet is definitely the easiest way. I'm guessing you already took a look at our example nginx config file. When it comes to certificates, I find that it's easiest to use .pem files on Linux. There are a lot of guides out there on how to convert certificates to .pem files and configure them in nginx. The best source is to check with your SSL provider on how to create a fullchain (includes the intermediate certificates) .pem file. We do have some notes in the HTTPS on Windows guide in the update config section that has some commands on how to convert a .pfx file to .pem, which includes some crossover with converting .crt files to .pem files. If you are planning to use a dynamic SSL provider like Let's Encrypt, certbot has an extension called certbot-nginx on most distros or via snap on ubuntu/debian distros. That will configure nginx for you. Thanks, Rich

Hi @sai.pabbareddy, If you could pull a full LDAP trace/packate capture that would be great. I also setup a single-domain/single-dc. I can even share my setup as I used a VM and docker to set it up. My VM is a base alpine install with docker, docker-compose, and nano installed. Here is my the compose file I tested with. NOTE: my container uses the host network mode because that was the only way I could get it to bind the port in Samba. This is probably not needed if ProGet sat in the same Docker network as the Samba container. version: '3.8' services: samba-test-ad: image: diegogslomp/samba-ad-dc:latest container_name: samba_test_ad hostname: DC1 privileged: true network_mode: host environment: - REALM=PLANETEXPRESS.COM - DOMAIN=PLANETEXPRESS - ADMIN_PASS=GoodNewsEveryone123! - DNS_FORWARDER=8.8.8.8 # NOTE: "ports" was removed because network_mode: host opens the container ports on the host natively samba-provisioner: image: alpine:latest container_name: samba_provisioner depends_on: - samba-test-ad # Shares host network context to communicate with the main container smoothly network_mode: host volumes: - /var/run/docker.sock:/var/run/docker.sock entrypoint: - /bin/sh - -c - | apk add --no-cache docker-cli echo "🚀 Monitoring Active Directory operational readiness..." while true; do if docker exec samba_test_ad /usr/local/samba/bin/samba-tool user list >/dev/null 2>&1; then break fi echo "⏳ Samba is compiling directory tree schema... checking back in 3s" sleep 3 done echo "🔌 Active Directory Engine Online and Accepting Modifications!" echo "--- Creating Test Groups ---" docker exec samba_test_ad /usr/local/samba/bin/samba-tool group add ship_crew || true docker exec samba_test_ad /usr/local/samba/bin/samba-tool group add admin_staff || true echo "--- Creating Pre-populated Test Users ---" docker exec samba_test_ad /usr/local/samba/bin/samba-tool user create fry FryPassword123! --given-name='Philip' --surname='Fry' --mail-address='fry@planetexpress.com' || true docker exec samba_test_ad /usr/local/samba/bin/samba-tool user create leela LeelaPassword123! --given-name='Turanga' --surname='Leela' --mail-address='leela@planetexpress.com' || true docker exec samba_test_ad /usr/local/samba/bin/samba-tool user create professor ProfPassword123! --given-name='Hubert' --surname='Farnsworth' --mail-address='professor@planetexpress.com' || true echo "--- Assigning Group Members ---" docker exec samba_test_ad /usr/local/samba/bin/samba-tool group addmembers ship_crew fry,leela || true docker exec samba_test_ad /usr/local/samba/bin/samba-tool group addmembers admin_staff professor || true echo "✅ Active Directory data successfully populated! Setup complete." Then for my ProGet configuration, I created a new V5: Active Directory and here were the settings: General Name: V5: Samba 4 Domain: planetexpress.com User name: Administrator Password: GoodNewsEveryone123! Connection Domain Controller Host: <IP Address of my VM> LDAP Connection: Use LDAP Then I tested using Load user by username for the user fry in the group ship_crew. For recursive groups I used the user Administrator and the Group Denied RODC Password Replication Group. Then I added ship_crew to the Administer task and I logged in using fry/FryPassword123!. Thanks, Rich

@atripp Hi Alana, Thanks for the clarification!

Hi @amy.j , Without a reliable publish date, there's no reasonable way to rely on an automated compliance rule that relies on the publish date. I would recommend developing a Maven-specific approach, since this feed type is so limited. You've probably noticed it already, but license detection is also not very reliable. But, I wouldn't worry too much about it. Keep in mind: the Java ecosystem seems to publish much less frequently than JavaScript there are fewer transient dependencies in Java version ranges tend to be less popular and much more conservative Also there seems to be an issue with pulling in certain jar files, eg, when org.springframework:spring-webflux 6.2.19 is promoted no jar file is listed - so cannot be consumed. This has happened for a few packages. This is probably related to that unreliable Maven Index file. The Maven API does not support "file listing", so there's no automated way to know what artifacts are contained within a particular release. You just "kinda know" by reading the project's release notes, etc. Early on, we just "assumed" there would always a .jar file, but I guess that's not the case because there are .war and .ear files too. We also considered parsing the web-based file listing page (e.g. spring-webflux/6.2.19, but a lot of repositories don't provide a listing. We're open to ideas, but it's just an unfortunately limited ecosystem. Thanks, Alana

Hi @sai.pabbareddy , Those are both "packages" that contain the same kind of license (ProGet Enterprise). A single ProGet Enterprise license will allow you to configure a ProGet instance as a HA/cluster. "Enterprise Essentials" contains ONE license of ProGet Enterprise and no services "Enterprise Complete" contains TWO licenses of ProGet Enterprise plus services Organizations will often get two licenses of ProGet Enterprise to create two different environments (one Production, one DR/Testing/Training). Hope that helps clarify :) Thanks, Alana

We've scheduled PG-3386 to resolve the slow multi-build analysis on Postgres. It will be included in ProGet 2026.12, which is scheduled for release on Oct 2.

Hi @amy.j , This package is a bit weird in that (1) it uses a file-embedded licenses, (2) there are 172 contained files, and (3) some of those files don't follow standard naming conventions. When those things happen, I think we get results like this. The easiest way to work-around this is to just assign a license directly to the package using the Purl (i.e. pkg:pypi/charset_normalizer@3.5.1). You can do that by editing the MIT license type. Thanks, Alana

Hi @forbzie22_0253, Unfortunately, this is still required. By default on Windows, HTTP.sys reserves all ports below port 1024. The netsh http add urlacl url=https://*:443/ user="NETWORK SERVICE" tells HTTP.sys that NETWORK SERVICE can register port 443 and listen to all traffic on it bypassing HTTP.sys. If you specified a domain, https://my-domain.com:443 instead of https:://*:443, then HTTP.sys will handle all traffic but will allow NETWORK SERVICE to subscribe at that domain. HTTP.sys will still handle all traffic though. That will then cause the integrated web server (IWS) to use HTTP.sys instead of Kestrel, which is why we recommend the port binding method. This is all outside of IIS. That reason is also we added documentation on how to Use IIS as a reverse proxy. Hope this helps! Thanks, Rich

Hi @joris.guex, Sorry for the delay - I've been out of the office for a bit. I've logged this as PG-3379, scheduled for the next release of ProGet 2026.12 on Oct 2. I haven't looked at the code yet, but it should be another trivial fix to bring this fully up to spec. Thanks! -Greg

Hi @sai.pabbareddy, Glad to hear it all works as expected! Thanks, Rich

Hi @sai.pabbareddy, My apologies. Looks like I typoed the date on that other post. I had the day of Friday correct, but the date should have been Sept 18, 2026. It will be releasing later today (normally in the evening in EST). I updated that response also to have the correct date. Thanks, Rich

@rhessinger Thanks.

@atripp , Thanks for the info.