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.


Cheers

Tore

Comments

Popular posts from this blog

Serialize data with PowerShell

Currently I am working on a big new module. In this module, I need to persist data to disk and reprocess them at some point even if the module/PowerShell session was closed. I needed to serialize objects and save them to disk. It needed to be very efficient to be able to support a high volume of objects. Hence I decided to turn this serializer into a module called HashData.



Other Serializing methods

In PowerShell we have several possibilities to serialize objects. There are two cmdlets you can use which are built in:
Export-CliXmlConvertTo-JSON
Both are excellent options if you do not care about the size of the file. In my case I needed something lean and mean in terms of the size on disk for the serialized object. Lets do some tests to compare the different types:


(Hashdata.Object.ps1)

You might be curious why I do not use the Export-CliXML cmdlet and just use the [System.Management.Automation.PSSerializer]::Serialize static method. The static method will generate the same xml, however we …

Build your local powershell module repository - ProGet

So Windows Powershell Blog released a blog a couple of days ago (link). Not too long after, a discussion emerged about it being to complicated to setup. Even though the required software is open source (nugetgalleryserver), it looks like you need to have Visual Studio Installed to compile it. I looked into doing it without visual stuidio, however I have been unable to come up with a solution. I even tweeted about it since I am not an developer. Maybe someone how is familiar with “msbuild” could do a post on how to do it without VS.

Anyhow one of my twitter-friends (@sstranger) came to the rescue and pointed me in the direction of ProGet, hence the title of this post. ProGet comes in 2 different licensing modes
Free (reduced functionality)Enterprise (paid version with extra features)The good news is that the free version supports hosting a local PowershellGet repository which was my intention anyway. So off we go and create a Configration that can install ProGet for us. This is the conf…

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…