bharris1 ✭✭✭✭✭

Is there a way to disable/hide the AI button?

Have you upgraded to 2026.1.1 yet? If so, how was it? I tried to upgrade from 2024.4.1 to 2025.4.3 a few months ago and had to roll back. I was waiting for the 2026.1.1 and we have an upgrade scheduled for later this week.

They were unable to find anything because I only had the main pollers diagnostics and not anything from the WPM servers.

How did the upgrade go? Our upgrade got moved and now with 2026.1.1 out, we may just go to that version.

Did current classic dashboards change in this release or are you talking about modern dashboards in general? We still use classic dashboards with various custom queries for filtering and other things.

Thats what I tried too, but the installer would just sit and hang even after uninstalling and rebooting.

Yeah this is the first time an agent upgrade just locked up and/or failed. For .net we have both 4.8 and 8 so we were covered with .net version. The whole thing was odd almost like a firewall block, but we made no changes and when we rolled back everything worked.

Yes it does. I'm tentatively scheduling another try at 2025.4.3 for 3/10. Hopefully now that I am aware of the issues, I can quickly get through them and troubleshoot the agents if they fail again.

@u303083 will you be retrying to upgrade? I'm trying to decide whether to attempt 2025.4.3 again or try 2026.1. I'm expecting the same errors to happen again so I would probably upgrade and take diagnostics from every poller right away to allow for troubleshooting.

No I didn't. I've never disabled it or turned off auto failover since we switched to AO like 4-5 years ago. We've done at least one upgrade a year during that time and never had any issues.

Ours is in a AO group too.

Yes, my DBA and I were able to find a KB article for a similar error as we were waiting for SW support to get back to us, which was dropping the two indexes. We did that and the installer continued. As it continued, support reached out and had the same fix we already put in (dropping indexes). Halfway through the config…

@tjkru Where did you get the new version? Our service is stuck "starting" and wont finish.

I am receiving this error following the upgrade from the offline installer for 2025.4.3. Install was successful, config wizard is failing. @bmrad Error while executing script- The index 'idx_voicdrs_orgphon_id' is dependent on column 'DateTimeDisconnectUTC'. The index 'idx_voipcdrs_destphoneid_id_pkid' is dependent on…

Did you upgrade successfully? We are on 2024.4.1 and are going to 2025.4.3 as well. @u303083

Does this 2025.4.3 upgrade also appear with the offline installer @bmrad or just through the updates tab under deployment on the website?

Are there any snags or bugs that have been discovered? I'm waiting to install in our environment until it is a final release.

I'm now using this as I rewrote it to remove all passing of variables other than the server name. param( $target_value = 1, [string]$servername='SERVERNAME' ) $reg_value = Invoke-Command $servername -Credential '${CREDENTIAL}'{Get-ItemPropertyValue "HKLM:\SOFTWARE\Reboot" -name PendingReboot} $KeyValue = $reg_value…

I'm getting an error when I run mine and yours: Get-ItemProperty : Cannot find drive. A drive with the name '"HKLM' does not exist. At line:7 char:14 + $reg_value = Get-ItemProperty $reg -name $Key + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: ("HKLM:String) [Get-ItemProperty], DriveNotFoundException…

Do you have the exact script you'd use? I can't get the one I was using to work with the "Powershell Monitor"

DanielleH, can you check and make sure all of my entries counted? Thanks!

I agree. In that resource it shows that both are dependencies.

I agree - the metric listed isn't listed as an answer so I did not choose it. Other questions in past months have wanted exact answers, but apparently for this question they don't?

This would be very helpful since we are building out a new environment.

Thanks for the help. I was about to type "multi-context support', but glad I looked at the comments first.

I just noticed this too. Please let us know when its fixed.

I haven't answered yet because I thought it was poorly written as well.

Wow, I got Q12 wrong even though the hint led me to believe I was choosing the correct answer. It is very vague.

The question shouldn't have the word average in the wording. It tripped me up and I imagine will trip others up too.

I think today's question has three answers that could be correct, but only one answer matches the actual question of "staying ahead."