PNP + EWF Failed getting protected volume with error 1

[Dan]

Hi guys,

Ok, I'm deploying an image to my target platform. Here's what happens:

1 - Deploy image to target platform. Reboot to run image w. PNP to
detect new hardware (single image deployed to multiple platforms
scenario).
2 - PNP occurs after reboot. Attempt to enable RAM EWF. Fails.

The ewfmgr fails with the "failed getting protected volume with error
1" error. If I reboot again and try to run ewfmgr, it works with no
problem.

My suspicion is that ewfmgr fails because in that boot cycle, PNP has
only just found the HDD and can't use it until the next reboot.
Rebooting allows the PNP changes to take effect and ewfmgr then works.

Does this make sense? Are there any workarounds, or will I need to
include another reboot in my deployment process?

Cheers,

Dan

 

[Slobodan Brcin \(eMVP\)]

Hi Dan,

Well this make some sense but I have not seen it in real usage.

I was surprised to see Reg RAM EWF not work during the first FBA boot. EWF start working only after one reboot is done, but I have
never investigated why this is happening.
Probably you have same problem after image copy.

Please be aware of the fact that EWF is bound to driver instances of partitions after first PnP FBA and if you have done binary copy
of your original disk to secondary disk your volumes should be same and same installed driver instances should work since they do
not depend on physical disk serial number.

Please use some program that does disk binary copy and let us know if it helps.

Regards,
Slobodan

 

[Dan]

HI Slobodan,

Thanks for the reply. I think I'm going to go with the extra reboot,
there's a bit of a time restriction here and I don't know 100% that
your solution will work. The box that the first FBA runs on and the
actual image are deployed on contain different HDDs. I suspect
therefore that the volume information will be different (if the volume
information we're talking about here is to do with:
HKLM\System\MountedDevices) across the platforms.

Cheers,

Dan

 

[Slobodan Brcin \(eMVP\)]

Hi Dan,

HKLM\System\MountedDevices) across the platforms.

Not these info but same principle should be used by windows on other registry entries.
Basically partition ID is composed from DiskID (DWORD from MBR) and partition start offset. So HDD model change do not influence
these entries.

My suggestion was that you do not use xcopy but rather ghost or similar copy tools.

Anyhow it is always your call

Regards,
Slobodan