How much does the ImageX /Compress Maximum setting save you on disk space?

Compression is a funny thing. You cannot accurately predict the exact compression ratio without knowing what the files are and the algorithms being used. Some files, like MP3s are already compressed. Text files compress a lot, JPG files do not. By using the /Compress Maximum switch in the ImageX command line will put a lot of work on the capturing of the image, and less on the transfer of that image.

For this reason, I make sure that I am absolutely satisfied with the image that I am about to make. We are going to have an upfront cost of more time to create the image, but we will make it up if this image is going to be sent across the network many times.

I decided to do an experiment with a new Windows 7 Home Premium edition client that I just picked up at the store today. I only ran the basic configuration and loaded the Anti-virus software. Only imaging the C: drive and using the default compression, the image file size was 20,949,078 KB. The size of the image file after making a new image with the maximum compression option set was 10,263,386 KB. That was a reduction of 10,685,692 KB or 51%. That can be a huge savings in network bandwidth.

For a Thick Image (one that contains software as well as an OS), you may have to start the image capture and come back in the morning. But again, we are making an investment now, to enjoy a greater return on that invest later.

Comments

The Savo said…

I agree. I am experimenting with vista 32bit. A Toshiba recovery image from the factory with SP 1 is 6 GB. That is XPRESS or fast compression. After installing SP2, removing some bloatware, and using MAX compression; the image size is now 6.5 GB

August 4, 2011 at 6:37 PM

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...

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection. In all cases, this will disrupt the user. First, you need PowerShell remoting enabled on the target machine. You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target. Remember, the target needs to be online and accessible to you.

Jason Yoder, MCT

Search This Blog