Skip to main content

Getting things done

Attended one of those sessions where the key selling point was “how to get things done”. In other words, get your sh*t together and get organized with zero emails in you inbox. It is a whole philosophy, google it :-)

Well one of the suggestions was to use the “send to onenote” program that is installed with OneNote. Of course that is way to may clicks for me and my mouse and I started to look into a quicker way of doing it in powershell, what else?

Turns out there are very few posts on the subject, sending things from powershell to OneNote. Found a couple of references using c# and that is almost powershell so of I went and created this function Out-Note.


The function takes two parameters. Note = The text you want to send to OneNote and an optional parameter Section that defaults to “General”.

UPDATE - 23 March 2015

Received a tweet from Jan Egil Ring (Powershell MVP - @JanEgilRing). He was having issues with the function. It would only create a new page in OneNote if OneNote was NOT running. We tried a couple of things, however the error remained (New-Object : Retrieving the COM class factory for component with CLSID {DC67E480-C3CB-49F8-8232-60B0C2056C8E} failed due to the following error: 80080005 Server execution failed (Exception from HRESULT:0x80080005 (CO_E_SERVER_EXEC_FAILURE))). Checking the eventlog we found this message:

The server {DC67E480-C3CB-49F8-8232-60B0C2056C8E} did not register with DCOM within the required timeout.

Well that did not help resolve the issue, however Jan Egil then tried to run the function from an powershell session that was not elevated as an administrator and that worked. So the error above is due to missing cached credentials for your local administrator. To fix it, start OneNote as an administrator (right click the icon and choose "Run as Administrator") and sign in to OneDrive from OneNote. 

I have also renamed the function from Send-Note to Out-Note as is a more powershell friendly name (thank you Jan Egil, I stole the name from you :-))




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.