Ghost Solution Suite

Hello,

I am a new user trying to run the Ghost console. When I try to execute task to create an image I get the error: Failed:To New partition

on details it says: Unable to write back new MBR to boot device.

Tech support is unfamiliar with this and I can find nothing in help or the PDF's that came with Ghost. The PC's are all XP Pro on a peer to peer workgroup, with the c: drives set to full share permissions.

Thank you for any help

What version of the console are you trying out?

I've not seen this error in many years, so I'm a little stumped as to possible causes beyond a couple of vague possibilities; the most plausible situations I can come with for this are either:
a) the code that is trying to manipulate the boot sector is running into trouble with identifying the correct underlying physical disk device in Windows, or
b) some third-party thing like a piece of antivirus software is trying to block the Ghost management client from altering the partition table.

In years past there were a couple of other possibilities like INT13 drive overlays (although we did cope with most of those, too) but thankfully that kind of nasty hackery is behind us these days. Permissions are unlikely to be involved, since the management client should be installed as a service with the full permissions services have (running under the built-in LocalSystem account with the "act as part of the operating system" privilege).

If you're running GSS2, you can send me the ngctw32.log file from the affected client machine after this has happened and I'll see if I can narrow this down at all.

Edit: forgot the address, send it to nigel dot bree at gmail dot com

Hello Nigel,

I emailed you the the log you requested. I am running Symantec Ghost Console ver. 11.0.0.1502, it should be the latest one as I just purchased it directly from Symantec. I notice that Windows does not allow the Windows System folder to be shared, and that
is were the MBR is stored.

Cheers!

Also,

Norton Antivirus disabled and the windows firewall turned off in both console and client PC

We've figured out that this is actually an interaction with GoBack; because GoBack uses a custom MBR of its own, by default it prohibits applications from modifying the real system MBR. We're trying to figure out a way around this, but right now there is no easy way to have both present; you have to disable GoBack before Ghost can do its thing.