the error is because you didnt put things back where they came from - the sector locations are important. Either that, or your image is of the partition, not the drive - you need the WHOLE drive, from sector 0 on - most partition tools skip the partition gap, but that's important as well.
As to the date, it uses the bios clock, nothing else.
You can set time in BIOS of that computer. In Windows, time also depends on time zone.
If File System is corrupted pointers to SBFS are lost, you will get that message. You did not elaborate how you captured disk image.
thanks for the replies...
first of all, I did check the date in BIOS and WinPE and they were correct, showing 5/14/10; the SBWintech console was showing 5/15/10.
As for my imaging process, admittedly I am a novice at using WinPe and GImagex (gui plug in for Imagex commands in winPe) and am more comfortable at using ghost. However, I was able to successfully use the same process with Gimagex on another machine, but did not have the COD problem in that case.
For this case, I was not applying the image, merely capturing it and then rebooting the system. Would capturing a .wim of the C drive make changes to the Safeboot file system?
Also, I am curious: since I was not able to use the COD and only authenticated using the SBFS, would that allow me to capture an uncrypted .wim or ghost of an encrypted hard drive?
As the the affected machine, I decided to scrap it and use an old ghost image to overwrite the entire hard drive...
1 of 1 people found this helpful
You need to be both: authorized and authenticated to see data in clear.
Sorry it's been a while. Thanks for the confirmation about needing bother authorization and authentication.
I never figured out why the sbwintech date was ahead. What I noticed that it would be correct until after 5 PM. I did a workaround by changing the BIOS date when this situation occurs.