Skip to main content

Help yourself if you ask for help

This is a slight modification of a Reddit post I created a few months ago. It was written for Reddit, however the analogy works even if you ask for help anywhere else too.

I have not been on Reddit for long, however I have been watching the posts being submitted. In all fairness, I have a couple of suggestions to you if you need help with something larger than a commandline or suggestion of a command line:

How to ask for help

  1. Always state the goal of the solution. What is the problem you have decided to try and solve. If your solution is to produce output, explain what it should output and what form (console, xml, json, text, csv etc).
  2. How will the solution be executed (as a script, as part of an module or as an function)
  3. If your solution is not working, share the whole script/function included dependency code, not just the line/command/function that is not working.
  4. If you code requires parameters and your code does not include any help/comments on how it works, explain what the parameters are and how you want them to work. Also important to include a section(just a few lines) of required input files like csv/cms/json or if the script is designed to receive input from an operator at the console.
  5. What version of powershell are you targeting and if it is executed on a client/server.
  6. Include error messages you are receiving when executing the code

Also if you manage to:

  1. Write and format your code (all codelines should start with 4 spaces (blanks)) to be rendered nicely)
  2. Avoid using aliases (use full cmdlet names)
  3. Use logical variable names (too long is better than too short, however that is a personal perference). This also applies to parameter names.

You will probably receive a reply to your request more quickly and to the point.

Examples of bad requests:

The googler:

"*Hey, have this powershell/script I found on the internet. It is failing on this line <insert line her> with this error..... Please help...*"

The csv lover:

"*Hey, I have this huge script that requires input from 2 csv files. It works when I input the values manually, but not when I pipe in the csv files with the import-csv cmdlet.....*"

Free ride lover:

"*Hey, I have this huge problem and I am thinking of learning powershell. I need to <insert required solution here>.... Please show me a script that can do this...*"

Ask and you shall receive, if you ask the right way

You will need to put some work in to your request, however in the long run you will most likely receive a reply sooner rather than later and it will provide you with a suggestion that is closer to the answer you where looking for. This is just my prediction, it is not an universal truth.

Consider this my 2cc. I love to help when I have a clear understanding of the issue and we can discuss options related to your requests.




Popular posts from this blog

Monitoring Orchestrator runbook events from Operations Manager

Today I will follow up on my colleague’s post Mr ITblog (Knut Huglen) about monitoring Orchestrator Runbook events.  He has build a nice double up SNMP loopback feature that does self monitoring in Orchestrator resulting in entries written to a special Windows Eventlog. Now we need to raise alerts in SCOM when one of his runbooks fails or sends a platform event, who knows there could be trouble lurking in his paradise.

We are not going to do anything fancy, however these are the steps we will be focusing on today:
Create a Management Pack for our customizations Create rules that collects the events from the orchestrator serverOff we go then and fire up the SCOM console and a powershell window. First we create a MP, I am going to use powershell to do this, however you may use the SCOM console as well (Administration – ManagementPacks – Action: Create Management Pack):

Import the Management Pack into SCOM and move on to the Authoring section in the SCOM console. Create a new rule:

Give the…

Powershell – Log like you mean it

How do you do logging in powershell? Why should you do logging? What should you log? Where do you put your log? How do you remove your log? How do you search your log? All important questions and how you answer then depends upon what your background is like and the preferences you have. This will be a 2 part blog post and this is part 1.

Why should you log?

Well it is not mandatory, however I have 2 reasons:
Help with debugging a script/module/functionSelf documenting script/module/function
Firstly; Do you know any program that does not contain any bugs? Working with IT for the last 2 decades, I cannot name one. When you create scripts/modules/functions, you will create bugs, that is where they live and try to make your life a living mess.

Secondly: Adding a little extra information to your logging will make them self documenting. Do you like writing documentation? Well I normally am not fond of it and use logging while debugging to get two birds with one stone.

What should you log?


Powershell - List information about your WIFI networks

This is just a quick post about this new function I have created. Basically this is a text-output to powershell object output function that uses netsh to query the WIFI information. This illustrates the importance of changing the authentication level on your WIFI-network. No matter if you use WEP/WPA/WPA2 your password is available in clear text in your profile.