Today I tried to remove an orphaned DPM 2010 agent from my DPM console. But I couldn’t find how to do that.

I found out that there is a powershell script to do just that. It’s called “Remove-ProductionServer.ps1″, sweet

Just startup your DPM Powershell environment and run the script.

It will ask you for your DPM server and the server to remove. You could also provide these as parameters, like so:

.\Remove-ProductionServer.ps1 <DPM Server Name> <Protected Server Name>

That’s it….

Wanna know if a particular service principal name is registered?

Add the following command to a batch file (called something like “get-spns.bat”) and you get a list of SPN’s registered with a given name and which account is associated with the SPN.

ldifde -f spns.txt -s domaincontroller -r "(|(msDS-AllowedToDelegateTo=*%1*)(servicePrincipalName=*%1*))" -l msDS-AllowedToDelegateTo,servicePrincipalName

usage: get-spns.bat servername/hostheader

open up the created spns.txt and voila.

Some times I check if my applications are still using the proper application pools (I am not the only administrator of the IIS servers ). You can do this with the IIS GUI ofcourse but you can also use scripting (checking a lot of servers/application and application pools can be a pain in the !@#$%). So I created a little script to do that. Read the rest of this entry

Ever wondered if the assemblies your developers gives you to install on a production server are from a release build? You can make a little C# console application to check this.

Read the rest of this entry