FredBainbridge

#2 Enjoyment - 10 Things You Need As An Enterprise Scripter

#2 Enjoyment This is a simple one and applies to many more aspects of life than enterprise scripting. If you know from the onset that you are not going to enjoy this work, plan appropriately. Aka, find someone else to do it. If you don’t love it, you are going to have a challenging time consistently outputting high quality work. This work never ends, it’s a practice of constant iteration and improvement. Read more →

#1 Tooling - 10 Things You Need As An Enterpise Scripter

#1 Tooling The use of proper tooling is the first and most important step on your journey to enterprise level scripting. Proper tooling can save you time in development, help you design better solutions and most importantly show the value of your hard work to anyone who may be interested. I will break this down into two sections, Development Tooling and Project Tracking tooling. Development Tooling First and foremost get used to change. Read more →

Intro - 10 Things You Need As An Enterprise Scripter

Introduction The main difference between enterprise level scripting and non-enterprise level scripting is professionalism. This is a simple truth. You may have the best code in the world and it may have the potential to save millions of dollars but without the proper attention to the small and large details it is most likely a script that will live and die with you. It won’t even be a foot note in the company’s internal wiki. Read more →

Pester - TestGroups Stack Corrupted

Exception calling "LeaveTestGroup" with "2" argument(s): "TestGroups stack corrupted: Expected name/hint of '$name','$hint'.. Found '[context]','Context'." $pester.LeaveTestGroup($testScript.Path, 'Script') This is caused when your function is calling “exit” while testing. Or at least it did in my case. Properly mock whatever is calling exit or find a way to not use exit! Look at the source code here for hints as to what is actually happening. Pester makes sure it is still in the context it started as before leaving a test group. Read more →

Import-SMAModule fails!

When using Import-SMAModule you get a wild error. Import-SMAModule : Could not import the module []: System.Data.Services.DataServiceClientException: The underlying connection was closed: An unexpected error occured on a receive. ---> ... Make sure the module you are importing is a zipped folder with the proper module files! This is clearly documented. :) Read more →

Hosting my blog in Azure

Operation Goodbye Wordpress. Notes on my blog migration. Requirements My main motivation for migration my website was primarily to get off the WordPress platform. I found myself spending as much or more time maintaining the site as opposed to creating content and after getting hacked a few times I decided enough was enough, time to make a change. My requirements were as follows: Easy to maintain static website. I want whatever ends up being published to be nothing more than html and css files. Read more →

Uninstall the OMS Agent

Just keeping this here for future use. This will remove the OMS client / Microsoft Management Agent. Cheers! $App = Get-WmiObject -Query 'select * from win32_product where ` IdentifyingNumber = "{742D699D-56EB-49CC-A04A-317DE01F31CD}"' $App.Uninstall() Read more →

Implementing a Sample ConfigMgr Web API

The following steps get you a working WebAPI that can show data retrieved from a ConfigMgr database. The project is hosted at https://github.com/fredbainbridge/CMWebAPI. Prerequisites: ASPNET Core GIT Visual Studio Code C# extension You need remote TCP Connectivity to the ConfigMgr database. (probably port 1433 ) Implementing a simple yet awesome ConfigMgr Web API. Clone the repository From PowerShell or commadn prompt run: git clone https://github.com/fredbainbridge/CMWebAPI This will create a folder named CMWebAPI containing all the source code. Read more →

Getting Starting with a ConfigMgr WebAPI

Accessing portions of your ConfigMgr database via a webAPI can really open some doors for some pretty spectacular solutions and of course some nifty automation. Most of the automation “low hanging fruit” for WebAPI usage is during OSD. You can do things like combine data from an asset management system and the CM database to do things like name the device, select appropriate applications, place the device in a proper OU, validate it is corporate owned, etc etc… if you can think it up and you have the data available to you, you should be able to right the logic into your web API. Read more →