Awful GUI experience in BESR7

[Brian_Gibson]

I use a network attached harddrive to store BESR images of data drives. With 6.5 and before I simply mapped a drive and was able to browse to this to backup and restore v2i images. However, in BESR7 when attempting to restore a data drive using the Recover Drive task at the point where I need to browse for the image, it complains when I use a mapped drive. It will not continue until I replace X: with a UNC - \\10.4.4.4\nethdd!

This is a tedious task for what should be a simple task! The browse is happy, just seems to be some sort of final check when clicking Next that deems the path invalid.

Is there a fix or work around?

[Bill_Felt]

Hello,

Are you performing the restore operation with BESR itself within Windows, or are you booting to the recovery environment?

Thanks.

[Brian_Gibson]

Hi Bill,

This is within the BESR software whilst booted in Windows.

Cheers,

Brian

[Bill_Felt]

Hello,

My understanding is that even if we are given a drive letter that represents a network location (mapped drive) we still resolve that drive letter to it's UNC path.  Still, it should work.

Have you opened a support ticket with Symantec support?

Thanks.