@theopenem_admin
Thanks! I think the inventory bug is what was causing the issue I saw - I was not seeing the deployment had happened and thought the failure was with Checkin. When I went to the Computer level and ran the commands I always ran the Checkin first, and then looked at the inventory. I assumed Checkin at group is what wasn't working, but probably had; the reality is the push had happened but the inventory hadn't updated until I ran Inventory on the Computer side.

Thank you for checking into it!

Maybe I'm missing the obvious here. I've created a couple Dynamic groups to push software, and after running "test query" and saving the Dynamic criteria, have a group of PCs that in one case were to receive Thunderbird and another to receive 7-Zip.
In both instances running the "Force Checkin" command from within the group indicates that it was run successfully, but the computers do not take the push.
If I run "Force Checkin" at the computer level, it checks in and installs the software perfectly. Do I have something misconfigured or just misunderstand what is happening here?

Edit: The same applies to the "Collect Inventory" command --works fine on individual PCs, and it says it works at group level but nothing changes.

Thanks!

@theopenem_admin
Thanks for pointing me in the right direction. There was no https binding and I'm getting that set up now.

Hi,

I'm running theopenem servers on a single Windows 10 box in my home lab and also have NGINX Proxy Manager on my network. I want to point https://toems.mydomain.com at the server and have SSL access to the Web GUI.
I can access the WebUI via http://192.168.10.50, no problem; however, I cannot connect via https on the IP or via the https://toems.mydomain.com URL.
I have verified that ports 443, 4444, and 8443 are all open in the Windows firewall, and I'm accessing the server from the same subnet so there is no filtering of the traffic.
It may be that the server is not listening on 443, but I'm not sure where to make that setting change. In the webconfig file I followed the directions and put http://192.168.10.50:8088. I'm guessing that has nothing to do with this as it is stated to be to allow communication between the SQL DB and the API server.

Any help is appreciated!