dsavercool
asked on
Adding a modified sysprep.inf file to a Ghost image via Ghost Explorer not functioning properly
I've been using Symantec's Ghost product for years now and have been looking forward for the version that has a functioning ability to add files to an NTFS filesystem image. That day seems to be here, but I am experiencing odd behavior that has me a bit worried.
I have one image that I use for all of my systems, Dell GX270, GX280, D600, D610, HP Compaq NC6400, NW8440 etc etc.. I created the image this way off the bat using sysprep. My company is moving to a new desktop standard in the coming months, and I figured this was the golden opportunity to take advantage of the latest version of ghost explorer 11 to edit the GHO file by adding the various drivers of the new system to my Temp/Drivers directory, and editing the oemPnPdriversPath to reflect the new drivers for this system.
I added the new drivers just fine, I was please to see them all in their respective directories with a simple right-click/Add procedure. I extracted the Sysprep.inf, add all of the information I needed and peformed the very same add method.
That was the history, now here is the problem:
When I extract this very same sysprep.inf file that I added to test that it was indeed there, the file is missing all important information. The only info that remains in the file is the middle of it, which is the long list of the -BMSD command (Mass Storage Section). It is apparent that this feature is broken and Live update says I am up to date... I'm concerned that any files I've added to this image are possibly corrupt/not in their entirety.
Has anyone experienced similar problems, know why this is happening, and/or have a resolution? This seems like a very neat feature that is included as part of the programs functionality that does not seem to work.
I have one image that I use for all of my systems, Dell GX270, GX280, D600, D610, HP Compaq NC6400, NW8440 etc etc.. I created the image this way off the bat using sysprep. My company is moving to a new desktop standard in the coming months, and I figured this was the golden opportunity to take advantage of the latest version of ghost explorer 11 to edit the GHO file by adding the various drivers of the new system to my Temp/Drivers directory, and editing the oemPnPdriversPath to reflect the new drivers for this system.
I added the new drivers just fine, I was please to see them all in their respective directories with a simple right-click/Add procedure. I extracted the Sysprep.inf, add all of the information I needed and peformed the very same add method.
That was the history, now here is the problem:
When I extract this very same sysprep.inf file that I added to test that it was indeed there, the file is missing all important information. The only info that remains in the file is the middle of it, which is the long list of the -BMSD command (Mass Storage Section). It is apparent that this feature is broken and Live update says I am up to date... I'm concerned that any files I've added to this image are possibly corrupt/not in their entirety.
Has anyone experienced similar problems, know why this is happening, and/or have a resolution? This seems like a very neat feature that is included as part of the programs functionality that does not seem to work.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
im also looking for a way to add new drivers into ghost image, can't find anything, please someone come up a way.....
I am having the same issue where my sysprep.inf is missing the critical information...
The problem seems to be with the version of Ghost explorer. I have notice that if the inf file is to big (32 768 bytes and up) the end of the file will be wrap to the start of the file. Since the bmsd section is so big, it overwrites the entire setup manager section. Try the test with a text file you will get the same result.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.