[djww]

Doesn’t look like I will be able to use this on my DMZ hosts as I have tried everything in the two links you provided and still to no avail (opened port 135/445 with full access inbound and out). But when the system hosts it on itself it works fine so I know it is not the WMI providers but a firewall issue, but this is a government office and government firewalls are the worst. I will not be able to modify the firewall any further than i have already done. Unless you have some other idea what could be causing this im lost. Or maybe a work around ? which in turn means we wasted money on the product and wont be using it at all in the future. If it cannot work on all of the machines then it is not viable at all.

[djww]

I just ran some tests in solarwinds on the three systems (there is a WMI diagnostics and repair tool built into it)(it also uses WMI to push patches) and it passes with everything on all 3 servers at this point I think it has to be a port that is not opened for BP to get through to the DMZ.

Other programs use WMI function properly without errors. All WMI services restarted and checked for functionality. WSUS / Solarwinds both patch these systems without fail and WMI is used for SW. DMZ systems report back to WSUS properly and BP is on the same server. This is not a WMI problem the more i look into it. It is a DMZ/BP problem.

[djww]

I just installed this yesterday and started using it and I will say when i click on a job queue and tell it to push to say 30 servers it takes about 45 seconds before i can click anything on the screen. then it catches up and all of the jobs start working. This is on a 16core VM with 64gb of ram on a SSD fast disk shelf netapp running server 2016 aka my WSUS server. Hardware is not the issue here. But I definitely see a “not responding” type action after initiating a job from the job queue.

[djww]

I need to add that all of the DMZ hosts are built on the same template as my non DMZ hosts, and other items use WMI to function (we were using solarwinds to patch prior and it uses WMI) so i know the WMI is working properly.

This is on server 2016. I ran the WMI diagnostics tool and i am not getting any errors.. Any ideas?

[Author]

Posts