With all the SSL vulnerabilities that have come out recently, we’ve decided to disable some of the older protocols at work so we don’t have to worry about them. After getting our group policies setup the way we wanted, we needed a way to validate that the protocols we wanted to disable were actually disabled on our servers.
I guess I should start off this post by saying what I’m doing is a dirty hack, in no way supported, and in general a terrible idea. But it’s also really awesome.
One of our SharePoint wiki libraries got in a state where we couldn’t edit any of the pages. When we clicked “Edit” we would get the document properties page instead of the wiki editor page. I believe the root cause was someone moving a page from another wiki and the page ended up in the library as a “document” instead of a “wiki page”.
I’m not going to cover how to setup your unattend file, or how to customize a PE image… there are plenty of people out there who have covered those topics. What I do want to cover here is how to edit your PE image so that you can force it to connect to a specific WDS server. This will help solve the problem where you want to deploy computers into two domains on the same subnet, but WDS only looks for prestaged computers objects on the domain it is joined to.
We’ve been having weekly script club meetings at work where anyone who is interested gets together in a conference room and we all work on scripts together so we all have a chance to learn new techniques while solving our real-world problems at the same time. This week I developed a script to mimic the behavior of the SysInternals utility SDelete. The script will be used to reclaim thin-provisioned space from our SAN, and I wanted to develop it during script club to use as an example of how to use the classes in the System.IO namespace to get better IO performance from PowerShell.