ConfigMgr object locked for editing

Often if editing something like a Boot Image or Task Sequence and you experience a console crash, then next time you try to edit that object you may see a message saying it is currently locked for editing, giving only a choice to wait or open as Read-Only.

Some quick (unsupported) database edits can clear the lock, or there is a Powershell command that does the trick as well. The Powershell is a bit trickier, but is the “proper” supported method.

PowerShell: How to unlock objects in SCCM

Powershell Unlock-CMObject: https://technet.microsoft.com/en-us/library/jj821915(v=sc.20).aspx

and more info on how SEDO works: http://blogs.technet.com/b/sudheesn/archive/2012/10/28/sedo-serialized-editing-of-distributed-objects-configmgr-2012.aspx

 

Compare running services against a baseline using Powershell

Some quick commands I hacked together to make it easier to check what services are running on a machine after it has restarted, and compare them against a “known good” baseline of the services that *should* be running.

The key purpose was for after a server crash to check the services such as SQL and exchange have all started again.

Hyper-V Powershell command are missing

In my never ending quest to learn a new thing everyday, I decided I needed to spend more time with Powershell. After a recent Hyper-V issue it seems it would be just the thing to help. So imagine my surprise when nothing I did could get the Hyper-V PS commands to work!

It turns out that because my server had been upgraded to Server 2012 from 2008R2, when the Hyper-V role is installed, the Hyper-V PS module isn’t.