D
Dennis Calhoun
I've read until my eyes are falling out of my head. I've been working
for two weeks trying to make Sysprep1.1 work so that I can use Ghost
2003 to clone several computers at our school. Despite my most intense
efforts, I can not get sysprep to do a single thing in the area of the
$OEM$ structure.
I've tried to keep it simple in the beginning, only trying to get it
to add two files (oeminfo.ini and oemlogo.bmp) to the system32
directory and make a new directory named pnpDrivers at the root of the
C drive on the target computer. I am certain that I have put things
where they belong in the oem tree too.
I've tried so many things it is a blur, but nothing has resulted in
anything at all happening right. No files are copied, No new directory
is created, never, after dozens of tries.
We are on a peer-to-peer network and the server that I want to
retrieve the $OEM$ structure from is named printservercm. The files
reside on a shared drive named repository18. The server is running
Windows 2000 Server.
OK, will someone please tell me exactly what I should put where in the
sysprep.inf file, or where ever it should go, to get the client to
connect to the server during bootup immediately after the client has
been restored from a ghosted image.
Second, I need anything I can get that might help explain why the
$OEM$ tree seems to be completely ignored and how I might do something
right to make it do as it is supposed to.
And yes, I have even tried using sysprep only, without ghost involved
at all, on a target machine (Win2000 Pro, Office XP and a couple other
things installed), but still, when it is rebooted it goes through the
windows setup routine fine, yet not one thing of the $OEM$ structure
is left on the drive when it is done.
I've used this on a couple other test machines too and the mass
storage devices are not a problem, works great. In order to get pnp
drivers that are not included with Win2000 to install I have to
manually add them to a directory on the target machine *before* making
an image of it, then set the OemPpnDrivers path to that directory,
outside of C:\Sysprep. When I do it that way it installs the drivers
automatically, as it should, but this means there is no way for me to
easily add more new drivers without having to make a whole new image.
Please, do not suggest that I read anything from the Deploy.chm file,
I've done that dozens of times, almost to a point of having it
memorized. Same is pretty much true for most stuff on the MS website.
I will get the sysprep.inf file as soon as I get to school in the
morning and post it as a followup to this post. Sorry I don't have it
with me at the moment.
Sincere thanks, for any serious help that anyone can offer,
Dennis Calhoun
for two weeks trying to make Sysprep1.1 work so that I can use Ghost
2003 to clone several computers at our school. Despite my most intense
efforts, I can not get sysprep to do a single thing in the area of the
$OEM$ structure.
I've tried to keep it simple in the beginning, only trying to get it
to add two files (oeminfo.ini and oemlogo.bmp) to the system32
directory and make a new directory named pnpDrivers at the root of the
C drive on the target computer. I am certain that I have put things
where they belong in the oem tree too.
I've tried so many things it is a blur, but nothing has resulted in
anything at all happening right. No files are copied, No new directory
is created, never, after dozens of tries.
We are on a peer-to-peer network and the server that I want to
retrieve the $OEM$ structure from is named printservercm. The files
reside on a shared drive named repository18. The server is running
Windows 2000 Server.
OK, will someone please tell me exactly what I should put where in the
sysprep.inf file, or where ever it should go, to get the client to
connect to the server during bootup immediately after the client has
been restored from a ghosted image.
Second, I need anything I can get that might help explain why the
$OEM$ tree seems to be completely ignored and how I might do something
right to make it do as it is supposed to.
And yes, I have even tried using sysprep only, without ghost involved
at all, on a target machine (Win2000 Pro, Office XP and a couple other
things installed), but still, when it is rebooted it goes through the
windows setup routine fine, yet not one thing of the $OEM$ structure
is left on the drive when it is done.
I've used this on a couple other test machines too and the mass
storage devices are not a problem, works great. In order to get pnp
drivers that are not included with Win2000 to install I have to
manually add them to a directory on the target machine *before* making
an image of it, then set the OemPpnDrivers path to that directory,
outside of C:\Sysprep. When I do it that way it installs the drivers
automatically, as it should, but this means there is no way for me to
easily add more new drivers without having to make a whole new image.
Please, do not suggest that I read anything from the Deploy.chm file,
I've done that dozens of times, almost to a point of having it
memorized. Same is pretty much true for most stuff on the MS website.
I will get the sysprep.inf file as soon as I get to school in the
morning and post it as a followup to this post. Sorry I don't have it
with me at the moment.
Sincere thanks, for any serious help that anyone can offer,
Dennis Calhoun