Related topics

Sysprep
If you reboot the computer at the point of failure to join the domain, you can run through mini-setup again using the same name and it works fine. We also used sysprep 1.1 to roll it out. The only one that we received that exact error on was on a laptop image where the NIC was not installed properly.

Ghost 2001 can save and burn partition to my Ricoh drive!!!
You need to do some special Sysprep settings before Ghosting "Run the latest version of Sysprep (v1.1) from the Microsoft site, and add the following lines TWO: If I have an IDENTICAL computer system in house to one I have at a customers site and they have a Hard Drive failure and I set a configure a system on

Win2k Sysprep auto driver installation failure
Oh well ... failure sucks but what can you do ?? Thanks all and happy easter. (do you celebrate that in the US ??) "Mark b...@gmail.com>" wrote: Oops my bad, I missed the direction the image was moving to. I've probably done this a half dozen times using sysprep either to or from the Virtual PC and it's never

Follow-up to: Windows 2000 Professional local auditing ...
Per that article, I have to defer to VMWare's instructions (if any), but perhaps one should first use sysprep - see http://support.microsoft.com/default.aspx? scid=kb;EN-US;Q240126. Now onto the problem <g>: First: try registering (and if that doesn't work then unregistering and reregistering) sqlsui.dll using

scandisk problem
I've created the image from an unattended.txt then added the additional drivers needed for the 7 different makes of PC's via setupmngr/Sysprep. We will not have any server available whilst rolling out the desktop hence the need for a cd build, the image with Sysprep drivers is now 2.2 Gb!!, also my drivers (display

Moved HDD to new MB, e-mail failure
You could setup sysprep so that you go through a manual sysprep, which is identical to doing a complete re-install except that all of your apps and software Q-is "sysprep" a common term for a process?..... or is this a feature in a modern version of Ghost.? Meaning If I have physically setup all my hardware

Moved HDD to new MB, e-mail failure
In article <MPG.16f1860559280b6b989...@msnews.microsoft.com>, usefirstinitiallastn...@technologist.com says... circa Thu, 7 Mar 2002 08:57:13 -0800, in microsoft.public.cert.exam.mcsa, Jtyc (y...@respondtothegroup.com) said, What we have here... is a failure... to.. communicate. And you are correct.

Help:sysprep didn't work
MarkGI Mar...@discussions.microsoft.com microsoft public windows server setup When trying to deploy an image, I am getting an error "Failed to create the data file" at the "Set Sysprep custom info in the sysprep.inf file" portion of the deployment. It performs the first 2 steps without any problems. Any ideas??

INACCESSIBLE_BOOT_DEVICE,...
Matt B z...@hotmail.com microsoft public windowsxp setup_deployment Hi all - getting a weird message when I try to run sysprep with -factory option The mass #E245 The device installation digital signature failure policy has been elevated from Ignore to Warn due to a proposed replacement of a protected system

Sysprep ProductKey not working
Dmail01 dmai...@gmail.com gougler-windows-server-2000-general Sysprep is a free Microsoft tool that is used w/ ghost to re-sid your machines after you image them. Once you pull down an image to a particular machine, you reboot it and then sysprep starts. It resembles the wizard that you see when you go through a

Sysprep -nosidgen
Colin Magor colin.ma...@akerkvaerner.com vmware guest windows2000 I can see that you can add aditional controllers by adding to the [SysPrepMassStorage] list in the sysprep.inf. But - and this may sound stupid - how do I create this list. I've been poking around ad it doesn't sem so obvious to me, since there are

Client 4.9 SP1 -> Unexpected login failure! Status 0x6A24A54F
The parts have been replaced because of an fatal hardware failure and the system is highly needed. The first thing i asked was, whether there are backups Here every system has been backed up and Os and data are seperated, so that on a 100% fail the os can be replaced on the fly from sysprep images and other

Sysprep -nosidgen
Since implementing Zen Suite 6.5, we want to use it's imaging and try to make a single base image that will work, if possible, on all the different systems. They are all Intel platforms. I tried a basic test creating an image from a sysprep'd XP install on a GX260 and putting it on a GX150. Big failure.

resolving BOOT failure after VM to native cloning
To create the image, I used the sysprep.ini file below and then issued the command: c:\sysprep\sysprep.exe -pnp. I believe this is related to my failure to add a [SysprepMassStorage] section. Is there a way to edit the sysprep.ini file on the machine? I tried booting to the repair console thinking I could edit the

restorinbg a system from server failure
With the advent of WIndows XP, this simplicity and grace went away, a more forceful approach (or actually using tools like sysprep) became necessary in The concerns with your conclusion is that you know when the failure is going to occur and what hardware you will be moving it to before that failure occurs.

temp admin rights granting failure
... to different hardware won't absolutely fail every time; all I'm saying is: it's more prone to failure than doing a normal reinstallation of the OS on the new hardware. I think that is true of most operating systems ;-) On NT/XP you can use the Microsoft Sysprep utility, to deal with driver issues.

sysprep and Windows File protection.
Sure - using Ghost to move an OS installation to different hardware won't absolutely fail every time; all I'm saying is: it's more prone to failure than doing a normal On NT/XP you can use the Microsoft Sysprep utility, to deal with driver issues. Ghost works well with Sysprep. It's described in the docs.

Moved HDD to new MB, e-mail failure
I have been using sysprep 2 which gives me a failure error before completing. "Sysprep has been unable to update the registry " or something like this. Sometimes the ghost image works on a machine and sometimes it doesn't. Is Drive image likely to be any better? Before you go any further you need to resolve your

Notice To All
... hardware won't absolutely fail every time; all I'm saying is: it's more prone to failure than doing a normal reinstallation of the OS on the new hardware. Ghost works well with Sysprep. It's described in the docs. Ghost is a fine product and I've used it with great success. I'm just saying that people are

registry file failure
I use the right HAL and run SYSPREP before cloning. Now I can clone my SCSI Workstation to my IDE Notebook in 15 Minutes! Great! -- cu o.pfeiffer ICQ# 84320006 eMail oliver.pfeif...@gmx.net -------------------------------------------- TECHNOLOGIE - ZENTRUM INFORMATIK / UNIVERSITAET BREMEN / GERMANY.