Author Archives: dmagalen

How to Migrate DHCP from Server 2003 to Server 2008 R2 in 5 Easy Steps

How to Migrate DHCP from Server 2003 to Server 2008 R2 in 5 Easy Steps

  Read more »


The out-of-the-box SharePoint 2010 workflow approver email notification no longer contains a link to the workflow task associated with the workflow item.  While that’s ok if the approver is using Microsoft Office 2010 and the document is an Office document, if either of those are not the case then there is no easy way for the approver to get back to the task to approve or reject it.  I went out in search of how to fix the OOTB workflow email and having to cull this information from a number of sources, I thought it would be helpful to have it all in one place.

Read more »

Password or PIN Code “protect” MDT 2010 LiteTouch

Well, let me start with this:

This is NOT a secure solution, it is more of a-controlling-the-wizard-so-it-will-be-harder-do-something-really-bad-thing. This story started 2-3 weeks ago, a customer wanted to deploy windows 7 using LiteTouch. But they need a function to limit the selection of Task Sequences showed to the technician. Now that somewhat is a challenge but can be done. Here is how you can do this on your own. Read more »

WMI GPO Filters for Windows Server 2012 and Windows 8

When deploying Group Policies in a Windows environment, often you may have different GPOs for different versions of the operating systems. With the recent release of Windows 8 and Windows Server 2012, it’s likely you will have new GPOs just for these operating systems. You could build out new OUs for the each OS type, but that can get messy rather quickly. Read more »

Exchange Server 2010: Using Database Portability for Disaster Recovery

Exchange Server 2010 has a feature called Database Portability. This is the capability for a mailbox database from one Mailbox server to be mounted on another Mailbox server within the same organization.

In this article I will demonstrate how you can use Database Portability in a disaster recovery situation. Read more »

Script to check a machine has a Windows patch

‘!!! This script returns specific Windsows patch information on Remote server!!! Read more »

Creating the ultimate SCCM 2007 Frontend HTA for OSD Part II

Let start building our  HTA so we can get that prompt for variables step going. I’m not going to make it pretty that’s not my department but you will get the idea and can customize it then make it look good. Read more »

Add HTA-Support to a Boot Image with ConfigMgr 2012

With ConfigMgr 2012 lot’s of things got simplified. One of those things is adding extra components to the Boot Images. Before it was possible to add these extra components by either using the MDT integration, or manually running DISM. Now it’s possible to do this from the console! Of course, in the background it’s still DISM that does the action. Read more »

Removing and rebuilding a malfunctioning Recovery HD partition

When updating to 10.7.2, there’s a Lion Recovery Update that goes along with it. This is meant to update your Recover HD recovery partition to 10.7.2 along with your Mac. However, when I tried updating, I could see from the logs that for whatever reason, my Recovery HD was staying at 10.7.1 and was not being successfully updated. As the new Find My Mac functionality in iCloud relies on Recovery HD being updated to 10.7.2, I wanted to be able to fix this problem without having to reinstall or reimage my Mac. Fortunately, thanks to the work of Clay Caviness at Google, there’s a way to rebuild your recovery partition (at least for 10.7.2) on a Mac that doesn’t have one. I did have one, but I knew how to fix that. See below the jump for the procedure.


Note: All commands shown are single lines.

Step One: Make a full backup of your boot drive.

This is absolutely the most important step of this process. Any time you’re moving partitions around, stuff can go wrong. Making a backup beforehand can turn a later “Something went wrong” moment from a crisis into a less-bad inconvenience.

Step Two: Remove the existing Recovery HD recovery partition

1. Get the disk identifier of your recovery partition by running the following command:

diskutil list

2. Once you’ve identified the entry, then remove it by running the following command. (In this case, I’ll be using disk0s4 for the recovery partition and disk0s3 for the main boot partition.):

diskutil eraseVolume HFS+ ErasedDisk /dev/disk0s4

3. Next, merge the recovery and boot partitions together to create one partition (the MacHD identifier is to give the partition a new name; your existing boot drive name shouldn’t be changed by this process):

diskutil mergePartitions HFS+ MacHD disk0s3 disk0s4

Step Three: Rebuilding the recovery partition:

1. Download the Lion Recovery Update from

2. Run the following commands to attach the correct disk image and rebuild the recovery partition:

hdiutil attach RecoveryHDUpdate.dmg

pkgutil –expand /Volumes/Mac\ OS\ X\ Lion\ Recovery\ HD\ Update/RecoveryHDUpdate.pkg /tmp/RecoveryHDUpdate

hdiutil attach /tmp/RecoveryHDUpdate/RecoveryHDUpdate.pkg/RecoveryHDMeta.dmg

/tmp/RecoveryHDUpdate/RecoveryHDUpdate.pkg/Scripts/Tools/dmtest ensureRecoveryPartition / /Volumes/Recovery\ HD\ Update/BaseSystem.dmg 0 0 /Volumes/Recovery\ HD\ Update/BaseSystem.chunklist

At this point, you will see a large amount of code fly by as the recovery partition is rebuilt. It should end with Creating recovery partition: finished

The next set of commands is clean-up and making the system recognize the updated recovery partition.

hdiutil eject /Volumes/Recovery\ HD\ Update
hdiutil eject /Volumes/Mac\ OS\ X\ Lion\ Recovery\ HD\ Update
sudo touch /Library/Preferences/SystemConfiguration/
sudo kextcache -f -u /

Once finished, restart your Mac and verify that you can boot to Recovery HD. To verify that your Recovery HD is now on 10.7.2, open the Terminal (available from the Utilities menu when booted from the Recovery HD partition,) and run the following command:


The following information should be displayed:

ProductName: Mac OS X
ProductVersion: 10.7.2
BuildVersion: 11C74

Adding drivers into WinPE boot image for use with Microsoft WAIK

WinPE is the preinstallation environment which will mostly be used to load an OS onto a new system. This article will explain how to inject LAN drivers into WinPE, allowing you to deploy OS installations to a larger variety of hardware.

Follow the instructions below. You will need to have the Microsoft WAIK (Windows Automated Installation Kit) installed to modify the image. WAIK provides the command line tools for working with WIM images, the image format used by Windows and WinPE. Read more »