39 posts in this topic

Posted

I thought I'd post my guide here also. Every guide I seen online is not detailed and we are all struggling to get things to work with their guides, so I thought I would post a detailed guide here as a contribution to the Neowin Community. If there is anything you'd like to know then leave a message or send me a private message. Cheers to all   :)

 

 

What you need:

  • install.wim image from the Windows installation media. If it is an install.esd image then you have to create a Virtual Machine and install Windows 8.1 on it. I will give instructions. The file is in the
1 person likes this

Share this post


Link to post
Share on other sites

Posted

Guys, this way is the Microsoft way. Those other GUI tools, well you have no idea what's happening. And they seem to always have bugs. There is no bugs in this way. You get the updates installed and that's it. To make a bootable USB: just use the Windows 7 USB/DVD download tool. Always use your original Windows 8.1 ISO and copy and replace the modified .wim file to the USB stick.

1 person likes this

Share this post


Link to post
Share on other sites

Posted

Hmm I'll just stick with my MSDN Windows 8.1 with Update 1 ISO :)

4 people like this

Share this post


Link to post
Share on other sites

Posted

This looks like it could be useful, but I'm not sure it would allow Secure Boot to be enabled?

 

I try to stick to network based installs where possible, but sometimes you need to dig out the USB drive.

 

Hmm I'll just stick with my MSDN Windows 8.1 with Update 1 ISO :)

I'm still confused why that ISO made me install Update 1 again from Windows update.

Share this post


Link to post
Share on other sites

Posted

Guys, this way is the Microsoft way.

Source?

Share this post


Link to post
Share on other sites

Posted (edited)

Source?

Um, look at the script commands. They all have DISM commands. Where do DISM command come from? UM they come from the Windows ADK for Windows 8.1. And so does the imageX command. Edited by zhangm

Share this post


Link to post
Share on other sites

Posted

Before you sysprep the image wouldn't it make sense to use DISM to cleanup the WinSXS folder to reduce the size of the WIM?

Share this post


Link to post
Share on other sites

Posted

this is nice.

Share this post


Link to post
Share on other sites

Posted

Before you sysprep the image wouldn't it make sense to use DISM to cleanup the WinSXS folder to reduce the size of the WIM?

you could do that and that would be a great idea, but most people have ESD files cause they either downloaded the upgrade or downloaded the full version online. When you convert back to ESD, it does what you said automatically.

Share this post


Link to post
Share on other sites

Posted

This looks like it could be useful, but I'm not sure it would allow Secure Boot to be enabled?

 

I try to stick to network based installs where possible, but sometimes you need to dig out the USB drive.

 

I'm still confused why that ISO made me install Update 1 again from Windows update.

Microsoft rereleased the Update1. Try and re-download the update and re-inject it and see if that works. And I believe Hyper-V supports secure boot. So see if the Virtual Machine way works.

Share this post


Link to post
Share on other sites

Posted

So, would you happen to possibly have a write up or know where I can get one for the Microsoft Development Toolkit, more specifically the part for the actually capturing of an image? I am having a heck of a time trying to capture a Server 2008 R2 image so that it deploys correctly.

Share this post


Link to post
Share on other sites

Posted

Later this month they are going to be releasing the ISO's with the update 1 update for the Upgrade to 8.1 product key only. This works for the retail version. For those who are doing the 8.0 to 8.1 store upgrade the 8.1 update is now included in that.

 

Lastly I am trying to see why the VM is even needed at all. You should be able to add the updates straight into the install.wim file with Dism. As far as the install.esd image imagex can read these but Dism can't. So you could do an apply to a blank folder or vhf file with imagex. From there you can recapture to a wim. There is no need to install Windows to do any of this.

Share this post


Link to post
Share on other sites

Posted

Type the following: imagex /compress maximum /capture F:\ C:\install.wim "Windows 8.1 Pro" (F is the drive letter you gave the virtual drive when you mounted it)

ImageX is deprecated and you should be using DISM to both capture and service WIMs

1 person likes this

Share this post


Link to post
Share on other sites

Posted

you could do that and that would be a great idea, but most people have ESD files cause they either downloaded the upgrade or downloaded the full version online. When you convert back to ESD, it does what you said automatically.

No it doesn't ESD format is just highly compressed. You basically get significantly more compression than you get using the max option on DISM. The cleaning up of WinSxS folder and such removes updates that got superseded by the newer updates. However if there are updates that need a reboot it won't allow the command to start. The only time I cleanup the folder like this is if I make a full system image that is the OS with apps and such. At that point space is at a premium so I would definitely need to the ESD thing.


ImageX is deprecated and you should be using DISM to both capture and service WIMs

While it is deprecated, its the only way to export ESD files without having to do an install of Windows.

Share this post


Link to post
Share on other sites

Posted

Guys, this way is the Microsoft way. Those other GUI tools, well you have no idea what's happening. And they seem to always have bugs. There is no bugs in this way. You get the updates installed and that's it. To make a bootable USB: just use the Windows 7 USB/DVD download tool. Always use your original Windows 8.1 ISO and copy and replace the modified .wim file to the USB stick.

I think a better "Microsoft" way is to utilize MDT 2013 and use a simple build and capture sequence and enable the Windows Update step to get all the latest patches.

There are many ways to skin a cat, however...


You could also just download the Windows 8.1 with Update 1 ISO from Volume LIcensing or MSDN, they're both available.

1 person likes this

Share this post


Link to post
Share on other sites

Posted

No it doesn't ESD format is just highly compressed. You basically get significantly more compression than you get using the max option on DISM. The cleaning up of WinSxS folder and such removes updates that got superseded by the newer updates. However if there are updates that need a reboot it won't allow the command to start. The only time I cleanup the folder like this is if I make a full system image that is the OS with apps and such. At that point space is at a premium so I would definitely need to the ESD thing.

 

IMO no point even going into audit mode until they have completed installing and configuring.

Share this post


Link to post
Share on other sites

Posted

I think a better "Microsoft" way is to utilize MDT 2013 and use a simple build and capture sequence and enable the Windows Update step to get all the latest patches.

There are many ways to skin a cat, however...


You could also just download the Windows 8.1 with Update 1 ISO from Volume LIcensing or MSDN, they're both available.

Actually I wrote this guide for people who DON'T have a volume License and who DON'T have a MSDN subscription. SO please, I reiterate, this Guide is NOT for those who have MSDN subscription and Volume Licenses. Also the Windows Assessment and Deployment Kit (ADK) for Windows 8.1 seems to do better with Wim images that come from the install disk and for people who don't have other computers but the one they are using. Also setting up a Hyper-V virtual machine and sysprepping it is allot easier.

Share this post


Link to post
Share on other sites

Posted

IMO no point even going into audit mode until they have completed installing and configuring.

If you know how to clean up the Winsxs folder without starting up the machine that we are injecting the updates in to, then please let us know the easiest way to do that. I'm all ears and eyes. And if you can add it to the script I posted then that would be what I am looking for.

Share this post


Link to post
Share on other sites

Posted

No it doesn't ESD format is just highly compressed. You basically get significantly more compression than you get using the max option on DISM. The cleaning up of WinSxS folder and such removes updates that got superseded by the newer updates. However if there are updates that need a reboot it won't allow the command to start. The only time I cleanup the folder like this is if I make a full system image that is the OS with apps and such. At that point space is at a premium so I would definitely need to the ESD thing.


While it is deprecated, its the only way to export ESD files without having to do an install of Windows.

so, What is the easiest way to decompress an ESD file? Basically ESD to WIM?

Share this post


Link to post
Share on other sites

Posted

If you know how to clean up the Winsxs folder without starting up the machine that we are injecting the updates in to, then please let us know the easiest way to do that. I'm all ears and eyes. And if you can add it to the script I posted then that would be what I am looking for.

dism /image:c:\mount(where mount is where you mounted the folder) /cleanup-image /startcomponentcleanup /resetbase This only works if the updates don't need a restart of the system.

Share this post


Link to post
Share on other sites

Posted

do you remember the /integrate flag from windows XP to integrate servicepacks and updates?

 

I just want to cry when I see how difficult and user-unfriendly it is today.

Share this post


Link to post
Share on other sites

Posted

do you remember the /integrate flag from windows XP to integrate servicepacks and updates?

 

I just want to cry when I see how difficult and user-unfriendly it is today.

I totally agree with you there. MS promised they would make this process easy when we had the first SP in vista but its gotten significantly worse with each version of Windows. If we ever got it as easy as it was in XP I would be ok with building images all day long.

1 person likes this

Share this post


Link to post
Share on other sites

Posted

do you remember the /integrate flag from windows XP to integrate servicepacks and updates?

 

I just want to cry when I see how difficult and user-unfriendly it is today.

 

Ha I was just thinking the same thing! I remember when Vista was in development and Microsoft were saying how easy it would be to build images with all the updates rolled in. This is just a horrible mess. A simple unattended install file or sysprep was all you needed back then. So glad I moved away from system administration if this is what life is like now!

Share this post


Link to post
Share on other sites

Posted

If you know how to clean up the Winsxs folder without starting up the machine that we are injecting the updates in to, then please let us know the easiest way to do that. I'm all ears and eyes. And if you can add it to the script I posted then that would be what I am looking for.

 

dism /online /cleanup-image /startcomponentcleanup /ResetBase (reset base only works on 8 and 8.1). Would recommend doing this before putting the machine into audit mode

 

After update 1 leaked this command saved me about 8 gigs of disk space.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.