Skip to main content

Enable Windows 7/2008 features using DISM offline servicing

By
One of the strong management points of Windows 7 deployment is the ability to manage you images without having to apply the image, make the changes, and then recapture the image.  DISM (Deployment Image Servicing and Management) allows you to mount a Windows image and make configuration changes to it.  All this while not having to take the time to first deploy the image.

To begin working with an image, we need to mount it.  First, make a new folder to hold the mounted image.  For this demo, I made one called ImageMount.  Both the folder and the image file are on my D: drive.

Next, open a command prompt with elevated permissions.
The .wim file I’m using for this demo is the install.wim file from the Windows Server 2008 R2 installation media.

Browse to the location where you stored the image file and the folder to mount it in.

Type DISM /mount-wim /wimfile:d:\install.wim /index:1 /Mountdir:d:\ImageMount

Depending on the size of the WIM file, this may take a few minutes,

image

Once completed, you can get information on the mounted WIM file by typing: DISM /get-mountedwiminfo and pressing Enter.

image

Here we are going to take a look at enabling and disabling features in a Windows 7 image.  To get a list of the features, type DISM /image:d:\ImageMount /get-features and press Enter.  Below is just a small sampling of what was returned.

image

We are going to enable the Printing-Server-Role

Type DISM /image:D:\ImageMount /enable-feature /FeatureName:Printing-Server-Role and press Enter.

image

You should see the message above if all went well.  By once again typing DISM /image:d:\ImageMount /get-features and pressing Enter, you should see the feature has been “Enable Pending.” This indicates the Optional Component is installed and enabled.

image

You can disable a feature by typing DISM /image:D:\ImageMount /Remove-feature /FeatureName:Printing-Server-Role and pressing Enter.

To commit the changes and close the image for use, type DISM /Unmount-Wim /MountDir:D:\ImageMount /Commit. If you do not want to save your changes, replace /Commit to /Discard.
Labels:

Comments

Post a Comment

Popular posts from this blog

With the AD Recycle Bin Turned on, What Happens when you Create a User Account with a Password that does not meet the Password Policy?

By
This was an interesting observation from one of my Windows Server 2012 classes.  While working with the AD Recycle bin in a lab, one of my students discovered some interesting accounts that were created. When he created user accounts that did not meet password complexity requirements, an account is temporarily made and then deleted.  When a new password is provided that meets the password requirements, then a new account is made. We discovered this in two places.  First off in the Active Directory Administrative Center.  This is what caused the initial confusion.  Take a look.  This is in the Deleted Objects OU. You can see multiple deleted accounts for Test2 and one for Test3.  Test3 is a valid, functioning user account.  Using the PowerShell command Get-ADObject –IncludeDeletedObjects –Filter * –Properties ObjectSID we can see that indeed, two accounts were created, with one of them deleted. Notice the RID portion of the SID is different. ...
Post a Comment
Read more

Sticky Key problem between Windows Server 2012 and LogMeIn

By
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 .
6 comments
Read more

Set up your Environment to utilize Invoke-GPUpdate

By
I’m sitting in O’Hare enjoying my 3 hour layover as I get ready to teach a Windows 10 class in Fort Wayne.  I’m actually prepping for my class in Fort Wayne in a few weeks, 10982 Supporting and Troubleshooting Windows 10.  This class is very much like the Windows 7 version that I used to teach so I decided to up the detail quite a bit.  In the GPO troubleshootin chapter, I’m including a demonstration on how to use PowerShell’s Invoke-GPUpdate.  I needed to make sure the environment is set up for me to be able to utilize this cmdlet.  If you read the Notes section on Invoke-GPUpdate’s help file, you will see there are three firwall rules that need to be in place:          Remote Scheduled Tasks Management (RPC)          Remote Scheduled Tasks Management (RPC-ERMAP)          Windows Management Instrumentation (WMI-IN) I decided to create a little PowerShell script to crea...
Post a Comment
Read more