You have an OEM Windows installation, you would like to know if Ghost Solution Suite can image this system successfully.
An OEM Windows installation is any Windows Operating System that is provided by the OEM vender, or any Windows Operating System that was installed using OEM media.
When working with OEM systems you may encounter problems while performing any of these tasks:
The following may be seen in the ghosterr.txt when attempting to image an OEM installation.
Error Number: 8027
Message: A GeneralException occurred
 No free space big enough to create volume
Generated at ..\VolumeContainerGpt.cpp:235
Users may also encounter the following errors:
Error 1969 encountered an NTFS volume that has not been flushed
Encountered an NTFS volume with a logfile that has not been flushed (536)
NTFS Problem Detected (1969) Ghost has detected problems with an NTFS volume. We recommend that you quit Ghost and correct the problem by rebooting NT and running chkdsk. Alternately, you may also continue normally.
Upon performing a restore the following error may be seen:
Internal error 36000
The following error may be seen when using a Distribute Software task to install Automation Folders:
Error 1073741845 installing package <path>
After an image is deployed and the Configuring Computer is taking place, if the image deployed and the computer couldn't boot up, or couldn't be accessed after booting the following error has been seen in the GSS Console Job Status:
Access is denied
As well this one can occur:
The issues experienced when imaging OEM installations are often but not exclusively caused by additional partitions, such as "Recovery" and "Tools" which are non-standard partitions loaded by the OEM manufacturer. In some cases these additional partitions do not perform normally and the drive cannot be imaged while they are present. In some cases it is not possible to get OEM Windows installations to image properly.
The issue can be caused as well because in some scenarios the OEM Recovery partition was mounting to the same drive letter as the drive with the image file, causing GSS to not be able to locate the folder. You can resolve it by changing the drive letter in your image mounts too.
Broadcom does not recommend attempting to image OEM Windows installations. If you are attempting to create backup images of OEM systems it may be possible to work around the issues that arise, but this is not always possible.
Please note Broadcom does not support the use of Diskpart. Using DiskPart incorrectly may result in loss of data, if you are not sure about what you are doing, do not use DiskPart. Here are the steps:
diskpart" and click "OK" to open a black command prompt window.
list disk" to display all the disks of your computer. Type "
select disk n" to identify which disk you need to work with. Here n stands for the disk letter.
list partition" to display all the volumes on the hard drive. Type "
select partition n" to identify which partition you want to remove. Here n stands for the volume letter.
delete partition override" to remove the OEM partition. Finally, type "
exit" to close the windows when you receive the message says, DiskPart successfully deleted the selected partition".
NOTE: If you continue to have problems imaging and restoring OEM media then consider using genuine Microsoft install media and Microsoft volume licenses as a workaround.