Re: Sysprep XP Home Ed. image

Can be quite simple.
1.) Build Reference machine
2.) Copy customized profile to "Default"
3.) Image the PC ( Acronis, Ghost )
4.) *Better yet, partition drive so it has a dedicated image volume
with your "Standardized" image on it.
5.) Image both the C: (Win-XP) and Image volume
6.) Restore both to client PC
7.) When PC needs rebuilding, boot to CD-R media and do a
3-4 minute restore from the Image volume on the disk itself.
8.) Post Processing - Machine Name, NewSID
Doing this way you can quickly restore each machine without having
to use a central image server.

I do some probono work for Charities and have created a similar type
setup for them.

"Pat Clifford" <PatClifford@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C2C3A77B-C0DC-41CB-8065-973D1BFDF019@xxxxxxxxxxxxxxxx
Ok, I am not sure what Newbie Coder means about stripping the SIDs out. I
understand that each machine needs unique SIDs, but why is (or would be)
stripping out the SIDs (which assumably are regenerated during the setup
boot) be better than changing the SIDs after the first boot?

All I am looking for is a way to propogate a "standard" setup to a number
of
machines for public use. (...and, yes, they do use 3rd party software to
"lock" down the machines. They also use limited accounts and are wiped
clean
and restored periodically.) In the past, this has all been done by hand
and
as the number of machines increases, this is becoming cumbersome. As we
are
a public institution (read: little/no money) I have to try to do this with
either free software or software already purchased (ie. sysprep).

As an aside, this seems to be a unnessarily complicated procedure for
something that on the surface should be a simple operation. I am sure
that I
am not the only person on the face of the planet that needs to do this,
but I
can find little to no information regarding how to sucessfully do this.

Pat


"R. McCarty" wrote:

Yep, I know. I was merely suggesting that instead of using Sysprep
for that small number of deployed PCs it might be easier to use a
simple Image ( Acronis, Ghost ) and then run NewSID on each PC
after 1st boot to generate new SIDs.
Probably since they are going to be "Public Access" PCs they need
some type of 3rd-Party restoration/maintenance application to prevent
changes or improper use. Hopefully they will be used only with limited
account privileges.



.

Relevant Pages

  • Re: Replacing Hard drive
    ... I haven't used Ghost since the 2003 version so I don't know if the problem ... partitions can be resized during the restore. ... else fails you can download the Ultimate Boot CD ... Laptop powered up, by the way I did select "copy master boot record" ...
    (microsoft.public.windowsxp.hardware)
  • Re: cloning, imaging, and backing up
    ... Be able to do regular incremental backups as well. ... I can't speak about other programs for this task, but Ghost has a good ... It works by saving a "restore point" to a network or USB ... You also create a boot CD. ...
    (microsoft.public.windowsxp.general)
  • Re: cloning, imaging, and backing up
    ... Be able to do regular incremental backups as well. ... I can't speak about other programs for this task, but Ghost has a good ... It works by saving a "restore point" to a network or USB ... You also create a boot CD. ...
    (microsoft.public.windowsxp.general)
  • Re: bios (81 hex)
    ... i put on ghost the backup was ok the restore said ok when i rebooted the error was **ntldr is missing*** ... If you can't delete the partition then you must have some sort of partition ... Boot from the XP CD itself not the hard ... partition from your Ghost backup. ...
    (microsoft.public.windowsxp.hardware)
  • RE: mlock(1)
    ... laptop against, what is their level of commitment, and what on the laptop are you ... The thingwe are trying to protect in the swap space are the ram images of the ... cryptoswap key at every boot and then throw it away. ... Any "restore" methodology can be attacked by definition because the attacker can ...
    (Linux-Kernel)