jholmes · Senior Network Engineer · ✭✭✭✭✭

Hi, there is an issue in UDT where you can't remove Windows Nodes without a SQL Query. Officially SolarWinds asks you open a support ticket. https://support.solarwinds.com/SuccessCenter/s/article/Remove-a-node-from-UDT?language=en_US However the query below has been used by other users to do so, I always advise you backup…

I can't think why your type of license (Node or Application) would come into play unless you're already at your limits of how many applications youre monitoring. 

Hello! You would need to apply the built in MSMQ monitoring for the server, specifically the "Bytes in Queue" component. Then you should be able to create a component alert based of the Component name and values returned, go through the Alert creation wizard, make sure to change the dropdown from Node (default) to…

You should look at CPU/Memory on your Primary server, if its high see what processes are high and move into it from there. Also make use of your APE's when you look at the Polling Engines Page in the webconsole try to get as many elements onto the APEs and off the Primary as you can, don't go over 12000 elements/8000 SAM…

Yeah the scanning overall is working, you may have other issues pending on how the subnets are setup or if the IP's aren't reachable from a particular Poller. Its just a matter of if something doesn't look right start checking through the process to figure it out. I typically would do the below to verify. 1. Try to ping…

Point of clarification on this thread, IPAM doesn't consider if your DNS server has a record as a way to verify if an IP is available or not it only gets status through DHCP (there being a lease time), Neighbor Scanning or ICMP sweeps. Your ping seems to target the Hostname see if when you Ping the IP does it return a…

I think youre asking to look for the query being used for the widgets. For this doing the below has helped me in the past its not the cleanest but it gets the job done. 1. Hit f12 and go to the Network Section of the browser console that pops up. 2. Refresh the page. 3. The various Queries will be on the left normally…

I agree with your assessment, I ended up going with All Nodes - Tree and filtered with Status != 1 then used the default grouping by status which got what we wanted. the custom table resource didn't let the nodename link which was required. 

I would add to this if you moved the installer over from another machine make sure its not set as read only, also if its on a network drive to move it to a local drive and once again make sure that doesn't set it to read only. 

Update: Hello Everyone, got it figured out by instead of adjusting select statement using additional where clause. SELECT [data].[DisplayName] AS [DisplayName], [data].[Status], [data].[Interfaces].[FullName], [data].[CustomProperties].[A], [data].IPAddress, [data].[CustomProperties].[B], [data].[CustomProperties].[C],…