Month: November 2015

Merge WIM into one – the space saver

I have gotten this question a couple of times “can i have two operating systems to choose from in one task sequence”. Well the correct answer to that is yes, but it takes up alot of unecessary space and if you are using ConfigMgr and need to download 2 wims instead of 1 well that adds alot of time.

What I would instead recommend is merging two Wim files into one, this will save alot of space and still give you the option to use different ref images in the same task sequence.

So how is this done?

First off you need to create two ref images. The most common senario for this is you have one with Office preinstalled and one without Office preinstalled. So if we look at how that looks you will get something like this:

RefImages

In this case I am using Windows 10 ref images but this works just as well with Windows Vista, 7, 8 and 8.1 (all Wim based OSes).

So as you can see they are around 4-5GB in size. The next step now is to merge them. To help with this i have a small script that you can use.

What the script does is it takes one wim and mounts it. Then it applies the mounted wim into the other wim so you get two indexes and next it cleans up the mounted directory and finally displays the different indexes in the merged wim file.

You can download the script here: http://bit.ly/1TAcO8Q

When that is complete you get something looking like this.

AfterMerge

As you can see the image is now a bit bigger but it has not doubled in size. This is due to the fact that when the wims are merged it will throw away all duplicate files to keep the file size down.

This method is the same method Microsoft have used when they have created Windows Server medias in the past containing core and gui versions on the same media.

The next step is to import this into whatever solution you are using (MDT/SCCM).

In this instance I have used MDT and it looks similar in SCCM but there are a couple of differentes. If you are unsure, drop me an email or pm and I can help you out.

So, import Operating system, custom image and point to the wim created erlier. When its done it looks something like this

Import

If we look at the preferences for these two operating systems you can see that they both use the same file in the background but different indexes.

ImageProperties

Now you can add another install operating system step and select different citeras to run the different steps. For instance, different blocks in CustomSettings.ini, some setting in the MDT database or add a new setting to the MDT database and use that. Use webservices and if the computer is this OU or AD group it should have office and if not it shouldn’t. The possibilities to create rules are as always limitless.

Happy deploying!

/Peter

Advertisements

System Center Configuration Manager 2012 R2 SP1 CU2

Here we are, its time for another upgrade – another update with some bugfixes and goodies inside.

This time its called Cumulative Update 2 for System Center Configuration Manager 2012 SP2 and 2012 R2 SP1. This CU also includes a number of hotfixes that has been released since CU1. Among others the important one for drivers where the size gets a bit bloated.

Installing this is pretty straight forward. Start with making sure you have a backup of the system! This should always be done but since this includes a DB update aswell it’s extra important. Next up is a reboot for good measure. You can always check if you want to se if there are any pending reboots but I prefer just to do a clean reboot to make sure anyway.

If you want to make use of snapshots/checkpoints, make sure the VM is turned off when you take to snapshot/checkpoint. This is to ensure data consistency since there is SQL database in the background.

When this is done you apply the patch and wait for it to complete. Options for automatic upgrade and client package creation will be included in the wizard.

When you are done make sure to to a reboot as the CU requires it!

After the reboot you can start upgrading your clients. And when they are done it should look something like this.

AfterUpgrade

Take not that the new version number is 5.00.8239.1301
Feel free to create a collection to include these so you also get collections with the previous version.

To create collections for most of the agent version you can use a powershell script i created. It can be downloaded here http://bit.ly/1TAeMGd

The Cumulative Update can be found here https://support.microsoft.com/en-us/kb/3100144

Good luck and make sure to have a backup!