in between

2025-Dec-28, Sunday 09:24 am
mellowtigger: (possum)

Minneapolis seems to be in the lull before a storm. Our weather prediction includes, "WINTER STORM WARNING REMAINS IN EFFECT FROM NOON TODAY TO 9 AM CST MONDAY" (emphasis in the original, scroll down to bottom). I see snow falling outside my bedroom window right now. That's good. The forecast was rain first, followed by snow, which would cause terrible ice conditions on sidewalks and roads for everyone. Only-snow is much better for everyone. It's still 2.5 hours until that noon arrival time.

I'm currently in between shifts of work today. Most people at the university have 1.5 weeks away from work. I, however, work on an "essential" team, so we have a skeleton crew during that time. We were actually and truly closed only on Christmas Eve, Christmas Day, and New Year's Day. I volunteered for shifts on Friday, Saturday, and today. If nobody volunteers, then somebody gets told to work, which is unpleasant stuff for the holidays, so... I volunteered on several shifts that were still empty.

I'm supposed to do an annual review of my Bingo 2025 card. I planned on it. I'm not sure that's going to happen. The thing about this job, where I'm constantly asked questions for which I don't know answers but have to find them on short notice, is that I don't have mental bandwidth to spare for other stuff after the work day has ended. I haven't done my annual tax review in a few years, for instance. It requires more thinking that my tired brain wants to avoid in favor of not-thinking to recover stamina.

I'll still do a Bingo 2026 card, though. I find it very useful to avoid stressful topics for a year. I'll continue that practice. Maybe I'll write more on that idea tomorrow.

a short update

2025-Dec-16, Tuesday 04:16 pm
mellowtigger: (sleepy)

You'd think that we'd be less busy after finals week (last week), but no. And I was short on sleep Monday morning, for no good reason. I wasn't even playing games, as that at least would be productive. :D

So after work on Monday, I crawled in bed shortly before 7pm and woke up shortly before 6am Tuesday. That's why there's no Moody Monday post, despite the wealth of material.

I'm much better rested today, but it's still busier at work than I expected for this pre-holiday week between semesters. I don't often get opportunities for "nice" (warm fuzzy humanitarian) things to do for people. Usually, I'm the bad guy who quotes the rules. But today I was able to help a shivering student get back into their warm dorm after they busted their phone, rendering many things about their account (including door access) inoperative. Lots of security vetting, then lots of steps for account repair with the student, and all should be well (and warm) for them again.

It's simultaneously impressive and worrisome how essential a smart phone is for anything and everything these days. And we generally only have one of them at a time. Woe unto ye who break your own horcrux.

busy day

2025-Dec-01, Monday 04:17 pm
mellowtigger: (possum)

Normally, my team working on 40-50 tickets per hour is a respectable pace. About 2.5 years ago, during the semester start of the worst semester of workload at my job, we crossed 100 tickets per hour a few times. That experience was awful.

Today, I saw 85 tickets per hour once, and 70+ tickets per hour at 2 other times. That, plus we had about 1/3 of our full-time staff out for vacation or sick leave, so the workload was higher for those of us who remained. It was a very busy day.

I had other topics planned for Moody Monday discussion, but I don't have the mental bandwidth for it now. If I had any booze in the house, I'd be drinking it. I may still dress warm and walk to the store to buy some. Despite marijuana being legal in Minnesota for 3 years already, there's still no widespread deployment yet. Too bad, since if I had any edibles in the house, I'd be eating that too. This article talks about the slow rollout here, and it even mentions firefighters as another group of workers needing edibles to make their brains stop rehearsing the stressors of the day.

RIP Get-EventLog

2025-Nov-15, Saturday 07:37 pm
mellowtigger: (penguin coder)

Today at work, I wanted/needed a faster way to collect particular events in the Microsoft Windows event logs. I had the obvious way to collect them from the gui, but I needed something better. I decided to try powershell.

Click to read the powershell code and follow the small adventure...

I had no idea beforehand that the log source name in the gui is different from the one accessed by powershell. It took some googling to figure out the right mix of parameters and clauses, but it worked. Sort of. Here's the code I came up with:

Get-EventLog -LogName System -Source Microsoft-Windows-Kernel-General -After (Get-Date).AddDays(-10) | Where-Object { $_.EventID -eq 1 -and $_.CategoryNumber -eq 5 } | Out-GridView

It definitely found the appropriate events from the log. It did not, however, provide the appropriate message about the reason for the log entry. Instead of the rational reason that the gui showed me, this script was telling me:

Possible detection of CVE: 2025-11-15T20:31:07.5402125Z
This Event is generated when an attempt to exploit a known vulnerability (2025-11-15T20:31:07.5402125Z) is detected.

Whoa. That sounds bad/dangerous. After digging into other properties of the software object I was given, I finally noticed the purple note in the official Microsoft documentation that this command has been deprecated! Argh! I was probably getting CVE-similarity notices because I was still using this deprecated 32-bit command. I am old, and what I formerly knew is now contraindicated. *laugh*

I switched to the new powershell command, and it again took me a while and several consultations with Google to hammer out the new (and actually better) command:

Get-WinEvent -FilterHashTable @{ProviderName='Microsoft-Windows-Kernel-General'; Id=1; StartTime=(Get-Date).AddDays(-10)} | Where-Object { $_.Message -match 'Change Reason:.*time zone.*' } | Select-Object TimeCreated, Message | Out-GridView

Finally! This new powershell command shows the correct reason for the log entry and the directory path to the program that produced it. That's exactly what I needed. Yay, although I'm clearly out of practice with powershell. After collecting data, I opened a ticket to have our next tier of IT take a look at my computer and find why this particular event keeps showing up. Something is changing my timezone (to the wrong timezone) throughout the day, even after I manually change it back to the correct timezone.

mellowtigger: (Pride)

Just 24 hours ago, I knew exactly what I was going to write about today for Moody Monday. Now, though, so I've seen so many things that it's hard to choose what topic to mention.

Like the Amazon internet outage that took out much of the internet for most of the day, including where I work. My first tech support phone call this morning was from the main in-person test center on the biggest campus. They called to report that multiple students were unable to work on quizzes in multiple courses. I confirmed it wasn't just them, the images in exam questions weren't loading for me too. Within an hour, we knew just how widespread the problem was across the USA. Eventually, the entire Canvas website (used for coursework and quizzes) itself was down, affecting universities around the globe. At least we got a semi-funny picture from their Canvas website about the outage, pictured in this news article. Eventually, our phone system was also affected, with me losing a caller mid-sentence then unable to call them back. I had to take my lunch almost 2 hours early, during a period that phones were simply not operational, because we anticipated the rush of calls when we would need "all hands on deck" when service resumed later. It was a frustrating day.

Even more important to me than the estimated 100s of billions of dollars in lost productivity, however, is the attempted bombing of one gay ice cream store here in Minneapolis.

There's a paywalled news story here. Before the paywall kicks in, maybe you can read some of the context and see a photo of the giant flag hanging on the front of the building that probably prompted the attack. If you can't see the flag there, then you can view it here in Google Maps. More interesting, however, is an eyewitness to the second attack who took photos of the accused-offender's car to give to police. It's posted here on Bluesky.

I did advocate that people move to Minnesota from other areas, anticipating the violence that Republicans would unleash (more on that topic next Monday, maybe) with a second Trump term. I still maintain that it's safer here than elsewhere in the USA for queer folk. Wherever you are, stay safe out there.

Profile

mellowtigger: (Default)
mellowtigger

About

January 2026

S M T W T F S
    123
4 56 78 910
11 12 1314 15 16 17
1819 20 21 22 23 24
25 26 2728293031

Most Popular Tags

Syndicate

RSS Atom
Powered by Dreamwidth Studios
Page generated 2026-Jan-29, Thursday 11:00 am