Comparison of PowerShell DISM Module and DOS DISM Commands

DISM has been used for many years to mount images and to make changes without actually first deploying the image and then re-capturing it. With the prevalence of Windows PowerShell. We now have DISM’s capabilities available to us in the familiar PowerShell syntax.

One of the issues that I have always had with DISM is the cumbersome parameters. Here is a DISM command:

DISM /Get-WimInfo /WimFile:Install.wim

And its PowerShell counterpart:

Get-WindowsImage –ImpagePath Install.wim

The green highlights are the switches. You can see a difference. Also, by using PowerShell, you are using a technology that will be supported well into the feature as well as the search and help features of Windows PowerShell. Below are the commands used to add the BITS feature to a Windows 2012 R2 server image. The length of typing may appear to be the same, but with PowerShell’s TAB completion, you will most likely not have typos on the PowerShell side. Good luck with not making a typo with DISM.

PowerShell	DISM	Description
Get-WindowsImage –ImpagePath install.wim	Dism /get-WimInfo /WimFile:install.wim	List all images inside of the WIM file
Mount-WindowsImage –Path E:\Offline –ImagePath Install.wim –Name “Windows Server 2012 R2 SERVERSTANDARDCORE”	Dism /Mount-WIM /WimFile:install.wim /Name:”Windows Server 2012 R2 SERVERSTANDARDCORE” /MountDir:E:\Offline	Mounts a specific image from a WIM file.
Get-WindowsOptionalFeature –Path e:\online	Dism /Image:e:\Offline /Get-Features	List all of the features for the image.
Enable-WindowsOptionalFeature –Path e:\Offline –FeatureName BITS	Dism /Image:E:\Offline /Enable-Feature /FeatureName:BITS	Enables a specific feature in the mounted image
Dismount-WIndowsImage –Path E:\Offline –Save	Dism /Unmount-WIM /MountDir:E:\Offline /Commit	Dismounts the image and saves all changes made.

Click here for a list of all DISM commands for PowerShell.

Comments

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this. First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction. The code below is correct. My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...

Backup and Restore AD LDS with DSDBUTIL.exe

Active Directory Lightweight Directory Services allow you to create a directory service that allows applications to have access to user accounts, groups, and authentication similar to Active Directory Domain Services. The big advantage here is that the schema of the directory service will not be bound by the rules of an Active Directory database. Exchange 2007/2010, for example, use an instance of AD LDS on the Edge Transport Server to provide for user authentication from the internet. Because your Active Directory database is not exposed to the internet, this is more secure. Applications will handle most of the dirty work should they require AD LDS. You may want to make sure the database is being backed up and also have a restore plan in place. Should the database become corrupt, the application that uses that database will fail. This document will walk you through backing up and restoring an instance of AD LDS using the dsdbutil.exe command. Fi...

Jason Yoder, MCT

Search This Blog