sysprep

[Guest]

Archived from groups: microsoft.public.win2000.general (More info?)

When i create an image of w2k using sysprep and then when i deploy the image
to machines do those machines have to be 100% the exact same or does that
part not matter. The sysprep command where do i run that from ?And is there a
website that has step by step instructions in doing it?

 

[Guest]

Archived from groups: microsoft.public.win2000.general (More info?)

From: "sthompson" <sthompson@discussions.microsoft.com>

| When i create an image of w2k using sysprep and then when i deploy the image
| to machines do those machines have to be 100% the exact same or does that
| part not matter. The sysprep command where do i run that from ?And is there a
| website that has step by step instructions in doing it?

99% -- Yes.

You can have different video or sound card or other periphery but the system must be the
same model.

--
Dave
http://www.claymania.com/removal-trojan-adware.html
http://www.ik-cs.com/got-a-virus.htm

 

[Guest]

Archived from groups: microsoft.public.win2000.general (More info?)

there is not a parameter switch that you can type in to make it so the model
number does not matter?

"David H. Lipman" wrote:

> From: "sthompson" <sthompson@discussions.microsoft.com>
>
> | When i create an image of w2k using sysprep and then when i deploy the image
> | to machines do those machines have to be 100% the exact same or does that
> | part not matter. The sysprep command where do i run that from ?And is there a
> | website that has step by step instructions in doing it?
>
> 99% -- Yes.
>
> You can have different video or sound card or other periphery but the system must be the
> same model.
>
> --
> Dave
> http://www.claymania.com/removal-trojan-adware.html
> http://www.ik-cs.com/got-a-virus.htm
>
>
>

 

[Guest]

Archived from groups: microsoft.public.win2000.general (More info?)

From: "sthompson" <sthompson@discussions.microsoft.com>

| there is not a parameter switch that you can type in to make it so the model
| number does not matter?

No. It has nothing to do with Sysprep and everything to do with cloning a platform. If the
motherboard chip-set is different the system won't boot.

--
Dave
http://www.claymania.com/removal-trojan-adware.html
http://www.ik-cs.com/got-a-virus.htm

 

[Guest]

Archived from groups: microsoft.public.win2000.general (More info?)

One of the requirements of sysprep is to have a 3rd party disk imaging
software, like goes. But ghost itself creates a image. Why use one program (
sysprep) to create an image and another ( ghost) to deploy it when you can
just use ghost?

"David H. Lipman" wrote:

> From: "sthompson" <sthompson@discussions.microsoft.com>
>
> | there is not a parameter switch that you can type in to make it so the model
> | number does not matter?
>
> No. It has nothing to do with Sysprep and everything to do with cloning a platform. If the
> motherboard chip-set is different the system won't boot.
>
> --
> Dave
> http://www.claymania.com/removal-trojan-adware.html
> http://www.ik-cs.com/got-a-virus.htm
>
>
>

 

[Guest]

Archived from groups: microsoft.public.win2000.general (More info?)

From: "sthompson" <sthompson@discussions.microsoft.com>

| One of the requirements of sysprep is to have a 3rd party disk imaging
| software, like goes. But ghost itself creates a image. Why use one program (
| sysprep) to create an image and another ( ghost) to deploy it when you can
| just use ghost?

Symantec/Norton Ghost is used to create an image of the platform only.

Sysprep is required in an organization to strip the SIDs and other information prior
creating the image. Then when you restore the image to a destination platform and reboot
it, it will run the MiniWizard Setup. Then you can assign a unique machine name, IP
address, and join the Domain. If you don't Sysprep the platform, the SIDs will remain and
cause problems in the Domain and the IP address and machine name will cause a conflict with
other PCs.

--
Dave
http://www.claymania.com/removal-trojan-adware.html
http://www.ik-cs.com/got-a-virus.htm