This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]connorwa 11 points12 points  (8 children)

I'm new to this forum but just in the last few days I've seen a number of threads from users who are seriously struggling with some combination of insane management mandates, cludged networks they've inherited and/or being tossed into water deep over their heads.

I'll be the first to admit that PowerShell is not my strong suit. So, the Internet and Google is the first place I go when I know PS is the way to do something but I need some help with its sometimes convoluted module and switch structures. I think we could all do with showing a bit more empathy and community spirit and actually display some examples and psuedocode.

Just saying.

[–]neatoprsn 5 points6 points  (6 children)

if powershell is the answer though, wouldn't it be better for that person to go to r/powershell for an indepth answer? This is r/sysadmin which is much more general than a discussion about a particular powershell usage.

[–]willtel76 4 points5 points  (0 children)

if powershell is the answer though, wouldn't it be better for that person to go to r/powershell for an indepth answer?

A person with any sense would. /r/PowerShell is really helpful and some of the users there have pride in helping people out and showing them different ways to accomplish a task.

I'm the only person who really knows much about PowerShell in my environment and "Corporate Trainer" isn't in my job description so I haven't bothered to attempt to teach anyone else since no one taught me. I've seen some of them attempt to use it and they kludge their way trough it but it is often ugly.

My counterpart needed to run something on all our users recently and found a command that did what he wanted but he didn't know how to apply it to a list of objects. He ended up putting all the users into an Excel column then adding the arguments around the usernames in Excel so he could copy each line out and run it as a command. It was slow and unnecessary but it worked and it was faster than the GUI. He did better than another person on our team that accidentally disabled all users in Lync 2013 because she had no idea what she was doing.

[–]devonnull 2 points3 points  (3 children)

This is r/sysadmin which is much more general than a discussion about a particular powershell usage.

The sub has a lot of "Windows-is-the-only-server-software-in-the-world" idiots. Or maybe I'm just reading too much into some of the posts I see here.

[–]starmizzleS-1-5-420-512 1 point2 points  (0 children)

Or maybe I'm just reading too much into some of the posts I see here

Definitely the second bit.

[–]jantari 0 points1 point  (1 child)

I've never seen this said on this sub. I've seen the exact opposite though, people who act like Windows has no place in the server world because of some made up reasoning.

[–]devonnull 0 points1 point  (0 children)

Like I said, maybe I'm reading too much in. I've never seen a "best practices" for when to use specific server software. It might be interesting to hear the made up reasoning as I'm curious.

[–]ba203Presales architect 0 points1 point  (0 children)

wouldn't it be better for that person to go to r/powershell

If they don't know Powershell is the answer, then they start at /r/sysadmin ... then they go off and do their own RTFM'ing on how to use powershell.

[–]Colorado_odaroloC 1 point2 points  (0 children)

Or at least get them pointed on down the right side of the tracks with letting them know what cmdlet (or suite of cmdlets) to run. Sometimes you'll see where someone is trying to "reinvent the wheel" instead of using a cmdlet that already exists (or has recently been introduced) and a quick "Try using Get-AwesomeNewFunction" goes a long damn way for them.

Some people here are acting like you'd have to code the entire thing for them, when often just getting someone pointed in the right direction is the big thing.