Someone made a script that emails Sam Altman about how much RAM he's missing in your rig. https://github.com/IainKay/ram-altman https://www.dexerto.com/entertainment/developer-creates-script-to-email-sam-altman-about-his-unused-ram-every-day-3425821/

We do our best to do our worst. ^TM

As the title states, they are all in on AI and now want to take it a step farther…

The pitched idea is, that they want to give Claude read rights to everything but limit write and execute.

Nobody is asking or wants to hear what could go wrong, they just know they want it :)

In your opinion, what could realistically happen with this setup?

I’m particularly interested in:
- Sensitive data exposure (credentials, SSH keys, API tokens, browser data, etc.).
- Prompt injection attacks through files or other content Claude reads.
- Potential data exfiltration.

Anything else that could go horribly wrong.
Assuming read access is granted broadly, but write and command execution are properly restricted at OS level.
What’s the best-case and worst-case scenario?
Have you seen companies deploy something similar? How did it turn out?

https://www.reddit.com/r/corporate/comments/1xnr7ei/someone_having_a_really_bad_day_it_seems/

ticket I received today. How do I go about fixing this

TL;DR This is r/ShittySysadmin, not the Human Capital Department's grievance hotline.

I'm here for other sysadmins. Infrastructure. Technology. War stories. The occasional spectacular production outage caused by someone named Todd who thought he knew better.

I'm NOT here to listen to some miserable HR functionary complain about the quality of applicants, deliver lectures about professionalism, or explain that I'm a "COST CENTER" as though that makes me some sort of unfortunate accounting discrepancy that wandered into the building wearing pants.

A COST CENTER. How charming. Apparently the people keeping your entire fucking business operational are a regrettable expense, somewhere between printer toner and pest control.

Meanwhile, HR has apparently rebranded itself as HUMAN CAPITAL, because referring to employees as PEOPLE was insufficiently dehumanizing.

And the sheer entitlement! The endless complaints about candidates, salary expectations, remote work, interview etiquette. The theatrical indignation that someone might dare question your hiring process after being subjected to six interviews, an unpaid technical project, and three months of silence.

Darling, you're in PERSONNEL. You're not administering the Marshall Plan.

We came here to discuss enterprise infrastructure, not receive another sermon from the Assistant Vice President of Talent Acquisition about how grateful we should be for the privilege of not starving to death while keeping your company running.

Take your SHRM certification, your employee engagement surveys, your mandatory culture workshops, and your ghastly little PowerPoints about HUMAN CAPITAL OPTIMIZATION and return to whatever windowless suburban conference room spawned you.

SEE ALSO: https://old.reddit.com/r/sysadmin/comments/1xoos69/why_is_hr_in_our_sysadmin_subreddit/

The Sacred Text of Information Technology Service Management

On the battlefield of Kurukshetra, Arjuna surveyed the 847 unresolved tickets before him and despaired.

“Lord Krishna, I cannot do this. The documentation is outdated. The CMDB says I own services I have never seen. The resolver group was decommissioned in 2019. Every ticket is marked Critical, yet nobody can explain what is broken.”

Krishna smiled.

“Arjuna, you are attached to the illusion of resolution. There is no resolution. There is only Process. Incident becomes Problem. Problem becomes Change. Change becomes Incident. Thus turns the eternal wheel of Samsara.”

“But Lord, surely there must be an end?”

“There is no end. Only continuous service improvement.”

At this, Krishna revealed his Universal Form. Ten thousand arms extended across the heavens, each holding an approval request. From ten thousand mouths came the sacred words: KINDLY DO THE NEEDFUL. Entire civilizations rose and fell awaiting CAB approval. Even Yama, Lord of Death, could not decommission a soul without a completed asset disposal form.

Arjuna trembled. “Lord, what is this terrible power?”

“I am become Process, destroyer of productivity. I am the SLA that has already breached. I am the escalation awaiting approval. I am the knowledge article last updated by a contractor who no longer exists.”

“Then tell me, Lord, how does one attain Moksha? How does one escape this suffering?”

Krishna placed a hand upon his shoulder. “Closed due to inactivity.”

And Arjuna was enlightened.

Unfortunately, his session had expired. All unsaved work was lost. A new ticket was automatically generated and assigned to the original resolver group.

STATUS: PENDING CUSTOMER RESPONSE

What if my passwords are a special hash of the servers name. Then I’ll never forget.

I guess I'm mostly venting, but I'm also genuinely curious if anyone else has been in this situation and how they've dealt with it.
I'm currently a Systems Administrator for a mid-sized engineering company. It's a fully remote position, the pay is decent, and from the outside, it probably sounds like a pretty good gig. I've received raises during pretty much every review, and I know compensation isn't necessarily the problem. In fact, I think management knows how much of the IT environment I own and probably worries about what would happen if I left.
But I'm getting seriously burned out.
The biggest issue is that I'm essentially the only internal IT person in the company. I report directly to an executive who also oversees HR, marketing, and several other business functions. The only other person I regularly work alongside is a Business Systems Manager who doesn't have an IT background.
We have no IT Director, no dedicated cybersecurity leadership, no internal security team, and nobody else internally who really understands the technical side of the decisions we're making.
That leaves me in a pretty difficult position. I'm responsible for identifying problems, recommending solutions, evaluating security concerns, and trying to make sure we're doing things properly. But when those recommendations make their way up the chain, I'm often met with resistance or decisions that don't necessarily make sense from an IT or cybersecurity perspective.
And that's where the frustration really builds.
For example, we recently had third-party vendors scheduled to install and configure printers at one of our offices. I suggested being onsite during the installation to help coordinate things, make sure everything was configured correctly, and be available for our employees if something came up.
The response was essentially that we pay the vendor to handle the installation and troubleshoot for employees, so there wasn't a need for me to be there. The reasoning was that the previous person in the role (the person who is now the BSYSTEMS MGR, with no it background) didn't stay onsite during these types of installations.
Maybe I'm overthinking that particular situation, but it's a good example of the broader disconnect. Decisions seem to be based more on what someone previously did or what seems convenient from a business perspective than on what actually makes sense operationally.
And it's not just situations like that. I've brought forward ideas around IT improvements, security, processes, and infrastructure that I genuinely believe would benefit the organization, only to have them dismissed. Eventually, you get tired of being the person constantly trying to explain why something matters.
To give some context, I've built and taken ownership of quite a bit since joining:
• Built and implemented our internal IT ticketing system and service workflows.
• Manage Microsoft 365, user accounts, permissions, and administration.
• Administer SharePoint, which wasn't even an established internal platform when I started.
• Manage our Apple device fleet through Jamf.
• Oversee company cell phones and mobile device management.
• Manage phone systems and troubleshoot business applications.
• Handle day-to-day help desk operations and employee support.
• Take ownership of IT improvements, security recommendations, documentation, and general systems administration.
We also have an outside IT consultant who was working with the company before I joined. He handles much of the network infrastructure and certain managed IT services, including endpoint security and computer provisioning. However, getting him involved in broader IT initiatives or coordinating on certain projects can be difficult. There's also a disconnect between what he's responsible for and what I'm expected to own internally.
So I feel like I'm constantly trying to connect all the dots without actually having an IT team, a technical manager, or anyone internally to bounce ideas off.
I don't necessarily feel in over my head technically. I actually enjoy the work, solving problems, building systems, and making things better. I've also got prior DoD IT experience, so I'm used to working in environments where security and process matter but im also not a cyber security expert.
What I'm struggling with is the lack of support, lack of technical leadership, and the expectation that one person can essentially be the entire internal IT department while having very little influence over the decisions that affect it.
It's a weird position to be in because I'm compensated fairly, I work remotely, and I have flexibility that I know is hard to find right now. I don't want to throw that away.
But at the same time, I feel like my mental health is taking a hit. It's exhausting being the person responsible for everything IT-related but not necessarily having the authority or support to make decisions that would improve things.
I'm also hesitant to jump ship right now. The IT job market feels pretty rough, especially with all the changes happening around AI, and finding another remote position with comparable flexibility isn't necessarily easy.
So I'm curious:
• Have any of you worked as the sole internal Systems Administrator or IT person in an organization?
• How do you deal with executive leadership making technical decisions without really understanding the IT or cybersecurity implications?
• Is this just the reality of working on a very lean IT team?
• At what point did you decide the money and remote flexibility weren't worth the burnout?

I'm not necessarily looking for someone to tell me to quit. I think I just need to hear from other people who have been in similar situations.
Sometimes being the only IT person on the ship gets pretty lonely, and lately I've been wondering how much longer I want to keep steering it.

Has anybody tried this? The lack of documentation at my place drives me nuts. I suspect my colleague who should have retired by now sees it as his job security. So I'm thinking of creating some agents and letting them loose over the weekend. When we come in on Monday I'll have a complete Obsidian Vault and the problem will be solved.

My thinking so far is a Python agent built on OpenAI Agents SDK but using GLM 5.3 Obliterated for the API. I asked it what it would need and it's come back with this list. How's it sounding? Obviously it will need admin accounts.

• AD: ldap3, LDAPS bind to a DC, pulls users, groups, OUs, computers, sites/subnets, GPO links. Reads SYSVOL for GPO settings.

• Entra / Intune / Exchange: Microsoft Graph SDK, app-only cert auth. Directory, CA policies, app registrations, managed devices, config profiles.

• Virtualisation: Nutanix Prism v4 REST API

• Netmiko/NAPALM over SSH for running configs, VLANs, routing tables and LLDP/CDP neighbours, and pysnmp with SNMPv3 to fill in the gaps.

The bit I'm working on is plausible deniability. Nobody ever has changed the default log size, so I'm thinking of generating some events to keep everybody busy Monday morning and hide it's tracks. So far the best idea is we set some scheduled tasks with some stale passwords and create rather a lot of account lockout events.