The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
The Guiding Principles and New Rules document is now in effect.
[sysadmin] sexy.code = new.underpants.required
Le_Goat
Frechified Goat PersonBostonRegistered User regular
Frechified Goat PersonBostonRegistered User regular
Below is a compilation of links we've found to be helpful for Sys Admins (capitalized because we're important, like a towel):
AntiVirus/AntiMalware Tools:
Networking Tools:
Miscellaneous Tools:
Stress Relief Tools:
...more to come
last updated 11.10.2015
AntiVirus/AntiMalware Tools:
- Kaspersky Disk
- Malwarebytes
- Sophos Virus Removal Tool (Sophos product not required; free)
Networking Tools:
- Angry IP Scanner
- Cisco Network Assistant - GUI for Cisco Products
- Royal TS - RDP Management Tool
- Terminals - RDP Management Tool
- Zenmap (Nmap)
Miscellaneous Tools:
- APC Power Estimator - estimates your power needs based on devices, which you can specify
- Dependency Walker - scans modules and builds a hierarchical dependency tree
- Greenshot -- Screenshot + utilies
- HJSplit -- Split/Join files
- Jing - Screenshot + utilities
- Notepad++ -- Enhanced Notepad (e.g., color coding)
- WinDirStat -- File space analysis
Stress Relief Tools:
...more to come
last updated 11.10.2015
While I agree that being insensitive is an issue, so is being oversensitive.
Le_Goat on
+2
This discussion has been closed.
Posts
Tell me about it.
If I could join a union I'd be all over that and give the 10 hours a week I do sys admin to someone else, probably get them a full time job out of it too.
XBL:Phenyhelm - 3DS:Phenyhelm
Pretty much the only way they can deny you in NYS is if you did something illegal. Even then, they have to have the paper trail to prove it.
There's a limit on how much you can collect per X employment time span, so it's mostly moot anyways.
At least in my state, she said she didn't really give a shit why I quit, these were benefits I paid into so they were mine to claim unless I did some egregious harm to the company and they could prove it. NYS also said I'd continue to get my benefits until it was determined it was my fault. She said a lot of company's use the "we'll contest unemployment" as a scare tactic.
How can I estimate the potential hit in resources to the Exchange server?
I'm pretty sure that is a picture of a new hire, just reading his instructional manual on how to commit seppuku, because MOTHERFUCK re-doing all that cabling...
In contrast,
"all this with zero downtime"
hnnngggg
Why not both?
I'm onto you, random internet liar who is the source of TLDR's link.
fuck up once and you break your thumb / if you're happy at all then you're god damn dumb
that's right we're on a fucked up cruise / God is dead but at least we have booze
bad things happen, no one knows why / the sun burns out and everyone dies
fuck up once and you break your thumb / if you're happy at all then you're god damn dumb
that's right we're on a fucked up cruise / God is dead but at least we have booze
bad things happen, no one knows why / the sun burns out and everyone dies
Yea I've seen that before. Took me way longer than it should have to figure it out.
As long as all your switching is redundant, it's possible, for some definitions of "downtime".
This whole "everything must be up at all times" is nuts. If someone had to audit your department back in the day, you just shut it down for the day or week and that's just how it worked. Whoever promised "oh there'll be no/minimal downtime" just shoots themselves in the foot.
Even Blizzard shuts down servers when they patch.
I tried explaining it to them that if 20 of their coworkers call me one after another and it takes me 2-5 minutes a phone call, they've easily eaten 1/8th of my day that I could've gotten the upgrade done. There's a really good chance that I could've done the 8 hour maintenance window in that 1-2 hour time span, too.
But nope, fuck you, all 8 fucking hours. I actually finished an upgrade in the first hour or so. I had the switch disabled and on a remote power strip I could power on or off from my phone. So exactly at 5:00 pm on that Saturday, I powered the switch back on.
Oh wait, no I don't.
The problem with company politics is if you refuse to play the game, it will chew you up.
Def.
You immediately become a target for both groups of people.
I see it like this. I have a choice when I schedule maintenance or equipment upgrades. I can choose to plan for downtime and blast an email and/or voicemail out a dozen times, which will get ignored a dozen times and end up sending calls to the helpdesk, my extension, my cell and so on regardless. Or I can stick a little more thought into planning the maintenance/upgrade and have my workflow mapped out ahead of time and my users will never know. I'll always choose the path that's less stressful, which is almost always the path of less interaction with users - the extra time spent planning and doing the work with minimal to no downtime is worth its weight in gold when my phone isn't ringing.
Oh my god you're worse than Joffrey
More specifically the switch I'm working on (abridged):
Function GetInput { $Office = read-host "Enter Office Location" Switch ($Office){ 'office1' {$Office = "OU=Users,OU=Location1,OU=Network Folder,DC=Company,DC=local"; break} 'office2' {$Office = "OU=Users,OU=Location2,OU=Network Folder,DC=Company,DC=local"; break} (et al...) default {GetInput} } } GetInputAll the rest of the script works fine. I'm plugging the $Office variable into -OrganizationalUnit if that matters? I swear it worked once upon a time, so I don't know if it's a possible issue where a small configuration change on the server broke it, or if I'm just doing something wrong.
1) You don't necessarily need to break, since the conditions are unique and shouldn't evaluate more than one of them.
2) I'd recommend assigning to something other than what you're switching on (if you switch on $Office, don't change it mid-switch by assigning to $Office, assign to something separate like $OU).
If your function just needs to return it right away, and your switch is the last statement of the function, you don't need to assign anything at all actually. Looks like you might be trying that, or half-trying it right now?
Function GetOfficeOU { $Office = read-host "Enter Office Location" Switch ($Office) { "office1" { "OU=Users,OU=Location1,OU=Network Folder,DC=Company,DC=local" } "office2" { "OU=Users,OU=Location2,OU=Network Folder,DC=Company,DC=local" } default { GetOfficeOU } } }The switch gives you the OU or calls itself to query again, ultimately unwinding and returning the correct OU once you enter a valid input.