Cloning systems

  • Thread starter Thread starter Mario Dambauer
  • Start date Start date
M

Mario Dambauer

I would it do in a little bit different way:

Keith Rathband said:
Hello,

So far i have been cloneing systems in the method suggested by MS,

ie

1. Deploy the target image to a target system
2. Setup the target system
3. Run fbreseal
4. Shutdown the system
5. Make a master image of the system, (i use norton ghost to do this)
6. Burn the master image onto other target machines
7. Boot-up the new targets

This works reasonably well. However if i need to change somthing in my
master image (say install a new peice of software etc..) i have to start
completely from scratch again, and create a new master image.

Is there anyreason why i can do the following, (if i want to modify my
master image, and deploy it)

1. Burn the original master image onto a target system
2. Boot-up target system
3. Install new software etc..
Click to expand...


run fbreseal.exe once again

4. Shutdown the system
5. Make a new master image of the system.

And then when it comes to deploying the new master image,

1. Burn the new master image to other target machines
2. Boot-up the new targets
3. Run "NewSID", a utlitiy that generates a new uniquie SID. (from
http://www.sysinternals.com/ntw2k/source/newsid.shtml)
Click to expand...


now you don't net to run the newsid tool..
 
And then when it comes to deploying the new master image,

1. Burn the new master image to other target machines
2. Boot-up the new targets
3. Run "NewSID", a utlitiy that generates a new uniquie SID. (from
http://www.sysinternals.com/ntw2k/source/newsid.shtml)
4. Re-boot new target.
Click to expand...

If the targets aren't in a network, step 3 even becomes pointless:
there's no real need to do it (or to use fbreseal in the original
version).

Note that "network" means "MS network" here, you can have an internet
connection and still not use unique SIDs as long as you don't use MS
networking to connect to/from other machines.
 
Hello,

So far i have been cloneing systems in the method suggested by MS,

ie

1. Deploy the target image to a target system
2. Setup the target system
3. Run fbreseal
4. Shutdown the system
5. Make a master image of the system, (i use norton ghost to do this)
6. Burn the master image onto other target machines
7. Boot-up the new targets

This works reasonably well. However if i need to change somthing in my
master image (say install a new peice of software etc..) i have to start
completely from scratch again, and create a new master image.

Is there anyreason why i can do the following, (if i want to modify my
master image, and deploy it)

1. Burn the original master image onto a target system
2. Boot-up target system
3. Install new software etc..
4. Shutdown the system
5. Make a new master image of the system.

And then when it comes to deploying the new master image,

1. Burn the new master image to other target machines
2. Boot-up the new targets
3. Run "NewSID", a utlitiy that generates a new uniquie SID. (from
http://www.sysinternals.com/ntw2k/source/newsid.shtml)
4. Re-boot new target.

Thanks,

Keith.
 
You can run fbreseal multiple times. So, you can make your image and reseal
it then if warranted, boot your copy then alter and once again fbreseal it.
 
Back
Top