Making installing iso

[zookeeper525]

Hey,

I'm trying to find out if there is a way to make a iso that i can burn after i install apps etc on windows 7? so that when i stall windows 7 all the apps will be pre-installed.

I've seen bootleg copies like this so i know it can be done, I just don't know how or where to start.

I just hate reinstalling apps after i do a reinstall etc and stuff.
so making a iso with all my apps would speed up stuff a lot.


sorry if i'm not aloud to ask about this or if this is the wrong place to ask about it.

 

[Tews]

Wouldnt it be a lot simpler to make an image of your system after you get it all set up???

 

[zookeeper525]

Wouldnt it be a lot simpler to make an image of your system after you get it all set up???

How would that work?

What if i want to install it on another pc? could i do so with making a image of my system?

 

[Tews]

You could, but chances it would fail validation when you went online...but you can try if you want...Acronis True Image Home 2010 will be able to do this..

 

[zookeeper525]

You could, but chances it would fail validation when you went online...but you can try if you want...Acronis True Image Home 2010 will be able to do this..

Do you know of a app that i could build a install iso if i wanted to?
I use to know one for vista but i haven't really done a lot with pcs in awhile.

 

[Tews]

Vlite might do it, but its going to be more trouble than its worth...I would stick with Acronis if it were me...

 

[pparks1]

I use a utility with Ubuntu linux called remastersys which does this. You can load the OS, then a handful of apps and then create a new ISO installer which contains the system as well as the installed apps and customizations. It's not an image though...it's an installer so you can use it with other machines.

I'm not familiar with any such utility for Windows...but it sure would be nice.

 

[whs]

Have a look at this ( http://www.sevenforums.com/software/43219-image-your-system-free-macrium.html ). It is dead simple. Forget the .iso. You'll get lost in the process.

 

[pparks1]

Have a look at this ( http://www.sevenforums.com/software/43219-image-your-system-free-macrium.html ). It is dead simple. Forget the .iso. You'll get lost in the process.

I think the point being missed is that we don't want a utility to "image" a machine. We'd like a utility to rebuild a full installer that contains the OS and the modifications made to it.

 

[whs]

Have a look at this ( http://www.sevenforums.com/software/43219-image-your-system-free-macrium.html ). It is dead simple. Forget the .iso. You'll get lost in the process.

I think the point being missed is that we don't want a utility to "image" a machine. We'd like a utility to rebuild a full installer that contains the OS and the modifications made to it.

pparks, usually I understand what you are saying. But here you lost me. What's the difference?

 

[gregrocker]

Vlite's latest version is what you need. You can slipstream drivers, apps, programs, etc and produce an ISO, even burn reliably.

Imaging would be easier of course, as urged, and activation issues can be avoided by either reimaging on the same machine, or if reimaged to another machine and the key is retail , then remove the key and reinsert at Computer>Properties link after Win7 changes out all of the drivers (quite a show) at first bootup. OEM keys cannot be transferred to another machine.

If internet activation fails when inserting key (as to be expected since MS activation computers still show old hardware config until new key overwrites it), the robo call should suffice as it will trade numbers to deactivate on the old hardware config and activate the new one. Or explain to a person that you have installed it to a new machine as is your right with a retail copy, but do not mention image or cloning as those words tend to spook MS.

People seem to think that MS for some reason can take your key back if they don't like something. But if you are migrating a retail key to a new machine, they have to activate it once they determine it is not on another machine.

 

[pparks1]

pparks, usually I understand what you are saying. But here you lost me. What's the difference?

A system image would have to be laid back down on top of the same machine with the same hardware.

An installer could be used to install on any machine that you chose. This would install the system and the various hardware drivers and such for the unique machine it is going on.

That's what that cool Ubuntu tool can do. It's quite handy.

 

[ccatlett1984]

you will need to use vlite, or something like it to do what you want. Unless all of the machines that you might want to install the image on are of the exact same model and configuration. There are ways to make a "general" image and then have seperate "add-on" images with drivers for each different model, but that is way more work than you will ever want to do.

 

[whs]

pparks, usually I understand what you are saying. But here you lost me. What's the difference?

A system image would have to be laid back down on top of the same machine with the same hardware.

An installer could be used to install on any machine that you chose. This would install the system and the various hardware drivers and such for the unique machine it is going on.

That's what that cool Ubuntu tool can do. It's quite handy.

OK, thanks - got you. In this case, I would choose cloning.

 

[Tews]

Lol... all this to say what I suggested 10 posts ago...

 

[gregrocker]

Lol... all this to say what I suggested 10 posts ago...

about the image failing activation on another machine?

 

[solar]

to OP... if it is for a perosnal computer and only ONE, then the best way is as the first reply was. making an image. Download Windows AIK, then you can do all your cusotmizations and capture the image. when you wish to "reinstall" with all those base programs, you just apply that image and voila. done.

To create an installer disk with pre-installed programs, (which consequently also can be used on other conputers), requires (with that WAIK), sysprepping with /generalize and setting up an autounattend file and a lot of silent install commands...I can heartily recommend MDT2010 for these tasks. However, from the way you pose your question I can tell you, you would take weeks at least to get all that sorted, so I recommend scenario 1. Sort out a perfect install for your one computer. (If you have several end user computers, it is relatively straight forward to make a template for all of them and apply on each).

When and if* I release SUCK ;p then I would say, as an end user, I'd use suck for scenario 1, and WAIK/MDT2010 for scenario 2.

If much of this sounds unknown to you, just go for scenario 1. trust me.

 

[solar]

Lol... all this to say what I suggested 10 posts ago...

yup but not sure if OP understood 'imaging' hence more posters... ^^