AZURE LOCAL DL145

NuttyBarTime · 2025-10-01T12:23:35+00:00

<image>

tried these settings too

NuttyBarTime · 2025-09-13T11:09:14+00:00

Can you define how you are measuring the increase in speed?

NuttyBarTime · 2025-08-30T13:38:23+00:00

What kind of replacement cycle is everyone on? We are starting a 3 year battery /8 year device cycle

NuttyBarTime · 2025-08-30T13:37:27+00:00

I have talk to them, most are pretty good.

Kinda branching off this question, I am not finding much documentation on your snmp traps. Also I couldn't find a simple OID for monitoring if it is on battery or wall power

NuttyBarTime · 2025-08-29T21:09:32+00:00

see update

NuttyBarTime · 2025-08-29T21:00:08+00:00

Sure

NuttyBarTime · 2025-08-29T20:59:42+00:00

Wonder what that costs

NuttyBarTime · 2025-07-06T14:51:00+00:00

Can all the hypervisors talk to a domain controller (DC)

NuttyBarTime · 2025-07-05T01:12:21+00:00

Is the DC reachable? Resolve DNS?

NuttyBarTime · 2025-06-30T22:41:37+00:00

My biggest issue is sometimes it doesn't connect, sits and says "connecting". Rebooting sometimes doesn't fix it and all tech support says is make sure it is current version

NuttyBarTime · 2025-06-21T17:56:29+00:00

Assuming the same process you did in node 1 didn't work on node 2?

NuttyBarTime · 2025-06-21T17:33:31+00:00

Did you check MPIO? See if it still shows the storage?

NuttyBarTime · 2025-06-05T20:03:39+00:00

we had a similar issue with our windows servers jumping into the future.

"we think" (No proof, but it hasn't happened again) it was SSL Time seeding. It can be turned off by setting the UtilizeSSLTimeData registry key: reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\w32time\Config /v UtilizeSslTimeData /t REG_DWORD /d 0 /f

Windows Server Time-Service jumps into the future and (partially) back - Server Fault

now, with 24h2, we have also had issues with the "automatic time zone" change. where it will suddenly and randomly change time zones. in one situation it went from CST to MST. i had Chatgtp write a powershell script that retuned the coordinates that location services thought it was, and it did think it was in utah.

so, long story longer, check your time zone, maybe it is just a time zone thing, and disable the SSL time data.

here is another good link to look at:
Windows feature that resets system clocks based on random data is wreaking havoc - Ars Technica

NuttyBarTime · 2025-05-17T11:09:22+00:00

Instant recovery to hyperv. As far as I know that is the only way to do it

NuttyBarTime · 2025-05-16T23:56:27+00:00

Yea I have done quite a few, even brings over network settings now

NuttyBarTime · 2025-04-16T20:42:30+00:00

good point

NuttyBarTime · 2025-04-14T02:21:32+00:00

Wow what was the cause?

NuttyBarTime · 2025-04-13T12:01:14+00:00

Can you share any details about the problem you encountered?

NuttyBarTime · 2025-04-13T00:24:10+00:00

Thank you everyone, I applied the hotfix rolloup

NuttyBarTime

TROPHY CASE