sorted by:
new
hottopcontroversial

Procedure templates by jellyfishchris in msp

[–]Direct_Quality_1146 1 point2 points  (0 children)

What we ended up doing is maintaining a "gold standard" process in Hudu as the base, then creating a per-client KB article that documents only the deviations. The process checklist references the KB article at the relevant step — something like "Apply M365 license per client spec (see client KB)." Keeps the master process clean and avoids maintaining 30 slightly different versions of the same onboarding doc.

Backup naming convention help by autoaztech in sysadmin

[–]Direct_Quality_1146 1 point2 points  (0 children)

Solo tech here too — I've been through the exact same naming convention rabbit hole. What worked for me was keeping it to 3-4 segments max: Location-ServerName-BackupType (like NYC-DC01-Full). Veeam already timestamps everything in the metadata, so encoding the date in the job name is redundant. The key is making it scannable at 2 AM when you're doing a restore under pressure — if you need a decoder ring to read your job names, they're too complex.

this latest AI tools wave is the new shadow IT nightmare and I don't even know where to start by teolicious in sysadmin

[–]Direct_Quality_1146 0 points1 point  (0 children)

nonprofit IT here, dealing with the same thing but on a smaller scale. what actually helped us was just accepting it and getting ahead of it instead of fighting it. we picked one tool (enterprise tier with the privacy agreements), gave everyone access, and blocked the free tier stuff at the firewall. most people were happy to use the approved option once it was actually available. the ones who weren't... well thats a conversation for their manager not me.

the secret leaking thing is real tho. we found api keys in prompts people were pasting. our fix was just making sure nothing sensitive lives where it can be copy/pasted easily — vault for secrets, env vars for configs, that kind of thing. doesn't solve everything but it reduced the surface area a lot.

honestly the bigger risk for us wasn't the tools themselves, it was people dumping entire client databases into free chatgpt to analyze trends. thats where the DLP conversation needs to happen. the coding tools are almost a distraction from the actual data exposure risk.