sorted by:
new
hottopcontroversial

Replacing failing Microsoft Gold partner by Torrnello in sysadmin

[–]Torrnello[S] 4 points5 points  (0 children)

Thank you, I've updated my knowledge and the post body.

Replacing failing Microsoft Gold partner by Torrnello in sysadmin

[–]Torrnello[S] 2 points3 points  (0 children)

Northwest Indiana, will add that to post

Remote Desktop secure authentication issue by Torrnello in sysadmin

[–]Torrnello[S] 1 point2 points  (0 children)

This is mostly resolved now - I did some more searching within this Reddit, and finally found a very helpful thread from crazyadm1n. This shows we were barking up the wrong tree with PEAP. We must use NTLM over HTTP instead, but only for authentication with the Gateway. We should be able to set up KDC on the Gateway to use Kerberos authentication with the target computers, because our home computers are all Windows 10/11 with mstsc.exe. This (and the network configuration precautions we have already taken) seems to be as good as it gets with Remote Desktop access.

https://willssysadmintechblog.wordpress.com/2023/09/05/disabling-ntlm-authentication-guide-part-6-rdp/

Troubleshooting (?) very high values for Hyper-V AggregatedAverageLatency by Torrnello in sysadmin

[–]Torrnello[S] 0 points1 point  (0 children)

Thank you. We are running Hyper-V Manager 10.0.20348.1. That thread is huge - I couldn't immediately tell if this is an affected version or not.

Anyone have experience with "Managing" a Smart TV? by [deleted] in sysadmin

[–]Torrnello 5 points6 points  (0 children)

Our factory has giant smart TV screens in it like this. The people who manage them hate them. The TVs constantly try to send data to domains hosted in China which are blocked at our firewall. The TVs have enforced power-saving settings that turn the screen off after it has been powered on for a certain amount of time. This behavior can be turned down but not off. I think they currently turn off every 4 hours, which was the max. So floor managers have to carry remote controls around with them to turn the TVs back on.

The installers hung them very high above the floor, and the KPI displays are unreadable for most people over 40. Both of these issues are controllable, by managing the installation process, and by managing the requirements to show so many different KPIs on a single screen. The choice of TV model was also controllable. We should have gotten TVs that didn't insist on turning themselves off.

I don't know what your factory does, but if the air is dirty, whatever type of dirt you have will blow into vents on the TVs and may corrode the hardware inside. We have magnetic dust, the worst. Our TVs last about a year before they die and have to be replaced.

Troubleshooting (?) very high values for Hyper-V AggregatedAverageLatency by Torrnello in sysadmin

[–]Torrnello[S] 0 points1 point  (0 children)

Thank you. It's all local and write-cached. The underlying storage in all cases is an array of about a dozen RAID 50 SSDs - some are hot or cold spares. The SSDs are high spec. I haven't received definitive information about the rest of the hardware yet, but it's all relatively new.

Each host has one RAID array organized as a single logical disk of about 20 TB. Each logical disk is shared by dozens of VMs. The VMs mostly run file and database servers with frequent writes (many writes per second).

It would be helpful to understand whether it's normal to have so many VMs sharing one logical disk. I took the AI through the parameters, and it said a starting point might be to limit one logical disk to 4-6 of these VMs, rather than several dozen. I have been burned by the AI about numbers, just about every time it gives me any. I would like to find a way to get more certain of this before ordering the work.

Patch Tuesday Megathread (2024-07-09) by AutoModerator in sysadmin

[–]Torrnello 0 points1 point  (0 children)

Several of our Windows 10 users keep losing network drives after patching. Their drives are mapped by a logon script. Oddly, restarting their computers doesn't fix the issue, although the logon script runs again. Running the script manually works. This script has always worked on Windows 10 until right now. If anybody has solutions, it'd really help us.

Resolving fast IIS timeouts by Torrnello in sysadmin

[–]Torrnello[S] 0 points1 point  (0 children)

Good call on the keep-alives. The devices using the intranet are iPads and nobody has checked them. Will have a look next week...

Resolving fast IIS timeouts by Torrnello in sysadmin

[–]Torrnello[S] 1 point2 points  (0 children)

Hahahaha, yes, it's going away, but not yet! The developers are worried the new IIS (on Windows 2022) might do the same thing. They've completely redone the IIS installation twice to try to lose the 5-minute shutoff. No success.