One of the first things I did when I received the BETA was test the backups and especially the restore process.

So far, in all instances of restoring different machines it seems the boot.ini file gets misconfigured, and I'll have to either manually edit it or use the Recovery Console's BOOTCFG to find, and then add the newly restored volume.

I'm thinking it has to do with the fact that some machines have a utility partition that isn't included in the backup, which results in the boot.ini referring to the wrong disk\volume\partition\.

Anyone else having similar issues? Is there a work-around, or is there something I'm possibly doing wrong?

Are you referring to the Client Restore functionality of WHS? I haven't personally experienced what you describe, though I do know some PC manufacturers use another partition for storing recovery data. Have you seen anyone on the WHS forums mention this issue?

Yes, the client-side restore using the Home Server's restore CD.

I've restored three machines, one HP, a Dell Latitude and a clone. All the machines needed their boot.ini edited for them to boot properly once the restore process was complete.

It's not a big deal to do it, but it's been consistent for me on all three restores. The restore process itself was very quick, and even when digging up drivers for the restore I was surprised at how smoothly things went.

Two restores were done on the BETA Home Server, and the last restore using the final release.

_________________
______________________________
VReggie

"We need BOTH horsepowers in this thing!"

Interesting, thanks for the additional details, perhaps it will help someone down the road. I'd recommend you log a Connect bug with Microsoft to make sure their R&D team is aware of what you've encountered.